Results for “mandatory_meaning”

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

Overview

QA_PLAN_TRANSACTIONS_V is an Oracle E-Business Suite (EBS) reporting view owned by the APPS schema in the Quality (QA) product module. It exposes collection plan and Quality Collection transaction information, joining the base transaction records to their parent plan and decoding several descriptive and flag columns into user-facing lookup meanings. The view carries a VALID status and is available in both 12.1.1 and 12.2.2 environments.

Its principal role is to provide a denormalized, presentation-ready projection of collection plan transactions. Rather than requiring report authors, integrations, or custom concurrent programs to repeatedly join QA_PLAN_TRANSACTIONS to QA_PLANS and to MFG_LOOKUPS, the view embeds those joins and delivers resolved MEANING values alongside the raw code flags. This is the reason a search for enabled_meaning resolves to this object: ENABLED_MEANING is one of the decoded lookup columns the view exposes.

Underlying Base Objects

The documented view text is defined over four referenced objects. QA_PLAN_TRANSACTIONS (SYNONYM) and QA_PLANS (SYNONYM) supply the transactional and plan-level data respectively, while MFG_LOOKUPS (VIEW) is referenced four times under separate aliases to resolve codes into meanings. The join conditions are:

• QPT.PLAN_ID = QP.PLAN_ID links each transaction to its collection plan.
• QPT.TRANSACTION_NUMBER = ML.LOOKUP_CODE with ML.LOOKUP_TYPE = 'QA_TXN_NAME' resolves the transaction name.
• QPT.MANDATORY_COLLECTION_FLAG, QPT.BACKGROUND_COLLECTION_FLAG, and QPT.ENABLED_FLAG each join to MFG_LOOKUPS under LOOKUP_TYPE = 'SYS_YES_NO' to yield the mandatory, background, and enabled meanings.

Key Columns

• PLAN_TRANSACTION_ID, PLAN_ID, TRANSACTION_NUMBER — primary identifiers for the transaction and its owning plan.
• PLAN_NAME, PLAN_DESCRIPTION — attributes of the associated collection plan.
• TRANSACTION_DESCRIPTION — the decoded QA_TXN_NAME meaning of the transaction.
• MANDATORY_COLLECTION_FLAG / MANDATORY_MEANING — the raw Yes/No code and its decoded SYS_YES_NO meaning.
• BACKGROUND_COLLECTION_FLAG / BACKGROUND_MEANING — indicates whether collection runs in the background, with decoded meaning.
• ENABLED_FLAG / ENABLED_MEANING — the enabling status code and its user-facing meaning; ENABLED_MEANING is the column matching the search term.
• EQR_LAYOUT_MODE — the layout mode indicator for the collection transaction.
• ROW_ID plus the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

Typical scenarios include building collection plan configuration listings, auditing which transactions are enabled or mandatory, and feeding downstream integration extracts that require human-readable lookups. The following query lists all enabled transactions for a given plan:

• SELECT plan_name, transaction_description, mandatory_meaning, background_meaning, enabled_meaning FROM qa_plan_transactions_v WHERE enabled_flag = 'Y' AND plan_id = :p_plan_id ORDER BY transaction_number;
• SELECT plan_id, plan_name, COUNT(*) txn_count FROM qa_plan_transactions_v WHERE enabled_meaning = 'Yes' GROUP BY plan_id, plan_name;

Because the SYS_YES_NO lookups are consistently applied to all three flag columns, ENABLED_MEANING reliably returns values such as 'Yes' or 'No', making it suitable for direct use in BI Publisher reports, OAF pages, and SQL*Loader extracts without additional lookup resolution.