Search Results load_msc_interface

Overview

MSC_REL_PS_PLAN_PUB is a public PL/SQL package in the APPS schema that supports the release of planned supply and demand records managed by Oracle Advanced Supply Chain Planning (ASCP). Its central role is to convert planning output — planned orders, requirements, and supply recommendations — into executable documents in the transactional systems, including discrete and repetitive work orders, purchase requisitions, purchase orders, and material transfers. The package also supports mass loading and mass rescheduling of these transactions via the MSC interface tables.

The package declaration is defined with AUTHID CURRENT_USER, meaning that privileges are evaluated against the calling schema rather than the package owner. This is typical for ASCP public APIs, which are frequently invoked from concurrent programs and custom extensions. The header (MSCPSRELS.pls, version 120.3) confirms the package has been stable since at least the 12.0 release cycle and remains compatible with EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes seven documented procedures:

• MSC_RELEASE_PLAN_SC — The principal plan release routine. It drives the release of planned orders and requirements for a given plan, accepting an organization or plan context and applying the grouping and mass-load options defined by the package constants.
• MSC_PS_RELEASE — A related release entry point, used for plan scenario or subset release processing.
• LOAD_MSC_INTERFACE — Loads records into the MSC interface tables. This is the procedure most directly associated with the user search term "load_msc_interface" and is the mechanism by which release output is staged before being transferred to the destination transactional interfaces.
• LOAD_WIP_DISCR_JOBS_PS — Mass-loads discrete work orders into the planning interface.
• LOAD_OSFM_LOT_JOBS_PS — Mass-loads lot-based (OSFM/process) jobs into the interface.
• RESCHEDULE_WIP_DISCR_JOBS_PS — Mass-reschedules existing discrete work orders according to revised planning dates.
• RESCHEDULE_OSFM_LOT_JOBS_PS — Mass-reschedules lot-based jobs.

The package also declares constants that govern grouping (by item, buyer, planner, vendor, category, location, or one-each), the release action type (WIP mass load, repetitive mass load, WIP reschedule, PO mass load, PO reschedule), order type codes (purchase order, purchase requisition, work order, repetitive schedule, planned order, material transfer, non-standard job, receipt, requirement, FPO supply), revision control, and WIP detail load types (resource, component, operation, resource usage).

Tables Accessed

The package reads and writes the following documented tables through APPS synonyms:

• MSC_PLANS, MSC_PARAMETERS, MSC_APPS_INSTANCES — Plan definition, parameter values, and instance/destination configuration used to determine release behavior.
• MSC_DEMANDS — Source demand records considered during release.
• MSC_BOM_COMPONENTS, MSC_COMPONENT_SUBSTITUTES — Component and substitute detail loaded into interface jobs.
• MSC_OPERATION_NETWORKS, MSC_JOB_OPERATION_NETWORKS — Routing and operation network data for WIP job loads.
• MSC_DEPARTMENT_RESOURCES, MSC_DEPT_RES_INSTANCES, MSC_RESOURCE_REQUIREMENTS, MSC_RESOURCE_INSTANCE_REQS — Resource and capacity information for WIP detail loading.
• MSC_PO_REQUISITIONS_INTERFACE, MSC_PO_RESCHEDULE_INTERFACE — Purchase requisition and purchase order reschedule staging tables.
• MSC_ITEM_ID_LID — Item identifier and LID mapping used to resolve planning item references.

Usage Notes

MSC_REL_PS_PLAN_PUB is invoked from the ASCP Planner Workbench when a planner releases planned orders, from the mass-load and mass-reschedule concurrent programs, and from custom extensions that need to push plan output to the MSC interface tables. The LOAD_MSC_INTERFACE procedure is the documented entry point for staging records into MSC interface tables before downstream transfer to Oracle Purchasing or Oracle Work in Process. The package is not referenced by other packages (referenced-by count of zero), so it is intended to be called directly by Oracle Forms, concurrent programs, or customer code rather than through a wrapping API. Because of its AUTHID CURRENT_USER declaration, callers must hold appropriate execute privileges on the package and on the underlying MSC tables.