Results for “mr_mesg_tbl”

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

Overview

MR_MESG_TBL is a table owned by the GMP schema within Oracle E-Business Suite, mapped to the Process Manufacturing Process Planning (GMP) product family. Its documented purpose is to serve as the MRP error message log, capturing diagnostic messages generated during the execution of material requirements planning and related planning runs for process manufacturing environments. In this capacity it functions as a transient staging and audit repository: planning engine output that cannot be fully resolved — for example, a shortage condition, an invalid formula reference, or a missing warehouse — is written to this table with enough context to allow a planner to investigate the underlying data problem.

From a heuristic Data Vault modeling perspective, the metadata classifies MR_MESG_TBL as a link. This is consistent with its structure, which is dominated by foreign-key references to master and transactional entities (items, warehouses, formulas, organizations, calendars, and the originating MRP run) rather than serving as a standalone hub of a business concept. The table is the association between a planning run and the set of messages it produced at a specific line number. Note that this classification is a modeling suggestion derived from the foreign-key topology, not a formal Data Vault designation.

Key Information Stored

The table is documented with 25 physical columns. The most operationally significant of these are outlined below.

• MRP_ID — Identifier of the MRP planning run that generated the message. Part of the composite primary key.
• MESSAGE_LINE_NO — Sequence number of the message within a run. Together with MRP_ID it forms the unique index MR_MESG_TBL_PK, the only documented business-key candidate.
• MESSAGE_CODE — Code identifying the category or type of error/warning message produced.
• SHOPDAY_NO — Shop-day (planning day) number within the planning horizon to which the message applies.
• CALENDAR_ID — References MR_SHCL_HDR; identifies the shop calendar used for the run.
• ITEM_ID1, ITEM_ID2 — The item or item pair implicated in the message; each is a foreign key to IC_ITEM_MST and IC_ITEM_MST_B.
• WHSE_CODE1, WHSE_CODE2 — Warehouse codes associated with the item(s), each referencing IC_WHSE_MST.
• FORMULA_ID — References FM_FORM_MST; identifies the formula implicated in the message.
• ORGN_CODE — Organization code; foreign key to SY_ORGN_MST and SY_ORGN_MST_B.
• REQUIRED_QTY — Quantity required at the point of the reported condition.
• START_DATE, END_DATE — Effective dates of the condition or requirement.
• LEADTIME — Lead time value associated with the reported item or requirement.
• ACTION_NO — Action number, typically tying the message to a planner action or recommendation.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID — Concurrent program context that produced the row, supporting traceability back to the submitting request.
• Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — Who/when metadata maintained automatically by the EBS framework.

The surrogate primary key per the documented unique index is the composite (MRP_ID, MESSAGE_LINE_NO). No separate single-column surrogate key is documented; the business-key candidates and the primary key are identical here.

Common Use Cases and Queries

The primary use case is diagnostic reporting on failed or exceptional planning runs. Planners and support analysts query MR_MESG_TBL to determine why a plan produced unexpected results or generated warnings.

• List all messages for a specific MRP run: SELECT MESSAGE_LINE_NO, MESSAGE_CODE, ITEM_ID1, WHSE_CODE1, ORGN_CODE, REQUIRED_QTY FROM GMP.MR_MESG_TBL WHERE MRP_ID = :p_mrp_id ORDER BY MESSAGE_LINE_NO;
• Messages by item: filter on ITEM_ID1 or ITEM_ID2 and join to IC_ITEM_MST for the item description.
• Run-level reconciliation: join to MR_PARM_DTL (via MRP_ID) to associate messages with the planning parameters used.
• Organization-scoped error review: filter on ORGN_CODE and join to SY_ORGN_MST for organization names.
• Traceability to the concurrent program: filter by REQUEST_ID to tie messages back to a specific SRS submission.

Typical SQL patterns join the table to its master references for reporting:

SELECT m.MRP_ID, m.MESSAGE_LINE_NO, m.MESSAGE_CODE, i.ITEM_DESC, m.WHSE_CODE1
FROM GMP.MR_MESG_TBL m, IC_ITEM_MST i
WHERE m.ITEM_ID1 = i.ITEM_ID
AND m.MRP_ID = :p_mrp_id;
ORDER BY m.MESSAGE_LINE_NO;

Because rows are log entries, reporting is usually direct selection with filters on MRP_ID, ORGN_CODE, or MESSAGE_CODE, rather than aggregation.

Related Objects

MR_MESG_TBL participates in a broad set of foreign-key relationships, all documented. The most significant related objects and their join columns are:

• MR_PARM_DTL — joined on MR_MESG_TBL.MRP_ID = MR_PARM_DTL.MRP_ID; the originating planning parameters for the run.
• IC_ITEM_MST and IC_ITEM_MST_B — joined on ITEM_ID1 and ITEM_ID2; master item definitions (base and translated).
• IC_WHSE_MST — joined on WHSE_CODE1 and WHSE_CODE2; warehouse master.
• FM_FORM_MST — joined on FORMULA_ID; formula master for process manufacturing.
• SY_ORGN_MST and SY_ORGN_MST_B — joined on ORGN_CODE; organization definitions.
• MR_SHCL_HDR — joined on CALENDAR_ID; shop calendar header supplying the planning calendar.

These relationships confirm the table's role as a central diagnostic link connecting a planning run to the items, warehouses, formulas, organizations, and calendars that were under consideration when each message was produced.