Results for “card_status”

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

Overview

MTL_KANBAN_CARD_ACTIVITY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the Inventory (INV) product family. It exposes the transactional activity history of Kanban cards, presenting one row per Kanban card activity record. The view is documented in ETRM as "Retrofitted," indicating it was introduced or re-pointed to bridge existing Oracle Forms and concurrent program logic with the underlying Kanban tables during an upgrade cycle. It is valid in both 12.1.1 and 12.2.2.

Its primary role is to present coded status values in decoded, human-readable form. Rather than returning raw lookup codes for supply status and card status, the view joins to MFG_LOOKUPS twice to resolve the corresponding meanings. This makes it well suited for reports, Oracle Discoverer or BI Publisher queries, inbound interfaces, and ad-hoc SQL where a business user must interpret Kanban activity without knowing the lookup code mappings.

Underlying Base Objects

The view is defined over two documented base objects: MTL_KANBAN_CARD_ACTIVITY (exposed via a synonym) and MFG_LOOKUPS (itself a view). The driving table is MTL_KANBAN_CARD_ACTIVITY, aliased MKA, which stores the actual Kanban card activity rows. MFG_LOOKUPS is joined twice under aliases MLK3 and MLK2.

• MLK3 resolves the supply status: it joins on LOOKUP_CODE = MKA.SUPPLY_STATUS where LOOKUP_TYPE = 'MTL_KANBAN_SUPPLY_STATUS', yielding SUPPLY_STATUS_NAME.
• MLK2 resolves the card status: it joins on LOOKUP_CODE = MKA.CARD_STATUS where LOOKUP_TYPE = 'MTL_KANBAN_CARD_STATUS', yielding CARD_STATUS_NAME.

Because both joins are inner joins, an activity row is only returned when a matching lookup code exists for both statuses. The view applies a DECODE to REPLENISHMENT_CYCLE_ID, translating the sentinel value of -1 into NULL so that "no replenishment cycle" is represented cleanly.

Key Columns

• KANBAN_ACTIVITY_ID — Primary key of the activity record.
• KANBAN_CARD_ID / KANBAN_CARD_NUMBER — Identifiers of the Kanban card involved.
• INVENTORY_ITEM_ID / ORGANIZATION_ID — The item and inventory organization context.
• SUBINVENTORY_NAME / LOCATOR_ID — The destination subinventory and locator for the card.
• SUPPLY_STATUS / SUPPLY_STATUS_NAME — Raw code and decoded meaning for supply status.
• CARD_STATUS / CARD_STATUS_NAME — Raw code and decoded meaning for card status.
• KANBAN_CARD_TYPE / SOURCE_TYPE — Card classification and replenishment source type.
• SOURCE_ORGANIZATION_ID / SOURCE_SUBINVENTORY / SOURCE_LOCATOR_ID — The supplying organization, subinventory, and locator; these define the origin of replenishment and are the columns most often used when tracing transfers (source_locator_id is the searched term).
• SUPPLIER_ID / SUPPLIER_SITE_ID — Supplier and supplier site for externally sourced cards.
• WIP_LINE_ID / SOURCE_WIP_ENTITY_ID — Work in process references for production-sourced cards.
• KANBAN_SIZE, DOCUMENT_TYPE, DOCUMENT_HEADER_ID, DOCUMENT_DETAIL_ID — Card sizing and linked document references.
• ERROR_CODE, REQUEST_ID, PROGRAM_ID — Error and concurrent program execution context.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — Descriptive flexfield segments.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, LAST_PRINT_DATE, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical scenarios include Kanban activity auditing, replenishment status reporting, and tracing the supply source of a card.

Activity by card number and decoded status:

SELECT kanban_card_number, supply_status_name, card_status_name, last_update_date
FROM   apps.mtl_kanban_card_activity_v
WHERE  kanban_card_number = :p_card_number;

Locating activity originating from a specific source locator:

SELECT kanban_activity_id, kanban_card_number, source_subinventory, source_locator_id, card_status_name
FROM   apps.mtl_kanban_card_activity_v
WHERE  source_locator_id = :p_locator_id;

Summary of activity grouped by card status for a given organization:

SELECT card_status_name, COUNT(*) activity_count
FROM   apps.mtl_kanban_card_activity_v
WHERE  organization_id = :p_org_id
GROUP  BY card_status_name;

Because the joins to MFG_LOOKUPS are inner joins, queries should account for the possibility that an invalid or unmapped status code will suppress a row; where completeness is critical, querying MTL_KANBAN_CARD_ACTIVITY directly and performing an outer join may be preferable.