Search Results call_process_order_for_ireq




Overview
Explore in AI Chat

Overview

OE_INTERNAL_REQUISITION_PVT is an internal Oracle E-Business Suite PL/SQL package owned by the APPS schema, classified as a private (PVT) API, and validated across EBS 12.1.1 and 12.2.2. It supports the Internal Requisition (IR) flow within Oracle Order Management, where a sales order line is converted into an internal requisition that drives an internal sales order (ISO) shipment from another organization. The package provides the business logic that governs whether an internal requisition-linked order line may be updated, cancelled, or held, and it orchestrates the processing that links Order Management order entities to their corresponding Purchasing requisition records. Because the package is private, it is not a published integration API; it is consumed by internal Order Management utilities and by Purchasing-side workflow components that must reason about internal requisition state.

Key Procedures and Functions

The ETRM 12.2.2 metadata documents nine procedures and functions:

  • GET_ELIGIBLE_ISO_SHIPMENT — Determines and returns eligible internal sales order shipment information associated with an internal requisition, used to identify valid shipping candidates for the requisition's demand.
  • UPDATE_ALLOWED — Returns whether the internal requisition or its associated order entity may be updated, enforcing business rules that protect requisitions already progressed in the fulfillment or purchasing cycle.
  • CANCEL_ALLOWED — Evaluates whether cancellation is permitted at the line level for an internal requisition-backed entity.
  • CANCEL_HEADER_ALLOWED — Evaluates whether cancellation is permitted at the header level, applying header-wide restrictions distinct from line-level checks.
  • PROCESS_LINE_ENTITY — Performs the core processing of a line entity tied to an internal requisition, synchronizing order line data with requisition data.
  • APPLY_HOLD_FOR_IREQ — Applies a hold to the order entity in the context of an internal requisition, using Order Management hold infrastructure.
  • RELEASE_HOLD_FOR_IREQ — Releases a previously applied internal requisition hold, permitting the entity to resume normal processing.
  • IS_IREQ_CHANGABLE — Determines whether the internal requisition is in a state that allows change, gating downstream update and processing logic.
  • CALL_PROCESS_ORDER_FOR_IREQ — Invokes order processing logic for the internal requisition, bridging requisition activity back into Order Management order processing.

Tables Accessed

The package operates across Order Management, Purchasing, and Shipping data:

  • OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL — the primary order header and line tables read and updated to reflect internal requisition state, holds, and cancellations.
  • PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL — Purchasing requisition records that represent the internal requisition generated from the order, used to validate change, update, and cancellation eligibility.
  • OE_HOLD_SOURCES_ALL and OE_ORDER_HOLDS_ALL — hold definition and hold application tables used by APPLY_HOLD_FOR_IREQ and RELEASE_HOLD_FOR_IREQ.
  • WSH_DELIVERY_DETAILS — shipping delivery detail data consulted to determine eligible ISO shipment and fulfillment status.
  • PLITBLM — a PL/SQL index-by table type used internally for bulk/array processing within the package.

Usage Notes

OE_INTERNAL_REQUISITION_PVT is referenced by six other packages, including OE_CONFIG_SCHEDULE_PVT, OE_HEADER_UTIL, OE_LINE_UTIL, OE_SCHEDULE_UTIL, PO_RCO_VALIDATION_PVT, and PO_REQCHANGEREQUESTWF_PVT, and it references OE_ORDER_PUB. This dependency profile indicates invocation from Order Management forms and utilities (order entry, scheduling, and line/header maintenance) as well as from Purchasing requisition change-request workflow validation. It is typically called indirectly—triggered when users modify, cancel, or hold an order line tied to an internal requisition, or when Purchasing-side workflow validates a change request. Because it is a private package, customizations should avoid direct calls; developers requiring similar behavior should use supported public APIs such as OE_ORDER_PUB or documented Purchasing requisition APIs, and must re-validate any assumptions after applying EBS patches, since private signatures may change between releases.