Search Results dpp_claim_types

Overview

APPS.DPP_XLA_CP_V is a reporting and integration view within the Oracle E-Business Suite 12.1.1 and 12.2.2 environment that correlates Oracle Subledger Accounting (XLA) transaction headers with Oracle Trade Management claim records. The view name reflects its composition: "DPP" denotes the Distributed Promotions / Trade Management schema family (historically sourced from the Oracle Claims and Deductions modules), "XLA" references the Subledger Accounting transaction layer, and "CP" refers to the claim-to-payment or claim processing association used by the ETRM (Enterprise Trade Management) application. The view provides a single denormalized result set that ties a claim to its accounting event, its trade transaction header, and its claim type description. This makes it valuable for reconciliation between trade operations data and the accounting engine, for audit reporting, and for downstream integration extracts where claim and accounting context must be presented together.

Underlying Base Objects

The view is defined over five referenced objects. From the Trade Management side it joins OZF_CLAIMS_ALL (the master claim and deduction table, holding amounts, dates, numbers, and currency) and two DPP transaction tables: DPP_TRANSACTION_HEADERS_ALL (the trade or promotional transaction header, providing transaction IDs and numbers) and DPP_TRANSACTION_CLAIMS_ALL (the association table linking transactions to claims, including the claim type code). From the accounting side it references DPP_XLA_HEADERS, which supplies the base transaction header identifier that bridges claims to their accounting event. A lookup view, FND_LOOKUP_VALUES_VL, provides the descriptive meaning of each claim type code, restricted to the lookup type 'DPP_CLAIM_TYPES', which explains the "claim types" search term associated with this object. In the documented 12.2.2 metadata these base objects are exposed as synonyms; FND_LOOKUP_VALUES_VL is the translated, security-aware lookup view. The joins are equality-based on ORG_ID, CLAIM_ID, and TRANSACTION_HEADER_ID, with an additional non-null condition on the XLA base transaction header.

Key Columns

The view projects a focused set of columns. TRANSACTION_HEADER_ID identifies the DPP transaction header. CLAIM_ID and CLAIM_NUMBER identify the claim in OZF_CLAIMS_ALL. TRANSACTION_NUMBER is the human-readable transaction identifier. AMOUNT is sourced from OCA.ACCTD_AMOUNT, the accounted amount from the claim record. CLAIM_DATE carries the claim date, and CURRENCY_CODE the claim currency. MEANING is the description resolved from FND_LOOKUP_VALUES_VL for the claim type code, giving business-friendly context to the claim's type.

Common Use Cases and Queries

Typical usage includes claim-to-accounting reconciliation, claim type analysis, and extracts feeding reporting schemas. Because the lookup join is date-bounded (SYSDATE between START_DATE_ACTIVE and END_DATE_ACTIVE), only currently active claim type lookups are returned.

• Reconcile accounted claim amounts to XLA transactions: SELECT transaction_number, claim_number, amount, currency_code FROM apps.dpp_xla_cp_v WHERE claim_number = :claim;
• Analyze claims by type description: SELECT meaning, COUNT(*), SUM(amount) FROM apps.dpp_xla_cp_v GROUP BY meaning ORDER BY 2 DESC;
• List claims over a date range with transaction context: SELECT claim_date, claim_number, transaction_number, meaning, amount FROM apps.dpp_xla_cp_v WHERE claim_date BETWEEN :from_date AND :to_date;

Queries should account for the view's restriction to records having a non-null XLA base transaction header, meaning claims without an associated accounting event will not appear.