QA Collection Plan Upload creates, updates and deletes Oracle Quality collection plans together with their full child hierarchy – transactions, collection triggers, plan elements, element values, action triggers, actions and action outputs – in one hierarchical spreadsheet.
When to use it
- Mass-create new collection plans with their elements, triggers, values and actions instead of using the Quality Collection Plans form.
- Clone or roll out a standardized set of plans across multiple organizations.
- Bulk-update plan headers or element settings (prompt, mandatory, displayed, default value, precision, UOM) across many plans.
- Add or remove collection elements on existing plans in bulk.
- Maintain action triggers, actions and action outputs (such as assign-value or send-email alert actions).
- Delete obsolete plans or specific child entities en masse.
Before you start
- Blitz Report is installed and you are signed in to a responsibility with access to the inventory organization.
- The collection elements, transactions, actions and alert action sets referenced already exist in Oracle Quality.
- This upload assigns existing elements to a plan; it does not create the element definitions.
How the rows work
Each spreadsheet row represents one entity in the plan’s hierarchy, and the upload recognizes which entity it is from the columns you fill. The organization and Plan Name repeat on every row of the same plan, processed top-down:
| Row | What it defines |
|---|---|
| Plan Header | The plan (name, type, description, effective dates, multirow). |
| Transaction | A quality transaction the plan collects against. |
| Collection Trigger | A trigger condition on a transaction. |
| Element | A collection element assigned to the plan, with its prompt and flags. |
| Element Value | An allowed value for an element. |
| Action Trigger / Action / Action Output | Conditional actions (e.g. alerts) and their output mappings. |
Step 1 – Choose a mode, set the parameters and download
In Blitz Report, open QA Collection Plan Upload, choose an Upload Mode (Create for an empty template, or Create, Update to download existing plans to edit), and set the parameters:
| Parameter | Purpose |
|---|---|
| Upload Mode | Create or Create, Update. Default is Create. |
| Organization / Plan Type / Collection Plan / Plan From / Plan To | Restrict which existing plans are downloaded. |
Run the upload to download and open the Excel file. Each plan and child entity is automatically handled as a create or an update depending on whether it already exists.
Step 2 – Enter the plans
On the header row enter the Organization Code, Plan Name, Plan Type and description. Add a row per transaction, trigger, element, element value, and action, repeating the organization and Plan Name on each and filling only that entity’s columns.
Step 3 – Delete entities (optional)
Set the Delete column to Yes to remove an entity. Deleting a parent cascades to its children (deleting the plan header removes everything).
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 applies each plan and its child entities and completes the plan automatically. When it finishes, a result report opens showing each row as success or error.
What’s produced
- Created, updated or deleted collection plans with their transactions, triggers, elements, values and actions.
- A result report listing every row with a status (success or error) and a message.
Common questions
Do I repeat the plan name on every line?
Yes. Each child row carries the same Organization Code and Plan Name as its plan header, so the upload attaches the child to the right plan.
I changed one field on an action and it created a second action instead of updating it.
Actions are identified by their full set of fields (trigger, action name, assign type, assigned element, alert action set/action, status, message). Changing any of these is treated as a new action – delete the old one and add the corrected one.
Can I create the collection elements through this upload?
No. This upload assigns existing elements to a plan and edits the plan-level element settings. Create element definitions with the QA Collection Element Upload.
Are CAR (Corrective Action Request) actions supported?
Not yet.
Do I need to do anything to “save” the plan after adding elements?
No – the upload runs Quality’s plan-completion processing automatically for every plan whose elements changed or that was newly created.
Troubleshooting
| Message | Cause | What to do |
|---|---|---|
| Plan Type is required for new plans | Creating a new plan header with no Plan Type. | Fill the Plan Type column for header rows that create a plan. |
| Plan not found | A child row references a plan that doesn’t exist yet (or wrong name/org). | Ensure the plan header row exists/created first with the exact same Plan Name and Organization Code. |
| Transaction not assigned to plan / action trigger not found | A trigger/action/output row references a parent that isn’t present on the plan. | Add the parent transaction / action-trigger row before its child rows. |
| Element not found for deletion | Delete = Yes but the target entity doesn’t exist. | Verify the keys identify an existing record, or remove the delete flag. |
| Create plan / add element failed (Oracle message) | The Oracle Quality API rejected the operation. | Read the appended Oracle message, correct the data, and re-upload. |