Search Results g_sup_cap_cum_date

Overview

MSC_ATP_PVT is a private PL/SQL package body in the APPS schema that implements the core Available-to-Promise (ATP) scheduling engine for Oracle Advanced Supply Chain Planning. Its principal business function is to accept a set of demand lines, evaluate them against ATP rules, sourcing profiles, calendars, supplier capacity, and pegging relationships, and return feasible schedule dates. The package is the workhorse behind the ATP checking performed during order promising and order scheduling in Oracle EBS 12.1.1 and 12.2.2.

The header comment identifies the package as the implementation of the main scheduling procedure, historically named Call_Schedule and later renamed Schedule. The body maintains several package-level globals that are deliberately scoped internally so that public entry points such as Call_Schedule and Call_Schedule_Remote can influence behavior without modifying the public specification. Examples include G_ATP_WORKFLOW, which carries the MSC_ALLOCATED_ATP_WORKFLOW profile value, G_LINE_OVERRIDE_FLAG, which is reset to null after the first level of a multilevel model, G_TIME_PHASED_SET for summary enhancement, and G_SUP_CAP_CUM_DATE, used for Supplier Capacity and Lead Time processing during recursive ATP_Check calls on buy items.

Key Procedures and Functions

The ETRM metadata documents seven entry points in this package body:

• SCHEDULE — The renamed main procedure invoked for scheduling. It is the primary driver that processes an input ATP table and produces scheduled dates for each line.
• ATP_CHECK — Performs the ATP availability check for a demand line. It is called recursively, notably for buy items where supplier capacity and lead time logic applies.
• CALL_SCHEDULE — The classic public entry point for scheduling. Its specification is intentionally left unchanged, so profile values such as MSC_ALLOCATED_ATP_WORKFLOW are passed to it indirectly through the internal global G_ATP_WORKFLOW.
• CALL_SCHEDULE_REMOTE — The remote counterpart to Call_Schedule, allowing scheduling requests to be forwarded to another instance in a distributed deployment. It shares the same internal mechanism for conveying the ATP workflow profile.
• PROCESS_TIME_STAMP_ERRORS — Consolidates and reports timestamp-related errors arising during scheduling processing.
• GET_SEQ_NUM — Retrieves a sequence number associated with a scheduling operation; used together with Get_Date_From_Seqnum to correlate schedule records.
• GET_DATE_FROM_SEQNUM — Converts a sequence number back into the corresponding date, supporting the time-phased and multilevel scheduling logic.

Tables Accessed

The package reads and writes through APPS synonyms. The temporary working tables MRP_ATP_DETAILS_TEMP, MRP_ATP_SCHEDULE_TEMP, and MRP_ATP_SCHEDULE_TEMP_S hold input detail lines and the schedule results produced during processing. MSC_ALLOC_DEMANDS, MSC_DEMANDS, and MSC_ATP_PEGGING supply demand and pegging information for allocation and ATP consumption. MSC_ATP_RULES and MSC_ATP_SRC_PROFILE_TEMP provide the ATP rules and sourcing profile definitions that govern how supply is selected. MSC_CALENDAR_DATES is used for working-day and lead-time calculations, while MSC_ITEM_SUPPLIERS, MSC_DESIGNATORS, and MSC_ASSIGNMENT_SETS support sourcing, supplier capacity, and assignment set resolution. MSC_APPS_INSTANCES and MSC_APPS_INSTANCE_NODES are referenced for distributed and remote scheduling. MSC_ATP_SUMMARY_SD and MSC_ATP_SRC_PROFILE_TEMP support the summary and time-phased enhancements noted in the source comments.

Usage Notes

MSC_ATP_PVT is a private (PVT) package and is not intended for direct invocation by end users or customer code. It is referenced by 22 other packages, which call Schedule, Call_Schedule, or Call_Schedule_Remote on its behalf. Typical invocation paths are Oracle Order Management order scheduling and ATP checking, the planning and scheduling concurrent programs, and inter-instance scheduling in distributed configurations. Because the package relies on package-level global state, calls are expected to be made within a single session and completed before the next scheduling request; the globals are reset internally as processing proceeds. The debug flag is controlled by the MSC_ATP_DEBUG profile option, and the ATP workflow behavior is influenced by MSC_ALLOCATED_ATP_WORKFLOW.