Search Results mrp_i2_bom_v

Overview

MRP_I2_BOM_V is a database view shipped with the Oracle E-Business Suite Master Scheduling/MRP (MRP) module and is classified as a "Rhythm" view. Rhythm views in EBS are typically exposed as read-only reporting and integration surfaces that flatten complex bill of materials, routing, and item relationships into a structure suitable for extract, downstream planning, and analytical consumption. The view's stated purpose is to support information regarding bill of materials, and its column set confirms that Remit encompasses assembly/component relationships, effectivity windows, alternate designators, yield factors, and engineering change attributes.

In ETRM documentation for release 12.2.2, the view is annotated as "Not implemented in this database." This means that while the view text and metadata are catalogued, no physical implementation exists in the reference instance. It does not indicate the view is unsupported in 12.1.1 or 12.2.2 generally; rather, it reflects that the object is not installed in every environment and may be absent where the underlying Rhythm packaged functions are not deployed.

Underlying Base Objects

The documented metadata lists no referenced base tables. The view text, however, reveals dependencies on standard MRP/BOM structures inferred from column aliases and joins, including BOM_COMPONENTS (aliased BC), the assembly item master (aliased ASSY), component item master (aliased COMP), and a routing source (aliased RTG). A dummy table (DL) drives decode logic.

The view also invokes several packaged ERP functions: MRP_I2_ERP.GENERATE_ROUTING, MRP_I2_ERP.GET_START_DATE, MRP_I2_ERP.GET_PARAMETER, and MRP_I2_ERP.GET_PARAMETER with the parameter MRP_I2_P_ENABLE_ABP. These functions supply the runtime logic for routing generation, effective dating, and profile-driven behavior. Because it is defined over these objects and functions, the view inherits the MRP module's organization-level filtering and cannot be queried meaningfully without valid organization context.

Key Columns

The projection exposes the following classes of data:

• Organization and item identifiers: ORGANIZATION_ID, INVENTORY_ITEM_ID, and PART_NUMBER for both assembly and component.
• Routing and BOM designators: ALTERNATE_BOM_DESIGNATOR and ALTERNATE_ROUTING_DESIGNATOR, plus a concatenated routing key generated via GENERATE_ROUTING.
• Quantity and yield: COMPONENT_QUANTITY and COMPONENT_YIELD_FACTOR, combined to derive effective usage.
• Effectivity and disable dates: EFFECTIVITY_DATE and DISABLE_DATE, with decode logic producing status flags 'A' (active) and 'D' (disabled).
• Ordering attributes: MINIMUM_ORDER_QUANTITY, MAXIMUM_ORDER_QUANTITY, and INCREMENTAL_LOT_SIZE.
• Change control: CHANGE_NOTICE, REVISED_ITEM_SEQUENCE_ID, USE_UP, and ACD_TYPE.
• Operation sequencing: OPERATION_SEQ_NUM links the component to its routing operation.

Common Use Cases and Queries

The view is suited to BOM explosion extracts, effectivity audits, and yield/quantity reconciliation. A representative query:

SELECT organization_id, part_number, component_part_number, component_quantity
FROM   mrp_i2_bom_v
WHERE  organization_id = :org_id;

Because the view references MRP_I2_P_ENABLE_ABP, attribute-based planning behavior may alter the returned attribute columns depending on the profile setting at the organization level. Analysts investigating ABP-related output should query this view in an environment where the Rhythm schema and MRP_I2_P_ENABLE_ABP are properly configured; in databases where the object is "not implemented," the view must be created from the documented definition before use.