Search Results call_atp_11

Overview

MSC_ATP_UTILS is an Oracle Applications (APPS) PL/SQL package body that supports the Available-to-Promise (ATP) and supply/demand scheduling functionality within Oracle Advanced Supply Chain Planning. It functions as a technical utility layer that moves ATP result sets, scheduling data, and pegging information into and out of temporary staging tables used by the planning engine. The package is classified under the generic API category OTHER, indicating it is an internal helper rather than a formal public interface. It is referenced by eight other packages, confirming its role as a shared low-level component. The header comment tag MSCUATPB.pls 120.9 is dated 2007/12/12, so the logic is stable across the EBS 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The package exposes twenty documented procedures and functions, organized around three functional clusters.

• Temporary table management: PUT_INTO_TEMP_TABLE, GET_FROM_TEMP_TABLE, PUT_INTO_BOM_TEMP_TABLE, PUT_SD_DATA, PUT_PERIOD_DATA, PUT_PEGGING_DATA, PUT_SCHEDULING_DATA, PUT_SCH_DATA_REQUEST_MODE, PUT_SCH_DATA_RESULT_MODE, and RETRIEVE_PERIOD_AND_SD_DATA write and read ATP, BOM, supply/demand, period, pegging, and scheduling records into the temporary structures.
• ATP and scheduling execution: CALL_ATP_11 invokes the ATP calculation logic, while PROCESS_SUPPLY_DEMAND_DETAILS and COPY_MRP_SD_RECS stage and duplicate supply/demand rows for processing.
• Data maintenance and transfer: TRANSFER_MRP_ATP_DETAILS_TEMP and TRANSFER_SCHEDULING_DATA move staged data between layers; EXTEND_MAST and TRIM_MAST manipulate the master scheduling structure; UPDATE_LINE_ITEM_PROPERTIES refreshes order-line attributes; TRUNCATE_DEMAND clears demand records; and TEST is a diagnostic entry point.

Consistent with the documented header, PUT_INTO_TEMP_TABLE accepts a database link, a session identifier, ATP record, supply/demand, period, and detail collection types plus a mode, and returns the standard FND_API return status, message data, and message count. It builds dynamic SQL with an optional database link to insert or delete staging rows.

Tables Accessed

Through APPS synonyms, the package reads and writes MRP_ATP_DETAILS_TEMP and MRP_ATP_SCHEDULE_TEMP, the primary ATP result staging tables keyed by session_id and order_line_id. MSC_BOM_TEMP, MSC_CTO_BOM, and MSC_CTO_SOURCES hold bill-of-material and configure-to-order structures. MSC_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS supply item attributes. MTL_DEMAND_INTERFACE and MTL_SUPPLY_DEMAND_TEMP carry inbound demand and supply transactions, while OE_ORDER_LINES_ALL provides the sales order line context. DBMS_SQL and PLITBLM are used for dynamic SQL and index-by table support respectively. These tables support the session-based exchange of ATP, scheduling, and pegging data between the forms layer and the planning engine.

Usage Notes

MSC_ATP_UTILS is an internal utility package and should not be called directly from custom code unless the calling application replicates the session and staging conventions used by the ATP engine. It is normally invoked by the ATP scheduling flow, by Oracle Supply Chain Planning concurrent programs, and by the other packages that reference it. Because many procedures depend on a session_id and an optional database link, invocations must occur within the same logical session that created the temporary data. The package honors the MSC_ATP_DEBUG profile option through FND_PROFILE.value, writing trace output via MSC_SCH_WB.ATP_DEBUG when set to Y or C. This behavior makes it useful for diagnosing ATP temp-table issues during 12.1.1 or 12.2.2 troubleshooting.