Search Results load_sd_net_unalloc

Overview

MSC_POST_PRO is a core Oracle Advanced Supply Chain Planning (ASCP) package body owned by APPS. It performs the posting phase of the planning cycle in Oracle E-Business Suite 12.1.1 and 12.2.2, transforming staged planning results into queryable summary and schedule data. The package orchestrates the movement of supply, demand, allocation, resource, and supplier data from work tables into the planning summary tables, and manages the partition structures that support plan refreshes.

A significant portion of the package supports the ATP summary enhancement referenced by the search term "msc_atp_summary." The body declares a large family of private helper procedures — Truncate_Summ_Plan_Partition, LOAD_PLAN_SUMMARY_SD, LOAD_SD_FULL_ALLOC, LOAD_SD_FULL_UNALLOC_OPT, LOAD_SD_FULL_UNALLOC_OPT_PF, LOAD_SD_FULL_UNALLOC_UNOPT, LOAD_SD_FULL_UNALLOC_UNOPT_PF, LOAD_SD_NET_ALLOC, LOAD_SD_NET_UNALLOC, LOAD_SUP_DATA_FULL, LOAD_SUP_DATA_NET, and LOAD_RES_FULL_UNOPT_BATCH — that populate MSC_ATP_SUMMARY_SD, MSC_ATP_SUMMARY_SUP, and related summary objects for both full and net (incremental) plan refreshes, in optimized and unoptimized modes, and with or without time-phased planning. Global variables such as G_ALLOC_ATP, G_CLASS_HRCHY, and G_ALLOC_METHOD control branching logic during posting, while the profile MSC_ATP_DEBUG (read through FND_PROFILE.value) governs diagnostic output.

Key Procedures and Functions

• ATP_POST_PLAN_PROC — Primary entry point that drives posting of ATP plan results.
• POST_PLAN_ALLOCATION — Posts allocation results for the plan.
• LOAD_SUPPLY_DEMAND / LOAD_PLAN_SD / LOAD_NET_SD / LOAD_NET_SO / LOAD_NET_PLAN — Load supply, demand, and net planning records for both full and net refresh processing.
• INSERT_SUPPLIER_DATA — Inserts supplier sourcing data into the plan summary structures.
• LOAD_RESOURCES — Loads resource capacity and requirement data.
• CREATE_PARTITIONS / CREATE_PLAN_PARTITIONS / CREATE_INST_PARTITIONS — Create the partition structures used to isolate plan data.
• CLEAN_PLAN_TABLES / CLEAN_TEMP_TABLES — Purge prior-run data and temporary working sets.
• ATP_PURGE_MRP_TEMP — Removes MRP temporary ATP records.
• GET_TOLERANCE_DEFINED — Retrieves tolerance configuration used during matching.
• LAUNCH_CONC_PROG — Submits concurrent programs from within the posting flow.
• ATP_SNAPSHOT_HOOK — Hook procedure invoked for ATP snapshot processing.
• DELETE_CTO_BOM_OSS — Removes Configure-to-Order BOM and order-specific sourcing data.

Tables Accessed

The package reads and writes the ATP summary tables MSC_ATP_SUMMARY_SD, MSC_ATP_SUMMARY_SO, MSC_ATP_SUMMARY_SUP, and MSC_ATP_SUMMARY_RES, which hold the post-processed supply, demand, supplier, and resource results. Working areas MRP_ATP_DETAILS_TEMP and MRP_ATP_SCHEDULE_TEMP provide intermediate ATP computation storage. Allocation results are drawn from MSC_ALLOC_DEMANDS and MSC_ALLOC_SUPPLIES. ATP rule and profile configuration come from MSC_ATP_RULES, MSC_ATP_PARAMETERS, MSC_ATP_SRC_PROFILE_TEMP, and MSC_CALENDAR_DATES. Instance and schema context is established through MSC_APPS_INSTANCES, FND_PRODUCT_INSTALLATIONS, and FND_ORACLE_USERID.

Usage Notes

MSC_POST_PRO is invoked internally by the ASCP planning engine rather than directly from a form. It is called during plan posting and refresh, including the summary/ATP enhancement path, and the LAUNCH_CONC_PROG procedure allows posting to submit additional concurrent requests. The package is referenced by eight other packages, indicating it functions as a shared posting utility. Direct custom invocation should be avoided; customizations typically attach through the ATP_SNAPSHOT_HOOK or extend the summary load procedures. The MSC_ATP_DEBUG profile option enables debug tracing when diagnosing posting or ATP summary issues.