Search Results flm_kanban_summary




Overview
Explore in AI Chat

Overview

The FLM_KANBAN_SUMMARY table is a core data repository within the Oracle E-Business Suite Flow Manufacturing (FLM) module. It serves as the central transactional table for managing and tracking Kanban cards and their associated replenishment signals. In the context of a pull-based manufacturing system, this table stores the aggregated summary data required to execute and monitor Kanban loops, which are fundamental to the Flow Manufacturing methodology for controlling material replenishment from suppliers, internal organizations, or production lines.

Key Information Stored

The table's primary key is SUMMARY_ID, which uniquely identifies each Kanban summary record. Its structure, as indicated by its foreign key relationships, is designed to link a Kanban signal to its specific supply and demand points within the manufacturing ecosystem. Key columns include ORGANIZATION_ID, which identifies the owning inventory organization, and WIP_LINE_ID, linking the record to a specific production line. For internal replenishment, SOURCE_ORGANIZATION_ID and SUBINVENTORY_NAME define the source location. For external supplier replenishment, SUPPLIER_ID and SUPPLIER_SITE_ID identify the vendor. While the provided metadata does not list all columns, typical data stored would include the Kanban card number, associated item, card status, calculated Kanban size, and transaction quantities, enabling the system to trigger replenishment orders when a card's threshold is reached.

Common Use Cases and Queries

This table is integral to operational and analytical processes. Common use cases include generating Kanban card printing reports, monitoring the status of active Kanban loops for shortage prevention, and analyzing replenishment cycle performance. A typical reporting query might join this table to inventory and supplier master data to provide a comprehensive view of all active Kanban signals. For example:

  • Identifying Kanban cards pending replenishment for a specific production line.
  • Summarizing total Kanban quantities by item and source (internal vs. supplier).
  • Troubleshooting replenishment failures by examining summary records with error statuses.

Sample SQL would often involve filtering on ORGANIZATION_ID and joining to MTL_SYSTEM_ITEMS_B for item details and PO_VENDORS for supplier names.

Related Objects

As evidenced by its foreign keys, FLM_KANBAN_SUMMARY has strong dependencies on several fundamental EBS tables. Its primary relationships are with inventory structures (MTL_PARAMETERS, MTL_SECONDARY_INVENTORIES), manufacturing execution (WIP_LINES), and procurement (PO_VENDORS, PO_VENDOR_SITES_ALL). The link to MTL_INTERORG_PARAMETERS governs inter-organization transfer rules. This table is also the likely base for key Flow Manufacturing forms and reports, and it may be referenced by public APIs or views such as FLM_KANBAN_CARDS_V for higher-level application logic and user interfaces. Direct modifications should be performed through standard Oracle APIs to maintain data integrity.