OPM Routing Upload creates and updates Oracle Process Manufacturing (OPM / GMD) routings – the routing header, its routing steps (each referencing an existing operation), and the step-to-step dependencies – from Excel, via the Oracle public APIs, with one spreadsheet row per routing step. It can also delete steps and dependencies.
When to use it
- Mass-create new OPM routings (header, steps and dependencies) instead of keying them in the Routing form.
- Load routings during a new OPM implementation or a new-plant rollout.
- Add extra steps or step dependencies to existing routings in bulk.
- Bulk-update the header fields the API permits, or step quantity / release type / yield / minimum transfer quantity.
- Remove obsolete routing steps or specific step dependencies across many routings.
- Maintain routing-header or routing-step descriptive flexfield values in bulk.
Before you start
- Blitz Report is installed and you are signed in under an OPM responsibility that has access to the routing’s organization (a process-enabled org).
- The operations referenced (operation number + version) already exist in the routing’s organization – this upload does not create operations.
- Routing class, UOM, status, owner, release type and any flexfield values exist.
Step 1 – Choose a mode, set the parameters and download
In Blitz Report, open OPM Routing Upload, choose an Upload Mode (Create for an empty template, or Create, Update to download existing routings), and optionally set the Organization Code and a specific Routing. Run the upload to download and open the Excel file. Each routing is automatically handled as a create or an update depending on whether it already exists.
Step 2 – Enter the routings and steps
Use one row per routing step; repeat the header columns on every step of the same routing, and keep a routing’s rows together (each routing needs at least one step). On the header enter the Routing, Routing Version, Routing Description and Routing UOM. On each step enter the Step No, Operation and Operation Version. To make a step depend on another, enter its Depends On Step No (add extra rows repeating the Step No for multiple predecessors).
Step 3 – Delete steps or dependencies (optional)
In Create, Update mode, set Delete Step to Yes to remove a step (its dependencies cascade), or Delete Dependency to Yes to remove one dependency.
Step 4 – 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 5 – Upload and view the result
Back in Blitz Report, click Upload and select your saved file. This submits the Blitz Upload request, which creates or updates each routing, its steps and dependencies. When it finishes, a result report opens showing each row as success or error.
What’s produced
- Created and updated routings with their steps and step dependencies; deleted steps/dependencies where flagged.
- A result report listing every row with a status (success or error) and a message.
Common questions
Can I create operations with this upload?
No. Operations must already exist; the upload only references them by operation number and version.
Why can’t I change a routing’s description or quantity on an existing routing?
The OPM public API only allows header changes to Status, Routing Class, Routing UOM, Fixed Process Loss UOM, Owner and Organization. Description, quantity, process loss and effective dates are set when the routing is first created.
How do I give a step two predecessors?
Add a second row that repeats the same Step No, leave Operation blank, and enter a different Depends On Step No.
Why don’t I see the Delete Step / Delete Dependency options on a row?
Delete Step appears only for rows tied to an existing step; Delete Dependency only when the row has a Depends On Step No. Both apply in Create, Update mode.
How does it know whether to create or update?
It matches Organization Code + Routing + Routing Version against existing routings – a match updates, no match creates.
Troubleshooting
| Message | Cause | What to do |
|---|---|---|
| A routing must have at least one step | A routing’s rows have no step (and no step/dependency deletes). | Add at least one step row (Step No + Operation) for that routing. |
| Organization is not a valid process-enabled organization | The Organization Code is not process-enabled, or not accessible to your responsibility. | Use a process-enabled org the running responsibility can access. |
| Operation version not found in organization | The referenced operation/version doesn’t exist in that org. | Create or correct the operation first; verify the number, version and organization. |
| Routing / step attributes error | A header or step descriptive flexfield value failed validation. | Provide a valid flexfield context and segment values. |
| Row shows the routing’s error on every row | One row failed; the whole routing is processed all-or-nothing. | Fix the reported issue on the offending row and re-upload that routing. |