Search Results claim_quantity

Overview

DPP.DPP_CUSTOMER_CLAIMS_GT is a global temporary table (GTT) in the Oracle EBS DPP schema, documented in ETRM 12.2.2 (valid in 12.1.1 and 12.2.2). It functions as a transient staging structure for customer claim data, typically loaded by concurrent programs or PL/SQL during claim processing and consumed within a single session. The table is a SYS$SESSION-scoped GTT: data placed by the current session is visible only to that session and is removed when the session ends, making it suitable for interim result sets rather than persistent storage.

Under a heuristic Data Vault classification, DPP_CUSTOMER_CLAIMS_GT is best modeled as a satellite. It captures descriptive claim attributes (amount, quantity, UOM, currency, item, customer, failure reason) rather than serving as a durable hub or link. It has no surrogate primary key declared in the documented metadata and no unique business keys; identifiers such as TRANSACTION_LINE_ID and CLAIM_ID function as foreign references or source keys for downstream joins.

Key Information Stored

The 14 documented columns fall into reference, descriptive, and diagnostic groups:

• TRANSACTION_LINE_ID — source transaction line reference; the primary driver for matching claim lines to inventory or order transactions.
• CLAIM_ID — foreign key to OZF_CLAIMS_ALL; the business link to the claim header.
• CLAIM_NUMBER — user-visible claim identifier used for reporting and reconciliation.
• CUST_ACCOUNT_ID — foreign key to HZ_CUST_ACCOUNTS; the customer account owning the claim.
• CUSTOMER_ID, CUSTOMER_NAME — customer identifier and display name for easy reporting.
• INVENTORY_ITEM_ID, ITEM_NUMBER, ITEM_DESCRIPTION — the claimed item reference and descriptive attributes.
• CLAIM_LINE_AMOUNT, CURRENCY — monetary value of the claim line and its currency.
• CLAIM_QUANTITY — the quantity asserted in the claim; the column most relevant to claim_quantity searches, and the basis for comparing expected versus claimed units with UOM.
• UOM — unit of measure for CLAIM_QUANTITY.
• REASON_FOR_FAILURE — diagnostic text (up to 2000 chars) populated when claim validation or processing fails.

No surrogate primary key is documented, and no unique indexes are defined; the table is intentionally keyless to allow bulk insertion of staging rows.

Common Use Cases and Queries

Typical uses include validating claim lines against customer accounts and items, summarizing claim quantities by customer, and diagnosing failed claims via REASON_FOR_FAILURE. Example patterns:

• Quantity reconciliation: SELECT CLAIM_NUMBER, ITEM_NUMBER, SUM(CLAIM_QUANTITY), UOM FROM DPP.DPP_CUSTOMER_CLAIMS_GT GROUP BY CLAIM_NUMBER, ITEM_NUMBER, UOM;
• Failed claim triage: SELECT CLAIM_NUMBER, ITEM_NUMBER, REASON_FOR_FAILURE FROM DPP.DPP_CUSTOMER_CLAIMS_GT WHERE REASON_FOR_FAILURE IS NOT NULL;
• Customer aggregation: join CUST_ACCOUNT_ID to HZ_CUST_ACCOUNTS and sum CLAIM_LINE_AMOUNT by CURRENCY.
• Joining to OZF_CLAIMS_ALL on CLAIM_ID to enrich with claim header status.

Because the table is session-scoped, queries must run in the same session that populated it; concurrent sessions see no rows.

Related Objects

• OZF_CLAIMS_ALL — joined on CLAIM_ID; the claim header source.
• HZ_CUST_ACCOUNTS — joined on CUST_ACCOUNT_ID; customer account master.
• APPS.DPP_CUSTOMER_CLAIMS_GT — the APPS synonym, the public access point.
• OZF_CLAIMS_LINES (or claim line equivalent) — related claim line detail for matching TRANSACTION_LINE_ID.
• HZ_CUST_ACCT_SITES_ALL / HZ_CUST_SITE_USES_ALL — for customer site context during claim validation.
• MTL_SYSTEM_ITEMS_B — INVENTORY_ITEM_ID resolution for item reporting.