Search Results supp_dstr_cl




Overview
Explore in AI Chat

Overview

The DPP_XLA_CLAIM_HEADERS_V view is an APPS-owned database object in Oracle E-Business Suite, defined under the DPP – Oracle Price Protection module. It functions as the SLA (Subledger Accounting) claim headers interface view, exposing the data required to generate accounting events and journal entries for price protection claims. In EBS 12.1.1 and 12.2.2, Price Protection supports both supplier (vendor) claims and customer claims arising from price fluctuations on previously transacted goods, and these claims must be accounted for through Subledger Accounting. This view supplies the header-level attributes that the SLA engine consumes when creating accounting events for claim settlements.

The view is not a transactional entry point but a reporting and integration construct. It joins XLA event data (from the XLA_EVENTS_GT global temporary table) to DPP transaction headers and claim records, and resolves the relevant accounting code combination IDs (CCIDs) at query time through calls to the DPP_XLA_EVENT_PUB package. This makes it a rendering and diagnostic layer over the price protection accounting flow rather than a base storage object.

Underlying Base Objects

The documented base objects referenced by the view are:

Key Columns

The view exposes several categories of columns. Accounting identifiers include PP_ACCRUAL_CCID, PP_COST_ADJ_CCID, PP_CONTRA_LIAB_CCID, PP_AP_CLEARING_CCID, and PP_AR_CLEARING_CCID, each resolved by a dedicated function in DPP_XLA_EVENT_PUB using organization, vendor, and site context.

Party resolution columns include PARTY_ID, PARTY_SITE_ID, and PARTY_TYPE. These are derived with a DECODE on the first character of CLAIM_TYPE: a value beginning with "C" is treated as a customer claim (party type 'C'), otherwise as a supplier claim (party type 'S'). Transaction context is provided by EVENT_ID, DISTRIBUTION_TYPE (fixed to 'PP_CLAIM_SETTLEMENT'), TRANSACTION_HEADER_ID, BASE_TRANSACTION_HEADER_ID, TRANSACTION_NUMBER, TRX_CURRENCY, TRANSACTION_STATUS, EFFECTIVE_START_DATE, and DAYS_COVERED. Vendor context is supplied through VENDOR_NAME, VENDOR_SITE_CODE, and ORG_ID. The full ATTRIBUTE1–ATTRIBUTE30 flexfield set plus CONTACT_EMAIL_ADDRESS, CONTACT_PHONE, and TRANSACTION_SOURCE are carried forward for descriptive and DFF reporting.

Common Use Cases and Queries

Primary uses include diagnosing price protection claim accounting, verifying that CCIDs resolve correctly, and building reconciliation reports between DPP claims and their SLA events. Because the view calls PL/SQL functions per row, queries should be filtered tightly by organization and transaction to avoid performance degradation.

A typical diagnostic query is:

SELECT event_id, transaction_number, pp_transaction_type,
       party_type, vendor_name, trx_currency,
       pp_accrual_ccid, pp_ap_clearing_ccid, pp_ar_clearing_ccid
FROM   apps.dpp_xla_claim_headers_v
WHERE  org_id = :org_id
AND    transaction_number = :trx_num;

To isolate customer versus supplier claims:

SELECT transaction_header_id, party_id, party_site_id
FROM   apps.dpp_xla_claim_headers_v
WHERE  party_type = 'C';

These queries support accounting verification, exception investigation, and integration with downstream reporting where price protection claim settlement events require traceable header-level accounting context.