Results for “component_item_org”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The MRP_SC_BILL_BOM_V view is a supply chain bill of material reporting object owned by the APPS schema within the Oracle E-Business Suite Master Scheduling/MRP product family. Its purpose is to flatten the structure of bills of material into a denormalized, presentation-ready form that joins assemblies, components, effectivity dates, and organizational context in a single queryable layer. Rather than requiring report authors and integrators to manually reconcile the BOM_BILL_OF_MATERIALS, BOM_INVENTORY_COMPONENTS, and MTL_SYSTEM_ITEMS_KFV structures, this view performs that work once and exposes the results through a simplified column set.

A defining characteristic of this view is its deliberate use of CONCATENATED_SEGMENTS from the key flexfield view MTL_SYSTEM_ITEMS_KFV. Both the assembly and the component are resolved through this flexfield-based view, and the view synthesizes composite display strings such as assembly_segment/organization_code and quantityX component_segment/organization_code. This design makes the view well suited to supply chain planning reports, graphical BOM displays, and any integration requiring human-readable item identification rather than raw inventory_item_id values.

Underlying Base Objects

The view is defined over the following documented base objects: BOM_BILL_OF_MATERIALS (view), BOM_CALENDAR_DATES (synonym), BOM_INVENTORY_COMPONENTS (view), ENG_REVISED_ITEMS (synonym), FND_GLOBAL (package), MRP_ASSIGNMENT_SETS (synonym), MTL_PARAMETERS (synonym), and MTL_SYSTEM_ITEMS_KFV (synonym).

Joins are constructed as follows: MTL_SYSTEM_ITEMS_KFV is aliased twice (KFV1 for assemblies, KFV2 for components), each joined to MTL_PARAMETERS on organization_id to obtain the organization code and calendar. BOM_INVENTORY_COMPONENTS links the component item to the BOM line, while BOM_BILL_OF_MATERIALS links the assembly through common_bill_sequence_id. ENG_REVISED_ITEMS is outer-joined on revised_item_sequence_id to honor the MRP_ACTIVE and implementation-date logic. BOM_CALENDAR_DATES constrains effectivity, and MRP_ASSIGNMENT_SETS supplies the assignment set identifier. FND_GLOBAL supplies session context. Importantly, the query applies SELECT DISTINCT and filters calendar dates between the component effectivity date and its disable date, defaulting to a high Julian date when no disable date exists.

Key Columns

• ASSEMBLY_ITEM_ORG — Concatenated assembly segment plus organization code.
• COMPONENT_ITEM_ORG — Concatenated quantity expression, component segment, and organization code.
• ASSIGNMENT_SET_ID — Identifier of the MRP assignment set in context.
• ORGANIZATION_ID / ORGANIZATION_CODE — Inventory organization scope.
• INVENTORY_ITEM_ID / ITEM_NAME — Assembly inventory item and its flexfield name.
• OPERATION_SEQ_NUM — Routing operation sequence for the component.
• COMPONENT_ITEM_ID / COMPONENT_NAME — Component inventory item and flexfield name.
• EFFECTIVE_DATE — Calendar date on which the component structure is effective.
• USAGE — Component quantity per assembly.

Common Use Cases and Queries

This view is typically used for multi-level BOM browsing, supply chain visibility reports, and integrations that require concatenated key flexfield segments rather than numeric identifiers. Because a search for "concatenated_segments" frequently precedes discovery of this object, the following query illustrates how those segments surface:

• SELECT assembly_item_org, component_item_org, usage, effective_date FROM mrp_sc_bill_bom_v WHERE organization_code = 'M1';
• SELECT DISTINCT concatenated_segments FROM mrp_sc_bill_bom_v; (when the caller resolves segments independently)
• SELECT inventory_item_id, item_name, component_name, operation_seq_num FROM mrp_sc_bill_bom_v WHERE assignment_set_id = :set_id;

Report authors should note that the SELECT DISTINCT and calendar-date expansion can produce multiple rows per component when several effectivity dates fall within the calendar range, so aggregation or date filtering is advisable before presentation.