Search Results mrp_ap_inv_comps_sn

Overview

MRP_AP_OPERATION_COMPONENTS_V is a reporting view in the Oracle EBS Master Scheduling/MRP (MRP) module. It presents a consolidated, denormalized picture of the relationship between assembly operations and their associated bill of material components, allowing planners, report developers, and integration specialists to resolve which components are consumed at which routing operation for a given assembly within a given organization.

The view is classified in ETRM documentation as "Not implemented in this database," and its owner is not recorded. This means the view is typically created dynamically by Oracle's planning data collection processes, or exists only in schemas where the Advanced Planning / MRP collections have materialized the relevant staging tables. The user search term "mrp_ap_inv_comps_sn" indicates that the view is closely associated with the MRP_AP_INV_COMPS_SN snapshot table, which supplies the component-level data joined into this view.

In the Oracle EBS 12.1.1 and 12.2.2 environments, this view serves primarily as a bridge between routing operations and bill components for MRP/MPS planning engine consumption, rather than as a transaction-processing object.

Underlying Base Objects

According to the documented view text, MRP_AP_OPERATION_COMPONENTS_V is defined over six snapshot (or "SN") tables prefixed with MRP_AP_:

• MRP_AP_MRP_PARAS_SN (aliased MP) — MRP planning parameters, providing organization context.
• MRP_AP_SYS_ITEMS_SN (aliased MSIK) — System items snapshot, supplying item validation.
• MRP_AP_OPR_SEQS_SN (aliased BOS) — Operation sequences, supplying operation sequence identifiers and effective/disable dates.
• MRP_AP_INV_COMPS_SN (aliased BIC) — Inventory components; the primary component source and the object referenced in the searched term.
• MRP_AP_OPR_RTNS_SN (aliased BOR) — Operation routings, linking assemblies to routing sequences.
• MRP_AP_BOMS_SN (aliased BBOM) — Bills of material snapshot, supplying assembly and bill sequence identifiers.

The joins are keyed on ASSEMBLY_ITEM_ID and ORGANIZATION_ID across the BOM, routing, and item snapshots, with the component snapshot linked through BILL_SEQUENCE_ID and the operation snapshot linked through ROUTING_SEQUENCE_ID and OPERATION_SEQ_NUM. Effectivity filtering is applied so that overlapping operation and component effective/disable date ranges are respected.

Key Columns

• ASSEMBLY_ITEM_ID — The inventory item identifier of the parent assembly whose components and operations are being described.
• ORGANIZATION_ID — The inventory organization in which the assembly is defined.
• COMPONENT_SEQUENCE_ID — Identifier of the component line within the bill of material; ties back to the component snapshot.
• OPERATION_SEQUENCE_ID — Identifier of the routing operation at which the component is consumed.
• BILL_SEQUENCE_ID — The bill of material sequence to which the component belongs.
• ROUTING_SEQUENCE_ID — The routing sequence providing the operation structure.
• OPERATION_TYPE — Classifies the operation (for example, standard versus other operation categories), derived from the operation sequence snapshot.

Common Use Cases and Queries

Typical uses include validating that each bill component maps to an active operation, building planning reports that show component consumption by operation, and diagnosing mismatches between BOM and routing effectivity. A representative query:

SELECT assembly_item_id, organization_id, component_sequence_id, operation_sequence_id, bill_sequence_id, routing_sequence_id, operation_type FROM mrp_ap_operation_components_v WHERE organization_id = :org_id AND assembly_item_id = :item_id;

Because the underlying objects are MRP snapshot tables, results reflect the state captured at the last planning data collection and should not be treated as real-time transactional data.