Search Results get_tolerance_defined
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
- LOAD_SUPPLY_DEMAND — Loads supply and demand records for a given instance and collection type into the planning tables.
- CREATE_PARTITIONS — Creates the necessary table partitions used during post-plan processing.
- LOAD_PLAN_SD — Loads plan-level supply and demand data; includes a calling-module parameter added for ATP Post Plan Processing identification.
- INSERT_SUPPLIER_DATA — Inserts supplier/partner data for a given plan, partition, and schema, typically during a full refresh cycle. This is the procedure the user searched for, and it is the entry point for populating supplier-related planning data.
- GET_TOLERANCE_DEFINED — Retrieves tolerance definitions used in allocation or ATP processing.
- LOAD_RESOURCES — Loads resource data into the planning schema.
- CLEAN_PLAN_TABLES — Cleans plan-specific temporary and working tables.
- CREATE_PLAN_PARTITIONS — Creates partitions specific to a plan.
- LOAD_NET_SO / LOAD_NET_SD / LOAD_NET_PLAN — Load netting-related sales order, supply/demand, and plan data.
- CREATE_INST_PARTITIONS — Creates instance-level partitions.
- LAUNCH_CONC_PROG — Launches a concurrent program from within the package.
- POST_PLAN_ALLOCATION — Executes post-plan allocation logic.
- ATP_POST_PLAN_PROC — Orchestrates ATP post-plan processing.
- ATP_PURGE_MRP_TEMP — Purges ATP temporary MRP data.
- CLEAN_TABLES / CLEAN_TEMP_TABLES — Removes stale data from permanent and temporary tables.
- ATP_SNAPSHOT_HOOK — Hook procedure for ATP snapshot processing.
- DELETE_CTO_BOM_OSS — Deletes CTO/BOM/Oss (order sourcing) records.
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.
-
PACKAGE: APPS.MSC_POST_PRO
12.1.1
-
PACKAGE: APPS.MSC_POST_PRO
12.2.2
-
PACKAGE BODY: APPS.MSC_POST_PRO
12.1.1
-
PACKAGE BODY: APPS.MSC_POST_PRO
12.2.2