Results for “mr_parm_dtl”

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

Overview

MR_PARM_DTL is a GMP (Process Manufacturing Process Planning) table that stores MRP run parameters in Oracle E-Business Suite 12.1.1 and 12.2.2. Each row captures the parameter set and execution metadata for a specific Material Requirements Planning run, including the schedule against which the plan is executed, run timing, status, and approval information. The table sits in the GMP schema and is documented as VALID in the ETRM repository, with 52 columns in the 12.2.2 physical schema.

Under the heuristic Data Vault classification mined from its foreign-key structure, MR_PARM_DTL is hub-leaning. This suggests modeling MRP_ID as a durable business hub key, with the descriptive attributes (run status, dates, approval details, descriptive flexfields) treated as satellite payload. The classification is a modeling suggestion rather than a documented EBS design constraint.

Key Information Stored

The surrogate primary key is MRP_ID, enforced by the unique index MR_PARM_DTL_PK. MRP_ID is also the single documented business-key candidate, so it serves simultaneously as the technical identifier and the join key propagated to dependent tables.

• MRP_ID — primary key and unique business identifier for the parameter record.
• SCHEDULE_ID — foreign key to PS_SCHD_HDR, tying the run to a production schedule.
• TEXT_CODE — foreign key to MR_TEXT_HDR, referencing descriptive text attached to the run.
• RUN_STATUS — current execution state of the MRP run.
• QUEUE_NO — queuing sequence for concurrent processing of the run.
• BATCH_DATE, ACTUAL_START_DATE, ACTUAL_END_DATE — planned batch date and actual execution window.
• RUN_BY, APPROVED_BY — the user who launched the run and the user who approved it.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying the submitting request and program.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• DELETE_MARK, DATA_DELETED — soft-delete and data-cleanup indicators.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — descriptive flexfield storage.

Common Use Cases and Queries

Typical reporting targets MRP run history, run performance, and the association between a run and the messages or transactions it produced. A frequent pattern joins the parameter row to its dependent tables through MRP_ID:

• Run status and timing review: SELECT MRP_ID, RUN_STATUS, BATCH_DATE, ACTUAL_START_DATE, ACTUAL_END_DATE FROM GMP.MR_PARM_DTL WHERE RUN_STATUS = :status.
• Schedule-linked run analysis: join MR_PARM_DTL.SCHEDULE_ID = PS_SCHD_HDR.SCHEDULE_ID to report runs by production schedule.
• Message and action volume per run: aggregate MR_MESG_TBL and MR_ACTN_TBL by MRP_ID to measure planning output.
• Transaction linkage: join MR_TRAN_TBL.MRP_ID = MR_PARM_DTL.MRP_ID to trace plan-generated transactions.
• Audit and approval reporting using RUN_BY, APPROVED_BY, and the WHO columns.

Queries should always constrain on MRP_ID or a run date range, since the table can accumulate one row per run over time.

Related Objects

The documented relationships connect MR_PARM_DTL to both parent and child tables:

• MR_TEXT_HDR — referenced via MR_PARM_DTL.TEXT_CODE.
• PS_SCHD_HDR — referenced via MR_PARM_DTL.SCHEDULE_ID.
• MR_ACTN_TBL — references MR_PARM_DTL via MR_ACTN_TBL.MRP_ID.
• MR_MESG_TBL — references MR_PARM_DTL via MR_MESG_TBL.MRP_ID.
• MR_TRAN_TBL — references MR_PARM_DTL via MR_TRAN_TBL.MRP_ID.

These dependencies confirm MR_PARM_DTL as the hub record for a given MRP run, with messages, actions, and transactions all keyed back to its MRP_ID.