Results for “flm_kanban_summary”

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

Overview

FLM_KANBAN_SUMMARY is a Flow Manufacturing (FLM) table that stores the Kanban Summary records used by Oracle E-Business Suite to drive pull-based, demand-driven replenishment. In a Flow Manufacturing environment, kanban cards and their replenishment status are continuously recalculated as production, consumption, and supply events occur; FLM_KANBAN_SUMMARY consolidates that state into summarized, queryable records tied to a kanban plan, an organization, a supply source, and a physical stocking location. The table participates directly in the Kanban execution and reporting layer of FLM and interfaces with inventory, work in process (WIP), purchasing, and inter-org planning data.

From a dimensional modeling perspective, the metadata heuristic classifies this object as a link. This classification is derived from its foreign key structure: the table resolves and relates multiple independent business entities — organization, kanban plan, source organization, supplier, supplier site, subinventory, locator, and WIP line — rather than acting as a standalone master (hub) or a purely descriptive history (satellite). Modeling it as a link reflects its role as the intersection of these reference dimensions.

Key Information Stored

The table is owned by the FLM schema and contains 19 documented columns. Its surrogate primary key is SUMMARY_ID, enforced by the FLM_KANBAN_SUMMARY_PK constraint; a unique index FLM_KANBAN_SUMMARY_U1 also exists on SUMMARY_ID, making it the documented business-key candidate. The most significant columns include:

• SUMMARY_ID — surrogate primary key uniquely identifying each kanban summary row.
• ORGANIZATION_ID — the inventory organization in which the kanban operates; a foreign key to MTL_PARAMETERS.
• KANBAN_PLAN_ID — the kanban plan this summary belongs to; a foreign key to MRP_KANBAN_PLANS.
• SUMMARY_TYPE and SUMMARY_CODE — classify and code the summarized kanban record.
• NODE_TYPE — identifies the kanban node category within the supply chain network.
• SOURCE_ORGANIZATION_ID — the supplying organization for inter-org replenishment; foreign key to MTL_INTERORG_PARAMETERS (and MTL_PARAMETERS).
• SUPPLIER_ID and SUPPLIER_SITE_ID — external supplier and site for externally sourced kanban; foreign keys to PO_VENDORS and PO_VENDOR_SITES_ALL.
• SUBINVENTORY_NAME and LOCATOR_ID — the stocking subinventory (foreign key to MTL_SECONDARY_INVENTORIES) and locator.
• WIP_LINE_ID — the production line associated with the kanban; foreign key to WIP_LINES.
• X_COORDINATE and Y_COORDINATE — spatial positions used for graphical kanban board layouts.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical uses include kanban replenishment reporting, graphical kanban board rendering, supplier and inter-org sourcing analysis, and reconciliation between planned kanban demand and actual supply. A basic lookup by primary key follows the pattern shown below.

SELECT summary_id, organization_id, kanban_plan_id, summary_type, summary_code, subinventory_name, supplier_id FROM flm.flm_kanban_summary WHERE summary_id = :p_summary_id;

Reporting by organization and plan is equally common:

SELECT ks.summary_id, ks.summary_code, ks.node_type, ks.subinventory_name, mp.organization_code FROM flm.flm_kanban_summary ks, mtl_parameters mp WHERE ks.organization_id = mp.organization_id AND ks.kanban_plan_id = :p_plan_id;

Analysts also aggregate summaries by source to evaluate external versus internal replenishment, joining PO_VENDORS and MTL_INTERORG_PARAMETERS, and use the X/Y coordinates to reproduce the visual kanban board. Because the table is periodically regenerated, queries should generally filter on ORGANIZATION_ID and KANBAN_PLAN_ID rather than relying on row persistence.

Related Objects

The following tables are the most significant dependencies, based on the documented foreign keys:

• MTL_PARAMETERS — joined on ORGANIZATION_ID (organization definition).
• MRP_KANBAN_PLANS — joined on KANBAN_PLAN_ID (kanban plan definition).
• MTL_INTERORG_PARAMETERS — joined on SOURCE_ORGANIZATION_ID and ORGANIZATION_ID (inter-org sourcing).
• PO_VENDORS — joined on SUPPLIER_ID (supplier master).
• PO_VENDOR_SITES_ALL — joined on SUPPLIER_SITE_ID (supplier site).
• MTL_SECONDARY_INVENTORIES — joined on SUBINVENTORY_NAME (stocking subinventory).
• WIP_LINES — joined on WIP_LINE_ID (production line).

Together these relationships place FLM_KANBAN_SUMMARY at the center of the Flow Manufacturing kanban replenishment model, linking planning, inventory, purchasing, and production entities into a single summarized view.