Search Results kanban_card_number




Overview
Explore in AI Chat

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

Overview

MTL_KANBAN_CARDS is the Inventory (INV) transactional master table that stores Kanban card definitions used by Oracle E-Business Suite's Kanban replenishment functionality. Each row represents a single Kanban card, which acts as the control record driving pull-based replenishment for an inventory item within an organization. Kanban cards trigger replenishment transactions such as inter-org transfers, WIP jobs, purchase requisitions, and supplier-sourced supplies. The table resides in the INV schema and is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2.

From a data-modeling perspective, the heuristic Data Vault classification for MTL_KANBAN_CARDS is hub. This reflects its role as the central entity whose KANBAN_CARD_ID is referenced by more than twenty downstream tables spanning WIP, Purchasing, EAM, and interface staging structures. The documented primary key is MTL_KANBAN_CARDS_PK on KANBAN_CARD_ID, and the table holds 52 documented columns.

Key Information Stored

The table's surrogate primary key is KANBAN_CARD_ID, uniquely enforced by unique index MTL_KANBAN_CARDS_U1. A second unique index, MTL_KANBAN_CARDS_U2, establishes (KANBAN_CARD_NUMBER, ORGANIZATION_ID) as the business-key candidate. Key user-facing and foreign-key columns include:

The table also carries the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and fifteen ATTRIBUTE columns for DFF extensions.

Common Use Cases and Queries

Typical usages include Kanban card status reporting, pull sequence analysis, replenishment exception monitoring, and integration with planning or procurement.

Listing all active cards for an organization:

  • SELECT kanban_card_number, inventory_item_id, subinventory_name, card_status FROM mtl_kanban_cards WHERE organization_id = :org AND card_status = 'ACTIVE';

Finding supplier-sourced cards requiring requisition creation:

  • SELECT kc.kanban_card_number, kc.supplier_id, kc.supplier_site_id FROM mtl_kanban_cards kc WHERE kc.source_type = 'SUPPLIER' AND kc.card_status = 'NEW';

Reporting replenishment activity against a card's activity history by joining to MTL_KANBAN_CARD_ACTIVITY on KANBAN_CARD_ID, and tracing to MTL_TXN_REQUEST_LINES via REFERENCE_ID for move-order generation. Reporting standards typically join INVENTORY_ITEM_ID to MTL_SYSTEM_ITEMS_B (with ORGANIZATION_ID) and PULL_SEQUENCE_ID to MTL_KANBAN_PULL_SEQUENCES to render fully described card listings.

Related Objects

The following are among the most significant dependent or referenced objects:

These relationships confirm the table's role as a central hub for Kanban-driven replenishment across inventory, manufacturing, and procurement flows.