Search Results item_pre_allocated_atp

Overview

APPS.MSC_AATP_REQ is a PL/SQL package body within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. Its principal business function is the computation of Available-to-Promise (ATP) information for planned items, including the allocation of existing supply and demand, and the derivation of forward-looking material availability. The package is part of the ATP and scheduling infrastructure that supports order promising and capable-to-promise decisions. It is classified as OTHER in ETRM, indicating that it is not a fully published public API but is invoked by the planning engine and dependent scheduling packages.

The package header comment ($Header: MSCRAATB.pls 120.5.12010000.2 2008/08/25) identifies it as a long-standing component of the MSC/ASCP code line, carried forward through the 12.1.1 and 12.2.2 releases. It relies on debug output controlled by the MSC_ATP_DEBUG profile option (FND_PROFILE.value), with the package-level variable PG_DEBUG defaulting to 'N'.

Key Procedures and Functions

The package body exposes two documented procedures:

• ITEM_PRE_ALLOCATED_ATP — The primary worker procedure. It calculates pre-allocated ATP for an item at a specified organization, considering plan, scenario, identifier, instance, demand class, and request date inputs. It returns ATP information through output parameters typed as MRP_ATP_PVT.ATP_Info, MRP_ATP_PUB.ATP_Period_Typ, and MRP_ATP_PUB.ATP_Supply_Demand_Typ. It accepts a material input record (MSC_ATP_REQ.get_mat_in_rec), refresh number, request item identifier, and ATF date, and supports a time-phased ATP mode. The procedure applies infinite time fence logic, default ATP rule, and calendar exception set resolution, and writes intermediate results into temporary allocation and ATP tables.
• GET_FORWARD_MATERIAL_ATP — This procedure is the documented entry point associated with the user search term get_forward_material_atp. It returns forward-looking material ATP — that is, the projected availability of an item beyond the current allocation horizon — by aggregating supply and demand from the allocation and summary ATP structures populated by the pre-allocation logic. It is typically consumed to answer the question of whether additional material will become available to promise within a given forward window.

No parameter lists are invented here; the documented signatures should be validated against the deployed package specification in the target instance.

Tables Accessed

The package operates against the following documented base objects through APPS synonyms:

• MSC_ALLOC_DEMANDS, MSC_ALLOC_SUPPLIES, MSC_ALLOC_TEMP — source and working allocation supply/demand data.
• MRP_ATP_DETAILS_TEMP, MSC_ATP_SD_DETAILS_TEMP — temporary ATP detail and supply/demand detail storage.
• MSC_ATP_SUMMARY_SD — summarized ATP supply/demand used for forward material availability.
• MSC_PLANS — plan context resolution.
• MSC_TRADING_PARTNERS, MSC_TRADING_PARTNER_SITES — partner and site information used in allocation and ATP referencing.
• PLITBLM — numeric PL/SQL table used for internal array processing.

Usage Notes

MSC_AATP_REQ is not a user-facing form API. It is invoked programmatically by the ASCP planning and ATP engine, and it is referenced by four other packages within the EBS schema. It is also commonly called from custom PL/SQL where forward material ATP must be retrieved for a plan, inventory item, and organization. Because it depends on the MSC_ATP_DEBUG profile for tracing, debugging should be enabled at the profile level prior to invocation. The package is release-safe for 12.1.1 and 12.2.2, but its continued status as an OTHER-classified object means that custom integrations should be validated against each patch level.