Search Results display_message

Overview

MSD_VALIDATE_DEMAND_PLAN is an Oracle EBS Advanced Planning and Demand Planning validation package owned by APPS. Its central purpose is to verify that a demand plan definition is internally consistent and complete before it is consumed by downstream planning or reporting processes. The package body encapsulates a large collection of private validation routines, each responsible for checking a discrete aspect of plan integrity: required dimensions, user and USD dimensions, dimension hierarchies and level values, input parameters, fact data, scenarios, time data, calendars, minimum time levels, units of measure, currency conversion data, output levels, and ISO organizations. When a user attempts to activate, execute, or generate output for a demand plan, these checks determine whether the plan is viable or whether validation errors must be reported back.

Key Procedures and Functions

The documented public entry point is VALIDATE_DEMAND_PLAN. It serves as the orchestrating routine that invokes the package's private validation procedures in sequence and returns an overall status. Its parameter list is intentionally not reproduced here, but its role is to accept a demand plan identifier and drive the complete validation cycle. The private procedures declared in the package body define the granular checks:

• chk_required_dim, chk_usr_dim, chk_usd_dim – verify that the plan has the mandatory, user-defined, and United States dimension members configured.
• chk_dim_hier, chk_dim_lvl_val – validate dimension hierarchy structure and the consistency of dimension level values.
• chk_input_param – validates plan input parameters, including multiple-flag and allocation/aggregation rules.
• chk_fact_data, chk_scenarios, chk_scen_events – confirm that fact data exists for the plan, that scenarios are defined, and that scenario events are internally consistent.
• chk_time_data, chk_calendars, chk_min_time – validate the time dimension, associated calendars, and that minimum time levels exist for each applicable level.
• chk_uom_data, chk_curr_data – verify units of measure and currency conversion data required by the plan.
• chk_output_levels, chk_dup_dim_output_levels – confirm output levels are defined and that no duplicate dimension output levels exist.
• chk_iso_org, chk_iv_org – validate inventory organization and ISO organization associations.
• update_plan – updates the plan record, typically to record the validation return code or status.

Helper routines chk_ip_multiple and chk_ip_allo_agg support input-parameter validation.

Tables Accessed

The package reads and writes a range of Demand Planning and shared tables, accessed through APPS synonyms. MSD_DEMAND_PLANS is the primary plan-definition table read and updated by the package. Dimension and level information is drawn from MSD_DP_DIMENSIONS and MSD_CS_CLMN_DIM_DTLS, MSD_CS_DEFN_DIM_DTLS, and MSD_CS_DEFN_COLUMN_DTLS. Plan configuration is validated against MSD_DP_PARAMETERS, MSD_DP_CALENDARS, MSD_DP_SCENARIOS, MSD_DP_SCENARIO_EVENTS, MSD_DP_PRICE_LISTS, MSD_DP_ISO_ORGANIZATIONS, and MSD_CURRENCY_CONVERSIONS. MSC_PLANS and MSC_APPS_INSTANCES provide cross-reference to the broader MSC planning schema and instance configuration.

Usage Notes

MSD_VALIDATE_DEMAND_PLAN is invoked when a demand plan must be validated before use, typically from Demand Planning setup or plan-maintenance flows and from concurrent processes that prepare a plan for execution. Custom code generally calls the public VALIDATE_DEMAND_PLAN procedure, passing the plan identifier; the private procedures are not exposed outside the package. The user search term "display_message" reflects the package's error-reporting behavior: validation failures are surfaced as messages to the caller, enabling the invoking form or program to display actionable feedback to the planner. Because the package is referenced by no other documented packages, it functions as a leaf-level validation utility rather than a shared API.