Search Results schedule_line

Overview

OE_OEOL_SCH is a PL/SQL package in the Oracle E-Business Suite Order Management (OM) module, owned by the APPS schema and declared with AUTHID CURRENT_USER. Its source header (OEXWSCHS.pls, version 120.0.12000000.1, dated 2007/01/16) identifies it as an Order Entry/Order Line scheduling utility package. In the 12.1.1 and 12.2.2 code lines, this package encapsulates the server-side logic invoked by Oracle Workflow processes that schedule order lines, firm demand, branch workflow execution based on source type, and release eligible lines to Purchasing.

The package is classified as OTHER in the ETRM repository, meaning it is not a formally published open API. It is an internal Workflow callback package whose procedures are called by activity function definitions in the Order Management workflow definitions, rather than being called directly by external applications or forms. The "SCH" suffix in the name reflects its focus on scheduling activities within the order line lifecycle.

Key Procedures and Functions

The documented procedures follow the standard Oracle Workflow PL/SQL callback signature (itemtype, itemkey, actid, funcmode, resultout), which allows each procedure to be registered as a workflow activity and return a named result that drives the subsequent branch in the process. ETRM documents one primary procedure, SCHEDULE_LINE, though the source excerpt also lists additional internal routines.

• Schedule_Line — the core scheduling routine. It evaluates an order line in the context of an Order Management workflow item and performs or validates the scheduling action for that line.
• Branch_on_source_type — implements conditional branching based on the originating source type of the order line, allowing the workflow to route lines differently depending on whether they originate from an internal order, an external source, or another channel.
• Release_to_purchasing — determines or performs the hand-off of a scheduled line to the purchasing flow, typically for drop-ship or back-to-back procurement scenarios.
• Is_Line_Scheduled — a predicate routine that returns a workflow result indicating whether the line has already been scheduled, preventing redundant scheduling activity.
• Is_Line_Firmed — a predicate routine that reports whether demand on the line has been firmed, used to gate downstream activities.
• Firm_demand — performs the demand-firming action for the line, marking it as firmed in the supply/demand chain.

Tables Accessed

The package reads and writes a range of Order Management tables through APPS synonyms. OE_ORDER_LINES and OE_ORDER_LINES_ALL are the central transactional tables holding the order line attributes being scheduled or firmed. OE_SCHEDULE_LINES_TEMP is a scheduling interface/temporary table used during the scheduling computation. MTL_SYSTEM_ITEMS and MTL_PARAMETERS provide item and inventory organization context needed for scheduling decisions.

Party and customer data are accessed through HZ_PARTY_SITES, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES_ALL, and HZ_LOCATIONS, reflecting ship-to and site validation during scheduling. FND_USER supplies the acting user context, and PLITBLM is an Oracle-supplied PL/SQL integer-table utility for array handling. Workflow status is read from WF_ITEM_ACTIVITY_STATUSES and WF_PROCESS_ACTIVITIES to determine activity state and result routing.

Usage Notes

OE_OEOL_SCH is invoked by the Oracle Workflow engine when Order Management order line workflows execute their scheduling-related activities. It is not intended for direct invocation by forms or custom concurrent programs. Developers extending OM workflows may reference these procedures as activity function definitions, but direct calls require careful handling of the workflow item context (itemtype, itemkey, actid) and the resultout parameter. Because the package is classified OTHER rather than as a public API, Oracle does not guarantee signature stability across patches; customizations should avoid calling these procedures directly and instead rely on supported scheduling APIs such as OE_ORDER_PUB or the scheduling concurrent programs. In 12.2.2 the package resides in the same APPS-based architecture as 12.1.1, with no online patching changes to its callable interface.