Search Results dpp_xla_lines

Overview

The DPP_XLA_LINES table resides in the DPP schema and forms part of the Oracle Price Protection (DPP) module within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store transaction extract lines information, effectively acting as a staging or mapping repository that links Subledger Accounting (XLA) event data to the underlying price protection transactions. The table captures the intersection between a transaction header and line and the corresponding base transaction header and line, enabling reconciliation between original transaction records and their extracted or derived accounting entries.

Based on the mined foreign key structure, the table is classified heuristically as standalone. In Data Vault modeling terms, this is best interpreted as a link-style or bridge candidate rather than a hub or satellite, since the table does not own independent business entities but instead represents associations between transaction pairings. Its composite primary key is a surrogate construct over four reference columns rather than a single meaningless sequence identifier.

Key Information Stored

The table contains ten documented columns. The most important structural columns are:

• TRANSACTION_HEADER_ID — identifies the transaction header for the extract line record.
• TRANSACTION_LINE_ID — identifies the specific transaction line within that header.
• BASE_TRANSACTION_HEADER_ID — identifies the base (source) transaction header against which the extract line is associated.
• BASE_TRANSACTION_LINE_ID — identifies the corresponding base transaction line.
• TRANSACTION_SUB_TYPE — classifies the nature or category of the transaction extract line, useful for filtering specific extract scenarios.

The remaining five columns are standard Oracle EBS audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. The surrogate primary key DPP_XLA_LINES_PK spans all four transaction identifiers (TRANSACTION_HEADER_ID, TRANSACTION_LINE_ID, BASE_TRANSACTION_HEADER_ID, BASE_TRANSACTION_LINE_ID). A unique index, DPP_XLA_LINES_U1, covers the same four columns, confirming that this quartet constitutes the true business-key candidate and that no duplicate pairing of transaction and base transaction lines may exist.

Common Use Cases and Queries

Typical use cases center on reconciliation, audit, and reporting of price protection transaction extraction. Analysts frequently need to trace which base transaction lines were extracted into a given transaction or vice versa. A common query retrieves all extract lines for a specific transaction header:

SELECT transaction_line_id, base_transaction_header_id,
       base_transaction_line_id, transaction_sub_type
FROM   dpp.dpp_xla_lines
WHERE  transaction_header_id = :p_header_id;

Another frequent pattern joins extract lines back to price protection transaction tables using the header and line identifiers to validate that every extracted record maps to a legitimate source. Reporting on TRANSACTION_SUB_TYPE distribution supports volume and trend analysis of extract activity, while the audit columns support "who changed what and when" investigations. Because the unique index enforces uniqueness across the four IDs, de-duplication queries are generally unnecessary.

Related Objects

The metadata describes DPP_XLA_LINES as standalone with no documented foreign key relationships. Logical dependencies include:

• DPP transaction header/line tables — referenced through TRANSACTION_HEADER_ID and TRANSACTION_LINE_ID.
• Base price protection transaction tables — referenced through BASE_TRANSACTION_HEADER_ID and BASE_TRANSACTION_LINE_ID.
• XLA (Subledger Accounting) event and extract structures — the table's name and purpose imply participation in the XLA extract flow, though no FK is documented.

Because relationship data is limited, implementers should confirm concrete parent tables in their specific instance before writing dependent joins.