Search Results msd_validate_demand_plan




Overview
Explore in AI Chat

Overview

The APPS.MSD_VALIDATE_DEMAND_PLAN package is a PL/SQL validation utility within the Oracle E-Business Suite Advanced Supply Chain Planning and Demand Planning module. Its object name and the collection of tables it references indicate that it is responsible for validating the configuration and structural integrity of a demand plan before the plan is executed, published, or consumed by downstream planning processes. In ETRM terms the package is classified as OTHER, meaning it is an internal support routine rather than a public, published API.

The package resides in the APPS schema and holds a status of VALID in both the 12.1.1 and 12.2.2 environments. Its dependency graph is deliberately narrow: it relies only on SYS.STANDARD, and no other APPS packages reference it. This self-contained nature confirms that it is a leaf-level validation module invoked indirectly, typically by demand planning setup forms or by a plan-validation concurrent program rather than through a documented public interface.

Key Procedures and Functions

ETRM documents a single callable unit for this package:

  • VALIDATE_DEMAND_PLAN — The sole documented procedure. Its purpose is to perform the validation logic for a specified demand plan, checking that the plan's associated definitions, dimensions, calendars, currencies, and parameters are internally consistent and complete. Because the metadata does not publish a parameter list, the exact signature is not reproduced here; callers should treat it as an internal routine whose arguments are determined by the MSD demand planning framework.

No functions or additional overloaded procedures are documented for this package. The absence of published parameters is consistent with its OTHER classification, indicating that Oracle does not guarantee a stable public interface.

Tables Accessed

The package reads from a broad set of MSD tables that collectively define a demand plan:

Usage Notes

Because MSD_VALIDATE_DEMAND_PLAN is referenced by no other APPS package, it is not part of a documented integration chain. It is most likely invoked from the Demand Planning setup forms when a planner saves or activates a plan, or from an internal validation step within the plan-generation concurrent program. Custom code should not call this package directly: the lack of a published parameter list and its OTHER classification mean the signature may change. Administrators encountering the name during diagnostic queries should treat it as a supporting validation routine whose failure typically indicates incomplete dimension, definition, or parameter setup for the affected demand plan.