Results for “co_code”

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

Overview

MR_TRAN_TBL is a table owned by the GMP schema within Oracle EBS Process Manufacturing Process Planning. Its documented description is "MRP transactions," indicating that it stores the transactional movement records consumed and produced by the process manufacturing MRP planning engine. Each row captures a single material transaction line associated with a planning run, tying an item, organization, warehouse, quantity, and unit of measure to a specific MRP_ID and line sequence.

Because the table records associations between planning runs and the items, warehouses, and organizations they involve, it functions as an intersection of independent business entities rather than a master or descriptive store. The heuristic Data Vault classification derived from its foreign key structure is link. Under that modeling suggestion, MR_TRAN_TBL represents a relationship between a planning parameter record (MR_PARM_DTL) and the inventory/organization masters, rather than a hub of a core business concept or a satellite holding descriptive attributes.

Key Information Stored

The table contains 21 documented columns. The most significant are the planning and inventory identifiers, the transaction quantities and dates, and the standard concurrent program audit columns.

• MRP_ID — Identifies the MRP planning run or parameter record that generated or owns the transaction. Part of both unique indexes and a foreign key to MR_PARM_DTL.
• LINE_NO — Line sequence within the planning run. Part of both unique indexes.
• ACTION_NO — Action sequence associated with the transaction line.
• ITEM_ID — The inventory item involved. Foreign key to IC_ITEM_MST and IC_ITEM_MST_B.
• WHSE_CODE — Warehouse code. Foreign key to IC_WHSE_MST.
• CO_CODE and ORGN_CODE — Company and organization codes. Foreign keys to SY_ORGN_MST and SY_ORGN_MST_B.
• TRANS_QTY and TRANS_UM — Transaction quantity and its unit of measure. TRANS_UM is a foreign key to SY_UOMS_MST.
• TRANS_DATE — Date of the transaction.
• DOC_TYPE and DOC_ID — Document type and identifier describing the source transaction.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Concurrent program audit columns identifying the process that populated the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard who-columns for row-level audit.

Two unique indexes are documented. MR_TRAN_TBL_PK on (MRP_ID, LINE_NO) defines the primary key, combining the planning run with the line sequence. MR_TRAN_TBLI1 on (MRP_ID, ITEM_ID, WHSE_CODE, TRANS_DATE, LINE_NO) is a business-key candidate that enforces uniqueness of an item's transaction at a warehouse on a given date within a planning run. Note that MR_TRAN_TBL_PK is the narrower key; the composite of the two indexes fully identifies a transaction line.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include reconciling planned MRP transactions against inventory movements, auditing which items and warehouses were touched by a given planning run, and validating unit-of-measure consistency across transactions. A common pattern joins MR_TRAN_TBL to the item and warehouse masters for descriptive reporting:

• Filtering by planning run: SELECT * FROM GMP.MR_TRAN_TBL WHERE MRP_ID = :p_mrp_id ORDER BY LINE_NO;
• Aggregating quantities by item and warehouse: SELECT ITEM_ID, WHSE_CODE, SUM(TRANS_QTY) FROM GMP.MR_TRAN_TBL WHERE MRP_ID = :p_mrp_id GROUP BY ITEM_ID, WHSE_CODE;
• Joining for descriptions: SELECT t.*, i.ITEM_DESC FROM GMP.MR_TRAN_TBL t, GMP.IC_ITEM_MST i WHERE t.ITEM_ID = i.ITEM_ID AND t.MRP_ID = :p_mrp_id;
• Auditing by program: filter on REQUEST_ID or PROGRAM_ID to trace rows to a specific concurrent request.

Because the primary key is (MRP_ID, LINE_NO), lookups by planning run and line number are the most efficient access path.

Related Objects

The following objects are the most significant relationships based on the documented foreign keys.

• MR_PARM_DTL — referenced via MR_TRAN_TBL.MRP_ID; the planning parameter detail that owns the run.
• IC_ITEM_MST — referenced via MR_TRAN_TBL.ITEM_ID; item master description and attributes.
• IC_ITEM_MST_B — referenced via MR_TRAN_TBL.ITEM_ID; the business-view item master.
• IC_WHSE_MST — referenced via MR_TRAN_TBL.WHSE_CODE; warehouse master.
• SY_ORGN_MST — referenced via MR_TRAN_TBL.CO_CODE and MR_TRAN_TBL.ORGN_CODE; organization/company master.
• SY_ORGN_MST_B — referenced via MR_TRAN_TBL.CO_CODE and MR_TRAN_TBL.ORGN_CODE; business-view organization master.
• SY_UOMS_MST — referenced via MR_TRAN_TBL.TRANS_UM; unit-of-measure master.