Search Results dpp_debug_log_id_seq

Overview

DPP_UTILITY_PVT is a private PL/SQL package body in the APPS schema that supplies shared utility services to the Oracle EBS Trade Management (formerly DPP) product family. Its principal role is to centralize common lookup and validation logic used across the DPP transaction processing stack, including vendor, customer, item, warehouse, and inventory retrieval routines. The package also encapsulates debug logging through the DPP_DEBUG_LOG_ID_SEQ sequence and the DPP_LOG_MESSAGES table, allowing other DPP packages to write diagnostic messages without embedding sequence or logging logic directly. Because the package body is classified as a private (PVT) API, its procedures are not intended for direct external invocation; they are consumed by sibling DPP packages and by the OZF (Trade Management) and PO (Procurement) modules that share trade management data. The package is VALID and depends on 28 documented procedures or functions. It is referenced by 19 other database objects, confirming its role as a foundational dependency rather than an entry-point API.

Key Procedures and Functions

The package exposes a set of search, get, and utility routines grouped by data domain:

• SEARCH_VENDORS, SEARCH_VENDOR_SITES, SEARCH_VENDOR_CONTACTS — Return sets of supplier records, supplier site records, and supplier contact records, typically for use in LOV-style lookups within DPP and OZF processing.
• SEARCH_ITEMS, SEARCH_CUSTOMER_ITEMS, SEARCH_CUSTOMER_ITEMS_ALL — Return inventory item information, including customer-specific item views and an "_ALL" variant that bypasses operating unit restrictions.
• SEARCH_WAREHOUSES — Returns warehouse and organization information from the inventory organization setup.
• SEARCH_CUSTOMERS, SEARCH_CUSTOMERS_ALL — Return customer account records from the trading community model, with the "_ALL" variant again spanning operating units.
• GET_COVEREDINVENTORY, GET_INVENTORYDETAILS, GET_CUSTOMERINVENTORY — Retrieve inventory quantities and detail rows, including customer-owned inventory, for claims and transaction validation.
• GET_LASTPRICE, GET_LISTPRICE — Return the last transaction price and the list price for an item, supporting claim valuation.
• GET_VENDOR, GET_VENDOR_SITE, GET_VENDOR_CONTACT — Return a single supplier, site, or contact record by identifier.
• GET_WAREHOUSE, GET_CUSTOMER, GET_PRODUCT — Return a single warehouse, customer, or product record by identifier.

All 28 documented procedures follow a search-then-get pattern: SEARCH_* returns collections, GET_* returns single records. Parameter lists are not reproduced here.

Tables Accessed

The package reads from and writes to several DPP and shared EBS tables, resolved through APPS synonyms. Supplier data is drawn from AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL, and PO_VENDOR_CONTACTS. Customer data is drawn from HZ_CUST_ACCOUNTS, HZ_PARTIES, and RA_CUSTOMER_TRX_ALL/RA_CUSTOMER_TRX_LINES_ALL. Inventory information is sourced from MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_KFV, MTL_ONHAND_QUANTITIES_DETAIL, MTL_PARAMETERS, and ORG_ORGANIZATION_DEFINITIONS. DPP-specific tables include DPP_INVENTORY_DETAILS_ALL, DPP_INVENTORY_DETAILS_ADJ_ALL, DPP_TRANSACTION_CLAIMS_ALL, DPP_TRANSACTION_HEADERS_ALL, DPP_TRANSACTION_LINES_ALL, DPP_LOG_MESSAGES, DPP_CUSTOMER_CLAIMS_ALL, and DPP_EXECUTION_PROCESSES. Sequences referenced are DPP_DEBUG_LOG_ID_SEQ, DPP_INVENTORY_DETAILS_SEQ, and DPP_INV_DETAILS_ADJ_ID_SEQ. The DPP_DEBUG_LOG_ID_SEQ sequence supplies primary keys for debug log entries written to DPP_LOG_MESSAGES. Financial context comes from FINANCIALS_SYSTEM_PARAMETERS, FINANCIALS_SYSTEM_PARAMS_ALL, GL_SETS_OF_BOOKS, and HR_OPERATING_UNITS.

Usage Notes

DPP_UTILITY_PVT is not a user-facing API and is not invoked directly from Oracle Forms or concurrent program definitions. It is called programmatically by the 19 dependent packages that comprise the DPP and OZF trade management stack, most notably OZF_UTILITY_PVT, PO_MOAC_UTILS_PVT, and the DPP transaction processing packages. Developers writing custom extensions or debugging DPP processing should call the package only through its documented SEARCH_* and GET_* routines, and only after confirming that the calling package does not already provide an equivalent wrapper. Debug logging should be performed through the package's logging routines rather than by inserting directly into DPP_LOG_MESSAGES, so that DPP_DEBUG_LOG_ID_SEQ is used consistently. Because the package accesses both operating-unit-restricted and cross-operating-unit tables, callers that require MOAC behavior should use the "_ALL" search variants and ensure that MO_GLOBAL is initialized before invocation.