Search Results qa_txn_grp




Overview
Explore in AI Chat

Overview

QA_PARENT_CHILD_PKG is an Oracle EBS Quality Management (QA) package owned by APPS that implements the parent-child plan relationship framework used by Oracle Quality collections and specifications. In Oracle Quality, plan elements can be linked so that child plan data is automatically inserted, related, aggregated, or copied whenever records are entered against a parent plan. This package supplies the PL/SQL infrastructure for that behavior: it parses lists of child plan identifiers, determines which descendants exist, evaluates parent-child criteria and LOV criteria, aggregates child results into parent results, and orchestrates the "enable and fire" sequence that triggers parent-child actions at transaction-header or collection level. It also encapsulates the gapless-sequence project logic referenced in the header comment. The package exposes a rich set of public procedures and functions — fifty-nine documented in the 12.2.2 ETRM metadata — that are called by Quality forms, concurrent programs, and other QA packages. Because it manipulates relationship records in the QA_PC_* tables, it is central to any customization involving parent-child plans, multi-level data entry, and automatic record generation.

Key Procedures and Functions

  • PARSE_LIST — Parses a delimited string of values into the ChildPlanArray PL/SQL associative array. Used at the entry point of routines such as INSERT_AUTOMATIC_RECORDS to convert a concatenated list of child plan IDs into a structured collection.
  • INSERT_AUTOMATIC_RECORDS — Creates automatic records for a plan, collection, and occurrence based on a supplied list of child plan IDs, relationship type, data entry mode, criteria values, organization, and specification. Returns a status and accepts an optional transaction header ID, making it the principal driver for automatic parent-child record generation.
  • ENABLE_AND_FIRE_ACTIONS — Enables parent-child actions for a collection and fires them, i.e., applies the configured relationship actions once the enabling conditions are met.
  • ENABLE_FIRE_FOR_TXN_HDR_ID / ENABLE_FIRE_FOR_COLL_ID — Variants that enable and fire actions scoped to a transaction header ID or collection ID respectively, allowing the caller to target a specific transaction or collection rather than an entire session context.
  • DELETE_CHILD_ROWS — Removes child relationship rows, typically when a parent-child relationship is broken or a transaction is rolled back.
  • RELATE — Establishes the parent-child relationship records between plans, collections, and occurrences.
  • DESCENDANTS_EXIST / GET_DESCENDANTS / GET_DISABLED_DESCENDANTS — Detection and retrieval routines for descendant plans; the disabled variant returns those descendants whose associated actions are not currently enabled.
  • EVALUATE_CHILD_LOV_CRITERIA / EVAL_UPDATEVIEW_LOV_CRITERIA / EVALUATE_CRITERIA / CRITERIA_MATCHED — Evaluate whether a child record satisfies configured LOV or update-view criteria, and return whether criteria match; these gate automatic insertion and copying.
  • AGGREGATE_FUNCTIONS — Applies aggregation (sum, average, count, and similar) over child result values to populate parent results.
  • GET_PLAN_NAME / FIND_PARENT / IS_PARENT_CHILD_PLAN / SHOULD_PARENT_SPEC_BE_COPIED — Metadata and decision helpers: resolve a plan name, locate a plan's parent, test whether a plan participates in a parent-child relationship, and decide whether the parent specification should be copied.
  • COMMIT_ALLOWED — Determines whether a commit may proceed at the current point in parent-child processing, guarding against committing partially processed relationship hierarchies.

Tables Accessed

  • QA_PLANS — Plan definitions, used to resolve plan names and validate parent/child plans.
  • QA_PLAN_CHARS and QA_CHARS — Plan characteristics and characteristic definitions used in criteria evaluation and specification copying.
  • QA_OCCURRENCE_S — Occurrence definitions for plans and collections, used when inserting automatic records and correlating occurrences.
  • QA_PC_CRITERIA — Stored parent-child criteria evaluated by the EVALUATE_* and CRITERIA_MATCHED routines.
  • QA_PC_PLAN_RELATIONSHIP, QA_PC_ELEMENT_RELATIONSHIP, QA_PC_RESULTS_RELATIONSHIP — The relationship tables that define parent-child links at plan, element, and results level; these are read and written by RELATE, INSERT_AUTOMATIC_RECORDS, DELETE_CHILD_ROWS, and the descendants routines.
  • QA_RESULTS — Result rows read for aggregation and written when automatic child or parent records are created.
  • MTL_MATERIAL_TRANSACTIONS_S — Referenced to correlate Quality transactions with material transactions, generally for transaction-header-scoped enable/fire operations.
  • DUAL, DBMS_SQL, and PLITBLM — Utility objects used for single-row evaluation and dynamic SQL during criteria evaluation.

Usage Notes

QA_PARENT_CHILD_PKG is an internal Quality application package rather than a documented open API. It is invoked by Oracle Quality forms and by the concurrent processes that generate automatic records and aggregate parent results, and it is referenced by roughly ten other packages, including the Quality specification and collection processing code. Customizations should call the higher-level documented Quality APIs where possible; direct invocation of PARSE_LIST, INSERT_AUTOMATIC_RECORDS, or ENABLE_AND_FIRE_ACTIONS requires careful handling of session context, organization ID, and transaction header ID, and callers must respect the COMMIT_ALLOWED guard to avoid committing mid-hierarchy. In 12.1.1 and 12.2.2 the package is installed under the APPS schema with public synonyms and grants typical of QA application code. Version 120.11.12010000.2 is the shipping version shown in the header, confirming that the logic is stable across both releases and that no Online Patching-specific changes to the signature set have been introduced for 12.2.2.