Search Results msc_atp_24x7




Overview
Explore in AI Chat

Overview

MSC_ATP_24X7 is a PL/SQL package in the APPS schema that supports around-the-clock available-to-promise (ATP) processing within the Oracle Advanced Supply Chain Planning (ASCP) and global order promising (GOP) architecture in Oracle E-Business Suite. In release 12.1.1 and 12.2.2 the package functions as a scheduling and synchronization utility layer that maintains the temporary ATP schedule that the planning engine uses to promise sales order demand against supply in real time. By combining profile-driven configuration, concurrent request logging, and direct access to the MSC ATP staging tables, MSC_ATP_24X7 enables continuous order promising outside the normal planning batch windows, which is essential for high-volume order capture environments where quotations and booking must reflect current supply conditions at all hours.

Key Procedures and Functions

The ETRM metadata documents four callable units:

  • CALL_SYNCHRONIZE — the primary entry point of the package. It synchronizes the 24x7 ATP schedule state, coordinating between the ATP temporary schedule data and the demand and plan records used by the planning engine. It is the routine invoked to refresh promising data so that order promising reflects current plan output.
  • CONC_LOG — writes informational messages to the concurrent program log. It provides standard logging behavior for calls initiated from concurrent managers, allowing administrators to trace execution.
  • CONC_DEBUG — emits diagnostic or debugging output, typically gated by a profile option or debug flag. It supports troubleshooting of ATP synchronization runs.
  • PARSE_SALES_ORDER_NUMBER — parses the sales order number into its component parts (for example order number, source, and organization context) so that MSC_SALES_ORDERS records can be matched and validated during synchronization.

Tables Accessed

The package reads and writes a range of ASCP and application foundation tables through APPS synonyms:

Usage Notes

MSC_ATP_24X7 is invoked indirectly rather than being called from a standard form. It is referenced by MSC_ATP_24X7 (self-reference from package-level calls), MSC_ATP_PROC, MSC_POST_PRO, and MSC_SATP_FUNC, confirming that it sits beneath the higher-level ATP processing and post-planning routines in the ASCP stack. In practice it is executed as part of concurrent program execution or scheduled planning activity, and it relies on FND_PROFILE values to determine whether 24x7 promising is enabled and at what debug level. Because it takes a DBMS_LOCK dependency, concurrent invocations are serialized to protect the temporary schedule; administrators should therefore avoid forcing parallel executions. Custom code should call the higher-level MSC_ATP_PROC or MSC_SATP_FUNC entry points rather than MSC_ATP_24X7 directly, and any invocation should be preceded by verification that the relevant plan has completed a refresh. As with all APPS-owned packages, the body should be treated as Oracle proprietary and extended only through supported APIs.