Search Results update_tables

Overview

APPS.MSC_ATP_PUB is a public PL/SQL package in the Oracle E-Business Suite application schema (APPS) that serves as the principal entry point for Available-to-Promise (ATP) processing within the Advanced Supply Chain Planning (ASCP) and Manufacturing modules. The package is classified as a PUB package, indicating it is intended for invocation by external concurrent programs, forms, and custom code rather than being restricted to internal package-to-package use. Its documented metadata confirms a VALID status in ETRM for both 12.1.1 and 12.2.2 releases, with 3 documented procedures and references to 14 underlying tables through APPS synonyms.

The core business function of MSC_ATP_PUB is to evaluate supply and demand signals across planning regions and return ATP availability results, supporting order promising, scheduling, and allocation decisions used by order management and manufacturing processes.

Key Procedures and Functions

Three procedures are documented for this package:

• CALL_ATP — The primary ATP driver procedure. It executes ATP checking logic for a given request, orchestrating the population of temporary ATP tables, invoking downstream private APIs, and committing results. It is the standard entry point for requesters requiring a full ATP evaluation with persistence of results.
• CALL_ATP_NO_COMMIT — A variant of CALL_ATP that performs the same ATP computation but does not issue a database commit. It is designed for callers that must control transaction boundaries themselves, for example when ATP is embedded within a larger transaction that must remain atomic.
• UPDATE_TABLES — A utility procedure that refreshes or synchronizes the working and staging tables used by ATP processing, ensuring consistency between the temporary result sets and the persistent planning tables.

No parameter lists are enumerated in the documented metadata; callers should consult the package specification in the database for exact signatures.

Tables Accessed

The package accesses 14 tables via APPS synonyms. The planning-domain tables include MRP_ATP_DETAILS_TEMP, MRP_ATP_SCHEDULE_TEMP, MSC_ATP_SRC_PROFILE_TEMP, MSC_REGIONS_TEMP, MSC_OE_DATA_TEMP, and MSC_PLANS, which hold intermediate and configuration data for ATP evaluation and region definition. MSC_ALLOC_DEMANDS, MSC_ALLOC_SUPPLIES, MSC_DEMANDS, MSC_SUPPLIES, and MSC_RESOURCE_REQUIREMENTS provide the supply/demand and capacity signals evaluated during ATP computation. MRP_AP_REFRESH_S is used for refresh sequencing, MSC_APPS_INSTANCES identifies participating application instances in multi-instance deployments, and HZ_CUST_ACCOUNT_ROLES and FND_USER supply customer and user context for order promising and responsibility-based access.

Usage Notes

MSC_ATP_PUB is referenced by seven other packages, including MRP_ATP_PUB, MSC_AATP_PVT, MSC_ATP_24X7, MSC_ATP_ALLOC, MSC_ATP_CTO, MSC_ATP_PVT, and MSC_ATP_UTILS, reflecting its role as a shared public interface within the ATP subsystem. It is typically invoked from ATP-related concurrent programs and from the ATP processing engine during order scheduling and promising flows. Custom integrations should prefer CALL_ATP_NO_COMMIT when embedding ATP logic inside a controlled transaction, and CALL_ATP when the package may manage its own commit. Because the package is PUBLIC and its dependencies span both the SYS STANDARD package and the MRP/MSC private layers, developers should treat it as a supported integration point and revalidate any extensions against ETRM documentation when upgrading between 12.1.1 and 12.2.2.