Search Results dpp_mig_adj_para_approval_pvt




Overview

DPP_MIG_ADJ_PARA_APPROVAL_PVT is a private (PVT) PL/SQL package in the APPS schema that supports Oracle E-Business Suite's supplier settlement and approval framework. Its documented purpose is to contain migration-related code for the adjustment flow and for parallel approval processing. The source header, dated June 2009 and authored by anbbalas, identifies the package as part of the DPP module (the supplier settlement/approval stack), and the AUTHID CURRENT_USER declaration indicates the package executes with the privileges of the calling user rather than the defining user.

The package is classified as PVT, meaning it is a private implementation component rather than a public, customer-callable API. It is not referenced by any other documented package, confirming that it sits at the boundary of a migration or upgrade process rather than in the mainstream runtime call path.

Key Procedures and Functions

The package exposes a single documented procedure:

  • update_transaction_status — The sole documented procedure in the package. Its name indicates that it refreshes or synchronizes the status of transactions involved in the adjustment and parallel approval migration. It returns the standard concurrent-program style OUT parameters errbuf and retcode, which signals that it is designed to be executed as a concurrent program entry point rather than called inline from another PL/SQL routine.

No other procedures or functions are documented in the ETRM metadata. The procedure is not exposed as a public API; consumers invoke it through the concurrent manager or an internal migration driver.

Tables Accessed

The package reads and writes the following tables through APPS synonyms, consistent with its migration and approval role:

  • DPP_TRANSACTION_HEADERS_ALL — The primary transaction repository. The status update procedure almost certainly writes back approval or migration status values here.
  • DPP_EXECUTION_PROCESSES and DPP_APPROVAL_ACCESS — Support the parallel approval engine, defining process definitions and approval access rules used to determine how transactions migrate through the approval flow.
  • AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL — Supplier and supplier site master data required to resolve the trading partners involved in each adjustment.
  • OZF_PROCESS_SETUP_ALL and OZF_SUPP_TRD_PRFLS_ALL — Oracle trade management process setup and supplier trading profiles, which drive the adjustment and approval configuration.
  • PLITBLM — The standard Oracle PL/SQL index-by table used for bulk processing and array binds, indicating set-based processing during the migration.

Usage Notes

Because the package is classified PVT and carries migration-specific logic, it is typically invoked in two contexts. First, during an upgrade or data migration from a prior release, an internal migration driver or concurrent program calls update_transaction_status to reconcile the pre-existing adjustment and parallel approval data with the new DPP data model. Second, it may be registered as a concurrent program entry point, since the errbuf/retcode signature is the standard contract for concurrent executable PL/SQL.

Custom code should not call this package directly. It is a private implementation artifact whose interface may change between releases without notice, and no other documented package depends on it. Teams that need to trigger the status refresh should locate and submit the corresponding concurrent program rather than invoking the procedure from bespoke PL/SQL. When debugging adjustment or parallel approval migrations, the DPP_TRANSACTION_HEADERS_ALL rows updated by this procedure provide the most direct trace of its activity.