Search Results mrp_plans

Overview

The MRP_PLANS table is a core data object within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It functions as the master definition table for planning entities, storing the foundational configuration settings and parameters associated with a specific plan name (compile designator). Every plan run within the system must have a corresponding record in this table. It acts as a central hub, linking the plan's operational settings to its execution outputs and related master data, thereby enabling the comprehensive material and capacity planning processes that are essential for manufacturing and supply chain operations.

Key Information Stored

The table's primary key is a composite of ORGANIZATION_ID and COMPILE_DESIGNATOR, uniquely identifying a plan within a specific inventory organization. While the provided metadata does not list all columns, the foreign key relationships indicate several critical fields. The COMPILE_DESIGNATOR column holds the unique identifier for the plan itself. Other key columns include CURR_SCHEDULE_DESIGNATOR and SCHEDULE_DESIGNATOR, which link to different schedule versions in the MRP_SCHEDULE_DESIGNATORS table. The ASSIGNMENT_SET_ID column links to the MRP_ASSIGNMENT_SETS table, defining sourcing and assignment rules for the plan. Collectively, these columns store the plan's identity, its active and baseline schedule references, and its rule-based configurations.

Common Use Cases and Queries

This table is primarily accessed for administrative reporting, data validation, and integration tasks. A common use case is generating a list of all configured plans within the system or for a specific organization to support audits or system documentation. Technical consultants often query this table to verify plan setup before a critical MRP run or to troubleshoot issues where plan parameters are suspected. A typical query would join MRP_PLANS to MRP_DESIGNATORS to retrieve descriptive plan names.

• Sample Query: List all plans with their designator description:
  SELECT mp.organization_id, mp.compile_designator, md.designator_description FROM mrp_plans mp, mrp_designators md WHERE mp.compile_designator = md.designator AND mp.organization_id = md.organization_id ORDER BY 1, 2;
• Data Validation: Queries are used to ensure foreign key integrity, such as verifying that every CURR_SCHEDULE_DESIGNATOR in MRP_PLANS exists in MRP_SCHEDULE_DESIGNATORS for the same organization.

Related Objects

As evidenced by its foreign key constraints, MRP_PLANS has integral relationships with several key tables in the MRP schema. The documented relationships are as follows:

• MRP_DESIGNATORS: Linked via MRP_PLANS.COMPILE_DESIGNATOR and ORGANIZATION_ID. This provides the master list of valid plan names.
• MRP_SCHEDULE_DESIGNATORS: Linked via three separate foreign keys for MRP_PLANS.CURR_SCHEDULE_DESIGNATOR, .SCHEDULE_DESIGNATOR, and .COMPILE_DESIGNATOR (all with ORGANIZATION_ID). This manages different schedule versions and snapshots associated with the plan.
• MRP_ASSIGNMENT_SETS: Linked via MRP_PLANS.ASSIGNMENT_SET_ID. This defines the sourcing and assignment rules applied during the plan run.
• MRP_FILES: Linked via MRP_FILES.ORGANIZATION_ID and .COMPILE_DESIGNATOR. This table likely stores the output or log files generated by the plan.
• MRP_PLAN_ORGANIZATIONS: Linked via MRP_PLAN_ORGANIZATIONS.ORGANIZATION_ID and .COMPILE_DESIGNATOR. This table defines which organizations are included in a multi-organization plan.
• MTL_ABC_COMPILE_HEADERS: Linked via MTL_ABC_COMPILE_HEADERS.ORGANIZATION_ID and .MRP_PLAN_NAME. This connects ABC analysis compilations to a specific plan.