Results for “msc_web_service_release”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.MSC_RELEASE_PK is a packaged body within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. Its principal business function is to release planned supply chain recommendations — planned orders, planned buy orders, planned transfer orders, discrete jobs, and purchase requisitions — into the corresponding execution systems, where they become actionable documents such as purchase orders, purchase requisitions, and work orders. The package encapsulates the release logic used by ASCP when planners convert a plan into executable demand and supply records.

The package body opens with an extensive set of named constants that identify the release target types and modes. Documented constants include WIP_DIS_MASS_LOAD (1), PO_MASS_LOAD (8), PO_REQUISITION (2), and WIP_DISCRETE_JOB (3), as well as order classification flags such as MAKE (1), BUY (2), and PLANNED_ORDER (5). Additional constants distinguish planned new buy orders (76), planned inter-org and external requisitions (77 and 78), and planned transfers (51). Plan-type constants cover MRP (1), MPS (2), MPP (3), DRP (5), and SRP (8). These constants provide the internal decision framework that determines how each planned record is routed during release.

Key Procedures and Functions

The ETRM metadata documents three procedures and functions within MSC_RELEASE_PK:

• MSC_AUTO_RELEASE — The core auto-release routine. It drives the automated release of eligible planned orders based on planner-defined criteria, plan parameters, and release authority. This is the primary entry point used by the auto-release concurrent process.
• MSC_WEB_SERVICE_RELEASE — Exposes release processing through a web service interface. It allows external or integration-driven callers to submit release requests for planned orders programmatically rather than through the standard ASCP planner workbench.
• QUERYBASEDAUTORELEASE — Performs auto-release driven by saved personal queries. It resolves a stored query against the planning data and releases the planned orders that satisfy the query criteria, allowing planners to define custom release rules.

Tables Accessed

The package reads and writes a broad set of ASCP and related tables through APPS synonyms. Planning data is sourced from MSC_DEMANDS, MSC_BOMS, MSC_ITEM_SUBSTITUTES, MSC_ITEM_SUPPLIERS, and MSC_FULL_PEGGING. Planning context is derived from MSC_PLANS, MSC_PLANNERS, MSC_PROCESS_EFFECTIVITY, MSC_CALENDAR_DATES, and MSC_DESIGNATORS. Release-rule evaluation relies on MSC_PERSONAL_QUERIES, MSC_PLAN_QUERIES, and MSC_PQ_RESULTS. Flexfield and application-instance information is retrieved from MSC_APPS_INSTANCES, and release exceptions are recorded in MSC_EXCEPTION_DETAILS. These tables supply the pegging, sourcing, calendar, and query data needed to validate and route each planned order at release time.

Usage Notes

MSC_RELEASE_PK is invoked from the ASCP Planner Workbench and through ASCP concurrent programs, including the auto-release process. It may also be called from custom code and integrations that require programmatic release of planned orders. The MSC_WEB_SERVICE_RELEASE entry point supports service-oriented invocation. The PO_REQUISITION constant, which is relevant to searches for "po_requisition," indicates the package's role in converting planned requisition supply into purchase requisition documents in Purchasing. Because the package is referenced by three other packages, its routines function as a shared release engine within the ASCP codebase. Modifications should be made cautiously, as release logic affects downstream purchasing and manufacturing documents.