Search Results mrp_parameters




Overview
Explore in AI Chat

Overview

The MRP_PARAMETERS table is a core configuration entity within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It functions as the central repository for planning parameters defined at the organization level. Each row in this table stores the specific set of rules, defaults, and control flags that govern how the MRP or Master Scheduling engine processes plans for a given inventory organization. Its role is critical, as the parameters stored here directly influence the generation of material plans, forecast consumption, planning time fences, and other fundamental planning behaviors. The table's one-to-one relationship with an organization, enforced by its primary key on ORGANIZATION_ID, ensures that each operating entity has a distinct and controllable planning configuration.

Key Information Stored

The table's columns collectively define the operational profile for planning. While the provided metadata does not list individual columns, standard implementation knowledge and foreign key relationships indicate it holds key control parameters. The PRIMARY_KEY on ORGANIZATION_ID is the fundamental identifier. Important fields typically include flags to control netting, planning time fence rules, default planning and forecast designators, consumption settings, and default values for critical planning attributes like the DEFAULT_ABC_ASSIGNMENT_GROUP, as evidenced by its foreign key to MTL_ABC_ASSIGNMENT_GROUPS. Other common parameters govern repetitive scheduling, sales order update behavior, and the release of planned orders.

Common Use Cases and Queries

This table is primarily referenced for configuration validation, audit reporting, and as a lookup in custom integrations. Common operational queries involve verifying the current parameter setup for an organization or troubleshooting plan output by checking specific flags. A fundamental query retrieves all parameters for a given organization, often joined to related designator tables for clarity. For example:

  • SELECT * FROM MRP.MRP_PARAMETERS WHERE ORGANIZATION_ID = 123;

Another common use case is generating a report that lists which organizations use a specific ABC assignment group as their default, leveraging the foreign key relationship:

Direct data manipulation via DML is rare and strongly discouraged; parameters are almost exclusively maintained via the Oracle EBS user interface, which ensures business logic and validation are applied.

Related Objects

As shown in the metadata, MRP_PARAMETERS sits at the center of a key relationship network. It has a mandatory foreign key to MTL_PARAMETERS (ORGANIZATION_ID), linking planning parameters to general inventory organization settings. It is referenced as a parent table by several critical planning setup tables, including MRP_DESIGNATORS, MRP_FORECAST_DESIGNATORS, MRP_SCHEDULE_DESIGNATORS, MRP_REPETITIVE_PERIODS, and MRP_SALES_ORDER_UPDATES, all via ORGANIZATION_ID. This structure enforces that these child configuration records cannot exist without a corresponding entry in MRP_PARAMETERS. Furthermore, its relationship with MTL_ABC_ASSIGNMENT_GROUPS via the DEFAULT_ABC_ASSIGNMENT_GROUP column integrates ABC analysis into the planning setup.