Search Results destination_subinv




Overview
Explore in AI Chat

Overview

APPS.PO_VAL_DISTRIBUTIONS2 is a validation package within the Oracle E-Business Suite Purchasing module. Its role is to evaluate the distribution lines of a purchasing document — requisitions, purchase orders, and their associated shipments and distributions — against the validation rules configured for the operating unit. Rather than performing a single monolithic check, the package exposes discrete validation procedures that each examine one attribute of a distribution line, such as the ordered amount, the ordered quantity, the destination organization, the destination subinventory, or the accounting context. Each procedure returns its findings through a shared PO_VALIDATION_RESULTS_TYPE record and a result-type indicator, allowing the calling process to accumulate multiple errors before presenting them to the user.

The package is part of the broader PO_VAL distributions validation layer in Release 12.1.1 and 12.2.2, and its procedures are invoked during document entry, document submission, and import/validation flows where the system must confirm that a distribution is internally consistent and legally valid before it is saved or approved.

Key Procedures and Functions

The documented interface contains seventeen procedures, each targeting a specific validation concern:

  • AMOUNT_ORDERED — validates the ordered amount on a distribution against business rules and tolerances.
  • QUANTITY_ORDERED — validates the ordered quantity, taking the order type into account.
  • DESTINATION_ORG_ID — checks that the destination organization is valid relative to the ship-to organization.
  • DELIVER_TO_LOCATION_ID — verifies the deliver-to location identifier.
  • DELIVER_TO_PERSON_ID — verifies the deliver-to person identifier.
  • DESTINATION_TYPE_CODE — validates the destination type (for example inventory, expense, or shop floor) using ship-to organization, item, transaction flow, accrual, and value/purchase basis inputs.
  • DESTINATION_SUBINV — validates the destination subinventory on the distribution; this is the procedure most relevant to searches for destination_subinv. It confirms that the specified subinventory exists and is permissible for the destination organization and item.
  • WIP_ENTITY_ID — validates the work in process entity associated with a shop-floor destination.
  • PREVENT_ENCUMBRANCE_FLAG — validates the prevent-encumbrance indicator.
  • CHARGE_ACCOUNT_ID, BUDGET_ACCOUNT_ID, ACCOUNT_ID — validate the various account identifiers carried on the distribution.
  • PROJECT_ACCT_CONTEXT and PROJECT_INFO — validate project-related accounting context information.
  • TAX_RECOVERY_OVERRIDE_FLAG — validates the tax recovery override indicator.
  • ACRN_VALUE_VALID — validates the ACRN (Accounting Classification Reference Number) value used in government contracting.
  • PARTIAL_FUNDED_FLAG — validates the partial funding indicator.

Tables Accessed

The package references a range of APPS synonyms. PO_DISTRIBUTIONS_ALL supplies the distribution records being validated, while PO_SYSTEM_PARAMETERS and FINANCIALS_SYSTEM_PARAMETERS provide the operating-unit defaults and accounting setup used as validation criteria. MTL_SYSTEM_ITEMS, MTL_SECONDARY_INVENTORIES, and MTL_ITEM_SUB_INVENTORIES are consulted to confirm item and subinventory validity for the destination subinventory and destination type checks. Organization and location data come from HZ_LOCATIONS, and accounting combinations from GL_CODE_COMBINATIONS. Work in process entities are verified through WIP_DISCRETE_JOBS, WIP_ENTITIES, and WIP_REPETITIVE_SCHEDULES. Document style rules are drawn from PO_DOC_STYLE_HEADERS. The package also uses the session and results structures PO_SESSION_GT and PO_VALIDATION_RESULTS_GT, and relies on DBMS_SQL for dynamic SQL.

Usage Notes

PO_VAL_DISTRIBUTIONS2 is an internal validation utility rather than a public application programming interface. It is invoked by the Purchasing forms and by the validation engine that runs when a document is saved, submitted for approval, or imported through the open interface and document validation concurrent programs. Because the procedures communicate through PL/SQL collection types and an IN OUT NOCOPY results record, custom code that calls the package directly must replicate the expected collection structures and interpret the returned result type. As the package is documented as referenced by one other package, extension developers should treat it as a supporting routine of the PO_VAL family and prefer the supported validation APIs where they exist.