Results for “supplier_site_code”

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

Overview

INVFV_KANBAN_CARD_ACTIVITIES is an APPS-owned database view in the Oracle Inventory (INV) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It presents denormalized kanban card activity information, joining the transaction-level activity table to item, organization, locator, supplier, sourcing, and WIP reference data. The view is a retrofitted ("- Retrofitted") object, meaning it was adapted to support multi-organization and referential integrity conventions used in later EBS releases. Its role is primarily reporting and integration: it flattens otherwise cryptic foreign keys and descriptive-flexfield lookups so that replenishment, sourcing, and kanban execution data can be queried directly by reporting tools, BI Publisher, and custom concurrent programs.

Underlying Base Objects

The documented base objects include MTL_KANBAN_CARD_ACTIVITY as the central transactional source, joined to MTL_SYSTEM_ITEMS, MTL_ITEM_LOCATIONS, and MTL_PARAMETERS for item and inventory-organization context. Organization identity is resolved through HR_ALL_ORGANIZATION_UNITS. Supplier data comes from PO_VENDORS and PO_VENDOR_SITES_ALL, while WIP context is provided by WIP_LINES and WIP_ENTITIES. The ETRM metadata also lists related procurement and internal-requisition objects — PO_DISTRIBUTIONS_ALL, PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_RELEASES_ALL, PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, MTL_TXN_REQUEST_HEADERS, and MTL_TXN_REQUEST_LINES — that are referenced in the wider dependency graph used to derive kanban sourcing and replenishment documents. Key joins are outer joins: source organization, source subinventory locator, supplier, and supplier site may be null for cards that are purely internal or not yet sourced.

Key Columns

• KANBAN_ACTIVITY_ID, KANBAN_CARD_ID, KANBAN_CARD_NUMBER — unique identifiers for the activity record and its parent card.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, ORGANIZATION_CODE, NAME — the item and owning inventory organization.
• LOCATOR_ID — the destination locator, joined to MTL_ITEM_LOCATIONS; this is the column most relevant to searches on inventory_location_id, since locator and inventory location identify the same physical stocking position.
• SUBINVENTORY_NAME, KANBAN_SIZE, SUPPLY_STATUS, CARD_STATUS, KANBAN_CARD_TYPE, SOURCE_TYPE — descriptive attributes decoded through MFG lookups.
• SUPPLIER_ID, SUPPLIER_NAME, SUPPLIER_SITE_ID, SUPPLIER_SITE_CODE — external sourcing details.
• SOURCE_ORGANIZATION_ID, SOURCE_SUBINVENTORY, SOURCE_LOCATOR_ID — internal sourcing details.
• DOCUMENT_TYPE, DOCUMENT_HEADER_ID, DOCUMENT_DETAIL_ID — the replenishment document driving the activity.
• ERROR_CODE, LAST_PRINT_DATE, WIP_LINE_ID, LINE_CODE, and standard WHO audit columns.

Common Use Cases and Queries

Typical scenarios include kanban card status reporting, replenishment cycle analysis, and locating all activity for a given stocking location. The following query returns activity for a specific inventory locator:

SELECT kanban_card_number, organization_code, subinventory_name, locator_id,
supply_status, card_status, source_type, last_print_date
FROM invfv_kanban_card_activities
WHERE locator_id = :inventory_location_id
ORDER BY creation_date DESC;

Because the view already resolves organization and item codes, it is commonly used in no-code extracts and in reconciliations between kanban activity and the underlying purchase or move-order documents referenced by DOCUMENT_HEADER_ID. Where supplier data is populated, an outer filter on supplier_id IS NOT NULL isolates externally sourced cards from internal ones.