Results for “dpp_transaction_status_map”

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

Overview

DPP_TRANSACTION_STATUS_MAP is a seeded reference table in the Oracle Price Protection (DPP) module of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. Its stated purpose is to store the mapping of transaction statuses so that the application can determine which transaction status changes are legally permitted. Rather than hard-coding allowable transitions in application logic, Oracle Price Protection externalizes them into data rows, allowing the transaction status engine to validate a requested change from one status to another before it is applied. The table is delivered with seeded content and is not intended for routine end-user maintenance.

From a data modeling perspective, the metadata classifies this object heuristically as standalone under the Data Vault convention. In practice, the table behaves as a small reference or lookup set rather than a transactional hub, link, or satellite: it carries no foreign key dependencies and exists purely to constrain the state machine of price protection transactions. Where a Data Vault model is applied, this object is best represented as a reference table or a static lookup satellite, since it holds descriptive mapping rows keyed by a composite business identifier rather than by a warehouse-generated surrogate key.

Key Information Stored

The documented physical schema comprises nine columns owned by the DPP schema. The most significant are:

• FROM_STATUS — The status a transaction currently occupies, and the first component of the composite primary key and of the unique index. This is the column most frequently referenced in searches and queries.
• TO_STATUS — The status to which a transaction may transition from FROM_STATUS; the second key component. Together, FROM_STATUS and TO_STATUS define one permitted transition.
• ENABLED_FLAG — Controls whether a given mapping row is active. Disabled rows remain in the table but are ignored by the status-change validation logic, supporting controlled enablement of transitions.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified each mapping row and when.
• ZD_EDITION_NAME — The editioning column used by the EBS online patching infrastructure (Edition-Based Redefinition) in Release 12.2, allowing seeded reference data to be versioned and switched without downtime.

The primary key is DPP_TRANSACTION_STATUS_MAP_PK defined on (FROM_STATUS, TO_STATUS), and the unique index DPP_TRANSACTION_STATUS_MAP_U1 covers (FROM_STATUS, TO_STATUS, ZD_EDITION_NAME). Because the primary key is composite and uses the two status codes directly, there is no separate surrogate key column; FROM_STATUS and TO_STATUS jointly function as the business key.

Common Use Cases and Queries

Typical uses include validating an intended status change before update, reporting the complete allowed transition matrix, and auditing which transitions are currently disabled. A query listing all permitted transitions from a given status is straightforward:

• SELECT to_status FROM dpp.dpp_transaction_status_map WHERE from_status = :p_from_status AND enabled_flag = 'Y' ORDER BY to_status;
• SELECT from_status, to_status, enabled_flag FROM dpp.dpp_transaction_status_map WHERE enabled_flag = 'N'; to identify transitions suppressed by configuration.
• SELECT COUNT(*) FROM dpp.dpp_transaction_status_map GROUP BY from_status; to profile the transition graph and detect statuses with no outgoing paths.

Reporting usage is typically low-volume and diagnostic: confirming that a business flow can reach a terminal status, or verifying that seeded data was refreshed after an upgrade or patch. Because the table is seeded, changes should be treated as configuration and documented.

Related Objects

The ETRM metadata records no foreign key relationships for this table, consistent with its standalone classification; it neither references nor is referenced by other tables through enforced constraints. Effectively it is consulted by the DPP transaction status-change logic and any application or concurrent program that drives price protection transaction workflow rather than being joined structurally to a parent entity. Dependent behavior therefore resides in DPP transaction tables that carry a status column, which reference FROM_STATUS and TO_STATUS by value rather than by constraint, along with the status code lookups that supply the valid status values appearing in these two key columns.