QA Plan Relationship Upload
QA Plan Relationship Upload creates, updates and deletes Oracle Quality parent-child collection-plan relationships from Excel – linking a parent plan to a child plan with optional element relationships and automatic-creation criteria – via the standard Oracle Quality parent-child API.
When to use it
- Mass-create parent-child links between collection plans across one or more inventory organizations.
- Set up automatic child-record creation by defining the entry mode plus element relationships and criteria in bulk.
- Standardize plan-relationship configuration across multiple organizations from a spreadsheet.
- Update existing relationships’ entry/layout mode, auto row count or default-parent-spec setting in bulk.
- Add or adjust element relationships and creation criteria on existing relationships.
- Remove obsolete plan relationships in bulk, or migrate setups between environments.
Before you start
- Blitz Report is installed and you are signed in to a responsibility with access to the inventory organization.
- Both the parent plan and child plan already exist in Oracle Quality for the chosen organization (this upload links existing plans).
- Any element used (parent / child / criteria element) is already defined on its plan.
Step 1 – Choose a mode, set the parameters and download
In Blitz Report, open QA Plan Relationship Upload, choose an Upload Mode (Create, Update – the default – downloads existing relationships to edit; Create gives an empty template), and set the parameters:
| Parameter | Purpose |
|---|---|
| Upload Mode | Create or Create, Update. Default is Create, Update. |
| Organization / Parent Plan / Child Plan | Restrict which existing relationships are downloaded. |
Run the upload to download and open the Excel file. Each relationship is automatically handled as a create or an update depending on whether the parent + child plan pair already exists.
Step 2 – Enter the relationships
On each row enter the Organization Code, Parent Plan and Child Plan, the Entry Mode (Immediate / Delayed / Automatic / History) and the relationship attributes. Optionally add an element relationship (Parent Element + Child Element) and a creation criterion (Criteria Element + Criteria Operator).
Step 3 – Delete relationships (optional)
Set Delete Record to Yes to remove the relationship for that parent/child plan. It errors if the relationship doesn’t exist.
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, updates or deletes each relationship. When it finishes, a result report opens showing each row as success or error.
What’s produced
- Created, updated or deleted parent-child plan relationships with their element relationships and criteria.
- A result report listing every row with a status (success or error) and a message.
Common questions
Do I need to create the plans first?
Yes. The upload links existing plans; the parent and child plans (and their elements) must already exist.
How does it know whether to create or update?
It looks up the parent-plan + child-plan pair. No match = create; match = update. You don’t set an action manually.
Are element relationships and criteria mandatory?
No. The base relationship is created on its own. The element relationship is processed only if both Parent Element and Child Element are filled; the criterion only if both Criteria Element and Criteria Operator are filled.
What do the entry modes mean?
Immediate = child entered right after the parent; Delayed = child entered manually later; Automatic = child auto-created when the parent meets the criteria; History = child auto-created when the parent is changed.
How do I delete a relationship?
Download in Create, Update mode, set Delete Record = Yes on the row, and upload.
Troubleshooting
| Message | Cause | What to do |
|---|---|---|
| Plan relationship does not exist for deletion | Delete Record = Yes but no relationship exists for that parent/child plan. | Confirm the exact parent and child plan names and organization; remove the Delete flag if the relationship was never created. |
| Plan relationship validation failed | Oracle rejected the combination (e.g. incompatible plans, invalid entry/layout mode). | Read the appended Oracle reason and correct the offending field. |
| Element relationship validation failed | Oracle rejected the parent/child element pairing. | Verify both elements exist on their plans and the element relationship type is valid. |
| Parent/Child Plan dropdown is empty | Organization Code not set, or the organization has no quality plans. | Set a valid Organization Code first; the plan lists are filtered by it. |
| Delete option not available in the cell | Parent Plan or Child Plan not yet filled on the row. | Fill both Parent Plan and Child Plan; the Yes delete option then appears. |
select null action_, null status_, null message_, null modified_columns_, mp.organization_code, qpp.name parent_plan, qpc.name child_plan, qpc.description child_plan_description, xxen_util.meaning(qppr.data_entry_mode,'QA_PC_DATA_ENTRY_MODE',250) entry_mode, xxen_util.meaning(qppr.layout_mode,'QA_PC_LAYOUT_MODE',250) layout_mode, qppr.auto_row_count, xxen_util.meaning(decode(qppr.default_parent_spec,1,'Y','N'),'YES_NO',0) default_parent_spec, qc_p.name parent_element, qc_c.name child_element, xxen_util.meaning(qper.element_relationship_type,'QA_PC_ELEMENT_RELATIONSHIP',250) element_rel_type, xxen_util.meaning(decode(qper.link_flag,1,'Y','N'),'YES_NO',0) link_flag, qc_cr.name criteria_element, xxen_util.meaning(qpcc.operator,'QA_PC_OPERATOR',700) criteria_operator, qpcc.low_value criteria_from_value, qpcc.high_value criteria_to_value, null delete_record, qppr.plan_relationship_id, qper.element_relationship_id, qpcc.criteria_id from mtl_parameters mp, qa_plans qpp, qa_pc_plan_relationship qppr, qa_plans qpc, qa_pc_element_relationship qper, qa_chars qc_p, qa_chars qc_c, qa_pc_criteria qpcc, qa_chars qc_cr where 1=1 and qpp.organization_id=mp.organization_id and qppr.parent_plan_id=qpp.plan_id and qpc.plan_id=qppr.child_plan_id and qper.plan_relationship_id(+)=qppr.plan_relationship_id and qc_p.char_id(+)=qper.parent_char_id and qc_c.char_id(+)=qper.child_char_id and qpcc.plan_relationship_id(+)=qppr.plan_relationship_id and qc_cr.char_id(+)=qpcc.char_id |
| Parameter Name | SQL text | Validation | |
|---|---|---|---|
| Upload Mode |
| LOV | |
| Organization |
| LOV | |
| Parent Plan |
| LOV | |
| Child Plan |
| LOV |