Search Results mtl_kanban_pull_sequences




Overview
Explore in AI Chat

Overview

The MTL_KANBAN_PULL_SEQUENCES table is a core data repository within Oracle E-Business Suite Inventory (INV) that defines and manages the supply sources for Kanban-controlled items. In the context of Oracle EBS 12.1.1 and 12.2.2, Kanban is a lean manufacturing methodology for replenishing materials based on actual consumption signals. This table stores the master definition of all possible pull sequences, which are the pre-defined rules specifying where and how a depleted Kanban card should be replenished. Each record acts as a template that can be referenced by multiple Kanban cards, enabling efficient and standardized material flow control within manufacturing and replenishment processes.

Key Information Stored

The table's primary key is PULL_SEQUENCE_ID, which uniquely identifies each pull sequence definition. Its critical columns define the item, location, and supply source parameters. Key columns include INVENTORY_ITEM_ID and ORGANIZATION_ID, which identify the specific item being replenished within an inventory organization. The SUPPLIER_ID and SUPPLIER_SITE_ID columns define external vendor sources for purchase order-based replenishment. For internal transfers, SOURCE_ORGANIZATION_ID and SOURCE_SUBINVENTORY specify the supplying organization and subinventory. For in-house production replenishment, WIP_LINE_ID indicates the manufacturing line. The SUBINVENTORY_NAME and LOCATOR_ID columns define the destination for the received material. These columns collectively enable the system to automatically generate the correct replenishment transaction—a purchase order, an internal requisition, or a work order—when triggered by a Kanban signal.

Common Use Cases and Queries

A primary use case is the analysis and maintenance of Kanban supply chain rules. Planners may run queries to audit all pull sequences for a specific item or to identify sequences sourcing from a particular supplier. Common reporting needs include listing all pull sequences within an organization or validating the setup before implementing new Kanban cards. A typical SQL pattern involves joining to related master tables for descriptive information:

  • Identifying all pull sequences for an item: SELECT * FROM MTL_KANBAN_PULL_SEQUENCES WHERE INVENTORY_ITEM_ID = &ITEM_ID AND ORGANIZATION_ID = &ORG_ID;
  • Reporting on pull sequence definitions with descriptions: SELECT MKPS.*, MSI.SEGMENT1 ITEM_CODE, MSI.DESCRIPTION FROM MTL_KANBAN_PULL_SEQUENCES MKPS, MTL_SYSTEM_ITEMS_B MSI WHERE MKPS.INVENTORY_ITEM_ID = MSI.INVENTORY_ITEM_ID AND MKPS.ORGANIZATION_ID = MSI.ORGANIZATION_ID;

These queries support setup validation, troubleshooting, and operational reporting.

Related Objects

MTL_KANBAN_PULL_SEQUENCES is centrally linked to numerous key Inventory, Purchasing, and Work in Process entities. As per the provided metadata, its primary foreign key relationships are fundamental. The table MTL_KANBAN_CARDS has a foreign key (PULL_SEQUENCE_ID) referencing this table, making it the direct parent for all Kanban card definitions. It references master data tables for items (MTL_SYSTEM_ITEMS_B), organizations (MTL_PARAMETERS), and subinventories (MTL_SECONDARY_INVENTORIES). For inter-organization transfers, it references MTL_INTERORG_PARAMETERS. For external supply, it links to supplier master data (PO_VENDORS, PO_VENDOR_SITES_ALL). For manufacturing supply, it references WIP_LINES. These relationships ensure data integrity and enable the seamless execution of replenishment transactions across the Oracle EBS modules.