WIP Job Upload  Help

WIP Job Upload creates and updates Oracle Work in Process discrete jobs – Standard and Non-standard – including their operations, resources and material requirements (components), from Excel. One file can hold jobs for several inventory organizations; the upload loads the WIP Mass Load interface and runs the standard WIP Mass Load program once per organization, then reports every row with its status and the created or updated job name.

When to use it

• Mass-create new discrete jobs instead of entering them one by one in the Discrete Jobs window.
• Bulk-update existing jobs – status, quantities, scheduled dates, class, completion subinventory and locator, schedule group, build sequence, line, project and task, descriptive flexfield.
• Add or change operations, resources and components on new or existing jobs.
• Reschedule jobs by changing the scheduled start or completion date.
• Load jobs for several inventory organizations in one file, for example during an implementation or data migration.

Before you start

• Your responsibility has access to the inventory organizations of the jobs.
• Standard jobs: the assembly is enabled for WIP in the organization, with a bill of material and routing if you want them exploded and scheduled from the routing.
• A WIP accounting class exists for the job type, and the departments, standard operations, resources, subinventories and locators you reference exist in the organization.
• Job dates fall within the organization’s manufacturing calendar.
• For automatically named jobs, the job name prefix (profile WIP:Discrete Job Prefix) is set as you want it.

Choose a template

Step 1 – Set the parameters

Open WIP Job Upload in Blitz Report, choose the template and set the parameters:

Step 2 – Run to download the Excel file

Click Run. The Excel file downloads and opens with one row per job (plus operation, resource and component rows if you asked for them), or an empty sheet in Create mode.

Step 3 – Enter or change the jobs

All rows with the same Organization Code and Upload Job Identifier belong to one job; on downloaded rows the identifier is the job name. For a new job enter a meaningful Upload Job Identifier, the Job Type, the Assembly (Standard jobs), Class Code, Job Status (defaults to Unreleased), Start Quantity and the scheduled dates. Mrp Net Quantity defaults to the start quantity.

• Jobs with a routing (the assembly’s routing for Standard jobs, the Routing Reference for Non-standard jobs): enter the Scheduled Start Date to schedule forward or the Scheduled Completion Date to schedule backward; the other date is calculated from the routing. If you enter both, the job is scheduled forward from the start date.
• Jobs without a routing: enter both dates; they are stored as entered.
• On an existing job with a routing, changing only the completion date reschedules it backward; any other change reschedules it forward from the start date.
• Operations, resources and components: enter the Operation Seq Num with the operation columns, the Resource Seq Num with the resource columns, or a Component with the component columns on rows of the job; existing details are updated, new ones added. One row can carry header, operation, resource and component values together.
• BOM and routing explosion: a new job without operation, resource or component rows gets its bill and routing exploded; a new job with detail rows keeps only the details in the file, so include all of them. Existing jobs are not re-exploded.

Step 4 – Validate and Save

Click Validate and Save. This checks for missing required values and saves the file. Correct any rows it flags before uploading.

Step 5 – Upload the file

In Blitz Report click Upload and select the saved file. This submits the upload request, which loads the WIP Mass Load interface and runs WIP Mass Load for each organization in the file.

Step 6 – Review the result report

When the requests complete, a result report opens listing every uploaded row with its status and message, and the Job Name of each created job.

What’s produced

• Discrete jobs created or updated, with their operations, resources and components.
• One WIP Mass Load request per inventory organization in the file.
• A result report listing every row with a status (success or error) and a message, such as Job created or Job updated.

Common questions

How does the upload decide between create and update?
It looks for the job name in the row’s organization: an existing job is updated, otherwise a new job is created.

How do I find the name of an automatically named job?
The result report shows it in the Job Name column, next to the Upload Job Identifier you entered.

Can it delete jobs, operations or components?
No. The upload only creates and updates.

What happens if one row of a job fails?
The whole job is rejected: all its rows show an error and nothing of the job is loaded, so a job is processed completely or not at all.

I changed the Start Quantity – why did the MRP net quantity change too?
If you change Start Quantity on an existing job and leave Mrp Net Quantity unchanged, WIP Mass Load sets the MRP net quantity to the new start quantity. Enter Mrp Net Quantity as well to keep a different value.

Can I force or prevent the BOM and routing explosion?
Yes. The hidden Explode Bom And Routing column overrides the default: Yes explodes the bill and routing, No keeps the uploaded details.

Why can’t my Non-standard job be updated?
A Non-standard job with neither an assembly nor a routing reference cannot be updated through WIP Mass Load. Change it in the Discrete Jobs window.

Troubleshooting