Search Results validate_delete_distribution

Overview

PO_DISTRIBUTIONS_SV is a server-side PL/SQL package body in the APPS schema that provides validation and utility services for purchase order distribution records in Oracle E-Business Suite releases 12.1.1 and 12.2.2. The suffix "SV" denotes a "server validation" package, a naming convention used throughout the Purchasing (PO) module for packages that encapsulate reusable business rules invoked by the Purchasing forms, the purchasing public APIs, and internal concurrent processing. The package operates primarily against the PO_DISTRIBUTIONS and PO_DISTRIBUTIONS_ALL tables, supplying the logic required to identify distributions, verify their existence, compute aggregate quantities, and determine whether a distribution may be safely deleted.

The package is classified as OTHER in the ETRM metadata rather than as a formal public API, which indicates that it is intended for internal consumption by Oracle's own application code rather than as a supported extension point. Nevertheless, the ETRM report confirms the package is referenced by five other database objects, demonstrating its role as a shared dependency within the Purchasing and receiving code paths.

Key Procedures and Functions

The ETRM metadata documents thirteen procedures and functions in this package. The documented members include:

• NAMES — Resolves or returns distribution name information, supporting identification of distribution records in downstream processing.
• NAME — The singular counterpart to NAMES; returns name data for an individual distribution record.
• GET_TOTAL_DIST_QTY — Returns the total distributed quantity across a distribution set, used to reconcile ordered versus allocated quantities during validation and submission.
• TEST_VAL_DISTRIBUTION_EXISTS — A Boolean-style existence test that confirms whether a valid distribution record exists for a given context before dependent processing proceeds.
• VALIDATE_DELETE_DISTRIBUTION — Determines whether a distribution may be deleted, typically by checking for downstream references such as invoice matching activity in AP_INVOICE_DISTRIBUTIONS or receiving activity in RCV_TRANSACTIONS.

The package also exposes GET_TOTAL_DIST_QTY and VALIDATE_DELETE_DISTRIBUTION behavior consistent with the PO_DIST_S and PO_COMPLEX_WORK_PVT dependencies listed in the dependency metadata. Parameter signatures are not published in the ETRM excerpt and should be confirmed against the deployed source in the target environment.

Tables Accessed

Through APPS synonyms, the package reads and writes several core tables. PO_DISTRIBUTIONS, PO_DISTRIBUTIONS_ALL, PO_LINES, PO_LINE_LOCATIONS, and PO_LINE_LOCATIONS_ALL supply the distribution, line, and shipment records central to its validation logic. AP_INVOICE_DISTRIBUTIONS is queried to detect invoice-match references that block deletion. RCV_TRANSACTIONS and RCV_TRANSACTIONS_INTERFACE are consulted for receiving activity tied to distributions. PA_PROJECTS_ALL and PA_TASKS provide project and task validation for project-related distributions. HZ_LOCATIONS and HR_LOCATIONS/HR_ORGANIZATION_UNITS resolve ship-to and deliver-to address information. OKC_K_LINES_B and OKE_K_DELIVERABLES_B represent the Oracle Contracts and Service deliverables integration points. Notably, MRP_SEIBAN_NUMBERS is referenced — this is the MRP module table that stores Seiban number (Japanese project/order numbering) definitions, which this package consults when distributions carry Seiban references. DUAL and STANDARD are used for trivial selects and standard PL/SQL constructs.

Usage Notes

PO_DISTRIBUTIONS_SV is invoked indirectly: the Purchasing forms call it during distribution entry and deletion validation, the receiving and invoicing flows call it to confirm distribution existence before recording transactions, and the supporting private packages PO_CORE_S, PO_DIST_S, PO_COMPLEX_WORK_PVT, and PO_MESSAGE_S depend on it through the five documented referencing objects. Because it is classified as OTHER rather than a public API, custom code should not call these procedures directly; extension developers should instead use the supported Purchasing public APIs, which internally invoke this validation layer. The MRP_SEIBAN_NUMBERS dependency means any customization or table change affecting Seiban numbering can influence distribution validation behavior.