Search Results insert_supplier_data




Overview

APPS.MSC_POST_PRO is a PL/SQL package in the Oracle Advanced Supply Chain Planning (ASCP) module of Oracle E-Business Suite. It serves as the primary post-planning processing engine, responsible for loading supply and demand data, building planning partitions, generating ATP (Available-to-Promise) summaries, and executing supply chain allocation and pegging logic. The package header (identified as MSCPOSTS.pls, version 120.1) exposes status constants (G_SUCCESS, G_WARNING, G_ERROR) along with a set of summary-flow state constants (G_SF_SUMMARY_NOT_RUN through G_SF_ATPPEG_COMPLETED) that allow callers to track the progress of the summary enhancement pipeline, from pre-allocation through 24x7 synchronization and ATP pegging generation. In EBS 12.1.1 and 12.2.2, this package is integral to the ASCP planning cycle and the ATP post-plan processing flow.

Key Procedures and Functions

Tables Accessed

The package reads and writes several ASCP and ATP tables via APPS synonyms, including MSC_ATP_SUMMARY_RES, MSC_ATP_SUMMARY_SD, MSC_ATP_SUMMARY_SO, and MSC_ATP_SUMMARY_SUP (summary result tables), MSC_ALLOC_DEMANDS and MSC_ALLOC_SUPPLIES (allocation data), MRP_ATP_DETAILS_TEMP and MRP_ATP_SCHEDULE_TEMP (ATP temporary working tables), MSC_ATP_PARAMETERS and MSC_ATP_RULES (ATP configuration), MSC_ATP_SRC_PROFILE_TEMP and MSC_CALENDAR_DATES (sourcing and calendar data), MSC_APPS_INSTANCES (instance registry), FND_ORACLE_USERID and FND_PRODUCT_INSTALLATIONS (application instance metadata used for schema and installation lookups).

Usage Notes

MSC_POST_PRO is typically invoked from ASCP concurrent programs, the ATP post-plan processing flow, and in some cases from custom extensions that need to load supplier data or regenerate ATP summaries. The INSERT_SUPPLIER_DATA procedure is generally called during a full refresh of planning data to seed supplier/partner information, and its parameter set (plan ID, share partition, APPS schema, and full refresh flag) indicates it operates in a partitioned, multi-schema context. Because the package is referenced by eight other packages and performs heavy partition and temporary table management, it should be invoked with the correct instance and plan identifiers, and cleanup procedures should be scheduled appropriately to avoid residual data in MSC_ALLOC_* and MRP_ATP_* temp tables. The summary-flow constants exposed in the package header provide a reliable way to monitor pre-allocation, 24x7 sync, and ATP pegging status programmatically.