Results for “msd_ws_dem_rename_forecast”

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

Overview

The APPS.MSD_WS_DEM_RENAME_FORECAST package body is a component of the Oracle E-Business Suite Demand Planning integration layer that governs the interaction between Demantra (Oracle Demantra Demand Management) and the Oracle Advanced Supply Chain Planning / Demand Planning data model within ETRM (Enterprise Territory and Resource Management) releases 12.1.1 and 12.2.2. Its principal business function is to rename, register, and materialize a forecast that has been exported from Demantra into the staging table MSD_DP_SCN_ENTRIES_DENORM. Because Demand Planning scenarios are represented internally by synthetic identifiers rather than user-facing plan names, this package provides the conversion layer that translates a planner-supplied plan name into a persisted scenario record and binds the exported forecast rows to that scenario. In practical terms, the package enables planners to archive prior forecast versions under meaningful names, publish new plan versions, and manage the lifecycle of the associated materialized views used for reporting.

Key Procedures and Functions

• ASSIGN_PLAN_NAME_TO_FORECAST — Assigns a user-specified plan name to a forecast uploaded from Demantra. It creates or replaces an entry in MSD_DP_SCENARIOS, using a hardcoded Demand Plan Id of 5555555 and a scenario sequence starting at 8888888. It records output levels via the data profile name and updates the scenario identifier in MSD_DP_SCN_ENTRIES_DENORM. Returns a status of SUCCESS, ERROR, or INVALID_DATA_PROFILE. Accepts an archive flag to indicate whether the prior forecast should be retained.
• ASSIGN_PLAN_NAME_TO_FORECAST_C — The concurrent-program wrapper for the core assignment routine, enabling invocation from a scheduled concurrent request rather than a direct call.
• ASSIGN_PLAN_NAME_PUBLIC — A publicly exposed entry point that prompts or accepts the plan name and delegates to the assignment logic.
• GET_PLAN_SCENARIO_MEMBER_ID — Resolves the scenario member identifier associated with a plan name, used to link planning hierarchy members to the scenario.
• PUSH_ODS_DATA — Transfers data into the operational data store layer for downstream consumption by planning engines.
• REFRESH_MVIEW and DROP_MVIEW — Manage materialized views tied to the forecast scenario, refreshing them after data publication or dropping them when a plan is retired.
• DELETE_PLAN — Removes a plan and its associated scenario records, supporting forecast cleanup and version pruning.

Tables Accessed

The package reads and writes several core Demand Planning tables through APPS synonyms. MSD_DP_SCENARIOS and its sequence-backed sibling MSD_DP_SCENARIOS_S hold the scenario definition generated for each plan name. MSD_DP_SCENARIO_OUTPUT_LEVELS captures the aggregation levels at which a forecast was exported. MSD_DEM_GROUP_TABLES, MSD_DEM_TRANSFER_QUERY, and MSD_DEM_TRANSFER_QUERY_LEVELS define the transfer queries and grouping used when moving Demantra output. DBA_OBJECTS and DBMS_MVIEW are consulted for materialized view management, while DUAL supports scalar validation and sequencing operations. The staging table MSD_DP_SCN_ENTRIES_DENORM is updated with the resolved scenario identifier.

Usage Notes

This package is typically invoked from the Demand Planning workbench, from concurrent programs that execute the rename-and-publish workflow, or through custom PL/SQL calls that integrate Demantra exports with EBS. Because it writes directly to scenario and denormalized staging tables, it should be run after a Demantra export has completed and before downstream planning or reporting consumes the data. The package is not referenced by any other documented package, so it acts as a top-level integration utility. When modifying or extending it, preserve the hardcoded identifiers and status contract, as callers rely on the SUCCESS, ERROR, and INVALID_DATA_PROFILE return values.