Search Results ref_document_number

Overview

DPP_WEBADI_V is a view owned by the APPS schema in Oracle E-Business Suite, associated with the DPP (Oracle Price Protection) product. As its name suggests, it is a WebADI view — a flattened, denormalized query surface designed to feed Oracle's Web Applications Desktop Integrator (WebADI) functionality, which allows business users to download, edit, and upload Price Protection transaction data using desktop spreadsheet tools. Because WebADI depends on a single, wide, human-readable row set, the view joins together the header, line, supplier, organization, and claim data that a spreadsheet user needs in one place rather than forcing the desktop integration layer to reconcile multiple base tables.

The view therefore plays a dual role: it is an integration surface for WebADI upload/download templates, and it also serves as a convenient reporting view for Price Protection transactions. Rather than treating DPP_WEBADI_V as a purely technical object, report developers can query it directly to obtain claim, supplier, and transaction attribute data without reconstructing the underlying join logic themselves.

Underlying Base Objects

Per the documented 12.2.2 metadata, DPP_WEBADI_V is defined over a mixture of synonyms, views, and packages. The principal transactional sources are DPP_TRANSACTION_HEADERS_ALL, DPP_TRANSACTION_LINES_ALL, and DPP_TRANSACTION_CLAIMS_ALL, which supply the header, line, and claim detail respectively. Supplier data originates from AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL, while claim-level information is drawn from OZF_CLAIMS_ALL and its associated lookup definitions in FND_LOOKUPS, which supply values such as the claim type meaning.

Organization and item context come from ORG_ORGANIZATION_DEFINITIONS and MTL_SYSTEM_ITEMS_KFV, the latter being the key-flexfield concatenated item view. Security and session context are handled by the FND_GLOBAL, HR_GENERAL, and HR_SECURITY packages, which typically enforce organization or responsibility-level access filtering. The view text recorded in the ETRM metadata confirms these joins, referencing ORGANIZATION_NAME, VENDOR_NAME, and CLAIM_NUMBER columns sourced from the respective base objects.

Key Columns

The view exposes a broad set of columns organized around three logical groupings:

• Transaction identifiers: REF_DOCUMENT_NUMBER, ORG_ID, EFFECTIVE_START_DATE, and DAYS_COVERED describe the Price Protection transaction itself.
• Claim data: CLAIM_NUMBER, CLAIM_TYPE (derived from the FL.MEANING lookup), and CLAIM_CURRENCY identify the associated claim and its currency.
• Supplier data: SUPPLIER_NAME, SUPPLIER_SITE, SUPPLIER_ID, SUPPLIER_SITE_ID, SUPPLIER_CONTACT_NAME, SUPPLIER_CONTACT_ID, SUPPLIER_CONTACT_EMAIL, and SUPPLIER_CONTACT_PHONE provide the trading partner details.
• Descriptive flexfield attributes: HEADER_ATTRIBUTE_CATEGORY and HEADER_ATTRIBUTE1 through HEADER_ATTRIBUTE30 expose the header DFF context and values. Notably, HEADER_ATTRIBUTE16 through HEADER_ATTRIBUTE30 are aliased from ATTRIBUTE1 through ATTRIBUTE15, indicating the view reuses the first fifteen physical attributes to populate a second logical block of attribute columns.

Common Use Cases and Queries

The most common use of this view is to retrieve Price Protection header data together with supplier and claim context, and to extract descriptive flexfield values such as HEADER_ATTRIBUTE1. A typical query might resemble:

SELECT ref_document_number, organization_name, supplier_name, claim_number, claim_type, header_attribute1 FROM dpp_webadi_v WHERE org_id = :p_org_id;

Because the column aliases HEADER_ATTRIBUTE16–HEADER_ATTRIBUTE30 map back to ATTRIBUTE1–ATTRIBUTE15, developers building reports must be aware that these fields are duplicated rather than distinct, and should not assume twenty-nine unique flexfield values are available from this view. This view is best used for read-oriented reporting and WebADI template population, not as an update target.