Search Results c_associate_parameter




Overview
Explore in AI Chat

Overview

MSD_WS_DEM_RENAME_FORECAST is an Oracle EBS APPS-owned PL/SQL package that supports the integration between Oracle Demantra Demand Management and Oracle Advanced Supply Chain Planning / Demand Planning within the E-Business Suite. Its principal business function is to assign a user-specified plan name to a forecast that has been exported from Demantra and uploaded into the EBS staging table MSD_DP_SCN_ENTRIES_DENORM. In effect, the package converts the anonymous, profile-driven Demantra forecast output into a named, identifiable plan record that planners can select and work with inside the EBS planning applications.

The package header carries the RCS header identifier MSDWDRFS.pls 120.7.12010000.1, dated 2008/05/01, and defines two constants: C_DUMMY_SCENARIO_ID_OFFSET (8888888), used as the base offset for generating scenario identifiers for newly named plans, and C_ASSOCIATE_PARAMETER ('Assign Plan Name'), which identifies the integration parameter that associates the rename operation with the Demantra data profile. The package is classified as OTHER in the ETRM API registry and is not referenced by any other documented package, indicating it is a leaf-level utility consumed directly by the planning integration layer.

Key Procedures and Functions

The ETRM metadata documents eight procedures and functions. Only the first two are expanded in the available source excerpt; the remainder are listed by name in the package header comment block and the documented procedure inventory.

  • ASSIGN_PLAN_NAME_TO_FORECAST — The core routine. It assigns a user-specified name to the forecast uploaded from Demantra into MSD_DP_SCN_ENTRIES_DENORM. It creates or replaces an entry in MSD_DP_SCENARIOS using a hardcoded demand plan identifier (5555555) and a scenario identifier drawn from a sequence starting at the offset constant 8888888. Using the supplied data profile name, it populates MSD_DP_SCENARIO_OUTPUT_LEVELS with the levels at which the forecast was exported, then updates the scenario identifier on the denormalized entries table. It returns a status of SUCCESS, ERROR, or INVALID_DATA_PROFILE.
  • ASSIGN_PLAN_NAME_PUBLIC — A public wrapper variant that accepts user, responsibility, application, security group, and language context in addition to the plan name, data profile name, and archive flag. It provides the entry point used when the operation must execute under a specific EBS security context.
  • ASSIGN_PLAN_NAME_TO_FORECAST_C — A companion procedure in the same assignment family, typically the internal callable form used by concurrent or programmatic invocation.
  • GET_PLAN_SCENARIO_MEMBER_ID — Resolves the scenario member identifier associated with a plan, supporting the downstream mapping between the named plan and its scenario definition.
  • REFRESH_MVIEW — Refreshes the materialized view(s) underpinning the forecast staging and reporting layer, ensuring that the newly named plan data is materialized and visible to planning queries. This is the object surfaced when users search for "refresh_mview" in the ETRM repository.
  • DROP_MVIEW — Removes the materialized view constructed for a plan, providing cleanup when a plan or its staging artifacts are no longer required.
  • PUSH_ODS_DATA — Propagates operational data store content, moving staged forecast data into the structures consumed by downstream planning processes.
  • DELETE_PLAN — Removes a named plan and its associated scenario records, complementing the assignment and view-management routines.

Tables Accessed

The package operates against the following documented tables through APPS synonyms:

  • MSD_DP_SCENARIOS and MSD_DP_SCENARIOS_S — The scenario definition and its sequence, where new named plans are created or replaced.
  • MSD_DP_SCENARIO_OUTPUT_LEVELS — Stores the output levels at which the forecast was exported, populated from the data profile name.
  • MSD_DP_SCN_ENTRIES_DENORM — The denormalized forecast staging table whose scenario identifier is updated to bind uploaded Demantra rows to the new plan name.
  • MSD_DEM_GROUP_TABLES, MSD_DEM_TRANSFER_QUERY, and MSD_DEM_TRANSFER_QUERY_LEVELS — Demantra transfer/grouping metadata used to determine how exported forecast data is organized and queried.
  • DBA_OBJECTS — Consulted to verify the existence and status of materialized views before refresh or drop operations, supporting REFRESH_MVIEW and DROP_MVIEW.
  • DBMS_MVIEW — The Oracle-supplied package invoked to perform the actual materialized view refresh, also used by the refresh and drop routines.
  • DUAL — Used for single-row evaluations and sequence/constant selection.

Usage Notes

MSD_WS_DEM_RENAME_FORECAST is invoked as part of the Demantra-to-EBS forecast publication flow. It is typically called from the planning integration concurrent programs or from the Demantra integration web service layer immediately after a forecast has been exported and loaded into the MSD_DP_SCN_ENTRIES_DENORM staging table. The ASSIGN_PLAN_NAME_PUBLIC entry point is the usual choice when the call must carry an EBS user, responsibility, application, security group, and language context. Because the package is not referenced by any other documented package, it should be treated as a top-level integration utility rather than a shared library routine.

Administrators and technical consultants searching for refresh_mview reach this package because REFRESH_MVIEW and DROP_MVIEW manage the materialized views that expose the newly named plan. When troubleshooting missing or stale plan data after a Demantra export, the materialized view refresh step performed by REFRESH_MVIEW is a common point of investigation. The package is available in both 12.1.1 and 12.2.2, with the 12.2.2 ETRM registry listing the same eight documented routines; no changes to the public interface are indicated between the two releases for the procedures described here.