Search Results cost_update

Overview

APPS.DPP_XLA_INV_HEADERS_V is an Oracle E-Business Suite view that exposes invoice-related transaction header data required for Subledger Accounting (SLA/XLA) event processing in the Procurement and Payables cost adjustment flow. It is defined with a fixed DISTRIBUTION_TYPE literal of 'PP_COST_UPDATE', indicating that the view is purpose-built to surface headers eligible for the PP_COST_UPDATE subledger event and its associated accounting distributions. The view joins the SLA events interface table to the DPP transaction headers and XLA headers, enriching the result with supplier and supplier site information plus the accrual, cost adjustment, and contra liability account combinations resolved through the DPP_XLA_EVENT_PUB package.

The view is typically consumed by the Create Accounting process, custom SLA mapping routines, reconciliation reports, and diagnostic queries that verify which PP_COST_UPDATE events have been staged and priced prior to accounting generation. It plays a supporting role in the Procure-to-Pay accounting lifecycle, particularly for cost updates on invoices that have already been processed.

Underlying Base Objects

The view is defined over the following documented objects:

• XLA_EVENTS_GT (SYNONYM) — the Subledger Accounting events global temporary table; the view filters on ENTITY_CODE = 'COST_UPDATE'.
• DPP_XLA_HEADERS (SYNONYM) — DPP XLA transaction headers; the view restricts to PP_TRANSACTION_TYPE = 'COST_UPDATE' and PROCESSED_FLAG = 'P'.
• DPP_TRANSACTION_HEADERS_ALL (SYNONYM) — DPP transaction header detail containing transaction number, vendor, currency, effective dates, and the ATTRIBUTE1–30 descriptive flexfield columns.
• AP_SUPPLIERS (SYNONYM) — supplier master used to derive VENDOR_NAME.
• AP_SUPPLIER_SITES_ALL (SYNONYM) — supplier site data used to derive VENDOR_SITE_CODE and ORG_ID.
• DPP_XLA_EVENT_PUB (PACKAGE) — the PL/SQL package called within the view to return the PP accrual, cost adjustment, and contra liability CCIDs.

Key Columns

• EVENT_ID — identifier from XLA_EVENTS_GT for the corresponding SLA event.
• DISTRIBUTION_TYPE — literal 'PP_COST_UPDATE', identifying the accounting line context.
• TRANSACTION_HEADER_ID / BASE_TRANSACTION_HEADER_ID — the DPP transaction header and its originating base transaction.
• TRANSACTION_NUMBER — user-facing transaction reference.
• VENDOR_NAME / VENDOR_SITE_CODE — supplier and site identification.
• PP_ACCRUAL_CCID, PP_COST_ADJ_CCID, PP_CONTRA_LIAB_CCID — account combinations returned by DPP_XLA_EVENT_PUB for the accrual, cost adjustment, and contra liability postings.
• TRX_CURRENCY, TRANSACTION_SOURCE, TRANSACTION_STATUS, EFFECTIVE_START_DATE, DAYS_COVERED — transaction-level attributes.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–30 — descriptive flexfield context and segments.
• CONTACT_EMAIL_ADDRESS, CONTACT_PHONE, ORG_ID — contact and organization identifiers.

Common Use Cases and Queries

The view is commonly used to reconcile PP_COST_UPDATE events, verify the account combinations the SLA engine will use, and troubleshoot events that failed to create accounting. A representative query:

• SELECT event_id, transaction_number, vendor_name, pp_accrual_ccid, pp_cost_adj_ccid, pp_contra_liab_ccid FROM apps.dpp_xla_inv_headers_v WHERE transaction_number = :trx_num;
• SELECT event_id, distribution_type, transaction_header_id FROM apps.dpp_xla_inv_headers_v WHERE event_id = :event_id;
• SELECT vendor_name, vendor_site_code, COUNT(*) FROM apps.dpp_xla_inv_headers_v GROUP BY vendor_name, vendor_site_code;

These patterns support SLA diagnostics, cost adjustment reconciliation, and reporting on cost update events across the Payables subledger.