Search Results check_substitutes

Overview

APPS.MSC_ATP_REQ is a PL/SQL package belonging to the Oracle Advanced Supply Chain Planning (ASCP) and Available-to-Promise (ATP) subsystem of Oracle E-Business Suite. Its primary business function is to satisfy ATP requests by gathering the material, resource, component, supplier, and transportation capacity information required to determine whether a demand can be promised against available supply. In effect, the package acts as the computational engine that translates ATP rules and BOM/planning data into feasible commit dates and quantities.

The package sits within the MSC_ATP_REQUEST framework and depends on the shared ATP utilities MRP_ATP_PUB and MRP_ATP_PVT for base calculations. It is itself consumed by a broad set of higher-level ATP routines including MSC_AATP_PVT, MSC_ATP_PVT, MSC_ATP_SUBST, MSC_POST_PRO, and its own request-oriented siblings MSC_AATP_REQ and MSC_ATP_REQ. This dependency pattern confirms its role as a reusable data-assembly service invoked by multiple ATP entry points rather than a standalone user-facing program.

Key Procedures and Functions

The package exposes nine documented procedures and functions covering the full ATP evaluation cycle:

• GET_MATERIAL_ATP_INFO — retrieves availability information for the material being promised.
• GET_RES_REQUIREMENTS — determines the resource capacity requirements associated with the ATP request.
• GET_COMP_REQUIREMENTS — derives component-level requirements, typically for configured or ATO items.
• GET_SUPPLIER_ATP_INFO — evaluates supplier-based availability where supplier ATP is enabled.
• GET_TRANSPORT_CAP_ATP_INFO — assesses transportation capacity constraints affecting the promise.
• CHECK_SUBSTITUTES — evaluates whether acceptable substitute components or items can satisfy the demand.
• INSERT_DETAILS — writes ATP detail rows into the temporary working tables.
• EXTEND_ATP_COMP_TYP — extends or classifies component types during ATP processing.
• ADD_TO_COMP_LIST — appends entries to the working component list.

Collectively these routines separate data acquisition (GET_* routines) from result persistence (INSERT_DETAILS) and list management (EXTEND_ATP_COMP_TYP, ADD_TO_COMP_LIST).

Tables Accessed

Via APPS synonyms the package reads and writes a documented set of fourteen tables. Working and result tables include MRP_ATP_DETAILS_TEMP, MSC_ATP_SD_DETAILS_TEMP, MSC_ATP_SUMMARY_RES, MSC_ATP_SUMMARY_SD, MSC_ATP_SUMMARY_SO, and MSC_ATP_SUMMARY_SUP, which hold temporary detail and summarized availability results. Configuration data is provided by MSC_ATP_RULES. BOM structure is supplied by MSC_BOMS, MSC_BOM_COMPONENTS, MSC_BOM_TEMP, MSC_CTO_BOM, and MSC_BOR_REQUIREMENTS, supporting configured-item ATP. Substitute logic uses MSC_COMPONENT_SUBSTITUTES, and demand/calendaring comes from MSC_DEMANDS and MSC_CALENDAR_DATES.

Usage Notes

MSC_ATP_REQ is not normally invoked directly by end users. It is called programmatically from ATP-related PL/SQL flows, notably the AATP (Advanced ATP) packages MSC_AATP_PVT and MSC_AATP_REQ, and from the posting and substitution routines MSC_POST_PRO and MSC_ATP_SUBST. The user search term "msc_aatp_pvt" reflects this close coupling with the Advanced ATP private API. Calls typically reach it through the ATP calculation triggered when sales order lines are scheduled, when a configure-to-order item is promised, or during batch ATP processing. Custom code should reference the package only with matching parameter signatures and must respect the temporary-table lifecycle, since INSERT_DETAILS populates session-scoped working tables consumed by downstream packages. Because the package is documented with an API classification of OTHER, backward compatibility is not guaranteed across upgrades, and extensions should be validated for each EBS release (12.1.1 versus 12.2.2).