Search Results dpp_customer_claims_log_pk

Overview

DPP_CUSTOMER_CLAIMS_LOG is a table in the DPP schema (Oracle Price Protection) within Oracle E-Business Suite 12.1.1 and 12.2.2. As its name and documentation indicate, the table stores updates to customer claim information associated with a Price Protection Transaction. In the Oracle Price Protection flow, customers submit claims when the price of inventory they hold declines after purchase; the application calculates a claim amount, offsets it against a supplier claim, and communicates the result back to the customer. DPP_CUSTOMER_CLAIMS_LOG captures the audit trail of changes made to that customer claim data, allowing the system and its users to reconstruct the evolution of a claim over time.

The physical schema documented for release 12.2.2 defines the table as owned by DPP with 52 columns. The primary key is the DPP_CUSTOMER_CLAIMS_LOG_PK constraint, defined on the LOG_ID column, and a unique index DPP_CUSTOMER_CLAIMS_LOG_U1 also exists on LOG_ID. From a data-modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is standalone, suggesting this table behaves as an independent log rather than as a hub, link, or satellite in a Data Vault model. Nevertheless, its CUSTOMER_INV_LINE_ID and CUST_ACCOUNT_ID foreign keys anchor each log row to operational entities in the Price Protection and receivables models.

Key Information Stored

The most significant columns in DPP_CUSTOMER_CLAIMS_LOG are the following:

• LOG_ID — Surrogate primary key (DPP_CUSTOMER_CLAIMS_LOG_PK) and the column on which the unique index DPP_CUSTOMER_CLAIMS_LOG_U1 is defined; it uniquely identifies each logged change record.
• LOG_MODE — Indicates the nature of the logged operation (for example, an insert, update, or delete) applied to the customer claim data.
• CUSTOMER_INV_LINE_ID — Foreign key to DPP_CUSTOMER_CLAIMS_ALL; ties the log row to the customer claim line whose change is being recorded.
• CUST_ACCOUNT_ID — Foreign key to HZ_CUST_ACCOUNTS; identifies the customer account to which the claim belongs.
• INVENTORY_ITEM_ID — The inventory item affected by the price protection claim.
• CUSTOMER_NEW_PRICE — The adjusted price used in computing the customer's claim.
• TRX_CURRENCY — The transaction currency in which the claim amounts are expressed.
• REPORTED_INVENTORY — The inventory quantity reported by the customer as the basis for the claim.
• CUST_CLAIM_AMT — The claim amount attributable to the customer.
• SUPP_CLAIM_AMT — The claim amount recoverable from the supplier.
• DEBIT_MEMO_NUMBER — The debit memo raised in connection with the customer claim.
• CUSTOMER_CLAIM_ID and SUPP_CUST_CLAIM_ID — Identifiers of the customer-facing and supplier-facing claim records.
• CUSTOMER_CLAIM_CREATED and SUPPLIER_CLAIM_CREATED — Flags or timestamps indicating that the respective claims were created.
• ORG_ID — The operating unit under which the claim was processed, enabling multi-org reporting.

Standard EBS audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the ATTRIBUTE_CATEGORY plus thirty ATTRIBUTE columns support traceability and customer-specific extensions.

Common Use Cases and Queries

Typical uses of this table include auditing how a customer claim changed over time, reconciling customer and supplier claim amounts, and producing claim history reports for finance and order management users.

• Full change history for a claim line: select from DPP_CUSTOMER_CLAIMS_LOG where CUSTOMER_INV_LINE_ID equals the claim line identifier, ordered by CREATION_DATE or LOG_ID, to reconstruct each recorded update.
• Customer-level claim audit: join the log to HZ_CUST_ACCOUNTS on CUST_ACCOUNT_ID to report all claim changes for a given customer account and operating unit (ORG_ID).
• Amount reconciliation: compare CUST_CLAIM_AMT and SUPP_CLAIM_AMT by TRX_CURRENCY to validate that customer and supplier claim figures balance.
• Debit memo tracking: filter on DEBIT_MEMO_NUMBER and CUSTOMER_CLAIM_ID to trace the log entries behind a specific debit memo.
• Period reporting: aggregate CUST_CLAIM_AMT by ORG_ID and CREATION_DATE for month-end price protection reporting.

Because the table is a log, queries should treat rows as append-only history rather than as current state.

Related Objects

The most significant related objects, based on the documented foreign-key relationships and the Price Protection model, are:

• DPP_CUSTOMER_CLAIMS_ALL — joined via CUSTOMER_INV_LINE_ID; holds the current customer claim data that this table logs.
• HZ_CUST_ACCOUNTS — joined via CUST_ACCOUNT_ID; provides customer account details.
• DPP_CUSTOMER_CLAIMS_LOG_PK / DPP_CUSTOMER_CLAIMS_LOG_U1 — the primary key constraint and unique index on LOG_ID that guarantee log row identity.
• Price Protection transaction entities in the DPP schema that produce customer and supplier claims and debit memos, and to which CUSTOMER_CLAIM_ID and SUPP_CUST_CLAIM_ID resolve.
• ORG_ID-based operating unit views and reporting objects that filter Price Protection data by organization.

Developers extending this table should use the ATTRIBUTE columns for custom data rather than altering the documented structure, preserving upgrade compatibility across 12.1.1 and 12.2.2.