Search Results mr_parm_dtl




Overview
Explore in AI Chat

Overview

The MR_PARM_DTL table is a core data object within the Oracle E-Business Suite Process Manufacturing (GMP) module, specifically for Process Planning. It serves as the primary repository for storing detailed parameters that define and control individual Material Requirements Planning (MRP) runs. Each record in this table represents a distinct MRP execution instance, capturing the specific planning rules, scope, and organizational context used to generate supply chain recommendations. Its role is critical for the MRP engine's operation, as it holds the configuration that drives the planning calculation and links the run to its resulting output data, such as action messages, exceptions, and planned orders.

Key Information Stored

While the provided metadata does not list specific columns beyond key relationships, the table's primary key and foreign keys indicate the essential data it holds. The MRP_ID column is the unique identifier for each MRP run and serves as the table's primary key. The TEXT_CODE column links the MRP run parameters to descriptive text or notes stored in the MR_TEXT_HDR table. The SCHEDULE_ID column establishes a relationship with the PS_SCHD_HDR table, connecting the MRP parameters to a specific production schedule. Typically, such a parameter table would also store columns for the planning horizon, demand time fence, planning method (e.g., MRP, DRP), the specific organization, and cutoff dates for the run.

Common Use Cases and Queries

The primary use case is the initiation and review of MRP runs within Process Manufacturing. Administrators and planners use this table to track historical runs and their parameters. Common queries involve joining MR_PARM_DTL to its related transaction and message tables to analyze planning output. For example, to retrieve basic run information, a query might be: SELECT MRP_ID, SCHEDULE_ID, TEXT_CODE FROM GMP.MR_PARM_DTL WHERE SCHEDULE_ID = <schedule_id> ORDER BY MRP_ID DESC;. For troubleshooting or auditing, a more complex join retrieves all action messages for a specific run: SELECT a.* FROM GMP.MR_ACTN_TBL a, GMP.MR_PARM_DTL p WHERE a.MRP_ID = p.MRP_ID AND p.MRP_ID = <mrp_id>;. Reporting often focuses on summarizing runs by schedule or date range to understand planning frequency and scope.

Related Objects

As defined by its foreign key relationships, MR_PARM_DTL is centrally connected to several key MRP execution tables. It is referenced as a parent table by:

  • MR_ACTN_TBL: Stores recommended action messages generated by the MRP run.
  • MR_MESG_TBL: Holds exception and process messages from the planning run.
  • MR_TRAN_TBL: Contains the detailed planned order and reschedule recommendations.
Furthermore, it has foreign key dependencies on:
  • MR_TEXT_HDR (via TEXT_CODE): For descriptive text associated with the parameters.
  • PS_SCHD_HDR (via SCHEDULE_ID): Linking the MRP run to a production schedule in Process Manufacturing.
This structure ensures data integrity and allows comprehensive tracing from a planning parameter set to all its generated results.