Search Results import_forecast

Overview

MSC_IMPORT_FORECAST is a PL/SQL package owned by the APPS schema that supports the import of forecast data into the Oracle Advanced Supply Chain Planning (ASCP) and Demand Planning staging and planning tables. The package header carries the RCS identifier $Header: MSCIFSTS.pls 120.1 2005/06/21 02:53:38 appldev ship $, indicating that the source file has remained stable across the 11i and Release 12 code lines and is present in both Oracle EBS 12.1.1 and 12.2.2. Its primary purpose is to accept staged forecast records and load them into the MSC tables that the planning engine consumes, resolving item and party references along the way. The package is classified as "OTHER" in the ETRM data model, meaning it is a utility/loader package rather than a callable business API exposed through a formal interface layer.

Key Procedures and Functions

The package exposes a single documented procedure:

• IMPORT_FORECAST — Performs the actual forecast load. It receives a request identifier so that concurrent processing status and logging can be associated with a specific concurrent program run, and it returns a conventional EBS error buffer and return code through which the caller inspects success or failure. The procedure orchestrates the validation and insertion of forecast demand rows into the MSC demand tables and refreshes dependent materialized views as required. No further parameters beyond the request ID, error buffer, and return code are declared in the documented package specification; parameter lists should not be assumed beyond this signature.

Tables Accessed

The package references the following tables, all resolved through APPS synonyms:

• MSC_ST_DEMANDS — The staging table into which external forecast rows are first collected before validation and promotion into the live planning demand tables.
• MSC_DEMANDS and MSC_DEMANDS_S — The base and translated demand tables that hold the imported forecast entries consumed by the planning engine.
• MSC_ITEMS, MSC_ITEMS_S, and MSC_SYSTEM_ITEMS — Used to resolve and validate the item, item description, and source system item references associated with each forecast row.
• HZ_PARTIES — Used to validate or derive customer and party identifiers attached to forecast demand records.
• DBMS_MVIEW — Invoked to refresh materialized views that must remain consistent after the import, ensuring downstream planning queries see current data.

Usage Notes

MSC_IMPORT_FORECAST is typically invoked from a concurrent program or a custom PL/SQL wrapper rather than from a standard Oracle Forms screen. Because it requires a concurrent request ID and emits the standard ERRBUF/RETCODE pair, it follows the common EBS concurrent-processing convention and is well suited to being registered as a stored procedure concurrent program or called from a host program script. Typical invocation scenarios include loading forecast data from external systems, refreshing forecast data staged through interface tables, and scheduled batch runs that populate MSC_DEMANDS ahead of a planning engine run. The package is referenced by no other packages according to the ETRM metadata, so dependencies run only in the inbound direction onto the listed tables. When customizing, callers should treat the procedure as a black-box loader: supply the request ID, capture the return code, and verify results in the MSC demand tables rather than relying on intermediate state.