Search Results dpp_xla_headers_pk

Overview

DPP_XLA_HEADERS is a table owned by the DPP schema (Oracle Price Protection) within Oracle E-Business Suite 12.1.1 and 12.2.2. Per the ETRM documentation, the table stores transaction extract header information, functioning as a staging and control structure that bridges Oracle Price Protection transactions to the Subledger Accounting (XLA) extract process. The "XLA" prefix in the object name indicates its role in feeding subledger accounting event extraction, while the "DPP" owner confirms it is specific to Price Protection rather than a shared subledger construct.

Under the heuristic Data Vault classification mined from the foreign key structure, DPP_XLA_HEADERS is assessed as standalone. In Data Vault modeling terms, this suggests the table operates as an independent component rather than as a strict hub, link, or satellite, meaning it carries both its own identifying attributes and descriptive/processing attributes without an enforced parent-child dependency to other DPP entities at the database constraint level. This classification is a modeling suggestion only; the physical implementation relies on a composite uniqueness constraint rather than referential dependencies.

Key Information Stored

The documented physical schema contains 10 columns. The most significant are described below.

• TRANSACTION_HEADER_ID — The primary identifier for the transaction extract header. It forms the leading column of the composite primary key and is central to every lookup against this table.
• PP_TRANSACTION_TYPE — The Price Protection transaction type, distinguishing the category of transaction being extracted. It participates in both the primary key and the unique business key, confirming that a single transaction header can recur across multiple transaction types.
• BASE_TRANSACTION_HEADER_ID — The base or originating transaction header reference, allowing extraction records to be traced back to their source transaction. It completes the three-column composite key.
• PROCESSED_FLAG — A status indicator reflecting whether the extract record has been successfully processed by the accounting extraction routine.
• ERROR_DESCRIPTION — Captures diagnostic text when extraction fails or validation errors occur, supporting troubleshooting of incomplete accounting transfers.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns recording who created and last modified each row, when, and through which login session. These support audit trails and compliance reporting.

The surrogate primary key is DPP_XLA_HEADERS_PK, defined over (TRANSACTION_HEADER_ID, PP_TRANSACTION_TYPE, BASE_TRANSACTION_HEADER_ID). The unique index DPP_XLA_HEADERS_U1 is defined over the identical column set, making the composite triple the definitive business-key candidate for this table.

Common Use Cases and Queries

Typical usage centers on monitoring the accounting extraction pipeline for Price Protection transactions and remediating failed extracts.

• Identifying unprocessed extract headers: SELECT transaction_header_id, pp_transaction_type FROM dpp.dpp_xla_headers WHERE processed_flag = 'N';
• Reviewing failures with diagnostics: SELECT transaction_header_id, error_description FROM dpp.dpp_xla_headers WHERE error_description IS NOT NULL;
• Tracing a specific transaction across its types: query by TRANSACTION_HEADER_ID joined with PP_TRANSACTION_TYPE to confirm whether all expected variants have been staged.
• Reporting throughput by creation period: aggregate COUNT(*) grouped by TRUNC(CREATION_DATE) to track daily extraction volumes.
• Auditing recent activity: filter on LAST_UPDATE_DATE to surface rows touched during a reconciliation window.

Related Objects

The ETRM metadata documents no foreign keys from DPP_XLA_HEADERS, consistent with its standalone classification. Related objects are therefore inferred through shared key columns and process context:

• DPP transaction header tables — joined on TRANSACTION_HEADER_ID and PP_TRANSACTION_TYPE to reconcile extract rows to source Price Protection transactions.
• XLA_HEADERS / XLA_EVENTS — Subledger Accounting tables that receive extracted header information downstream.
• DPP_XLA_LINES — the presumed line-level companion table, linked by TRANSACTION_HEADER_ID.
• DPP_TRANSACTIONS — the operational Price Protection transaction store, referenced via BASE_TRANSACTION_HEADER_ID.
• Subledger Accounting extraction concurrent programs — the processes that populate PROCESSED_FLAG and ERROR_DESCRIPTION.