WIP Job Upload creates and updates Oracle Work in Process discrete jobs – Standard and Non-Standard – including job headers, operations, resources and material requirements (components), across one or more inventory organizations, from Excel. It loads the WIP Mass Load interface and runs the standard WIP Mass Load program (one run per organization).
When to use it
- Mass-create new discrete jobs (Standard or Non-Standard) instead of keying them one by one.
- Bulk-update existing job headers – status, quantities, dates, scheduling, class, completion subinventory/locator, schedule group, line, project/task, flexfields.
- Add or change job operations, resources and components in bulk, including on existing jobs.
- Load jobs across several inventory organizations in one file.
- Seed or migrate jobs during an implementation or data load.
Before you start
- Blitz Report is installed and you are signed in to a WIP-enabled responsibility with access to the organization.
- For Standard jobs, the assembly item exists in the organization (and has a routing/BOM where you want it scheduled or exploded).
- A valid WIP accounting class exists for the job type; referenced departments, operations, resources, subinventories and locators exist in the org.
- The WIP accounting period for the job dates is open.
Choose a template
| Template | Use it for |
|---|---|
| Default | The full template – job header plus operation, resource and component detail rows. |
| Job Headers | Create or update job headers only – a lighter file with no operation/resource/component columns. |
Pick the template that matches the work; this upload has no pre-set site default, so choose one when you download.
Step 1 – Choose a template and mode, set the parameters and download
In Blitz Report, open WIP Job Upload, choose your template, and set the parameters:
| Parameter | Purpose |
|---|---|
| Upload Mode | Create (empty template for new jobs) or Create, Update (download existing jobs to edit). Default is Create. |
| Auto Generate Job Name | Yes (default) lets the system name new jobs; No lets you name them manually. |
| Organization Code | The inventory organization (defaults to your manufacturing org). |
| Job / Job From / Job To / Job Status / Type / Assembly / dates / Schedule Group / Line / Project / Task | Filters that restrict which existing jobs are downloaded. |
Run the upload to download and open the Excel file. Each job is automatically handled as a create or an update depending on whether it already exists in the organization.
Step 2 – Enter the jobs
Each spreadsheet row is one item; the Upload Job Identifier groups a job’s header and detail rows. On the header row enter the Organization Code, Type (Standard/Non-Standard), Assembly, Class, Job Status, Start Quantity and the scheduling dates. For jobs with a routing supply one of Scheduled Start Date or Scheduled Completion Date; for jobs without a routing supply both. Add rows for Operations, Resources and Components as needed.
Step 3 – Validate and Save
Click Validate and Save. This checks for missing required values and runs the upload’s validation, then saves the file. Correct anything it flags before continuing.
Step 4 – Upload and view the result
Back in Blitz Report, click Upload and select your saved file. This submits the Blitz Upload request, which loads the WIP Mass Load interface and runs WIP Mass Load (one run per organization). When it finishes, a result report opens showing each row as success or error.
What’s produced
- Created and updated discrete jobs with their operations, resources and components.
- A result report listing every row with a status (success or error) and a message; auto-generated job names are written back.
Common questions
Does it create both Standard and Non-Standard jobs?
Yes – the Type column selects Standard or Non-Standard.
How does it know whether to create or update?
It looks the job up by name/identifier in the selected organization – not found = create, found = update. There is no per-row action switch.
Can it delete jobs, operations or components?
No. The upload only creates and updates.
What dates do I need?
For a job with a routing, supply just the start date (forward-schedules) or the completion date (backward-schedules). For a job without a routing, supply both.
When is the BOM/routing exploded?
By default only for new header-only jobs. If you include operation/component rows, they are kept and the BOM/routing is not auto-exploded; updates are never auto-re-exploded.
My Non-Standard job won’t update – why?
A Non-Standard job with no assembly and no routing reference cannot be updated through WIP Mass Load; edit it in the Discrete Jobs form.
Troubleshooting
| Message | Cause | What to do |
|---|---|---|
| Non-standard jobs without an assembly or routing reference cannot be updated via WIP Mass Load | Updating a Non-Standard job that has neither an assembly nor a routing reference. | Edit that job directly in the Discrete Jobs form. |
| A scheduled start or completion date is required for jobs with a routing | A routed job was entered with both date columns blank. | Supply the start date (forward-schedule) or the completion date (backward-schedule). |
| Both scheduled start and completion dates are required for jobs without a routing | A non-routed job is missing one of the two dates. | Enter both dates. |
| Resource is not assigned to the operation’s department | The resource on a resource row isn’t assigned to that operation’s department. | Fix the department’s resource assignment, or use a resource valid for that department. |
| One or more rows for this job are in error | A validation error on any row of a job cascades to the whole job (a job is processed in full or not at all). | Read the per-row Message in the result, fix the offending rows, and re-upload the job. |