Search Results dpp_txn_headers_int_all

Overview

DPP_TXN_HEADERS_INT_ALL is the header-level interface (staging) table for Oracle Price Protection (DPP), a module within the Oracle E-Business Suite supply chain and procurement family. It stores price protection transaction header details as received from a supplier before validation and transfer into the base Price Protection transaction tables. Price protection arrangements typically cover inventory or open commitments whose value declines after purchase; suppliers submit claims for the difference, and this table captures the incoming header record that anchors each such claim.

The table resides in the DPP schema and is documented as a standalone object in the ETRM 12.2.2 physical schema with 63 columns. Following Data Vault modeling heuristics mined from its foreign-key structure, this table can be characterized as a hub-like interface entity: it is not itself a subordinate satellite, and it owns the primary key referenced by dependent records. This is a modeling suggestion only, as the physical implementation relies on a classic single-column Oracle primary key rather than Data Vault hash keys.

Key Information Stored

The table's surrogate primary key is TRANSACTION_INT_HEADER_ID, defined by the constraint DPP_TXN_HEADERS_INT_ALL_PK and mirrored by the unique index DPP_TXN_HEADERS_INT_ALL_U1. Although the index is documented as a candidate business key, it functions in practice as the surrogate interface identifier rather than a natural business identifier. The most significant columns fall into several groups:

• Source and document identification: ORIG_SYS_DOCUMENT_REF, REF_DOCUMENT_NUMBER, and SUPP_DIST_CLAIM_ID / SUPP_DIST_CLAIM_NUMBER identify the supplier-submitted claim and its originating system reference.
• Supplier and site: VENDOR_NAME, VENDOR_ID, VENDOR_SITE, VENDOR_SITE_ID, VENDOR_CONTACT_NAME, VENDOR_CONTACT_ID, CONTACT_EMAIL_ADDRESS, and CONTACT_PHONE describe the submitting party.
• Approval and terms: SUPPLIER_APPROVED_BY and SUPPLIER_APPROVAL_DATE track supplier approval; EFFECTIVE_START_DATE, DAYS_COVERED, and CURRENCY define the claim period and monetary basis.
• Organizational context: ORG_ID and OPERATING_UNIT_NAME scope the record to a specific inventory organization and operating unit.
• Interface control: TRANSACTION_SOURCE, INTERFACE_STATUS, and ERROR_CODE drive the import process and error reporting.
• Audit and extensibility: the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), concurrent program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE), ATTRIBUTE_CATEGORY, and ATTRIBUTE1 through ATTRIBUTE30 provide auditing and user-defined extensibility.

Common Use Cases and Queries

This table supports supplier data import, error reconciliation, and pre-transfer validation reporting. A typical diagnostic query identifies failed interface rows:

• SELECT transaction_int_header_id, ref_document_number, vendor_name, interface_status, error_code FROM dpp_txn_headers_int_all WHERE interface_status = 'ERROR';
• Joining to line-level data: SELECT h.transaction_int_header_id, h.vendor_name, l.* FROM dpp_txn_headers_int_all h, dpp_txn_lines_int_all l WHERE h.transaction_int_header_id = l.transaction_int_header_id;
• Auditing by loader: filter on REQUEST_ID or PROGRAM_APPLICATION_ID to trace records created by a specific concurrent program run.
• Reporting by vendor and period: aggregate on VENDOR_ID, CURRENCY, and EFFECTIVE_START_DATE to summarize pending supplier claims.

Related Objects

The principal relationship is to its line-level child table. The documented foreign key is:

• DPP_TXN_LINES_INT_ALL.TRANSACTION_INT_HEADER_ID → DPP_TXN_HEADERS_INT_ALL.TRANSACTION_INT_HEADER_ID — the line interface table, which carries detail claim lines belonging to each header.

Beyond the documented FK, the header record logically connects to Oracle supplier and organization entities through VENDOR_ID, VENDOR_SITE_ID, and ORG_ID, which resolve to the PO/AP vendor and HR organization tables. The interface columns INTERFACE_STATUS and ERROR_CODE follow Oracle's standard interface-table conventions used throughout supply chain modules, so error-handling and purge routines commonly associated with interface tables apply. Downstream, validated records are transferred into the Price Protection base transaction tables by the module's import concurrent programs, at which point the staging rows are typically archived or purged.