Search Results msc_items_s

Overview

MSC_IMPORT_FORECAST is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its ETRM classification is OTHER, and its object status is VALID in the documented environment. The package serves the Advanced Supply Chain Planning (ASCP) module of the Oracle Value Chain Planning family, providing the programmatic mechanism by which externally sourced demand data — most commonly forecast figures produced outside the planning schema — is validated and loaded into the MSC staging tables that ASCP engines subsequently consume.

In the ASCP data model, external data is not written directly into the final planning tables. Instead, records are first inserted into staging tables and then processed by a package such as MSC_IMPORT_FORECAST, which normalizes the rows, resolves references, and populates the operational MSC_DEMANDS structure. The presence of both MSC_DEMANDS and MSC_DEMANDS_S in the dependency list confirms that the package participates in the standard pattern of writing primary demand rows and their corresponding shadow or summary records, which downstream planning runs and collection processes rely upon.

Key Procedures and Functions

The ETRM documentation records a single documented program unit within this package body:

• IMPORT_FORECAST — The principal entry point of the package. Based on the metadata, its role is to accept forecast information that has been staged and to transfer that information into the MSC demand tables used by ASCP. The documented metadata does not expose a parameter list, so no signature is asserted here; the procedure is understood to orchestrate the validation and insertion of forecast demand lines. Because the package body is marked VALID and is not referenced by any other database object, this procedure is intended to be called directly by external processes rather than as a dependency of another API.

No additional public procedures or functions are documented for this package body. The dependency listing references APPS.MSC_IMPORT_FORECAST itself, indicating internal or recursive references within the package body rather than a second documented program unit.

Tables Accessed

• MSC_ST_DEMANDS — The staging table for demand records. Rows arrive here first from external interfaces and are the primary source read by IMPORT_FORECAST.
• MSC_DEMANDS — The ASCP demand table. The procedure writes validated forecast records into this structure for use by planning.
• MSC_DEMANDS_S — The companion or shadow table associated with MSC_DEMANDS, maintained in tandem to support planning data retrieval.
• MSC_ITEMS and MSC_ITEMS_S — Item master information used to validate that forecast lines reference valid planning items.
• MSC_SYSTEM_ITEMS — System-level item attributes required to confirm that an item is eligible for forecast demand in the destination organization.
• HZ_PARTIES — The Trading Community Architecture party table, used to resolve customer or party identifiers attached to forecast rows.
• DBMS_MVIEW — Invoked for materialized view refresh operations, ensuring that dependent summaries and planning views reflect the newly imported demand data.
• FND_GLOBAL — The standard EBS applications context package, used to establish the runtime environment (user, responsibility, and application) during processing.

Usage Notes

MSC_IMPORT_FORECAST is typically invoked from the ASCP collection and data-loading flow rather than interactively. Common invocation paths include concurrent programs that load forecast data through the ASCP Open Interface, custom PL/SQL wrappers written by implementers to bulk-load forecast figures from external planning systems, and ETL routines that stage rows in MSC_ST_DEMANDS before calling the import. It may also be reached indirectly through the standard Import Demand Schedule or forecast upload interfaces.

Because the package reads staging data and writes directly into planning tables, it should be executed in the correct application and responsibility context so that FND_GLOBAL is populated consistently. The dependency on DBMS_MVIEW indicates that materialized views related to demand planning must be refreshable at the time of execution, and the absence of any object referencing this package confirms that it sits at the top of its dependency chain and must be scheduled or called explicitly. As with all ASCP data-loading utilities, backups of the affected staging tables should be taken before large imports in a production environment.