11.11.1.2 Validations in EDMCS

EDMCS automatically enforces two critical validation rules when working with alternative hierarchies inside a dimension.

1. Leaf Node Consistency Across Alternative Hierarchies (Bottom Node Hierarchy Check)

• Purpose: All leaf nodes (lowest-level members without children) must be identical across all alternative hierarchies within the same dimension.
• When it applies: Only when a dimension has more than one alternative hierarchy.
• How it works: If "Product A" exists as a leaf node in one hierarchy, it must also appear as a leaf node in all other hierarchies for that dimension.

  Example: If Product A is a leaf node in one hierarchy, it must also exist as a leaf node in every other alternative hierarchy for that dimension.

No Duplicate Parent–Child Relationships Across Alternative Hierarchies (Intermediate Node Cannot be Shared)

• Purpose: The same parent–child pair cannot appear in more than one alternative hierarchy for the same dimension.
• Allowed: A node can exist in multiple hierarchies, but it must have a different parent in each hierarchy.

  Example: If X is the parent of Y in one hierarchy, this exact X–Y relationship cannot be repeated in another alternative hierarchy for the same dimension.

  Note:

  These validations help ensure that alternative hierarchies are structurally sound, consistent, and logically distinct while maintaining alignment at the leaf-node level.