Search Results add_atp_exception

Overview

The APPS.MSC_ATP_EXCEPTIONS package body is a PL/SQL component within the Oracle Advanced Supply Chain Planning (ASCP) module of Oracle E-Business Suite. Its primary business function is to evaluate planning constraints and to create and manage Available-to-Promise (ATP) exception records. ATP exceptions represent conditions under which supply cannot fully satisfy demand—for example, capacity shortages or material shortages—and are surfaced to planners so that these conditions can be reviewed and resolved.

The package operates against planning data stored in the MSC (Multi-Organization Supply Chain) schema. It determines whether a given plan is optimized or constrained by inspecting the plan's designator and constraint-related attributes, then uses that determination to drive the creation of exception records. The documented package metadata classifies the API as OTHER and notes that it is referenced by one other package, indicating its role as a supporting utility within the broader ASCP exception-handling framework.

Key Procedures and Functions

The package exposes two documented procedures:

• GET_PLAN_CONSTRAINTS — Determines the plan type for a given plan identifier. It returns a plan type of 1 when the plan is optimized or constrained, and 0 otherwise. The procedure first checks plans.plan_type and inspects the daily, weekly, and period material and resource constraint flags on the plan record. It also considers the MSO_BATCHABLE_FLAG profile option value. On exception, the procedure returns a plan type of 0 and, when debug is enabled, writes a diagnostic message through msc_sch_wb.atp_debug. This procedure is intended to be replaced by checks in a Get_Plan_Info routine.
• ADD_ATP_EXCEPTION — Adds a new ATP exception record. As indicated by the package header comment and the user search term add_atp_exception, this is the primary API through which callers register ATP exceptions. It is the entry point used to persist exception details for a plan so that they can be reported and managed by planners.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• MSC_DESIGNATORS — Joined with MSC_PLANS in GET_PLAN_CONSTRAINTS to resolve the compile designator, source instance, and organization for the plan.
• MSC_PLANS — Provides plan type and the daily, weekly, and period material and resource constraint flags used to classify the plan.
• MSC_ITEM_EXCEPTIONS — Stores item-level exception records created by the add operation.
• MSC_EXCEPTION_DETAILS and MSC_EXCEPTION_DETAILS_S — Hold the detail and child (denormalized/sequential) rows for each exception, written when a new ATP exception is added.

Usage Notes

MSC_ATP_EXCEPTIONS is typically invoked from within the ASCP planning engine and related supply chain workbench processes rather than directly by end users. In Oracle EBS 12.1.1 and 12.2.2, it is called programmatically as a supporting package by the plan exception generation logic, and it may also be called from custom code or concurrent programs that need to register ATP exceptions. Because its procedures depend on plan and profile data, callers should ensure the plan identifier is valid and that the plan's constraints and designator records are populated before invocation. Diagnostic output is controlled through debug flags maintained in Order_Sch_Wb.mr_debug, and messages are emitted through msc_sch_wb.atp_debug when debugging is enabled.