Results for “qa_txn_name”

24 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.QABV_COLPLNTXN is a read-only database view in the Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 environments, defined in the APPS schema. It presents a denormalized, decoded projection of collection plan transaction data drawn from the Quality Management module. Specifically, the view exposes records from QA_PLAN_TRANSACTIONS and resolves the internal lookup codes stored on those rows into human-readable meaning text by joining to the MFG_LOOKUPS view. This design allows report developers, integration specialists, and functional analysts to query collection plan transactions without manually decoding SYS_YES_NO style flags or the QA_TXN_NAME lookup, which is the lookup type referenced by the user search term.

The view is defined with the WITH READ ONLY clause, so it is strictly a querying surface. It carries no DML capability and is intended for reporting, data extraction, and integration interfaces that require a stable, descriptive representation of the underlying base tables.

Underlying Base Objects

The documented base objects for this view are:

  • QA_PLAN_TRANSACTIONS — referenced in the metadata as a synonym. This is the primary source of transaction rows (alias QPT), supplying the plan transaction identifier, collection plan ID, the background/mandatory/enabled flags, the transaction number, and standard audit columns.
  • MFG_LOOKUPS — referenced in the metadata as a view. It is joined four times (aliases MF1 through MF4) to translate stored lookup codes into meaning values.

Three of the four MFG_LOOKUPS joins (MF1, MF2, MF3) use the outer-join operator (+) against lookup type SYS_YES_NO, meaning rows are returned even when a flag lookup cannot be resolved. The fourth join (MF4) is an inner join against lookup type QA_TXN_NAME, keyed on QPT.TRANSACTION_NUMBER. Because this join is mandatory, only transaction rows whose TRANSACTION_NUMBER exists in QA_TXN_NAME as an enabled lookup code are returned.

Key Columns

Common Use Cases and Queries

Typical use cases include building Quality collection plan transaction reports, feeding integration extracts, and auditing which transactions are enabled, mandatory, or background-collected under a given plan.

SELECT plan_transaction_id,
       collection_plan_id,
       parent_transaction,
       background_collection_flag,
       mandatory_collection_flag,
       enabled_flag
FROM   apps.qabv_colplntxn
WHERE  collection_plan_id = :p_plan_id
ORDER  BY plan_transaction_id;

To resolve a specific transaction by its decoded QA_TXN_NAME value:

SELECT plan_transaction_id, collection_plan_id, parent_transaction
FROM   apps.qabv_colplntxn
WHERE  parent_transaction = :p_txn_name;

Because the QA_TXN_NAME join is inner, queries naturally return only valid, defined transaction names. The view is best used for read-only reporting against collection plan activity in Oracle Quality.