Search Results qa_parent_child_copy_pkg




Overview
Explore in AI Chat

Overview

QA_PARENT_CHILD_COPY_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the Quality Management (QA) module. Its primary business function is to support the propagation and duplication of quality plan definitions across parent and child records, allowing organizations to define reusable quality plan templates and copy their associated characteristics, actions, criteria, and relationships to dependent plans. This capability is central to enterprise quality planning, where a master or template plan must be replicated to downstream items, organizations, or successor plans without manual re-entry. The package is classified as an "OTHER" API type within the ETRM documentation for release 12.2.2 and is reported with a VALID status.

Key Procedures and Functions

The package exposes two documented procedures:

  • COPY_ALL — The principal routine responsible for performing the bulk duplication of quality plan data from a source (parent) plan into one or more target (child) plans. It orchestrates the copying of the plan header, associated characteristics, indexed characteristics, action definitions, and the parent-child relational structures that tie these elements together.
  • SETUP_PLANS — A supporting routine that performs the preparatory configuration required before a copy operation proceeds. It typically establishes or validates the plan-level and criteria-level setup records so that COPY_ALL can execute against a consistent, properly initialized set of plans.

The ETRM metadata does not enumerate individual parameter lists for these routines, and no parameters are asserted here. Callers should obtain exact signatures from the package specification in the database.

Tables Accessed

The package reads and writes a range of Quality and shared Foundation tables through APPS synonyms. Documented references include:

Usage Notes

QA_PARENT_CHILD_COPY_PKG is typically invoked from Quality Management forms or concurrent programs that manage plan setup, plan copy, or parent-child plan maintenance. It is not referenced by any other documented package (referenced-by count is zero), indicating it functions as a top-level utility rather than a shared library dependency. Customizations that automate plan duplication should call the package through its public procedures rather than manipulating the underlying QA tables directly, ensuring relationship integrity and consistent setup handling. Because the package performs coordinated inserts across multiple parent-child relationship tables, callers should treat COPY_ALL as a transactional unit and ensure commit or rollback control aligns with their surrounding process.