Search Results msd_level_values_u3

Overview

APPS.MSD_BOM_COMPONENTS_V is a reporting and integration view in Oracle E-Business Suite (12.1.1 / 12.2.2) that exposes bill-of-material (BOM) component data in a flattened, denormalized form suitable for consumption by Oracle Advanced Supply Chain Planning (ASCP) and related planning engines. It joins the MSC (Advanced Planning) mirror tables for BOMs and system items against the MSD level-value hierarchy tables, producing a single row per qualified component relationship. The view resolves bill structure context — parent assemblies, components, and their hierarchical level values — while applying planning-profile and item-attribute filters that determine which components are eligible for planning. Because it depends on the planning collection mirror (MSC_*) rather than the operational BOM tables directly, the view reflects the state of data as of the most recent planning data collection run, not the live operational tables.

Underlying Base Objects

The view is built on several documented base objects. The core data sources are MSC_BOMS and MSC_BOM_COMPONENTS, which hold the collected bill headers and component lines respectively. These are joined to two aliased instances of MSC_SYSTEM_ITEMS — one for the using (parent) assembly and one for the component item. Structural context is supplied by three aliased references to MSD_LEVEL_VALUES (mv1, mv2, mv3), which resolve level primary keys and level values for the hierarchy. FND_PROFILE (package) provides the MSD_PLANNING_PERCENTAGE profile option, and MSC_APPS_INSTANCES supplies instance (organization) validation. The MSD_COMMON_UTILITIES package furnishes the uom_conv function used to normalize usage quantities into a common unit of measure. DUAL is referenced in an inline subquery that materializes the profile value. All MSC/MSD objects are synonyms in the APPS schema over the planning mirror tables.

Key Columns

The view exposes three paired level columns — (mv1.level_pk, mv1.level_value), (mv2.level_pk, mv2.level_value), and (mv3.level_pk, mv3.level_value) — representing the hierarchical level context anchored on organization/instance (level_id 7), the parent item (level_id 1), and additional structural levels. Planning semantics are carried by planning_factor and by a decoded usage quantity expression that divides usage_quantity by the component yield factor, converting via MSD_COMMON_UTILITIES.uom_conv against the component item's inventory_item_id and uom_code. Effectivity_date and disable_date define the component's validity window, while optional_component flags whether the component is optional. The final decoded column returns 'Y' or 'N' based on whether a matching MSC_APPS_INSTANCES.validation_org_id exists, indicating whether the owning organization is a validated planning instance.

Common Use Cases and Queries

Typical uses include extracting planning-eligible BOM structures, validating component effectivity, and reconciling collected BOM data against planning results. A representative query retrieves components for a given organization and parent item:

• SELECT level_value, planning_factor, optional_component, effectivity_date, disable_date FROM apps.msd_bom_components_v WHERE ...
• Filtering by effectivity_date range to isolate currently effective components.
• Joining back to MSC_SYSTEM_ITEMS to enrich component descriptions.
• Auditing optional_component = 'Y' rows to validate planning assumptions.

Because the view filters on profile values (MSD_PLANNING_PERCENTAGE) and item planning attributes (mrp_planning_code, pick_components_flag, ato_forecast_control, bom_item_type), results reflect the same eligibility logic used by the planning engine. Queries that reference msd_level_values_u3 typically do so to interrogate the underlying level hierarchy rather than the view output, since the view already embeds those level-value joins internally.