Search Results get_import_view_name

Overview

The QA_PARENT_CHILD_COPY_PKG package body is a quality management utility within the Oracle E-Business Suite Quality module (QA). Its principal business function is to replicate the parent-child relationship structure that exists between quality plans. When a source parent plan and source child plan are linked through a relationship record, this package can recreate an equivalent relationship between a different target parent plan and target child plan. This capability is used primarily during plan setup activities, where an administrator needs to duplicate an established planning hierarchy onto new or template-like plans without manually reconstructing each association.

The package is classified in the ETRM registry with an API classification of OTHER and resides in the APPS schema. It is not referenced by any other database package, indicating that it is intended to be called directly by forms, concurrent programs, or custom code rather than through a layered internal dependency chain. Its header revision (120.0.12020000.2) reflects ongoing maintenance aligned with EBS 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

Two procedures are documented for this package body:

• COPY_ALL — Serves as the primary entry point for the bulk duplication of parent-child plan relationships. It orchestrates the copying of relationship records from a source context to a target context, invoking the underlying copy logic and returning the resulting relationship identifiers and status information to the caller.
• SETUP_PLANS — Handles the preparatory work required before relationships can be copied, including the identification and validation of the plans involved. It ensures that the target plans exist and are in a state suitable for receiving copied relationship definitions.

The body additionally contains an internal COPY_PLAN_REL procedure (visible in the source excerpt) that performs the actual relationship copy. It queries QA_PC_PLAN_RELATIONSHIP for the most recently created relationship between a source parent and source child plan, ordered by creation date descending, and returns the old and new relationship identifiers along with a return status. When no matching source relationship exists, it returns a sentinel value of -1. This internal procedure is not part of the documented public interface but underpins the documented behavior.

Tables Accessed

The package interacts with a defined set of quality and shared application tables, accessed through APPS synonyms:

• QA_PC_PLAN_RELATIONSHIP — The core table read and written by the copy logic; stores parent-to-child plan associations along with attributes such as data entry mode, auto row count, relationship type, default parent specification, and layout mode.
• QA_PLANS — The master plan definition table, consulted to validate and resolve source and target plans.
• QA_PC_CRITERIA and QA_PC_ELEMENT_RELATIONSHIP — Supporting plan-collection criteria and element relationship structures tied to collections copied with the plans.
• QA_PLAN_CHARS, QA_CHARS, and QA_CHAR_INDEXES — Characteristic and index definitions associated with plans, referenced during plan setup.
• QA_PLAN_CHAR_ACTIONS and QA_PLAN_CHAR_ACTION_TRIGGERS — Action and trigger metadata attached to plan characteristics.
• ALR_ACTIONS and FND_USER — Alert action definitions and application user records used in action and ownership resolution.
• MTL_PARAMETERS — Inventory organization parameters, consulted for organizational context.
• DUAL and DBMS_SQL / PLITBLM — Used for scalar queries and dynamic SQL or PL/SQL table manipulation within the setup logic.

Usage Notes

QA_PARENT_CHILD_COPY_PKG is typically invoked during quality plan configuration, most commonly from the Quality Plans setup forms or from concurrent programs that automate plan creation across organizations. Because the internal copy routine deliberately bypasses QA_AK_MAPPING_API (as noted in the source comments) and instead inserts directly through the table handler, callers should be aware that attribute mapping processing is not triggered by this path. The package is best used when a managed duplication of an existing, verified plan hierarchy is required. Custom integrations should call the documented COPY_ALL and SETUP_PLANS procedures rather than the private COPY_PLAN_REL routine, and should validate target plans prior to invocation to prevent orphaned or duplicate relationships.