Search Results mrp_plan_organizations




Overview
Explore in AI Chat

Overview

The MRP_PLAN_ORGANIZATIONS table is a core data structure within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It serves as the definitive repository for defining and storing the relationship between a specific planning run (MRP, MPS, or DRP plan) and the inventory organizations that are included within its scope. This table is fundamental to the multi-organization planning capabilities of Oracle EBS, enabling planners to execute a single plan that spans multiple manufacturing or distribution entities. The integrity of this relationship is enforced by a primary key and critical foreign keys linking it to the master plan definition.

Key Information Stored

The table's structure captures the essential identifiers that bind an organization to a plan. The primary key is a composite of ORGANIZATION_ID, COMPILE_DESIGNATOR, and PLANNED_ORGANIZATION, ensuring a unique record for each organization planned under a specific plan. The ORGANIZATION_ID and COMPILE_DESIGNATOR columns together foreign-key to the MRP_PLANS table, identifying the master plan itself. The PLANNED_ORGANIZATION column stores the identifier of the specific inventory organization being planned. The PLAN_LEVEL column is a critical attribute that indicates the hierarchical position of the organization within a distributed planning (DRP) network, such as designating an organization as a source, destination, or both, which dictates the flow of planned orders.

Common Use Cases and Queries

This table is central to setup validation, plan analysis, and custom reporting. A common use case is verifying all organizations assigned to a plan, often performed during plan setup or troubleshooting. A typical query would join to INV_ORG_PARAMETERS to resolve organization codes:

  • SELECT mp.plan_name, hou.name planned_org_name, mpo.plan_level FROM mrp_plan_organizations mpo, mrp_plans mp, hr_operating_units hou WHERE mpo.compile_designator = mp.compile_designator AND mpo.organization_id = mp.organization_id AND mpo.planned_organization = hou.organization_id AND mp.plan_name = '<PLAN_NAME>';

Another key scenario involves analyzing the DRP network structure by filtering or ordering results based on the PLAN_LEVEL. Developers also query this table within custom programs or integrations that must process plan data, using it to determine the organizational scope before fetching detailed planned orders or material requirements.

Related Objects

The MRP_PLAN_ORGANIZATIONS table maintains a direct and mandatory relationship with the master plan definition table. As documented in the provided metadata, its primary foreign key relationship is:

  • MRP_PLANS: The table is linked via a foreign key on the composite columns (ORGANIZATION_ID, COMPILE_DESIGNATOR). This ensures every record in MRP_PLAN_ORGANIZATIONS is associated with a valid, existing plan in MRP_PLANS.

While not listed in the brief metadata, this table is intrinsically linked to core planning engine logic and is referenced by numerous standard views (such as MRP_PLAN_ORGANIZATIONS_V) and the transaction tables that store the plan output (e.g., MRP_RECOMMENDATIONS, MRP_FORECAST_DATES) for the organizations defined within it.