QA Collection Plan Upload

➜ Back to Library
XMLXML import file

Description

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 – from one Excel sheet. Download existing plans to review or change them, or enter new plans row by row.

When to use it

  • Create new collection plans with their elements, values, triggers and actions without keying them into the Collection Plans window.
  • Roll out a standard set of plans to several inventory organizations.
  • Migrate plans to another instance, or copy them, with each element keeping the result column it has in the source plan.
  • Update plan headers or element settings (prompt, sequence, mandatory, displayed, default value, decimal precision, UOM) across many plans.
  • Add elements to, or remove them from, existing plans in bulk.
  • Maintain action triggers, actions (such as assign a value or send an email alert) and their output variables.
  • Delete obsolete plans or individual child records.

Before you start

  • Your responsibility has access to the inventory organizations of the plans.
  • The collection elements, quality transactions, actions and alert action sets you reference already exist. This upload assigns existing elements to plans; to create user-defined elements use the QA Collection Element Upload.
  • Corrective Action Request (CAR) actions are not supported.

Step 1 – Set the parameters

Open QA Collection Plan Upload in Blitz Report and set the parameters:

ParameterMeaning
Upload ModeCreate (default) opens an empty sheet for new plans; Create, Update downloads existing plans with all their child records for editing and lets you add new rows.
OrganizationDownloads the plans of these inventory organizations.
Plan TypeDownloads plans of this type, for example WIP Inspection or Receiving Inspection.
Collection PlanDownloads the selected plans.
Collection Plan From / Collection Plan ToDownloads a range of plans by name. Collection Plan To defaults to Collection Plan From.
Blitz Report run screen for QA Collection Plan Upload with Upload Mode Create, Update, Organization M1 and Collection Plan PROCESS FAILURE PLAN

Step 2 – Run to download the Excel file

Click Run. The Excel file downloads and opens with one row per plan header, transaction, collection trigger, element, element value, action trigger, action and action output of the selected plans, or an empty sheet in Create mode. Every row repeats the plan header columns.

Excel file with the plan header, element and element value rows of PROCESS FAILURE PLAN

Step 3 – Enter or change the plans

Each row is one record of a plan. Organization Code and Plan Name are required on every row and attach the row to its plan. The upload recognises the record type from the columns you fill, checking from the deepest level first:

RecordColumns to fill (besides Organization Code and Plan Name)
Plan headerPlan Description, Plan Type (required for a new plan), Effective From, Effective To, Multirow. Leave all element and child columns empty.
TransactionTransaction Description, Mandatory Collection, Background Collection, Transaction Enabled.
Collection triggerTransaction Description of a transaction on the plan, Collection Trigger, Trigger Operator, Trigger Low Value, Trigger High Value.
ElementElement Name, Prompt Sequence, Element Prompt, Element Enabled, Element Mandatory, Default Value, Displayed, Read Only, Ss Poplist, Information, Decimal Precision, UOM Code, Result Column.
Element valueElement Name, Value Code, Value Description.
Action triggerElement Name, Action Trigger Seq, Action Operator, Action Low Value, Action High Value.
ActionElement Name, Action Trigger Seq, Action Name and the action details: Assign Type and Assigned Element, Alert Action Set and Alert Action, Status Code, Action Message.
Action outputThe columns of its action, plus Output Variable and Output Element.

Put the plan header row of a new plan before its child rows, and parent records (transaction, action trigger, action) before the rows that refer to them. Enter new plan names in upper case: Oracle stores plan names in upper case and child rows are matched to the stored name. For a new element, an empty Element Prompt, Default Value or Element Mandatory is taken from the element definition. Result Column is the column of the quality results table that holds the element’s values. Fill it only when you migrate or copy a plan and each element must keep the result column it has in the source plan: pick the column from the list, which offers the free columns that suit the element. In all other cases leave it empty, and the element takes the next free column of its type, as in the Collection Plans window. The result column of an element already on a plan cannot be changed. When you update a downloaded element row, empty Default Value, Decimal Precision and UOM Code values are cleared on the plan, and empty flags are set to their defaults. Set Delete Record to Yes to remove a record: deleting a plan header deletes the whole plan, deleting a transaction also removes its collection triggers, and deleting an action trigger also removes its actions and outputs. The example changes the description of an existing plan and creates a new plan with the elements Item, Surface Roughness and Inspector.

Excel file with the plan description of PROCESS FAILURE PLAN changed, marked Update, and a new plan M1 SURFACE INSPECTION with the elements Item, Surface Roughness and Inspector, marked Create

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.

All edited rows show status Valid after Validate and Save

Step 5 – Upload the file

In Blitz Report click Upload and select the saved file. This submits the upload request, which processes each row against its plan. For every plan that was created or had elements added or removed, the upload then runs Quality’s plan completion, which submits the Quality Dynamic Plan View Creator request to regenerate the plan’s views.

File Upload page with the saved Excel file selected for upload

Step 6 – Review the result report

When the request completes, a result report opens listing every uploaded row with its status and message, for example “Plan created. Plan ID: …”, “Element added to plan.” or “Plan updated.”.

Result report showing the updated plan, the created plan M1 SURFACE INSPECTION and its three added elements with status Success

What’s produced

  • Collection plans created, updated or deleted, with their transactions, collection triggers, elements, element values, action triggers, actions and action outputs.
  • Regenerated plan views for created plans and plans with added or removed elements.
  • 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 row?
Yes. Each child row carries the Organization Code and Plan Name of its plan, so the upload attaches it to the right plan.

I changed one field of an action and the upload created a second action.
An action is identified by all its fields (action trigger, action name, assign type, assigned element, alert action set, alert action, status code and message). Changing any of them creates a new action. Delete the old action with Delete Record = Yes. Several actions of the same type, such as two assign-value actions with different formulas, can exist under one action trigger.

Can I create collection elements with this upload?
No. It assigns existing elements to plans and maintains their plan-level settings. Create user-defined elements with the QA Collection Element Upload.

Does a migrated or copied plan keep its result columns?
Yes, when its element rows carry the Result Column of the source plan: the download shows each element’s result column, and a new element takes the one entered. Custom reports and integrations that read the results table by column then work on the new plan as on the source plan.

Do I need to save or complete the plan in Oracle after the upload?
No. The upload runs Quality’s plan completion automatically for new plans and for plans whose elements were added or removed.

Troubleshooting

MessageCauseWhat to do
Plan Type is required for new plans.A plan header row for a plan that does not exist has no Plan Type.Enter the Plan Type, or correct the Plan Name of an existing plan.
Plan “…” not found.A transaction or element row refers to a plan that does not exist in this organization, for example because the plan name is not in upper case or its header row failed.Enter the plan name exactly as stored (upper case) and put the plan header row first.
Plan “…” not found for deletion.Delete Record = Yes on a header row of a plan that does not exist.Check the Organization Code and Plan Name.
Transaction not assigned to plan.A collection trigger row refers to a transaction that is not on the plan.Add a transaction row before the collection trigger row.
Plan and transaction are required for collection triggers.
Plan and element are required for values.
Plan and element are required for action triggers.		The plan does not exist, or the Transaction Description or Element Name is empty.Fill the parent columns of the row.
Plan, element, and action trigger sequence are required for actions.
Plan, element, action trigger sequence, and action are required for output variables.		An action or action output row is missing the Element Name, Action Trigger Seq or Action Name.Fill the columns that identify the parent action trigger and action.
Action trigger sequence … not found.No action trigger with this sequence exists for the element on the plan.Add the action trigger row (with Action Operator) before its action rows.
Parent action not found for the specified trigger and message. Make sure the matching action row exists before this output row.The action columns of an output row do not match an existing action exactly.Copy the action columns from the action row, and put the action row first.
Action not found for deletion.Delete Record = Yes on an action whose fields do not match an existing action.Use the downloaded action row unchanged with Delete Record = Yes.
Result column … is not valid for element …The column does not suit the element’s type, or the element is a seeded element with a fixed column.Pick the result column from the list, or leave it empty.
Result column … is already used by element …Another element of the plan has this column.Pick a free column from the list, or leave it empty.
The result column of an element in a plan cannot be changed.A row for an element already on the plan names a different result column.Enter the element’s current result column, or leave it empty.
Create plan failed: …
Add element failed: …
Delete element failed: …
Delete plan failed: …		Oracle Quality rejected the operation, for example a duplicate plan name or an element already on the plan.Read the Oracle message that follows, correct the data and upload again.

SQL 540 lines

Parameters 6

ParameterTypeList of values SQL
Upload ModeLOV
:p_upload_mode like '%' || xxen_upload.action_update
OrganizationLOV
mp.organization_code=:p_organization
Plan TypeLOV
qp.plan_type_code=:p_plan_type
Collection PlanLOV
qp.name=:p_plan
Collection Plan FromLOV
qp.name>=:p_plan_from
Collection Plan ToLOV
qp.name<=:p_plan_to