Search Results mrp_id




Overview
Explore in AI Chat

Overview

The MR_TRAN_TBL is a core transactional table within the Process Manufacturing Process Planning (GMP) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the central repository for Material Requirements Planning (MRP) transaction records. Its primary role is to log and track all MRP-driven material movements and planned orders generated by the planning engine. This data is fundamental for analyzing planning output, understanding material flow, and supporting inventory and production planning processes within a process manufacturing environment.

Key Information Stored

The table's structure is designed to uniquely identify and detail each MRP transaction. Its composite primary keys, MR_TRAN_TBLI1 and MR_TRAN_TBL_PK, enforce uniqueness based on a combination of planning identifiers and transaction sequence. The critical columns include MRP_ID, which links to the MR_PARM_DTL table to associate transactions with a specific MRP planning run; ITEM_ID and WHSE_CODE, which identify the planned item and its warehouse location, linked to IC_ITEM_MST and IC_WHSE_MST respectively; and TRANS_DATE, which records the date of the planned transaction. Other significant columns are LINE_NO for sequencing, ORGN_CODE and CO_CODE for organizational context (linked to SY_ORGN_MST), and TRANS_UM for the unit of measure of the transaction quantity (linked to SY_UOMS_MST).

Common Use Cases and Queries

A primary use case is auditing and reporting on the results of an MRP planning run. Analysts query this table to review planned orders, reschedules, and suggested material issues or receipts. Common SQL patterns involve filtering by MRP_ID and a date range to isolate a specific plan's output, or joining with item master tables to add descriptive information. For example, a query to list all planned receipts for a specific item might be: SELECT mt.trans_date, mt.trans_qty, i.item_code, i.desc1 FROM gmp.mr_tran_tbl mt, ic_item_mst_b i WHERE mt.item_id = i.item_id AND mt.item_id = :p_item_id AND mt.trans_type = 'PLANNED ORDER' ORDER BY mt.trans_date;. This data is also crucial for generating MRP action and exception reports that inform planners of necessary purchasing or production activities.

Related Objects

MR_TRAN_TBL is integrally connected to several key EBS base tables through foreign key relationships, as documented. Its main dependencies are:

  • MR_PARM_DTL: The MRP_ID foreign key ties each transaction to its originating planning run parameters.
  • IC_ITEM_MST_B / IC_ITEM_MST: The ITEM_ID links to the item master for product details.
  • IC_WHSE_MST: The WHSE_CODE links to the warehouse master for location details.
  • SY_ORGN_MST_B / SY_ORGN_MST: The ORGN_CODE and CO_CODE columns link to the organization master for legal entity and operating unit context.
  • SY_UOMS_MST: The TRANS_UM column links to the unit of measure master.
These relationships ensure referential integrity and enable comprehensive reporting by joining transactional data with master descriptive flexfields.