Results for “mandatory_collection_flag”

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

Overview

QA_PLAN_TRANSACTIONS is a Quality Management (QA) module table in Oracle E-Business Suite that stores information about Quality Collection Plans and the Quality Collection transactions with which those plans are associated. In EBS 12.1.1 and 12.2.2, this table functions as the linking construct between a collection plan definition and the transaction context in which the plan is applied, enabling quality data collection to be triggered, controlled, and audited at transaction level.

The documented primary key is QA_PLAN_TRANSACTIONS_PK, defined on PLAN_TRANSACTION_ID. The table references QA_PLANS through the PLAN_ID foreign key, and it is referenced by QA_PLAN_COLLECTION_TRIGGERS through PLAN_TRANSACTION_ID. A unique index, QA_PLAN_TRANSACTIONS_U1, exists on (PLAN_TRANSACTION_ID, ZD_EDITION_NAME). Based on the foreign key topology, a Data Vault classification of satellite-leaning is suggested: the entity is dependent on QA_PLANS for its descriptive context, while also serving as a parent for downstream trigger records.

Key Information Stored

The table comprises 13 documented columns in the 12.2.2 physical schema. The most significant are listed below.

• PLAN_TRANSACTION_ID — the surrogate primary key and the unique identifier for each plan transaction record.
• PLAN_ID — foreign key to QA_PLANS, identifying the collection plan associated with the transaction.
• TRANSACTION_NUMBER — the business-facing identifier for the transaction record, typically used in reporting and lookup.
• MANDATORY_COLLECTION_FLAG — indicates whether collection results must be captured for the transaction before it can proceed.
• BACKGROUND_COLLECTION_FLAG — indicates whether collection occurs in background mode rather than through interactive entry.
• ENABLED_FLAG — controls whether the plan transaction is active and available for use.
• EQR_LAYOUT_MODE — governs the layout mode used when rendering the associated collection plan for the transaction.
• ZD_EDITION_NAME — the edition discriminator used in the 12.2.2 editioning infrastructure and part of the unique index QA_PLAN_TRANSACTIONS_U1.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN capture the standard EBS who-column audit trail.

The unique index QA_PLAN_TRANSACTIONS_U1 on (PLAN_TRANSACTION_ID, ZD_EDITION_NAME) reinforces the primary key in the editioned 12.2.2 model, while TRANSACTION_NUMBER serves as the principal human-readable business key candidate.

Common Use Cases and Queries

Typical usages include identifying which collection plans are enabled for a given transaction, determining mandatory versus background collection behavior, and tracing trigger records produced for a plan transaction.

• List enabled plan transactions for a plan: select PLAN_TRANSACTION_ID, TRANSACTION_NUMBER, MANDATORY_COLLECTION_FLAG, BACKGROUND_COLLECTION_FLAG from QA.QA_PLAN_TRANSACTIONS where PLAN_ID = :plan_id and ENABLED_FLAG = 'Y'.
• Join to the plan definition to report plan names alongside transaction behavior: select p.PLAN_NAME, t.TRANSACTION_NUMBER, t.EQR_LAYOUT_MODE from QA.QA_PLAN_TRANSACTIONS t join QA.QA_PLANS p on p.PLAN_ID = t.PLAN_ID.
• Locate triggers originating from a plan transaction: select c.* from QA.QA_PLAN_COLLECTION_TRIGGERS c join QA.QA_PLAN_TRANSACTIONS t on t.PLAN_TRANSACTION_ID = c.PLAN_TRANSACTION_ID.
• Audit recent configuration changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Related Objects

• QA_PLANS — parent table; joined on QA_PLAN_TRANSACTIONS.PLAN_ID = QA_PLANS.PLAN_ID.
• QA_PLAN_COLLECTION_TRIGGERS — child table; joined on QA_PLAN_COLLECTION_TRIGGERS.PLAN_TRANSACTION_ID = QA_PLAN_TRANSACTIONS.PLAN_TRANSACTION_ID.
• QA_PLAN_TRANSACTIONS_PK — primary key constraint on PLAN_TRANSACTION_ID.
• QA_PLAN_TRANSACTIONS_U1 — unique index on (PLAN_TRANSACTION_ID, ZD_EDITION_NAME), supporting edition-aware access.
• Quality Collection public APIs and concurrent programs that process collection plans and triggers, which read and write plan transaction configuration.