Results for “insert_automatic_records”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
QA_PARENT_CHILD_PKG is the Oracle Quality parent-child plan engine in Oracle E-Business Suite. It implements the relationship between a parent collection plan and the child collection plans attached to it, resolving which child specifications apply to a given transaction, collection, or plan occurrence and aggregating results upward from children to parents. The package is central to the R12 online transaction (OAF) integration for Quality, as indicated by the header comment referencing the R12 OAF Txn Integration Project and the addition of the p_txn_header_id parameter to several entry points.
The public API is deliberately platform-neutral. As stated in the package header, every function returns the character 'T' or 'F' rather than the PL/SQL BOOLEAN type, so that the same servlets may be called from Java or other external platforms. The package is owned by APPS and exposed through APPS synonyms, and it is referenced by ten other packages, making it a foundational dependency for Quality data collection, specification copying, and action firing.
The user search term "c_rc" most likely corresponds to this package and its related objects (parent-child, RC), the Quality parent-child relationship logic documented below.
Key Procedures and Functions
- RELATE — Establishes the parent-child linkage between plans and records the association in the relationship tables.
- FIND_PARENT and IS_PARENT_CHILD_PLAN — Determine whether a given plan participates in a parent-child hierarchy and identify its parent.
- GET_DESCENDANTS, GET_DISABLED_DESCENDANTS, and DESCENDANTS_EXIST — Traverse the plan hierarchy downward, returning descendants or confirming their existence; the disabled variant filters for inactive child entries.
- CRITERIA_MATCHED, EVALUATE_CRITERIA, EVALUATE_CHILD_LOV_CRITERIA, and EVAL_UPDATEVIEW_LOV_CRITERIA — Evaluate the parent-child criteria (attribute/result conditions) that decide whether a child plan applies to the current collection or transaction.
- AGGREGATE_FUNCTIONS — Executes a dynamically supplied SQL aggregation string and returns the numeric result; two overloads exist, the second adding a transaction header identifier for OAF transaction context. Both return 'T'/'F' and apply NVL to the computed value.
- COMMIT_ALLOWED — Determines whether the collection may be committed, based on incomplete child plans and the supplied occurrence and child plan list.
- INSERT_AUTOMATIC_RECORDS and DELETE_CHILD_ROWS — Create and remove the child result rows that the hierarchy requires.
- ENABLE_AND_FIRE_ACTIONS, ENABLE_FIRE_FOR_TXN_HDR_ID, and ENABLE_FIRE_FOR_COLL_ID — Enable and trigger the actions associated with matching child criteria at transaction header or collection level.
- SHOULD_PARENT_SPEC_BE_COPIED — Controls whether the parent specification is copied down to the child.
- GET_PLAN_NAME, PARSE_LIST, and EVAL_UPDATEVIEW_LOV_CRITERIA — Utility routines for resolving plan names, parsing delimited identifier lists, and evaluating LOV criteria at update time.
Tables Accessed
The package reads and writes the Quality plan and results schema: QA_PLANS and QA_PLAN_CHARS for plan and characteristic definitions; QA_CHARS for specification characteristics; QA_OCCURRENCE_S for collection occurrences; QA_RESULTS for collected result values; and QA_PC_PLAN_RELATIONSHIP, QA_PC_CRITERIA, QA_PC_ELEMENT_RELATIONSHIP, and QA_PC_RESULTS_RELATIONSHIP for the parent-child definition, criteria, element linkage, and computed relationship results. It also queries MTL_MATERIAL_TRANSACTIONS_S (transaction context), DUAL, DBMS_SQL (dynamic aggregation), and PLITBLM (the PL/SQL index-by table used by the packaged LIST type referenced in PARSE_LIST).
Usage Notes
QA_PARENT_CHILD_PKG is invoked from the Quality collection plan setup forms, from the online data collection pages during the R12 OAF transaction flow, and from concurrent/background processing that evaluates criteria and fires actions. The transaction-aware procedures accept the transaction header identifier added for the OAF integration. Custom code should call the package-qualified functions through APPS and must test for the 'T'/'F' return convention rather than a BOOLEAN. Because ten other packages depend on it, signature changes should be treated as high-impact.