Search Results supp_cust_cl




Overview
Explore in AI Chat

Overview

APPS.DPP_XLA_CLAIM_HEADERS_V is a reporting and integration view in Oracle E-Business Suite that exposes claim and settlement transaction headers enriched with Subledger Accounting (SLA/XLA) event identifiers and derived accounting flexfield identifiers. It functions as the header-level source for the Payables and Procurement (DPP) claim settlement stream, feeding the XLA event model that generates accounting entries for supplier claims and related transactions governed by the Oracle Claims and Settlement (OZF/DPP) framework.

The view consolidates transaction header attributes, party (supplier or customer) details, and accounting distribution references into a single denormalized structure. The presence of EVENT_ID from XLA_EVENTS_GT, together with multiple package function calls in the select list, indicates that this view is intended for use within the Create Accounting or Transfer to GL processing flow, or for accounting diagnostics. It returns a literal distribution type of 'PP_CLAIM_SETTLEMENT' and a 'Y' constant, aligning it with the DPP XLA event publication pattern.

Underlying Base Objects

The view is defined over the following documented base objects, all owned by APPS:

Key Columns

The view exposes several categories of columns of particular interest to extenders and report authors:

Common Use Cases and Queries

Typical applications include auditing claim settlement accounting, verifying that the correct accrual, clearing, and contra liability accounts are derived, and building custom reports that join claim headers to their XLA events. A representative query follows:

SELECT EVENT_ID, TRANSACTION_NUMBER, PP_TRANSACTION_TYPE, VENDOR_NAME, VENDOR_SITE_CODE, PARTY_TYPE, TRX_CURRENCY, TRANSACTION_STATUS, PP_ACCRUAL_CCID, PP_AP_CLEARING_CCID FROM APPS.DPP_XLA_CLAIM_HEADERS_V WHERE ORG_ID = :p_org_id AND TRANSACTION_STATUS = 'PROCESSED';

Because the view invokes several package functions per row and joins a global temporary table, direct queries should be filtered by organization and event context for performance. It is best consumed within the XLA event processing window rather than as a high-volume operational report source.