Search Results msd_dimensions




Overview
Explore in AI Chat

Overview

APPS.MSD_OBJECTS_V is a consolidated Oracle E-Business Suite dictionary view that unifies several Advanced Supply Chain Planning and Demand Planning metadata sources into a single, uniform object registry. Its principal purpose is to expose every selectable planning entity — dimension levels, hierarchies, dimension lookup values, and demand plans — through one consistent three-column projection of object_id, object_name, and object_type. This standardization allows integration components, concurrent programs, and reporting tools to populate pick lists and resolve identifiers without issuing separate queries against each underlying planning table.

The view is particularly significant for users searching on the term msd_dimensions, because the MSD_DIMENSIONS lookup type supplies one full branch of its UNION. Dimension definitions are surfaced here as first-class planning objects, enabling planning setup screens and third-party integrations to present dimensions alongside levels, hierarchies, and demand plans in a single homogeneous list.

Underlying Base Objects

The documented definition is a four-branch UNION. Each branch maps a source table to the canonical object_type value:

  • MSD_LEVELS (synonym) → object_type = '5'. Restricted to rows where PLAN_TYPE IS NULL, isolating shared level definitions from plan-specific ones.
  • MSD_HIERARCHIES (synonym) → object_type = '4'. Also filtered on PLAN_TYPE IS NULL.
  • FND_LOOKUP_VALUES_VL (view) → object_type = '3'. Filters on LOOKUP_TYPE = 'MSD_DIMENSIONS', which is the branch that registers dimensions. Because it reads the MLS-enabled lookup view, dimension meanings respect the session language.
  • MSD_DEMAND_PLANS (synonym) → object_type = '2'. Excludes liability-type plans via NVL(PLAN_TYPE,'-1') <> 'LIABILITY'.

All branches normalize their numeric primary keys to character form using TO_CHAR, ensuring the UNION columns are type-compatible.

Key Columns

Common Use Cases and Queries

The view is typically consumed to build selection lists or to resolve an object name from a stored identifier. Filtering by OBJECT_TYPE limits results to a single family; omitting the filter returns the complete registry.

Retrieve all dimension definitions:

  • SELECT object_id, object_name FROM apps.msd_objects_v WHERE object_type = '3' ORDER BY object_name;

Resolve a stored identifier to its display name:

  • SELECT object_name FROM apps.msd_objects_v WHERE object_id = :p_id AND object_type = :p_type;

Validate a dimension lookup code before assignment:

  • SELECT COUNT(*) FROM apps.msd_objects_v WHERE object_type = '3' AND object_id = :dimension_code;

Because the view joins four independent sources, queries benefit from an explicit OBJECT_TYPE predicate; this avoids evaluating irrelevant branches and prevents identifier collisions, since IDs are unique only within a given type.