Results for “input_designator”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MRP_KANBAN_PLANS is the Kanban Plan Names table in the Oracle E-Business Suite Master Scheduling/MRP (MRP) product. It resides in the MRP schema and serves as the master definition repository for Kanban plans, which drive replenishment signaling across pull-based manufacturing and distribution environments. Each row in this table represents a named Kanban plan that governs how demand signals are calculated for a set of kanban items within a specific inventory organization. In Oracle EBS 12.1.1 and 12.2.2, this table is central to the Kanban Planning process, providing the input parameters, planning horizon, and designator linkage required to generate kanban demand and pull sequences.

From a heuristic Data Vault modeling perspective, MRP_KANBAN_PLANS is best classified as a link table. Its foreign key relationships to MRP_FORECAST_DESIGNATORS and MRP_SCHEDULE_DESIGNATORS confirm its role in connecting plan definitions to demand designators, while the presence of descriptive attributes such as KANBAN_DESIGNATOR and DESCRIPTION reflects the typical link-with-attributes pattern.

Key Information Stored

The documented 36-column structure includes several columns critical to plan definition and operational processing:

• KANBAN_PLAN_ID — The surrogate primary key (enforced by MRP_KANBAN_PLANS_PK and an alternate unique index MRP_KANBAN_PLANS_U1) that uniquely identifies each plan and is referenced by downstream transactional tables.
• ORGANIZATION_ID — The inventory organization context in which the plan operates.
• KANBAN_DESIGNATOR — The human-readable name/identifier of the Kanban plan.
• DESCRIPTION — Free-text description of the plan's purpose.
• INPUT_TYPE and INPUT_DESIGNATOR — Define the plan's source of demand; INPUT_DESIGNATOR carries the foreign key to forecast or schedule designators.
• PLAN_START_DATE, PLAN_COMPLETION_DATE, PLAN_CUTOFF_DATE, and DISABLE_DATE — Govern the active planning horizon and the point at which the plan is disabled.
• BOM_EFFECTIVITY_DATE — Controls Bill of Material effectivity used during plan calculations.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — Standard concurrent program audit columns.
• LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit trail columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield (DFF) columns for extensibility.

Common Use Cases and Queries

Typical usage centers on identifying active plans, mapping plans to organizations, and tracing demand designators. A common reporting query lists plan names and their horizons:

• Retrieve active Kanban plans by organization: SELECT KANBAN_PLAN_ID, KANBAN_DESIGNATOR, PLAN_START_DATE, PLAN_COMPLETION_DATE FROM MRP_KANBAN_PLANS WHERE ORGANIZATION_ID = :org_id AND (DISABLE_DATE IS NULL OR DISABLE_DATE > SYSDATE);
• Join to MRP_FORECAST_DESIGNATORS or MRP_SCHEDULE_DESIGNATORS via INPUT_DESIGNATOR and ORGANIZATION_ID to identify the demand source driving demand signals.
• Trace generated demand by joining MRP_KANBAN_DEMAND.KANBAN_PLAN_ID to determine which plan produced a given kanban card demand.
• Audit recent plan changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.

These queries support supply chain analysts reconciling Kanban replenishment activity and administrators troubleshooting plan configuration.

Related Objects

The following tables most significantly relate to MRP_KANBAN_PLANS through documented foreign key relationships:

• MRP_FORECAST_DESIGNATORS — Referenced via INPUT_DESIGNATOR (with ORGANIZATION_ID) to source forecast-based demand.
• MRP_SCHEDULE_DESIGNATORS — Referenced via INPUT_DESIGNATOR (with ORGANIZATION_ID) to source schedule-based demand.
• MTL_KANBAN_PULL_SEQUENCES — References KANBAN_PLAN_ID; holds the pull sequence definitions executed against the plan.
• MRP_KANBAN_DEMAND — References KANBAN_PLAN_ID; stores calculated kanban demand generated by the plan.
• FLM_KANBAN_SUMMARY — References KANBAN_PLAN_ID; provides a flow-manufacturing summary view of plan results.
• FLM_EKB_HORIZONTAL_PLAN_TEMP — References KANBAN_PLAN_ID; a temporary processing table for horizontal plan data.

Together these objects form the Kanban planning data model, with MRP_KANBAN_PLANS acting as the definitional anchor linking configuration to execution.