Results for “msd_dp_scenarios_s”

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

Overview

The APPS.MSD_DP_SCENARIO_PKG package body is an Oracle E-Business Suite database object that supports the administration, loading, and multilingual maintenance of Demand Planning scenario definitions within the Advanced Supply Chain Planning (ASCP) / Demand Planning (DP) product family. The MSD_DP_SCENARIOS entity stores the core scenario records used by planners to model alternative demand and supply conditions, compare outcomes, and publish planning results. This package provides the programmatic layer that Oracle's setup and language utilities rely upon to move scenario data into the E-Business Suite schema, in particular during implementation, environment cloning, and multilingual (MLS) patch or seed data loading.

The object is documented with a status of VALID in the APPS schema and is classified as OTHER within the ETRM metadata. It is a supporting utility rather than a business-transaction API: it does not expose public REST or form-level entry points, and it is not referenced by any other database object. Its functional relevance derives entirely from the tables it manipulates and the Oracle-standard loading utilities it depends upon.

Key Procedures and Functions

The package body exposes three documented procedures. Parameter signatures are not published in the reference metadata and should be confirmed against the deployed source in each environment before use.

• LOAD_ROW — Bulk-loads a single row (or set of rows) of scenario definition data into the underlying scenario tables. It is the primary insertion routine used to seed or migrate MSD_DP_SCENARIOS records from external files, FNDLOAD-style staging, or upgrade scripts.
• TRANSLATE_ROW — Populates and maintains the translated (language-dependent) columns of scenario records in MSD_DP_SCENARIOS_TL, ensuring scenario names and descriptions are available in each installed language.
• ADD_LANGUAGE — Registers a new language dimension for the scenario entity, creating the required language rows so that subsequent TRANSLATE_ROW calls can populate text for that language.

Tables Accessed

The package reads and writes the following objects through APPS synonyms, as documented:

• MSD_DP_SCENARIOS — the base scenario definition table; the principal target of LOAD_ROW.
• MSD_DP_SCENARIOS_S — the sequence-generated identifier table that assigns unique scenario IDs; the user's search term "msd_dp_scenarios_s" maps directly to this object.
• MSD_DP_SCENARIOS_TL — the translated table holding language-specific scenario names and descriptions, manipulated by TRANSLATE_ROW.
• MSD_DEMAND_PLANS — the parent demand plan entity, referenced to validate the plan context under which a scenario is defined.
• FND_LANGUAGES — the Oracle Applications installed-language repository, used by ADD_LANGUAGE to determine which languages are active.
• DUAL and Oracle's STANDARD package — referenced for scalar computations and PL/SQL runtime support.

Usage Notes

MSD_DP_SCENARIO_PKG is not intended for direct invocation by end users or by custom application code. In practice it is called by Oracle's language and seed-data loading framework, where FND_LOAD_UTIL invokes the LOAD_ROW, TRANSLATE_ROW, and ADD_LANGUAGE entry points during NLS installation, patch application, or environment migration. Typical triggers include running the language installation process after a new language is enabled, and executing seed-data uploads that recreate demonstration or template scenarios in a fresh instance.

Because the package is not referenced by any other database object, changes to it carry a limited static blast radius, but they can still affect any concurrent program or external loader that depends on the standard loading contract. Custom code should not reference this package directly; instead, scenario records should be created through the supported Demand Planning application interfaces. Any direct DML against MSD_DP_SCENARIOS, MSD_DP_SCENARIOS_S, or MSD_DP_SCENARIOS_TL bypassing this package risks orphaning translation rows and invalidating sequence assignments. Always confirm the current signature and behavior from the deployed source in the target 12.1.1 or 12.2.2 instance before relying on these routines.