Search Results por_autosource_util_pkg




Overview
Explore in AI Chat

Overview

POR_AUTOSOURCE_UTIL_PKG is a utility package body in the APPS schema that supports Oracle EBS sourcing and requisition autosourcing logic. Its central role is to determine whether items can be sourced automatically into purchasing and shipping flows, and to execute the autosource operation that assigns a valid source to a requisition line. The package consolidates several eligibility checks — internal orderability, purchasability, shippability, valid shipping network membership, and item assignment to a source — into reusable PL/SQL that other EBS modules and extensions can call. Because it reads from inventory and sourcing views and tables such as MTL_SYSTEM_ITEMS, MTL_ITEM_SUB_INVENTORIES, MTL_INTERORG_PARAMETERS, and the item sourcing levels view MRP_ITEM_SOURCING_LEVELS_V, it bridges supply chain and procurement data. The package also leverages FND_PROFILE and FND_LOG for profile option access and debug logging, and it may delegate to POR_AUTOSOURCE_CUSTOM_PKG to allow customer-specific autosourcing behavior. Its status is VALID in both 12.1.1 and 12.2.2, and it is an internal EBS utility rather than a public API; no other database object depends on it, so it is primarily invoked by Oracle application code during requisition processing.

Key Procedures and Functions

  • IS_INTERNAL_ORDERABLE — Determines whether an item qualifies for internal ordering, typically by checking internal ordering flags and inventory organization parameters. Used to gate internal sales order or internal requisition eligibility.
  • IS_ITEM_PURCHASABLE — Evaluates whether an item can be purchased, considering item attributes on MTL_SYSTEM_ITEMS such as purchasable and purchasing-enabled settings.
  • IS_ITEM_SHIPPABLE — Checks whether an item can be shipped, based on shippable item attributes and inventory/shipping setup.
  • IS_VALID_SHIPPING_NETWORK — Verifies that a source and destination organization pair is part of a valid shipping network, consulting interorg parameters and related setup.
  • IS_ITEM_ASSIGNED — Determines whether an item is assigned to a given source, subinventory, or sourcing rule, using item subinventory assignments and sourcing level data.
  • AUTOSOURCE — The primary routine that performs the autosourcing action, selecting and validating a source for an item and applying that source to the requisition line. It orchestrates the eligibility checks above and may invoke POR_AUTOSOURCE_CUSTOM_PKG for customized sourcing logic.

Tables Accessed

  • MTL_SYSTEM_ITEMS — Provides item attribute values used by the purchasable, shippable, and internal-orderable checks.
  • MTL_ITEM_SUB_INVENTORIES — Supplies item-to-subinventory assignments relied on by IS_ITEM_ASSIGNED and sourcing checks.
  • MTL_ITEM_LOCATIONS / MTL_ONHAND_SUB_V / MTL_RESERVATIONS — Referenced for subinventory-level supply, on-hand, and reservation context during autosourcing.
  • MTL_INTERORG_PARAMETERS — Used to establish valid shipping network relationships between organizations.
  • MTL_SECONDARY_INVENTORIES — Provides subinventory definitions for sourcing and assignment validation.
  • MRP_ITEM_SOURCING_LEVELS_V — Supplies sourcing rules and sourcing level information to determine eligible sources.
  • PO_ASL_SV, PO_REQ_LINES_SV1, POR_AUTOSOURCE_CUSTOM_PKG — Referenced for approved supplier list integration, requisition line manipulation, and customer-specific autosourcing extensions.

Usage Notes

POR_AUTOSOURCE_UTIL_PKG is not referenced by any other database object, indicating it is consumed internally by Oracle application code rather than exposed as a documented public API. It is typically invoked during requisition creation and processing, where purchasing forms and the autosource workflow must decide whether an item can be sourced and which source to assign. The presence of FND_PROFILE and FND_LOG dependencies indicates that behavior can be controlled by profile options and that the package supports debug-level logging for troubleshooting. The dependency on POR_AUTOSOURCE_CUSTOM_PKG signals that customers can extend or override autosourcing decisions through the supported custom package, preserving modifications across upgrades. Because the procedures are function-style eligibility checks, custom code may call them to validate items before submitting requisitions or internal orders. Care should be taken not to modify the package body directly; extensions should be placed in the custom package. This guidance applies equally to Release 12.1.1 and 12.2.2.