Search Results mrp_timing

Overview

APPS.ORDER_SCH_WB is a valid PL/SQL package body in the Oracle E-Business Suite APPS schema that supports the Order Scheduling workbench functionality used by Advanced Supply Chain Planning (ASCP) and available-to-promise (ATP) processing. It acts as an integration and orchestration layer between the scheduling workbench user interface and the underlying planning engine packages. The package collects supply, demand, sourcing, and ATP data from planning and order management sources, formats it for scheduling calculations, and returns results to the calling workbench. It is classified as an OTHER-type API, meaning it is not published as a formal public interface, but is a functional internal package supporting the scheduling workbench and related diagnostic and utility routines. Its dependency on MSC_SCH_WB confirms that it works closely with planning workbench logic, while its dependency on FND_PROFILE shows it relies on profile option settings to control behavior. The package body is VALID in the APPS schema and is referenced by approximately twelve other database objects, indicating it is used broadly across order scheduling functionality.

Key Procedures and Functions

The package exposes sixteen documented procedures and functions. Their purpose is described below; parameter lists are not documented and are therefore not stated.

• GET_SUPPLY_SOURCES_LOCAL — Returns supply source information relevant to local scheduling decisions.
• GET_ATP_RESULT — Retrieves the outcome of an available-to-promise calculation for the scheduling context.
• GET_ATP_RULE_NAME — Resolves and returns the ATP rule name applicable to the current scheduling request.
• GET_ASSIGNMENT_SET — Returns the assignment set used to determine sourcing and planning assignments.
• MRP_TIMING — Provides MRP timing or scheduling horizon information used in planning calculations.
• ATP_DEBUG — Supports diagnostic output for ATP processing.
• GET_PERIOD_ATP_STRINGS — Returns period-based ATP result strings used in workbench display and calculation.
• CALC_EXCEPTIONS — Calculates exceptions raised during scheduling or ATP evaluation.
• PIPE_UTILITY — A utility routine, typically used for pipelined or delimiter-based data handling.
• SET_SESSION_ID — Establishes the session identifier for the current scheduling workbench run.
• GET_MASTER_ORG — Returns the master organization identifier relevant to the scheduling request.
• DELETE_LINES — Removes workbench or scheduling lines from the working data set.
• GET_SUPPLY_DEMAND_SOURCE_NAME — Returns the descriptive name of a supply or demand source.
• EXTEND_OTHER_COLS — Extends or populates additional columns in the result set.
• COMMIT_DB — Commits pending database changes made by the workbench process.
• GET_PROFILE — Retrieves a profile option value used to drive package behavior.

Tables Accessed

ETRM metadata for this object does not enumerate specific base or synonym tables. The documented dependencies show direct references to FND_PROFILE, MSC_SCH_WB, ORDER_SCH_WB, and STANDARD. FND_PROFILE is read to obtain profile option values controlling scheduling behavior. MSC_SCH_WB represents the planning scheduling workbench package with which this body cooperates, and ORDER_SCH_WB is the corresponding specification. Because the package handles supply, demand, sourcing, ATP, and exceptions, it operates against planning and order management data sources accessed through these packages rather than directly documented table names.

Usage Notes

ORDER_SCH_WB is typically invoked from the Order Scheduling workbench and related scheduling flows, either from forms or concurrent processing, and it may be called by custom code that reuses its utility routines. Because it is classified as OTHER and is not referenced by external published interfaces, it should be treated as an internal implementation package. Customizations should avoid modifying it directly; instead, callers should rely on documented public APIs. Oracle EBS 12.1.1 and 12.2.2 share this object with the same owner, status, and dependencies, so behavior is consistent across both releases.