Results for “destination_type_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PO_VAL_DISTRIBUTIONS2 is a validation package body within the Oracle E-Business Suite Purchasing module. Its business function is to perform row-level validations on the distribution records associated with a purchasing document line, such as a purchase order, blanket agreement, or release. When a user enters or modifies a distribution — including the destination organization, destination subinventory, deliver-to location, deliver-to person, charge account, budget account, and encumbrance-related attributes — this package validates that the entered values are internally consistent and conform to the setup defined in Purchasing and Financials system parameters. It is a sibling package to PO_VAL_DISTRIBUTIONS and is invoked from the distribution validation framework coordinated by PO_VALIDATIONS.

The package is instrumented with the PO_LOG diagnostic and error-handling framework. Each validation subprogram declares a module base using po_log.get_package_base and po_log.get_subprogram_base, taking the package base from the constant c_entity_type_distribution defined in PO_VALIDATIONS. This structure allows validation messages and errors to be traced to a specific subprogram during debugging of purchasing document entry.

Key Procedures and Functions

The documented interface consists of seventeen validation subprograms, each named for the distribution attribute it validates:

• AMOUNT_ORDERED and QUANTITY_ORDERED — validate the ordered amount and quantity relative to the line and document tolerances.
• DESTINATION_ORG_ID — validates the destination inventory organization.
• DELIVER_TO_LOCATION_ID — validates the deliver-to location against HZ locations.
• DELIVER_TO_PERSON_ID — validates the deliver-to person.
• DESTINATION_TYPE_CODE — validates the destination type (for example, inventory, expense, or shop floor).
• DESTINATION_SUBINV — validates the destination subinventory against the organization's subinventory setup.
• WIP_ENTITY_ID — validates the work in process entity associated with a shop-floor destination.
• PREVENT_ENCUMBRANCE_FLAG and PARTIAL_FUNDED_FLAG — validate the encumbrance control and partial funding indicators on the distribution.
• CHARGE_ACCOUNT_ID, BUDGET_ACCOUNT_ID, and ACCOUNT_ID — validate the account code combinations used for charging and budgeting.
• PROJECT_ACCT_CONTEXT and PROJECT_INFO — validate project accounting context and project information for project-related distributions.
• TAX_RECOVERY_OVERRIDE_FLAG — validates the tax recovery override indicator.
• ACRN_VALUE_VALID — validates the ACRN (Accounting Classification Reference Number) value used for funding.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• PO_SYSTEM_PARAMETERS and FINANCIALS_SYSTEM_PARAMETERS — retrieve purchasing and financials options that govern validation rules and defaulting.
• GL_CODE_COMBINATIONS — validates charge, budget, and account identifiers.
• HZ_LOCATIONS — validates deliver-to locations.
• MTL_SYSTEM_ITEMS, MTL_SECONDARY_INVENTORIES, and MTL_ITEM_SUB_INVENTORIES — validate item, subinventory, and item-subinventory relationships.
• PO_DISTRIBUTIONS_ALL — the primary distribution records being validated.
• PO_DOC_STYLE_HEADERS — document style information used in validation logic.
• PO_SESSION_GT and PO_VALIDATION_RESULTS_GT — global temporary tables holding session context and accumulating validation results.
• WIP_DISCRETE_JOBS, WIP_ENTITIES, and WIP_REPETITIVE_SCHEDULES — validate work-in-process entity identifiers for shop-floor destinations.
• DBMS_SQL — used for dynamic SQL execution within validation logic.

Usage Notes

PO_VAL_DISTRIBUTIONS2 is not intended to be called directly by end users or custom integrations. It is invoked by the Purchasing validation framework, typically when a user enters or updates distributions in the Purchase Orders form, or when distributions are created programmatically through purchasing APIs that route through PO_VALIDATIONS. The package is referenced by one other package, reflecting its role as a subordinate validator rather than a public API.

Because it operates within the PO_VALIDATIONS entity-type framework, any custom validation behavior should be implemented by extending the standard validation framework rather than by modifying this package. Custom code that requires distribution validation should call the higher-level PO_VALIDATIONS entry points so that the full set of package-level checks, including those in PO_VAL_DISTRIBUTIONS2, is applied consistently.