OPM Recipe Upload  Help

OPM Recipe Upload creates and updates Oracle Process Manufacturing (OPM / GMD) recipes – the recipe header plus its validity rules, routing-step overrides, step/material associations, per-organization process loss, customers, and org-specific operation and resource overrides – all in one spreadsheet. A Row Type column on each row tells the upload which recipe entity that row represents.

When to use it

• Load new OPM recipes in bulk from a spreadsheet instead of keying them in the Recipe form.
• Mass-update recipe header fields (status, yield, process loss, flexfields) across many recipes.
• Add or update recipe validity rules in bulk.
• Set routing-step quantities/yields, step/material transfer quantities and delays, or per-organization process loss.
• Assign customers to recipes en masse.
• Apply org-specific operation (activity factor) and resource (usage, capacity, process parameters) overrides.

Before you start

• Blitz Report is installed and you are signed in to a responsibility with access to a process-enabled organization.
• The formula and routing the recipe is built on already exist in that organization.
• Steps, operations and material items referenced exist in the recipe’s routing and formula.

How the Row Type works

Each row represents exactly one recipe entity, chosen in the Row Type column. The recipe key (Organization Code + Recipe + Recipe Version) repeats on every row of the same recipe, and the rows are grouped and applied together.

Step 1 – Choose a mode, set the parameters and download

In Blitz Report, open OPM Recipe Upload, choose an Upload Mode (Create for an empty template, or Create, Update to download existing recipes), and optionally set the Organization Code and a specific Recipe. Run the upload to download and open the Excel file. Each recipe is automatically handled as a create or an update depending on whether it already exists.

Step 2 – Enter the recipe rows

On every row fill the recipe key (Organization Code, Recipe, Recipe Version) and choose the Row Type, then fill only that entity’s columns and leave the rest blank. A recipe normally has one Recipe row plus any number of detail rows.

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 applies each recipe and its detail entities in order. When it finishes, a result report opens showing each row as success or error.

What’s produced

• Created and updated recipes with their validity rules, step and material overrides, process loss, customers, and org operation/resource overrides.
• A result report listing every row with a status (success or error) and a message.

Common questions

How does the upload know which fields apply to a row?
The Row Type column. Each row is one recipe entity; fill only that entity’s columns and leave the rest blank.

Do I repeat the recipe key on every row?
Yes – Organization Code, Recipe and Recipe Version must be filled on every row so the rows group to the correct recipe.

Does it create or update, and how do I choose?
It decides automatically per recipe – existing recipe = update, new = create. Use Create, Update to download existing recipes for editing; Create gives an empty template.

Can I delete recipes or rows with this upload?
No. This upload only creates and updates.

Why must the formula and routing already exist?
A recipe is built on an existing formula and routing – the upload references them by name/version and does not create them.

Troubleshooting