Search Results dpp_customer_claims_log_u1

Overview

The DPP.DPP_CUSTOMER_CLAIMS_LOG table is a transactional audit table within the Oracle E-Business Suite Price Protection (DPP) module. As documented in the ETRM metadata, its stated purpose is to "store updates to the customer claim information for a Price Protection Transaction." In the context of Oracle EBS 12.1.1 and 12.2.2, this table captures the incremental change history associated with customer claims, allowing distributors and suppliers to reconcile price protection amounts across inventory held by customers.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT FREE of 10, and its indexes are housed in APPS_TS_TX_IDX, reflecting standard EBS transaction data segregation. The primary key DPP_CUSTOMER_CLAIMS_LOG_PK is enforced on LOG_ID. The heuristic Data Vault classification mined from the foreign key structure is standalone; from a modeling perspective, this table would most naturally be treated as a satellite or link-style record capturing claim events, rather than a pure hub, because it stores descriptive measures alongside its relationships.

Key Information Stored

The table contains 52 documented columns. The most significant are:

• LOG_ID — surrogate primary key and lead log identifier; uniquely enforces each log entry via DPP_CUSTOMER_CLAIMS_LOG_U1.
• LOG_MODE — indicates the nature of the logged update to the claim record.
• CUSTOMER_INV_LINE_ID — foreign key to DPP_CUSTOMER_CLAIMS_ALL, tying the log row to the customer inventory detail line.
• CUST_ACCOUNT_ID — customer account reference, linked to HZ_CUST_ACCOUNTS.
• INVENTORY_ITEM_ID — the item for which price protection is claimed.
• CUSTOMER_NEW_PRICE — the new price decided by the distributor for the product/customer combination.
• TRX_CURRENCY — currency of the transaction.
• REPORTED_INVENTORY — inventory quantity reported by the customer.
• CUST_CLAIM_AMT and SUPP_CLAIM_AMT — the customer claim amount and the supplier claim for the customer amount respectively.
• DEBIT_MEMO_NUMBER, CUSTOMER_CLAIM_ID, and SUPP_CUST_CLAIM_ID — external references to the debit memo and both claim identifiers.
• CUSTOMER_CLAIM_CREATED and SUPPLIER_CLAIM_CREATED — Y/N status flags indicating whether each claim has been generated.
• ORG_ID — the operating unit, supporting multi-org security.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) plus a descriptive flexfield structure (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30).

The unique index DPP_CUSTOMER_CLAIMS_LOG_U1 on LOG_ID serves as the single documented business-key candidate.

Common Use Cases and Queries

Typical reporting scenarios include reconstructing the claim lifecycle for a customer inventory line, auditing changes to claim amounts, and verifying whether customer or supplier claims were successfully created.

Sample query — claim history for a specific customer inventory line:

• SELECT log_id, log_mode, customer_new_price, cust_claim_amt, supp_claim_amt, customer_claim_created, supplier_claim_created FROM dpp.dpp_customer_claims_log WHERE customer_inv_line_id = :line_id ORDER BY creation_date;

Sample query — pending supplier claims by operating unit:

• SELECT org_id, customer_claim_id, supp_cust_claim_id, cust_claim_amt FROM dpp.dpp_customer_claims_log WHERE supplier_claim_created = 'N' AND org_id = :org_id;

Because ATTRIBUTE1 through ATTRIBUTE30 are available, DFF-based reporting and cross-referencing external legacy claim identifiers are also common.

Related Objects

The metadata documents the following key relationships:

• DPP.DPP_CUSTOMER_CLAIMS_ALL — referenced via CUSTOMER_INV_LINE_ID; the parent claim record to which each log row belongs.
• HZ_CUST_ACCOUNTS — referenced via CUST_ACCOUNT_ID; provides customer account master data.
• DPP_CUSTOMER_CLAIMS_LOG_PK — the primary key constraint on LOG_ID.
• DPP_CUSTOMER_CLAIMS_LOG_U1 — the unique index on LOG_ID in APPS_TS_TX_IDX (the object the user searched for).

Additional dependent objects typically include the DPP customer claim concurrent programs and DFF definitions tied to ATTRIBUTE_CATEGORY, though these are not itemized in the supplied metadata.