Search Results oe_schedule_grp




Overview
Explore in AI Chat

Overview

OE_SCHEDULE_GRP is a PL/SQL package owned by the APPS schema within the Oracle E-Business Suite Order Management (OM) module. The suffix _GRP designates it as a group-type package, a naming convention used in EBS to identify packages whose primary role is to expose a small number of high-level public entry points that coordinate multiple lower-level program units. OE_SCHEDULE_GRP is responsible for the scheduling of order lines — that is, the process by which Order Management determines availability, reserves supply, and records scheduling outcomes against sales order lines. It functions as the scheduling logic hub invoked during order booking, order import processing, and release of order lines to downstream execution systems.

Key Procedures and Functions

The ETRM metadata documents one public program unit in this package:

  • UPDATE_SCHEDULING_RESULTS — Writes the outcome of a scheduling attempt back to the order line records. After the scheduling engine evaluates availability against on-hand, supply, and demand information, this procedure persists the returned scheduling status, quantities, dates, and related attributes so that the order line reflects its post-scheduling state. It is the primary public interface through which the scheduling subprocess communicates results into the Order Management transaction tables. No parameter list is published in the ETRM metadata; callers should rely on the documented behavior rather than assumptions about signature.

Because the package is classified as a GRP package, the internal package body contains the bulk of the procedural logic (scheduling calculation, item validation, line iteration), while the specification exposes only the entry points required by external callers.

Tables Accessed

Based on documented APPS synonym references, OE_SCHEDULE_GRP reads from and writes to the following tables:

  • OE_ORDER_LINES_ALL — The central sales order line table. Scheduling results, including quantities, schedule dates, and status flags, are updated here. This is the primary target of UPDATE_SCHEDULING_RESULTS.
  • MTL_SYSTEM_ITEMS — The item master. The package references it to retrieve item-level scheduling attributes such as item type, planning flags, and ATP eligibility that determine how a line is scheduled.
  • PLITBLM — The PL/SQL integer table type (index-by table of BINARY_INTEGER) used as a shared collection structure. It supports bulk processing and array-based parameter passing within the package and to dependent program units.

Usage Notes

OE_SCHEDULE_GRP is not typically called directly by end users. Its documented dependency graph shows that it is referenced by six other packages, including MRP_CREATE_SCHEDULE_ISO, MRP_RELEASE_SO, MSC_BAL_UTILS, OE_LINE_UTIL, OE_PROCESS_REQUISITION_PVT, and OE_SCHEDULE_UTIL. This indicates that scheduling activity originating in Planning, Order Management line processing, and requisition import flows all funnel through this package.

Typical invocation points include the Order Management order booking concurrent program, the Order Import concurrent program, and any scheduling or availability workflow triggered when a line is created or modified. Customizations that need to update scheduling results outside the standard flow — for example, third-party scheduling engines — may call UPDATE_SCHEDULING_RESULTS, but must respect the same validation and data-consistency rules applied by the standard EBS modules. Because the package resides in APPS and is status VALID in both 12.1.1 and 12.2.2, it remains a supported dependency for extensions, though direct modification or overriding of the package body is not recommended. All access should occur through the documented public entry point, and records in OE_ORDER_LINES_ALL must be locked and committed consistently with the surrounding Order Management transaction to avoid inconsistent scheduling states.