Search Results mrp_kanban_plans




Overview
Explore in AI Chat

Overview

The MRP_KANBAN_PLANS table is a core data repository within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It serves as the master definition table for all Kanban plans created within the system. A Kanban plan is a key component of lean manufacturing and just-in-time (JIT) replenishment strategies, defining the rules and parameters for pull-based material flow. This table stores the high-level metadata for each plan, including its name, status, and associated designators, enabling the system to manage and execute Kanban replenishment processes. Its role is foundational, as it provides the primary identifier and control information for the Kanban planning engine.

Key Information Stored

The table's primary purpose is to store the unique identifier and descriptive attributes for each Kanban plan. The most critical column is KANBAN_PLAN_ID, which serves as the system-generated primary key and unique identifier for a plan. Other significant columns include KANBAN_PLAN_NAME, which holds the user-defined name for the plan, and ORGANIZATION_ID, which ties the plan to a specific inventory organization. The INPUT_DESIGNATOR column is crucial for linking the Kanban plan to a specific source of demand, such as a forecast or master production schedule, by referencing a designator in the MRP_FORECAST_DESIGNATORS or MRP_SCHEDULE_DESIGNATORS tables. Additional columns typically track the plan's LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY for auditing, along with a PLANNED_FLAG or similar column to indicate the plan's processing status.

Common Use Cases and Queries

This table is central to administrative and reporting activities related to Kanban. A common use case is generating a simple list of all active Kanban plans within an organization for review or maintenance. Technical consultants and DBAs often query this table to diagnose data integrity issues or understand plan configurations. A typical reporting query joins MRP_KANBAN_PLANS with related setup tables to provide a comprehensive view.

  • Basic Plan Listing: SELECT kanban_plan_id, kanban_plan_name, organization_id, last_update_date FROM mrp.mrp_kanban_plans WHERE organization_id = :org_id ORDER BY kanban_plan_name;
  • Plan Details with Designator: SELECT mkp.kanban_plan_name, mfd.designator_code FROM mrp.mrp_kanban_plans mkp, mrp.mrp_forecast_designators mfd WHERE mkp.input_designator = mfd.designator_code AND mkp.organization_id = mfd.organization_id;

Related Objects

The MRP_KANBAN_PLANS table has defined foreign key relationships with other critical MRP setup tables, establishing its role in the data model. As per the provided metadata, it references the following objects:

  • MRP_FORECAST_DESIGNATORS: Linked via the composite foreign key on INPUT_DESIGNATOR and ORGANIZATION_ID. This allows a Kanban plan to consume forecast data as its demand source.
  • MRP_SCHEDULE_DESIGNATORS: Also linked via the composite foreign key on INPUT_DESIGNATOR and ORGANIZATION_ID. This allows a Kanban plan to be driven by a master production schedule.

Furthermore, the table is referenced by numerous child tables that store the detailed output and card definitions of a Kanban plan, such as MRP_KANBAN_PLAN_CARDS and MRP_KANBAN_PLAN_ITEMS. The primary key, KANBAN_PLAN_ID, is the central point of join for these detailed transactional tables.