Search Results check_transaction_flow

Overview

PO_SHARED_PROC_PVT is a private (PVT) PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It consolidates shared validation and lookup logic used throughout the Oracle Purchasing module, providing a single repository of reusable routines that support procurement transactions across organizations, operating units, and inventory structures. The package is classified as a private API, meaning its procedures are intended for internal consumption by other Purchasing and Supply Chain packages rather than as an externally supported integration interface.

The core business purpose of PO_SHARED_PROC_PVT is to centralize checks that would otherwise be duplicated across Order Management, Requisitions, and Purchasing forms. These checks include cross–operating unit purchasing validation, ship-to organization validation, inventory item validity, and multi-organization (transaction flow) support. By consolidating this logic, the package enforces consistent configuration and security rules across the entire procure-to-pay flow while respecting the Multi-Org Access Control (MOAC) model introduced in Release 12.

Key Procedures and Functions

The documented package exposes 15 procedures and functions. Their purposes are summarized below.

• CHECK_TRANSACTION_FLOW — Verifies whether a given transaction flow is valid for the entities involved in a purchasing document.
• GET_COA_FROM_INV_ORG — Derives the Chart of Accounts associated with a specified inventory organization.
• GET_OU_AND_COA_FROM_INV_ORG — Returns both the operating unit and Chart of Accounts for a given inventory organization.
• IS_SPS_DISTRIBUTION — Determines whether a distribution is sourced through Supplier Scheduling (SPS) processing.
• IS_PA_PROJECT_REFERENCED — Checks whether a Project Accounting project is referenced on a transaction.
• VALIDATE_CROSS_OU_PURCHASING — Validates cross–operating unit purchasing setups and constraints.
• VALIDATE_CROSS_OU_TBL — Supports cross-OU validation at the table/record level.
• CHECK_ITEM_IN_INVENTORY_ORG — Confirms an item exists and is valid within a specific inventory organization.
• VALIDATE_SHIP_TO_ORG — Validates the ship-to organization on a purchasing document.
• IS_TXN_FLOW_SUPPORTED — Determines whether transaction flow functionality is enabled/supported.
• GET_INV_QUALIFIER_CODE — Retrieves the inventory qualifier code used in transaction flow processing.
• DO_ITEM_VALIDITY_CHECKS — Performs a bundle of item validity checks prior to processing.
• GET_LOGICAL_INV_ORG_ID — Returns the logical inventory organization identifier.
• GET_PO_SETUP_PARAMETERS — Fetches Purchasing system setup parameters.
• CHECK_ITEM_IN_LINV_POU — Validates an item within a logical inventory organization / POU context.

Tables Accessed

The package reads configuration and transactional data through APPS synonyms, including:

• FINANCIALS_SYSTEM_PARAMETERS / _ALL — Financials setup, Chart of Accounts and ledger context.
• PO_SYSTEM_PARAMETERS_ALL — Purchasing module setup parameters.
• HR_ALL_ORGANIZATION_UNITS and HR_ORGANIZATION_INFORMATION — Organization and operating unit classification.
• MTL_PARAMETERS, MTL_SYSTEM_ITEMS_B, MTL_ITEM_REVISIONS_B — Inventory organization and item master data.
• MTL_TRANSACTION_FLOW_HEADERS / _LINES — Transaction flow definitions for multi-org support.
• PO_HEADERS_ALL, PO_REQUISITION_LINES_ALL, PO_REQ_DISTRIBUTIONS_ALL — Purchasing document data.
• HZ_LOCATIONS — Address/location data for ship-to validation.
• FND_NEW_MESSAGES — Message lookups for error reporting.

Usage Notes

PO_SHARED_PROC_PVT is invoked internally by Oracle Purchasing forms, workflow activities, and concurrent programs that require consistent validation of items, ship-to organizations, and cross-OU purchasing rules. It is referenced by 12 other packages and does not itself reference any database object beyond the documented dependencies. Because it is a PVT (private) API, Oracle does not guarantee its signature for external consumption; customizations should call supported public APIs (such as PO_CORE_S or PO_GA_PVT) rather than invoking these procedures directly. Developers tracing validation behavior should treat this package as the authoritative source for shared Purchasing validation logic.