Results for “claim_number”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

DPP_CUSTOMER_CLAIMS_GT is a table owned by the DPP schema, the database schema for Oracle Price Protection, a component of Oracle's Trade Management and channel revenue management family. The "_GT" suffix conventionally denotes a global temporary table used to stage, transform, or interface claim data during processing runs rather than to persist permanent transactional records. In the Oracle EBS 12.1.1 and 12.2.2 releases, this object serves as an intermediate workspace for customer claim lines that flow through the price protection claims lifecycle. It captures item-level claim detail — quantities, amounts, currency, and unit of measure — alongside customer and item descriptive attributes, and it also records a reason-for-failure value, which indicates the table is frequently used to hold validation results during a claims load, recalculation, or submission program.

The ETRM metadata classifies this object heuristically as standalone within a Data Vault modeling approach, meaning it does not participate in a hub-and-link constellation through mined foreign key relationships. In practice a standalone classification suggests it functions more like a staging or satellite-style structure: it references dimension-like business entities (customer account, claim) without itself being a core hub. This classification should be treated as a modeling suggestion rather than a definitive architectural designation.

Key Information Stored

The table exposes 14 documented columns. The most significant include:

• CLAIM_ID — foreign key to OZF_CLAIMS_ALL, the primary business link tying each staged row to its parent claim header.
• CUST_ACCOUNT_ID — foreign key to HZ_CUST_ACCOUNTS, placing the claim line against a specific customer account.
• CUSTOMER_ID and CUSTOMER_NAME — customer identifier and denormalized descriptive name for reporting convenience.
• TRANSACTION_LINE_ID — the source transaction line reference underlying the claim.
• INVENTORY_ITEM_ID, ITEM_NUMBER, and ITEM_DESCRIPTION — item identity and descriptive attributes for the claimed product.
• CLAIM_LINE_AMOUNT and CURRENCY — monetary value and its currency context.
• CLAIM_QUANTITY and UOM — claimed quantity and its unit of measure.
• CLAIM_NUMBER — the human-readable claim reference.
• REASON_FOR_FAILURE — diagnostic text explaining why a staged claim line failed validation or processing.

The metadata does not document a single-column surrogate primary key or a declared unique business-key index; CLAIM_ID combined with TRANSACTION_LINE_ID and INVENTORY_ITEM_ID typically constitutes the practical business-key composite for identifying a staged line.

Common Use Cases and Queries

Typical usage centers on staging claim lines for validation before submission to OZF_CLAIMS_ALL, reconciliation of failed lines, and reporting of claim value by customer and item. A validation-failure review query might filter rows where REASON_FOR_FAILURE is not null, joining to HZ_CUST_ACCOUNTS and OZF_CLAIMS_ALL:

SELECT g.CLAIM_NUMBER, g.CUSTOMER_NAME, g.ITEM_NUMBER, g.CLAIM_QUANTITY, g.CLAIM_LINE_AMOUNT, g.REASON_FOR_FAILURE FROM DPP.DPP_CUSTOMER_CLAIMS_GT g WHERE g.REASON_FOR_FAILURE IS NOT NULL

Because global temporary tables are session- or transaction-scoped, queries should run within the same session that populated the table. Reporting use cases include claim value summaries by customer account and item number, and currency-denominated claim line analysis.

Related Objects

• OZF_CLAIMS_ALL — joined via CLAIM_ID; the parent claims table.
• HZ_CUST_ACCOUNTS — joined via CUST_ACCOUNT_ID; the customer account master.
• HZ_CUST_ACCOUNT_ROLES / HZ_PARTIES — often joined to resolve the CUSTOMER_ID to party detail.
• MTL_SYSTEM_ITEMS_B — referenced by INVENTORY_ITEM_ID to resolve item attributes.
• OE_ORDER_LINES_ALL / RA_CUSTOMER_TRX_LINES_ALL — source transaction lines underlying TRANSACTION_LINE_ID.
• OZF_CLAIM_LINES / DPP claim processing programs — consumers of staged rows during submission.