Search Results publish_order_forecast

Overview

MSC_X_CP_FLOW is a collaborative planning integration package in the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) and Supply Chain Event Management (SCEM) modules. It is owned by the APPS schema and is defined with the AUTHID CURRENT_USER privilege, meaning its SQL executes under the privileges of the calling user rather than the package owner. The package header is versioned as MSCXCPFS.pls 115.7, with the last check-in dated 2003/08/05, reflecting the long-standing and stable nature of this integration code across the 12.1.1 and 12.2.2 releases.

The package's core purpose is to bridge Oracle Workflow with the SCEM and ASCP planning engines and with external trading partners. It provides thin wrapper procedures that launch the SCEM and ASCP engines, receive forecast and supplier capacity data from external partners, and publish supply commits and order forecasts back to partners. These wrappers are invoked as Workflow function activities, which is why the majority of the documented procedures share the standard Workflow callback signature (itemtype, itemkey, actid, funcmode, resultout).

Key Procedures and Functions

The package exposes fifteen documented procedures and functions, organized into several functional groupings.

• START_SCEM_ENGINE_WF and LAUNCH_SCEM_ENGINE — The first starts the Workflow process that runs the SCEM engine; the second is the Workflow function activity that actually launches the SCEM engine and returns a result to Workflow.
• START_DP_RECEIVE_FORECAST_WF and DP_RECEIVE_FORECAST — Initiate and execute the receipt of forecast data from a trading partner (DP, demand planning), using a customer, horizon, responsibility key, and recipient parameters.
• RECEIVE_SUPPLIER_CAPACITY_WF and RECEIVE_SUPPLIER_CAPACITY — Initiate and execute the receipt of supplier capacity information over a defined horizon window.
• START_ASCP_ENGINE_WF and LAUNCH_ASCP_ENGINE — Initiate and launch the ASCP planning engine. START_ASCP_ENGINE_WF accepts a constrained plan flag, while LAUNCH_ASCP_ENGINE is the Workflow callback that performs the launch. This is the procedure targeted by the search term "launch_ascp_engine".
• AUTO_SCEM_MODE — A function returning a numeric indicator of whether automatic SCEM mode is enabled.
• PUBLISH_SUPPLY_COMMITS_WF and PUBLISH_SUPPLY_COMMITS — Initiate and execute the publication of supply commit data for a given plan to trading partners.
• PUBLISH_ORDER_FORECAST_WF and PUBLISH_ORDER_FORECAST — Initiate and execute the publication of order forecast data to partners.
• PRINT_DEBUG_INFO and PRINT_USER_INFO — Diagnostic utilities that write debug and user context information for troubleshooting.

Tables Accessed

The package references the following tables via APPS synonyms:

• MSC_PLANS — Defines the plan whose engine is launched and whose supply commits are published.
• MSC_TRADING_PARTNERS and MSC_TRADING_PARTNER_MAPS — Identify and map external trading partners for forecast and capacity exchange.
• MSC_COMPANY_RELATIONSHIPS, MSC_COMPANY_USERS, and MSC_DESIGNATORS — Determine the companies, users, and designated contacts participating in collaborative planning.
• MSC_SUP_DEM_ENTRIES_S — Stores supply and demand entries used by the planning and publish processes.
• FND_USER, FND_RESPONSIBILITY, and WF_LOCAL_ROLES — Resolve the invoking user, responsibility, and Workflow role context.
• DUAL — Used for singleton queries and simple evaluations.

Usage Notes

MSC_X_CP_FLOW is not intended for direct invocation by end users. Its procedures are registered as Workflow function activities within the collaborative planning Workflow processes, and they are triggered when those processes execute, for example when a planner chooses to launch the ASCP or SCEM engine from the planning application, or when a scheduled collaborative planning process exchanges data with a trading partner. LAUNCH_ASCP_ENGINE in particular is called by the Workflow engine with the standard activity parameters and returns a result code that directs the Workflow branch.

Because the package is referenced by five other packages, extensions or customizations that call these procedures should preserve the documented signatures to avoid invalidating dependent Workflow definitions. The package is a stable, long-lived component of the ASCP collaborative planning infrastructure, and its diagnostic procedures PRINT_DEBUG_INFO and PRINT_USER_INFO can be used when investigating Workflow or integration failures.