Search Results msc_cl_publish




Overview

MSC_CL_PUBLISH is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the outbound publication of supply chain planning and collaborative planning data collected within the Advanced Supply Chain Planning (ASCP) and Collaborative Planning modules. Its name follows the MSC_CL_* naming convention, where "CL" denotes Collaborative Planning and "PUBLISH" reflects the package's role in exposing collected planning data to external consumers or dependent planning processes.

The package operates within the Oracle Data Warehouse / planning data model, reading staging, company, supplier, and customer records and publishing them so downstream planning engines, trading partner exchanges, or refresh mechanisms can consume consistent data. In the ETRM 12.2.2 metadata it is classified as an "OTHER" API, indicating it is not a public, documented interface intended for direct customer invocation, but rather an internal utility supporting the planning collection and publication cycle. It reports a VALID status in both 12.1.1 and 12.2.2, confirming availability across releases.

Key Procedures and Functions

The documented interface exposes a single procedure: PUBLISH. This procedure performs the core publication activity of the package, taking the collected collaborative planning and supply/demand data and making it available for downstream use. It encapsulates the logic required to consolidate and distribute planning records, and is the entry point that callers (internal Oracle planning programs or scheduled collection processes) invoke.

No additional procedures or functions are documented in the ETRM metadata. The package body contains further private logic supporting PUBLISH, but these are not exposed as documented APIs and should not be relied upon for customization.

Tables Accessed

MSC_CL_PUBLISH reads from a broad set of planning and reference tables, resolved through APPS synonyms. The primary dependencies include:

Usage Notes

MSC_CL_PUBLISH is an internal Oracle package with no documented references from other APPS packages ("referenced by 0 other packages" in the ETRM data), meaning it is typically invoked through Oracle's own planning collection and collaborative planning concurrent programs rather than from customer-written code. It should not be called directly from custom concurrent programs or forms unless Oracle explicitly exposes it as a public API.

Typical invocation occurs during the collaborative planning collection and publication cycle, where PUBLISH runs after collection has populated the MSC staging and planning tables. Because it depends on profile options and instance/organization setup, the correct operating unit and planning instance context must be established before invocation. Customizations should avoid modifying the package body, as patches and upgrades may overwrite it; any extensions should be implemented through supported integration points or by copying data from the published tables rather than altering this package.