Search Results msc_auto_release




Overview
Explore in AI Chat

Overview

MSC_RELEASE_PK is an Oracle Applications (APPS) schema PL/SQL package within the Advanced Supply Chain Planning (ASCP) module of Oracle E-Business Suite. It is classified under the ETRM metadata as an "OTHER" API type, indicating that it is not a standard public-interface API but rather an internal or supporting package used by the planning engine and its web service entry points. Its principal business function is to orchestrate the release of planned orders — discrete jobs, purchase requisitions, purchase orders, and repetitive schedules — from a planning schedule into the execution systems (Oracle Purchasing, Oracle Manufacturing, and Oracle Order Management). The package's name, "release," reflects this core responsibility: transforming plan-generated recommendations into actionable execution documents. The package is owned by APPS and is documented as VALID in both EBS 12.1.1 and 12.2.2 environments. The dependency metadata shows that MSC_RELEASE_PK references only the SYS.STANDARD package for its PL/SQL runtime, while it is referenced by three other APPS packages: MSC_WS_ASCP, MSC_WS_DRP, and MSC_WS_SRP. These are web service wrappers for ASCP, Distribution Requirements Planning (DRP), and Service Resource Planning (SRP), confirming that MSC_RELEASE_PK is invoked through planning web service layers as well as directly by the planning engine.

Key Procedures and Functions

The ETRM metadata documents three procedures or functions within this package:

  • MSC_AUTO_RELEASE — Drives the automatic release of planned orders based on planner-defined parameters and system-level auto-release profiles. This is the primary batch-oriented entry point, typically invoked by concurrent programs that process eligible planned orders in a plan and push them to the execution systems without manual intervention.
  • MSC_WEB_SERVICE_RELEASE — Provides the web-service-facing implementation of the release logic. It is called by the MSC_WS_ASCP, MSC_WS_DRP, and MSC_WS_SRP packages, enabling external or distributed planning clients to submit release requests programmatically rather than through the EBS forms interface.
  • QUERYBASEDAUTORELEASE — Supports query-based auto-release, a feature that allows planners to define saved queries (through personal or plan queries) that select specific planned orders for automatic release. This procedure evaluates the stored query criteria and releases the matching planned orders accordingly.

Tables Accessed

MSC_RELEASE_PK reads and writes a range of MSC tables via APPS synonyms. The core planning data — planned orders and their attributes — is stored in tables such as MSC_DEMANDS, MSC_BOMS, MSC_DESIGNATORS, MSC_ITEM_SUBSTITUTES, MSC_ITEM_SUPPLIERS, and MSC_FULL_PEGGING, which supply the structural and pegging context needed to validate and transform a planned order. MSC_PLANS, MSC_PLANNERS, MSC_APPS_INSTANCES, and MSC_PROCESS_EFFECTIVITY provide the plan configuration, planner assignment, source instance mapping, and process effectiveness controls that govern whether and how a release should proceed. MSC_CALENDAR_DATES supplies scheduling dates for order conversion. MSC_PERSONAL_QUERIES and MSC_PLAN_QUERIES store the saved query definitions used by QUERYBASEDAUTORELEASE, with results materialized in MSC_PQ_RESULTS. Finally, MSC_EXCEPTION_DETAILS records any exceptions raised during the release process, allowing planners to diagnose failures in the planning workbench.

Usage Notes

MSC_RELEASE_PK is not intended for direct ad hoc invocation by end users. It is most commonly executed through the planning concurrent programs that perform automatic release of planned orders, and through the ASCP, DRP, and SRP web service packages (MSC_WS_ASCP, MSC_WS_DRP, MSC_WS_SRP) that expose release functionality to external planning clients. Planners interact with it indirectly via the Supply Chain Planner responsibility when they initiate manual or auto-release actions from the Planner Workbench. Custom extensions that need to release planned orders programmatically should generally call the appropriate wrapper package rather than MSC_RELEASE_PK directly, since the package is classified as "OTHER" rather than a supported public API. Because release writes to execution tables and can create jobs and requisitions, any custom usage must respect plan scope, process effectiveness, and security controls. Test releases in a non-production plan before enabling auto-release in production environments.