Search Results using_assembly_item_id




Overview
Explore in AI Chat

Overview

The MRP_ASSEMBLY_OPERATIONS table is a data object within the Oracle E-Business Suite (EBS) Master Scheduling/MRP (MRP) module. According to the official ETRM documentation, its primary description is "Not currently used." This indicates that while the table structure exists within the MRP schema in both releases 12.1.1 and 12.2.2, it is not actively populated or utilized by standard application logic in these versions. Its presence is likely a legacy artifact from earlier implementations or a placeholder for potential future functionality. The table's intended role, inferred from its name and structure, would be to store operation-specific data for assemblies within the context of a Material Requirements Planning (MRP) or Master Production Schedule (MPS) compile, linking assembly items to their manufacturing routing operations.

Key Information Stored

The table's structure is defined by its primary key and foreign key relationships. The primary key (MRP_ASSEMBLY_OPERATIONS_PK) is a composite key consisting of five columns, establishing a unique record for a specific operation within a compiled plan. The key columns are INVENTORY_ITEM_ID, which identifies the assembly item; ORGANIZATION_ID, specifying the inventory organization; COMPILE_DESIGNATOR, denoting the specific MRP/MPS plan name; USING_ASSEMBLY_ITEM_ID, which references the assembly being used; and OPERATION_SEQ_NUM, defining the sequence number of the manufacturing operation. Other columns typically found in such operational tables, like DEPARTMENT_ID or RESOURCE requirements, are not detailed in the provided metadata but may exist. The core data model focuses on linking an item and plan to a specific assembly operation sequence.

Common Use Cases and Queries

Given the documented status of "Not currently used," there are no standard application use cases for this table in EBS 12.1.1 or 12.2.2. It should not be referenced in custom reports, integrations, or data extracts intended for production use, as it contains no application-managed data. If queried for diagnostic or exploratory purposes, a sample join to its related item table would follow the foreign key structure. For example, a theoretical query to list all defined records (which would return no rows in a standard installation) might be structured as:

  • SELECT mao.*, msi.concatenated_segments
  • FROM mrp.mrp_assembly_operations mao,
  • mrp.mrp_system_items msi
  • WHERE mao.inventory_item_id = msi.inventory_item_id
  • AND mao.organization_id = msi.organization_id
  • AND mao.compile_designator = msi.compile_designator;

Any direct data manipulation (DML) on this table is unsupported and could compromise system integrity.

Related Objects

The ETRM metadata explicitly documents foreign key relationships for MRP_ASSEMBLY_OPERATIONS. It has two foreign key dependencies on the MRP_SYSTEM_ITEMS table, which holds item information specific to an MRP compile. The first relationship joins on the columns (INVENTORY_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR) to link to the primary assembly item. The second foreign key joins on the columns (USING_ASSEMBLY_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR) to link to the specific assembly item being utilized in the operation. There is no metadata indicating that other tables possess foreign keys referencing MRP_ASSEMBLY_OPERATIONS, consistent with its inactive status.