Search Results msc_atp_exceptions




Overview
Explore in AI Chat

Overview

MSC_ATP_EXCEPTIONS is a PL/SQL package in the APPS schema that supports availability-to-promise (ATP) exception handling within the Oracle Advanced Supply Chain Planning (ASCP) and global order promising infrastructure. In Oracle EBS 12.1.1 and 12.2.2, ATP exceptions are the mechanism by which the planning engine records circumstances under which a requested promise date, quantity, or sourcing arrangement cannot be satisfied as requested. The MSC_ATP_EXCEPTIONS package provides the programmatic layer through which these exceptions are defined, captured, and associated with the plan and designator context in which they were raised.

The package is registered in ETRM with an API classification of OTHER, indicating that it is an internal planning utility rather than a documented public API. It is consumed primarily by the ATP processing logic (MSC_ATP_PVT) and is referenced by only one other package, confirming its role as a supporting component of the broader ATP exception framework rather than a standalone interface. In both 12.1.1 and 12.2.2 the package status is VALID and it depends only on the SYS STANDARD package, meaning no external Oracle EBS package dependencies constrain its behavior.

Key Procedures and Functions

The ETRM metadata documents two callable units within the package:

  • GET_PLAN_CONSTRAINTS — Retrieves the plan-level constraint definitions that govern how ATP exceptions are evaluated for a given plan. This procedure supplies the ATP engine with the planning constraints applicable to the exception context, ensuring that exception detection respects the plan's configured rules.
  • ADD_ATP_EXCEPTION — Inserts or registers an ATP exception when an availability or promise condition cannot be met. This procedure persists the exception record so that it can be surfaced to planners, order management users, or downstream exception reporting.

No parameter lists are documented in ETRM; consumers should refer to the package specification in the target environment for exact signatures.

Tables Accessed

MSC_ATP_EXCEPTIONS operates against the following tables (referenced through APPS synonyms):

  • MSC_DESIGNATORS — Provides the designator context that ties an exception to a specific planning designation or scenario.
  • MSC_EXCEPTION_DETAILS and MSC_EXCEPTION_DETAILS_S — Store the descriptive detail and translated/seed rows for each exception, forming the core of the exception record written by ADD_ATP_EXCEPTION.
  • MSC_ITEM_EXCEPTIONS — Associates exceptions with specific items, enabling item-level reporting and resolution.
  • MSC_PLANS — Supplies plan definitions read by GET_PLAN_CONSTRAINTS to determine which constraints apply.

Usage Notes

MSC_ATP_EXCEPTIONS is an internal package and is not intended for direct invocation by end users. It is invoked within the ATP processing flow, principally from MSC_ATP_PVT during order promising and scheduling calculations. Customizations should not call this package directly; instead they should use the supported ATP and planning APIs that wrap it. Because it writes to MSC_EXCEPTION_DETAILS and related tables, any concurrent or custom process invoking it must respect the transactional boundaries of the ATP run. Planners typically consume the resulting exceptions through standard exception workbenches and planning exception reports rather than through this package.