Results for “msd_dp_scenario_pkg”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSD_DP_SCENARIO_PKG is an Oracle Application Object Library (APPS) schema PL/SQL package that belongs to the Oracle Demand Planning (MSD) module within Oracle E-Business Suite. Its primary business function is to support the data-driven loading and multilingual translation of demand planning scenario definitions — the named planning scenarios used by planners to model, compare, and publish demand forecasts across products, customers, and time horizons. The package is classified under the ETRM metadata as an "OTHER" API type, meaning it is not part of a formally published public interface but rather an internal utility package consumed by Demand Planning components. It operates against the MSD_DP_SCENARIOS base table, its MLS-enabled translation tables, and the FND_LANGUAGES reference table. In Oracle EBS 12.1.1 and 12.2.2, this package is a valid, compiled object owned by APPS and depends only on the SYS.STANDARD package, indicating a lightweight, self-contained implementation focused on row-level data manipulation and translation handling.

Key Procedures and Functions

The documented metadata exposes three procedures within MSD_DP_SCENARIO_PKG:

• LOAD_ROW — Inserts or maintains a single demand planning scenario row, populating the scenario definition records that the Demand Planning engine relies upon. It acts as the internal DML wrapper for scenario persistence.
• TRANSLATE_ROW — Manages the translated (MLS) attributes of a scenario, writing language-specific name and description values into the TL table for the session or specified language.
• ADD_LANGUAGE — Installs translation rows for any language that lacks them, ensuring every active scenario has a corresponding entry in the translation table for newly enabled or installed languages.

These procedures follow the standard Oracle seed-data and MLS maintenance pattern found throughout APPS-based loaders. No public parameter lists are documented; callers are expected to use the procedures as part of controlled seeding or upgrade scripts rather than ad-hoc invocation.

Tables Accessed

The package references the following tables via APPS synonyms:

• MSD_DP_SCENARIOS — The base scenario definition table; the primary target of LOAD_ROW.
• MSD_DP_SCENARIOS_S — The MLS shadow table that stores language-independent keys and links each scenario to its translated rows.
• MSD_DP_SCENARIOS_TL — The translation table holding language-specific names and descriptions; written by TRANSLATE_ROW and ADD_LANGUAGE.
• MSD_DEMAND_PLANS — The demand plan master table, referenced to associate a scenario with an owning plan.
• FND_LANGUAGES — Oracle Applications' installed-language registry, used by ADD_LANGUAGE to determine which languages require translation rows.
• DUAL — Used for single-row PL/SQL constructs and sequence or expression evaluation.

The reference list confirms the package is a data-seeding utility rather than a runtime forecasting routine; it writes configuration data that the planning engine later consumes.

Usage Notes

MSD_DP_SCENARIO_PKG is not invoked by Oracle Forms or standard concurrent programs during normal end-user operation. It is typically executed during implementation, patching, or language installation, when demand planning scenarios must be seeded or their translations synchronized. The ADD_LANGUAGE procedure in particular is characteristic of post-install or post-patch language activation scripts that guarantee MLS completeness. Because ETRM reports zero referencing packages, MSD_DP_SCENARIO_PKG has no downstream dependents inside the APPS schema — a strong indication that it is called only from standalone SQL*Plus scripts, Oracle Application Object Library seed routines, or upgrade driver scripts. Custom integrators requiring programmatic creation of demand planning scenarios may call these procedures directly, but given the absence of a documented public parameter interface, direct database inserts or the supported Demand Planning APIs are generally preferable. The package's only declared dependency is SYS.STANDARD, confirming it uses no external application utilities and should compile and execute on both 12.1.1 and 12.2.2 without additional prerequisites.