Search Results mtl_kanban_card_activity

Overview

The MTL_KANBAN_CARD_ACTIVITY table is a core transactional repository within Oracle E-Business Suite Inventory (INV) that logs all significant events and lifecycle state changes for Kanban cards. In the context of Oracle EBS 12.1.1 and 12.2.2, it serves as the system of record for the Kanban pull-based replenishment process. Its primary role is to track the progression of a Kanban card from its initial generation through its various consumption, replenishment, and fulfillment states, providing a complete audit trail. This activity data is essential for monitoring supply chain efficiency, troubleshooting replenishment issues, and generating historical performance reports for Kanban-controlled items.

Key Information Stored

The table's primary key is KANBAN_ACTIVITY_ID, which uniquely identifies each logged event. The table stores identifiers that link the activity to the specific Kanban card (KANBAN_CARD_ID), the item involved (INVENTORY_ITEM_ID), and the organization (ORGANIZATION_ID). Crucially, it holds references to the various transactional documents generated by the system in response to card signals, such as purchase orders, requisitions, work orders, or material transactions. These are stored in DOCUMENT_HEADER_ID and DOCUMENT_DETAIL_ID columns. Other significant columns track the activity type or status, source and destination subinventories (SOURCE_SUBINVENTORY, SUBINVENTORY_NAME), and supplier information (SUPPLIER_ID, SUPPLIER_SITE_ID) for externally sourced cards.

Common Use Cases and Queries

A primary use case is tracing the complete history of a specific Kanban card to diagnose why a replenishment signal was not acted upon. Analysts query this table to identify cards stuck in a particular status. Another common scenario is generating a report on Kanban activity volume over a period to assess process health. A sample query to find all activities for a card and their associated documents would be:

SELECT activity.KANBAN_CARD_ID,
       activity.INVENTORY_ITEM_ID,
       activity.ACTIVITY_TYPE,
       card.CARD_NUMBER,
       po.segment1 PO_NUMBER
FROM   INV.MTL_KANBAN_CARD_ACTIVITY activity,
       INV.MTL_KANBAN_CARDS card,
       PO.PO_HEADERS_ALL po
WHERE  activity.KANBAN_CARD_ID = card.KANBAN_CARD_ID
AND    activity.DOCUMENT_HEADER_ID = po.po_header_id(+)
AND    activity.organization_id = :p_org_id
ORDER BY activity.KANBAN_ACTIVITY_ID;

This data is also vital for custom integrations that need to react to Kanban status changes or for building operational dashboards.

Related Objects

As indicated by its extensive foreign key relationships, MTL_KANBAN_CARD_ACTIVITY is a central hub connecting Kanban operations to other EBS modules. Key documented relationships include:

• MTL_KANBAN_CARDS: The parent Kanban card definition, joined on KANBAN_CARD_ID.
• MTL_SYSTEM_ITEMS_B: The item master, joined on INVENTORY_ITEM_ID and ORGANIZATION_ID.
• PO_HEADERS_ALL & PO_REQUISITION_HEADERS_ALL: Purchase and requisition documents, joined on DOCUMENT_HEADER_ID.
• PO_DISTRIBUTIONS_ALL & PO_REQUISITION_LINES_ALL: Document lines, joined on DOCUMENT_DETAIL_ID.
• WIP_ENTITIES & WIP_LINES: Work order and line details for production Kanbans.
• MTL_TXN_REQUEST_HEADERS & MTL_TXN_REQUEST_LINES: Material transaction requests (Move Orders).
• MTL_SECONDARY_INVENTORIES: For both source and destination subinventories.
• PO_VENDORS & PO_VENDOR_SITES_ALL: Supplier information for external replenishment.