Results for “parent_transaction”
20 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
QABV_COLPLNTXN is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the Oracle Quality (QA) product family and exposes collection plan transaction data in a denormalized, business-friendly form. The view is documented as "Retrofitted," indicating it was introduced or re-pointed during an upgrade or localization effort to preserve compatibility with prior customizations or reports. The view definition includes the WITH READ ONLY clause, so it supports query and reporting access only; no DML is permitted against it. Its principal role is to support reporting and integration scenarios that require plan transaction attributes — in particular the background collection flag — in decoded, human-readable form rather than as raw lookup codes stored in the base table.
Underlying Base Objects
Per the documented ETRM metadata for 12.2.2, the view references two base objects: QA_PLAN_TRANSACTIONS (exposed through a synonym) and MFG_LOOKUPS (a view). QA_PLAN_TRANSACTIONS is the driving table, aliased QPT in the view text, and supplies the transaction-level columns such as plan transaction ID, flags, foreign keys, and audit columns. MFG_LOOKUPS is joined four times under the aliases MF1 through MF4 to translate stored lookup codes into their meanings or descriptions. MF1, MF2, and MF3 use the lookup type SYS_YES_NO and are outer-joined (the (+) operator), so rows are returned even when a flag is null or has no matching lookup. MF4 uses the lookup type QA_TXN_NAME and is joined with an inner-join predicate, linking transaction numbers to a descriptive parent transaction label.
Key Columns
- PLAN_TRANSACTION_ID — Unique identifier of the collection plan transaction; the primary key carried through from QA_PLAN_TRANSACTIONS.
- BACKGROUND_COLLECTION_FLAG — Decoded meaning of QPT.BACKGROUND_COLLECTION_FLAG via MF1 (lookup type SYS_YES_NO). Indicates whether the transaction is collected in the background.
- MANDATORY_COLLECTION_FLAG — Decoded meaning of QPT.MANDATORY_COLLECTION_FLAG via MF2 (SYS_YES_NO). Indicates whether collection of the transaction is mandatory.
- ENABLED_FLAG — Decoded meaning of QPT.ENABLED_FLAG via MF3 (SYS_YES_NO). Indicates whether the transaction is active.
- PARENT_TRANSACTION — Description resolved from QPT.TRANSACTION_NUMBER via MF4 (lookup type QA_TXN_NAME), naming the parent transaction.
- COLLECTION_PLAN_ID — The plan identifier (QPT.PLAN_ID) to which the transaction belongs.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard EBS audit columns for change tracking and accountability.
Common Use Cases and Queries
The view is typically queried to report on collection plan transactions with their flags already decoded, avoiding repeated joins to MFG_LOOKUPS. A frequent scenario is identifying transactions configured for background collection, which corresponds directly to the background_collection_flag search term:
- List background-collected transactions for a plan:
SELECT collection_plan_id, parent_transaction, background_collection_flag, mandatory_collection_flag FROM qabv_colplntxn WHERE collection_plan_id = :plan_id AND background_collection_flag = 'Yes'; - Audit recently changed configurations:
SELECT plan_transaction_id, parent_transaction, last_updated_by, last_update_date FROM qabv_colplntxn ORDER BY last_update_date DESC; - Integration extracts: feed enabled and mandatory flags to downstream quality or MES systems by selecting the decoded columns rather than raw codes.
- Reconciliation: compare decoded flag meanings against QA_PLAN_TRANSACTIONS to validate lookup configuration.
Because the flags are outer-joined, reports should treat null decoded values as "no lookup match" rather than "No." Standard EBS security and the APPS schema privileges apply to all queries.
-
View: QABV_COLPLNTXN 12.1.1
- Retrofitted
APPS.QABV_COLPLNTXN·↳ MFG_LOOKUPS·↳ QA_PLAN_TRANSACTIONS·Explore QA module →
-
View: QAFV_COLPLNTXN 12.2.2
- Retrofitted
APPS.QAFV_COLPLNTXN·↳ MFG_LOOKUPS·↳ QA_PLANS·↳ QA_PLAN_TRANSACTIONS·Explore QA module →
-
View: QABV_COLPLNTXN 12.2.2
- Retrofitted
APPS.QABV_COLPLNTXN·↳ MFG_LOOKUPS·↳ QA_PLAN_TRANSACTIONS·Explore QA module →
-
View: QAFV_COLPLNTXN 12.1.1
- Retrofitted
APPS.QAFV_COLPLNTXN·↳ MFG_LOOKUPS·↳ QA_PLANS·↳ QA_PLAN_TRANSACTIONS·Explore QA module →
-
VIEW: APPS.QAFV_COLPLNTXN 12.2.2
-
VIEW: APPS.QAFV_COLPLNTXN 12.1.1
-
VIEW: APPS.QABV_COLPLNTXN 12.2.2
-
VIEW: APPS.QABV_COLPLNTXN 12.1.1
-
VIEW: APPS.QABV_COLPLNTXN 12.1.1
-
VIEW: APPS.QABV_COLPLNTXN 12.2.2
-
VIEW: APPS.QAFV_COLPLNTXN 12.2.2
-
VIEW: APPS.QAFV_COLPLNTXN 12.1.1
-
View: RCV_FTE_TRANSACTIONS_V 12.2.2
Rolled up transactions for logistics
APPS.RCV_FTE_TRANSACTIONS_V·↳ MTL_UNITS_OF_MEASURE·↳ RCV_TRANSACTIONS·Explore PO module →
-
View: RCV_FTE_TRANSACTIONS_V 12.1.1
Rolled up transactions for logistics
APPS.RCV_FTE_TRANSACTIONS_V·↳ MTL_UNITS_OF_MEASURE·↳ RCV_TRANSACTIONS·Explore PO module →
-
PACKAGE BODY: APPS.CSTPPINV 12.2.2
-
PACKAGE BODY: APPS.CSTPPINV 12.1.1
-
eTRM - QA Tables and Views 12.1.1
Define information on applicability of a collection plan for a Quality Collection transaction
-
eTRM - QA Tables and Views 12.2.2
Define information on applicability of a collection plan for a Quality Collection transaction