Results for “mrp_rhx_bom_components_v”

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

Overview

The MRP_RHX_BOM_COMPONENTS_V view is a component of the Oracle E-Business Suite Integration Toolkit, delivered within the Master Scheduling/MRP (MRP) product family. Its documented purpose is to support the exchange of time-phased bill of material and revision information for each component of a manufactured item. In practice, the view flattens the complex, multi-table structure of Oracle Bills of Material and Engineering Change Management into a single queryable interface that external systems, planning engines, and customer-built integrations can consume.

The "RHX" prefix identifies the object as part of the Integration Toolkit (also referred to as the Open Interface / XML integration framework). Such views are intended to expose data in a stable, denormalized form so that third-party planning tools, advanced supply chain systems, or custom reports can retrieve BOM component structure without directly navigating the underlying transactional tables. In Oracle EBS 12.1.1 and 12.2.2 the view is a schema-level database object; the ETRM metadata notes it is "not implemented in this database" for the catalogued environment, meaning it is a seeded definition rather than a runtime-populated table.

Underlying Base Objects

As documented in the ETRM view text, MRP_RHX_BOM_COMPONENTS_V is defined over five base objects joined together:

• BOM_INVENTORY_COMPONENTS (BIC) — the core component records of a bill of materials, supplying component sequence, quantity, yield factor, planning factor, optional flag, effectivity and disable dates, supply type, and descriptive flexfield attributes.
• BOM_BILL_OF_MATERIALS (BBM) — the bill header, providing the alternate BOM designator, bill sequence, common bill sequence, and header-level descriptive flexfields.
• ENG_REVISED_ITEMS (ERI) — engineering change order revision data, joined via REVISED_ITEM_SEQUENCE_ID, supplying change notice, status type, use-up, revised item, and revised item sequence information.
• MRP_RHX_PLANNED_ITEMS_V (MSI) — the parent planned item, providing organization, inventory item, item number, and planning attributes such as fixed order quantity, minimum/maximum order quantity, and fixed days supply.
• MRP_RHX_PLANNED_ITEMS_V (MSI_COMP) — the component planned item, aliased separately to supply component item number and WIP supply type fallback.

The outer joins on ENG_REVISED_ITEMS allow components without an active engineering revision to still appear in the result set.

Key Columns

The view exposes a broad column list. Among the most significant are:

• COMPONENT_SEQUENCE_ID / COMPONENT_ITEM_ID — unique identifiers for the component row and its item.
• ORGANIZATION_ID / INVENTORY_ITEM_ID / ITEM_NUMBER — the parent assembly context; a parallel set exists for the component item.
• COMPONENT_QUANTITY, COMPONENT_YIELD_FACTOR, PLANNING_FACTOR — the standard BOM usage quantities.
• OPERATION_SEQ_NUM, OPERATION_LEAD_TIME_PERCENT — routing linkage for the component.
• USE_UP and USE_UP_ITEM_ID — the columns most directly relevant to the search term use_up_item_id. They are derived from ENG_REVISED_ITEMS using a DECODE(NVL(ERI.STATUS_TYPE, 6), 6, NULL, ERI.USE_UP_ITEM_ID) expression, meaning the use-up item is populated only when an active engineering status exists (status type other than 6).
• OPTIONAL, EFFECTIVITY_DATE, DISABLE_DATE — component validity and optionality.
• STATUS_TYPE, CHANGE_NOTICE, REVISED_ITEM_ID, REVISED_ITEM_SEQUENCE_ID — engineering change context.
• FIXED_ORDER_QUANTITY, MINIMUM_ORDER_QUANTITY, MAXIMUM_ORDER_QUANTITY, FIXED_DAYS_SUPPLY, FIXED_LOT_MULTIPLIER — planning-related item attributes.
• ATTRIBUTE1–15 (on both BBM and BIC) — descriptive flexfield segments.

Common Use Cases and Queries

Typical scenarios include feeding component structures into an external planning tool, auditing engineering change use-up items, and reporting BOM component detail for a specific organization and assembly.

SELECT ORGANIZATION_ID,
       ITEM_NUMBER,
       COMPONENT_ITEM_ID,
       COMPONENT_QUANTITY,
       USE_UP,
       USE_UP_ITEM_ID,
       EFFECTIVITY_DATE,
       DISABLE_DATE
FROM   MRP_RHX_BOM_COMPONENTS_V
WHERE  ORGANIZATION_ID = :org_id
AND    INVENTORY_ITEM_ID = :assembly_item_id
ORDER BY COMPONENT_SEQUENCE_ID;

To identify use-up items tied to engineering changes:

SELECT ITEM_NUMBER, COMPONENT_ITEM_ID, CHANGE_NOTICE, STATUS_TYPE, USE_UP_ITEM_ID
FROM   MRP_RHX_BOM_COMPONENTS_V
WHERE  USE_UP_ITEM_ID IS NOT NULL;

Because the view is an Integration Toolkit object, it should be treated as read-only reference data. Any joins should honour the outer-join semantics on ENG_REVISED_ITEMS to avoid inadvertently excluding components lacking an active revision.