Search Results start_mscatp_wf

Overview

MSC_WF_ALLOC_ATP is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema. It belongs to the Oracle Advanced Supply Chain Planning (ASCP) family of objects, where the MSC prefix denotes tables and program units managed by the MSC (Supply Chain Planning) product. The package serves as the integration bridge between the Oracle Workflow engine (WF_ENGINE) and the available-to-promise (ATP) and allocation logic used during order promising.

Its principal business role is to evaluate whether an item can satisfy a requested quantity on a requested date at a specified trading partner or site, and to drive a workflow-based notification or approval path when ATP checks are performed. In practice it supports the ATP and allocation processing that underlies global order promising and constrained supply allocation, allowing planners and order-entry applications to determine feasible promise dates and to detect conditions where allocation cannot be met.

Key Procedures and Functions

The package exposes six documented program units, all classified under the standard package structure:

• DEBUG_WF — a diagnostic helper used to trace workflow activity during ATP and allocation processing, typically writing to the database session context for troubleshooting.
• START_MSCALLOC_WF — initiates the allocation workflow, launching the Workflow Engine process that governs allocation-related decisions and notifications.
• START_MSCATP_WF — launches the ATP workflow, used when an ATP evaluation requires a workflow-driven response such as a message, notification, or human action.
• WITHIN_ALLOCATION — determines whether a request falls within the defined allocation, returning a Boolean-style result that governs subsequent processing.
• QTY_STOLEN — quantifies quantity that has been taken from or reallocated against a supply, supporting reconciliation of shortage or over-commitment conditions.
• ATP_SATISFY — the core ATP satisfier, evaluating whether demand can be matched to supply and driving the resulting outcome.

No parameter lists are documented in the source metadata; callers should verify signatures against the deployed package specification for the specific release.

Tables Accessed

The package reads and writes a defined set of ASCP and Workflow objects through APPS synonyms:

• MRP_ATP_DETAILS_TEMP — working structure holding ATP detail rows during evaluation.
• MRP_ATP_SCHEDULE_TEMP_S — the ATP schedule temporary table, central to storing schedule-level ATP results; the user's search term maps directly to this object.
• MSC_PLANS, MSC_PLANNERS, MSC_SYSTEM_ITEMS — planning context, ownership, and item definition data.
• MSC_TRADING_PARTNERS, MSC_TRADING_PARTNER_SITES, MSC_TP_ID_LID, MSC_TP_SITE_ID_LID — trading partner identity and site resolution.

It also references FND_PROFILE for profile option values and the V$ dynamic performance views (V$PARAMETER, V$PROCESS, V$SESSION) for session and context diagnostics used by the DEBUG_WF helper.

Usage Notes

MSC_WF_ALLOC_ATP is an internal planning package. It is not referenced by any other database object, and it is invoked indirectly by ASCP allocation and ATP processing, with two packages documented as referencing it. Typical entry points include planning runs, ATP checks triggered from order entry or shipping, and workflow-driven allocation events started through START_MSCALLOC_WF and START_MSCATP_WF.

Because the procedures are not documented as a public API and depend on temporary tables and session-level v$ views, custom code should avoid direct invocation. Modifications should be validated against Oracle Support guidance, since the object is marked VALID and proprietary.