Search Results msc_aatp_proc




Overview
Explore in AI Chat

Overview

MSC_AATP_PROC is an APPS-owned PL/SQL package body that implements the Available-to-Promise (ATP) processing logic used by Oracle Advanced Supply Chain Planning (ASCP) and related availability calculations in Oracle E-Business Suite 12.1.1 and 12.2.2. Its role is to support the accumulation, adjustment, consumption, and cleanup of ATP quantities within the planning and order-promising flow. The package operates in close coordination with the public ATP engine interfaces — MRP_ATP_PUB and MRP_ATP_PVT — and with the scheduling workbench package MSC_SCH_WB. It also relies on FND_API for the standard EBS API error-handling and message conventions and FND_PROFILE for session-level profile option access. In that sense, MSC_AATP_PROC functions as a supporting "A-ATP" (available ATP) utility layer rather than a standalone public API, exposing internal procedures that are called from the surrounding ATP infrastructure.

Key Procedures and Functions

The ETRM metadata documents five procedures and functions within the package body:

  • ADD_TO_CURRENT_ATP — Adds a specified quantity to the currently accumulated ATP figure. It is typically used during the incremental build-up of available supply when processing ATP rules or demand/supply records in sequence.
  • ATP_FORWARD_CONSUME — Performs forward consumption of ATP, i.e., allocates available supply against later-dated demands in accordance with the ATP rule's consumption window and forward/backward consumption settings.
  • ATP_ADJUSTED_CUM — Calculates or applies the "adjusted cumulative" ATP value, adjusting the running cumulative ATP for movements, lead-time offsets, or planner-defined adjustments.
  • ATP_REMOVE_NEGATIVES — Removes or clamps negative ATP values, ensuring the returned ATP figures are non-negative and consistent with the availability rules before they are presented to the scheduling or order-promising logic.
  • GET_UNALLOC_DATA_FROM_SD_TEMP — Reads unallocated (unallocated ATP) data from the temporary scheduling-detail table, making it available to the ATP calculations. This procedure is the primary consumer of the MSC_ATP_SD_DETAILS_TEMP table and thus the functional point behind the user's search term "msc_atp_sd_details_temp."

Tables Accessed

The package body reads and writes the following documented tables. Both are referenced through APPS synonyms:

  • MSC_ATP_SD_DETAILS_TEMP — This is the temporary staging table holding scheduling-detail records relevant to ATP. The procedure GET_UNALLOC_DATA_FROM_SD_TEMP extracts the unallocated data from this table, which is then fed into the ATP accumulation, consumption, and adjustment procedures. Because the table name is a temporary/details staging structure, its rows are session- or run-specific work data rather than permanent history.
  • PLITBLM — This is the standard Oracle PL/SQL-supplied public synonym for the DBMS_STANDARD package's package-body table (the internal "PACKAGE BODY" and "PACKAGE" entries shown in the dependency listing). It represents Oracle's built-in PL/SQL support and is not an application data table.

At the package-body level, the dependency metadata additionally documents references to FND_API, FND_PROFILE, MRP_ATP_PUB, MRP_ATP_PVT, MSC_AATP_PROC, and MSC_SCH_WB. Standard and PUBLIC references (STANDARD, SYS) reflect regular PL/SQL runtime dependencies.

Usage Notes

MSC_AATP_PROC is not referenced by any other database object in the documented dependency metadata, and the ETRM classification for the package is OTHER, i.e., it is not published as a formal public API. The package is therefore invoked internally by the Oracle Advanced Supply Chain Planning ATP engine and by the scheduling workbench rather than being called directly by customer code. In practice it is reached through MRP_ATP_PUB and MRP_ATP_PVT when availability is calculated and through MSC_SCH_WB when the scheduling workbench performs ATP-related operations.

Because the package and its temporary table MSC_ATP_SD_DETAILS_TEMP are part of the ASCP product schema, customizations should not call these procedures directly. Instead, integrators and support analysts generally inspect MSC_ATP_SD_DETAILS_TEMP only for diagnostic purposes, understanding that it is populated and consumed during the active ATP calculation run. The procedures are executed in a defined sequence — unallocated data is read from the staging table, quantities are added to current ATP, forward consumption is applied, adjusted cumulative values are computed, and negative values are removed — reflecting the internal pipeline of the A-ATP calculation.