Search Results msd_cs_data_s

Overview

MSD_SCE_RECEIVE_FORECAST_PKG is an APPS-owned PL/SQL package body in Oracle E-Business Suite, classified within ETRM as an OTHER-type API. Its role is to load customer forecast demand into the MSD supply chain planning staging structures used by the Advanced Supply Chain Planning (ASCP) and related MSD schemas. The package receives external customer forecast data, resolves the trading partner and trading partner site identifiers associated with that demand, applies intra-ship lead time offsets, and stores the resulting records in the MSD_CS_DATA family of tables for subsequent planning consumption.

The object is reported with a status of VALID, and it references a defined set of schema objects including FND utilities, MSC item and trading partner views, and the MSD_CS_DATA tables. The presence of the MSD_CS_DATA_S sequence reference indicates the package performs inserts into the customer schedule data table and derives keys from that sequence. No other database object references this package, making it a top-level load routine rather than a shared library component.

Key Procedures and Functions

• RECEIVE_CUSTOMER_FORECAST — The primary entry point. It accepts incoming customer forecast records, validates and translates the source trading partner and item information, and writes the resolved demand into the MSD_CS_DATA and MSD_CS_DATA_HEADERS tables. This procedure embodies the core business function of the package.
• DELETE_OLD_FORECAST — Removes previously staged customer forecast records, typically to prevent duplication when a forecast batch is reloaded or superseded by a newer snapshot.
• GET_SR_TP_SITE_ID — Resolves the trading partner site identifier for a given source, using the MSC_TP_SITE_ID_LID and MSC_TRADING_PARTNER_SITES structures.
• GET_INTRASIT_LEAD_TIME — Determines the in-transit lead time applied to forecast demand, using the MSC_ORGCUSTOMER_SHIP_METHODS_V and related shipping method data so that demand is scheduled with the correct transit offset.

Tables Accessed

• MSD_CS_DATA / MSD_CS_DATA_HEADERS / MSD_CS_DATA_HEADERS_S / MSD_CS_DATA_S — The target staging tables and sequences for customer schedule forecast demand and its header records.
• MSD_CS_DEFINITIONS and MSD_LEVEL_VALUES — Provide the definition and level metadata that govern how incoming forecast columns map to planning levels.
• MSC_SYSTEM_ITEMS, MSC_ITEM_ID_LID — Item validation and inventory item identifier resolution.
• MSC_TRADING_PARTNERS, MSC_TRADING_PARTNER_SITES, MSC_TRADING_PARTNER_MAPS, MSC_TP_SITE_ID_LID — Trading partner, site, and mapping resolution for customer demand.
• MSC_ORGCUSTOMER_SHIP_METHODS_V, MSC_SUP_DEM_ENTRIES, MSC_PLANNING_ORGS — Shipping method, supply/demand entry, and organization context used during lead time and demand processing.
• FND_DATE, FND_FILE, FND_GLOBAL, FND_LOOKUP_VALUES, STANDARD, DUAL — Standard date conversion, file/log output, session context, lookup, and dual utilities.
• MSD_COMMON_UTILITIES, MSD_TRANSLATE_FACT_DATA, MSD_LAST_REFRESH_NUMBER_S — Shared MSD processing helpers and refresh numbering.

Usage Notes

This package is normally invoked by the MSD data collection and forecast loading infrastructure, not directly by end users. It is typically called from concurrent programs or the MSD collection processing chain that stages customer forecast data prior to a planning run. Because it is not referenced by any other database object, it functions as an independent load routine whose results are consumed by downstream planning processes reading the MSD_CS_DATA tables. Customizations should respect the sequence-driven key generation and the refresh numbering conventions enforced through MSD_LAST_REFRESH_NUMBER_S. Direct modification of this package is generally not recommended; extensions should be made through supported collection interfaces.