Search Results msd_sce_receive_forecast_pkg




Overview
Explore in AI Chat

Overview

MSD_SCE_RECEIVE_FORECAST_PKG is an APPS-owned PL/SQL package in Oracle E-Business Suite that supports the inbound receipt of customer forecast data within the Supply Chain Execution (SCE) and Advanced Supply Chain Planning (ASCP) integration flow. Its primary business function is to consume external customer forecast transmissions, stage that data in the MSD (MSD_CS_*) tables, and reconcile it against prior forecast records so that planning engines operate on a clean, current demand picture. The package is classified as OTHER within the ETRM repository, indicating it is an internal integration utility rather than a formally published open API.

The user query delete_old_forecast corresponds directly to the DELETE_OLD_FORECAST procedure, which is the housekeeping entry point that purges superseded forecast rows ahead of, or in conjunction with, a fresh forecast load.

Key Procedures and Functions

The package exposes four documented program units:

  • RECEIVE_CUSTOMER_FORECAST — The main entry point for loading a customer forecast into the SCE staging structure. It accepts a designator, order type, organization code, planner code, item, customer, and customer site, together with a horizon start and horizon day count. It drives the receipt and validation of incoming forecast records for the requested scope.
  • DELETE_OLD_FORECAST — Purges stale forecast data for a specified source instance, concurrent/CS definition, designator, organization, item, customer, and customer site, bounded by a horizon start and horizon end date and qualified by a "new fresh number." This procedure ensures obsolete versions do not persist and interfere with planning. The inclusion of item, customer, and customer site parameters reflects an enhancement delivered under Bug 4710643, tightening the deletion scope to specific demand entities.
  • GET_SR_TP_SITE_ID — A lookup function returning the trading partner site identifier given a customer site and source instance identifier.
  • GET_INTRASIT_LEAD_TIME — A lookup function returning the in-transit lead time between a source instance/organization and a destination location.

Tables Accessed

The package reads and writes a defined set of APPS-synonym tables. The MSD_CS_DATA, MSD_CS_DATA_S, MSD_CS_DATA_HEADERS, MSD_CS_DATA_HEADERS_S, and MSD_CS_DEFINITIONS tables form the staging and definition layer for collected supply chain data and hold the forecast records created or removed by the two main procedures. MSD_LEVEL_VALUES supplies level and level-value context. MSC_SYSTEM_ITEMS provides item, UOM, and planner code attributes, while FND_LOOKUP_VALUES supplies lookup meanings used in validation or translation.

Trading partner resolution relies on MSC_TRADING_PARTNERS, MSC_TRADING_PARTNER_SITES, MSC_TRADING_PARTNER_MAPS, and the MSC_TP_SITE_ID_LID and MSC_ITEM_ID_LID interfaces. Planning organization context is drawn from MSC_PLANNING_ORGS, and supply/demand entries are held in MSC_SUP_DEM_ENTRIES.

Usage Notes

This package is an internal integration component invoked by the SCE forecast collection process rather than by end users directly. It is typically called from concurrent program logic or from other PL/SQL packages that orchestrate forecast receipt; the metadata records the package as referenced by one other package. Custom code should not call these procedures unless replicating the standard forecast load, since the procedures depend on correctly populated staging and definition records. The DELETE_OLD_FORECAST procedure is commonly triggered as part of a scheduled forecast refresh cycle to remove outdated demand before new data is committed.