Search Results msd_sce_publish_forecast_pkg




Overview
Explore in AI Chat

Overview

APPS.MSD_SCE_PUBLISH_FORECAST_PKG is a PL/SQL package in the Oracle E-Business Suite APPS schema that supports Supply Chain Exchange (SCE) forecast publishing within the Advanced Supply Chain Planning (ASCP) and Collaborative Planning footprint. Its business purpose is to extract forecast demand information from the MSC staging and planning tables, transform that data into supplier or trading-partner demand entries, and publish the resulting forecast to external supply chain partners. In effect the package acts as the outbound bridge between Oracle's planning engine and downstream trading partners who need visibility of committed or planned demand.

The package carries VALID status and is classified as OTHER under the API classification scheme, confirming that it is an internal support package rather than a formally published open interface. It is owned by APPS, depends on MSC planning tables and FND lookups, and is referenced by no other packages, meaning it is typically invoked as a top-level unit of work rather than as a called utility.

Key Procedures and Functions

The ETRM documentation records five packaged subprograms:

  • PUBLISH_CUSTOMER_FORECAST — The principal driver procedure. It orchestrates the end-to-end publication of customer forecast data, resolving the relevant companies, sites, items, and demand rows before building the outbound supplier demand records.
  • EXPLODE_DATES — Expands the forecast horizon across the planning bucket dates so that demand quantities can be assigned to individual daily, weekly, or periodic buckets as required by the planning calendar.
  • GET_OPTIONAL_INFO — Retrieves ancillary or configurable attribute information needed during publication, typically sourced from lookups and descriptive flexfield data, so the outbound record is complete.
  • INSERT_INTO_SUP_DEM — Performs the physical write into the supplier demand entries table, materializing the forecast lines that will be consumed externally.
  • DELETE_OLD_FORECAST — Cleanses previously published forecast records that are obsolete or superseded, preventing duplication when a forecast is republished.

Tables Accessed

The package reads from several MSC planning objects and writes to the supplier demand entries tables. Reference data comes from FND_LOOKUP_VALUES (lookup codes), MSC_COMPANIES and MSC_COMPANY_SITES (organization and site definitions), MSC_TRADING_PARTNER_SITES and MSC_TRADING_PARTNER-like mapping tables (MSC_TP_ID_LID, MSC_TP_SITE_ID_LID) that translate internal identifiers to partner identifiers. Item and demand detail is drawn from MSC_DEMANDS, MSC_SYSTEM_ITEMS, MSC_ITEMS, MSC_ITEM_CUSTOMERS, MSC_PLANNING_ORGS, MSC_COMPANY_RELATIONSHIPS, and MSC_CL_REFRESH_S. Output is written to MSC_SUP_DEM_ENTRIES and its child/interface table MSC_SUP_DEM_ENTRIES_S.

Usage Notes

Because the package is not referenced by any other package and is not a published interface, it is normally driven by a concurrent program, a scheduled planning request, or a custom wrapper that calls PUBLISH_CUSTOMER_FORECAST with the appropriate organization, partner, and planning parameters. Sites running 12.1.1 or 12.2.2 should treat it as an internal dependency of the SCE forecast publishing flow rather than a callable API. Customizations that invoke it directly must respect the ordering of DELETE_OLD_FORECAST before INSERT_INTO_SUP_DEM to avoid duplicate supplier demand entries, and must ensure the MSC collection has been refreshed so that MSC_DEMANDS and MSC_ITEMS reflect current planning results.