Search Results claimed_amount

Overview

DPP_TXN_DASHBOARD_V is a reporting view owned by the APPS schema within the Oracle Price Protection (DPP) module, a component of Oracle E-Business Suite Advanced Pricing and Trade Management. The view consolidates transaction header, supplier, operating unit, status, and claim amount information into a single denormalized projection intended to support dashboard-style reporting and operational monitoring of price protection transactions. In Oracle EBS 12.1.1 and 12.2.2, the object is registered as VALID, and no PL/SQL API or form is required to consume it — it is queried directly.

The view's primary role is to expose the transactional and financial state of price protection claims at a summary level. Each row represents a price protection transaction header, enriched with descriptive attributes from master and lookup sources, plus two aggregated monetary measures derived from child tables. Because it includes a currency conversion expression for customer claim amounts, the view is positioned as a cross-currency reporting artifact rather than a pure operational data source. The view carries no claim amount stored on the header itself; the CLAIMED_AMOUNT and CUST_CLAIM_AMOUNT values are computed at query time, which is the column a search for "claimed_amount" resolves to.

Underlying Base Objects

The view is defined over the following documented base objects:

• DPP_TRANSACTION_HEADERS (synonym) — the driving table (aliased DAH), supplying transaction number, transaction header ID, dates, source, status, currency, vendor ID, and org ID.
• DPP_TRANSACTION_LINES_ALL (synonym) — the source of the summed CLAIM_AMOUNT that produces CLAIMED_AMOUNT.
• DPP_CUSTOMER_CLAIMS_ALL (synonym) — the source of the summed, currency-converted CUST_CLAIM_AMT.
• AP_SUPPLIERS (synonym) — joined on VENDOR_ID to resolve the supplier name.
• HR_ALL_ORGANIZATION_UNITS (synonym) — joined on ORG_ID to resolve the operating unit name.
• FND_LOOKUP_VALUES_VL (view) — joined on LOOKUP_TYPE = 'DPP_TRANSACTION_STATUSES' to translate the status code into its meaning, filtered by the effective date range.
• FND_PROFILE (package) — invoked for the DPP_CURRENCY_CONVERSION_TYPE profile value.
• GL_CURRENCY_API (package) — invoked for CONVERT_CLOSEST_AMOUNT_SQL to convert customer claim amounts into the transaction currency.

The joins are effectively equijoins on transaction header ID, org ID, vendor ID, and organization ID, with the lookup join constrained by SYSDATE between START_DATE_ACTIVE and NVL(END_DATE_ACTIVE, SYSDATE).

Key Columns

• OPERATING_UNIT — name of the organization unit owning the transaction.
• REF_DOCUMENT_NUMBER — external reference document on the transaction header.
• SUPPLIER_NAME — vendor name from AP_SUPPLIERS.
• TRANSACTION_HEADER_ID / TRANSACTION_NUMBER — primary key and human-readable transaction identifier.
• CREATION_DATE / EFFECTIVE_START_DATE — audit and effective dating columns.
• TRANSACTION_SOURCE / TRANSACTION_STATUS / MEANING — source indicator, status code, and the decoded status meaning.
• CLAIMED_AMOUNT — aggregate of DPP_TRANSACTION_LINES_ALL.CLAIM_AMOUNT for the header and org; the column most commonly targeted by the "claimed_amount" search.
• ONHAND_INV_CURRENCY — the transaction currency, since the header currency is the inventory on-hand currency context.
• CUST_CLAIM_AMOUNT — aggregate customer claim amounts converted to the transaction currency.
• CLAIM_CURRENCY — the currency in which the claim amounts are expressed (TRX_CURRENCY).

Common Use Cases and Queries

Typical uses include monitoring outstanding price protection claims, reconciling supplier claim totals, and reporting claim values by operating unit or supplier. A basic query filtering by status and summing claim value:

SELECT operating_unit, transaction_number, supplier_name,
       meaning, claimed_amount, claim_currency
FROM   apps.dpp_txn_dashboard_v
WHERE  transaction_status = 'APPROVED'
ORDER  BY creation_date DESC;

Aggregation by supplier to compare claimed vs customer claim amounts:

SELECT supplier_name,
       SUM(claimed_amount)      total_claimed,
       SUM(cust_claim_amount)   total_cust_claimed,
       claim_currency
FROM   apps.dpp_txn_dashboard_v
GROUP  BY supplier_name, claim_currency;

Because CLAIMED_AMOUNT and CUST_CLAIM_AMOUNT are correlated scalar subqueries evaluated per row, performance-sensitive extracts should filter on TRANSACTION_HEADER_ID, ORG_ID, or TRANSACTION_STATUS and consider materializing results for large volumes. The view is read-only and should not be used for transactional writes.