Search Results dpp_cust_hdr_rec_type

Overview

DPP_CUSTOMERCLAIMS_PVT is a private PL/SQL package in the APPS schema within Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the pricing and channel revenue management functional area, specifically supporting customer claims processing. Customer claims typically represent requests from trading partners or customers for credits related to pricing discrepancies, promotional accruals, or inventory adjustments. The package is designated with a PVT classification, meaning it is an internal implementation package not intended for direct invocation by external code or end users. It is referenced by two other packages, which act as the public-facing entry points that delegate processing logic to this private unit. The header declaration uses AUTHID CURRENT_USER, indicating the package executes with the privileges of the calling user rather than the definer, which is consistent with Oracle Application Object Library security conventions.

Key Procedures and Functions

• SELECT_CUSTOMERPRICE — This procedure selects customer and price information required for processing customer claims. Based on the package's declared record types, it operates against a customer header record containing transaction identifiers, effective dates, organizational context, execution detail references, output XML, provider process identifiers, and currency codes. It accepts and returns a customer table collection of records, each carrying transaction line identifiers, inventory item identifiers, unit of measure codes, and a nested customer price table. The procedure follows the Oracle EBS API standard signature pattern, including API version, initialization message list flag, commit flag, and validation level as input parameters, and standard return status, message count, and message data as outputs. The nested price table resolves account-level last price and invoice currency for each customer.
• POPULATE_CUSTOMERPRICE — This procedure populates the customer price structures used during claim processing. It complements SELECT_CUSTOMERPRICE by assembling the record collections defined at package level, including the global record and table types G_MISS_DPP_CUSTOMER_REC and G_MISS_DPP_CUSTOMER_TBL. Together these procedures isolate the data retrieval and assembly logic needed to match customer claims against pricing and transaction data without exposing that logic to calling modules.

Tables Accessed

The package reads and writes across several documented APPS synonyms. DPP_CUSTOMER_CLAIMS_ALL is the primary claims table, storing claim header information. DPP_EXECUTION_DETAILS and DPP_TRANSACTION_LINES_ALL support execution tracking and claim line detail. The sequence DPP_CUST_INV_LINE_ID_SEQ generates line identifiers. Order data is sourced from OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL, while receivable and invoice data comes from RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES_ALL, and RA_CUST_TRX_TYPES_ALL. Customer account information is resolved through HZ_CUST_ACCOUNTS. XML output and provider process identifiers suggest integration with Oracle XML Gateway or provider processing frameworks, using XMLTYPE. DUAL and PLITBLM are used for PL/SQL utility operations.

Usage Notes

Because this is a private package, it is not called directly from Oracle Forms, concurrent program definitions, or external integrations. Instead, it is invoked by the two higher-level packages that reference it, which orchestrate customer claim processing and expose the appropriate public APIs. Developers extending customer claims functionality should not modify or call this package directly; doing so risks conflicts during patching and upgrades. In the context of a search for "vitori health claims address," this package does not store or manage provider or customer addresses directly. Address data would reside in the HZ_CUST_ACCOUNTS and related TCA (Trading Community Architecture) tables, which this package only reads to associate claims with the correct customer account. Any address-related customization for customer claims should target the TCA layer rather than this pricing package.