Search Results invfv_kanban_location_items




Overview
Explore in AI Chat

Overview

INVFV_KANBAN_LOCATION_ITEMS is a seeded Oracle E-Business Suite view owned by the APPS schema within the Inventory (INV) product family. It exposes Kanban pull sequence configuration at the inventory item and location level. In ETRM it is catalogued as a retrofitted object in both 12.1.1 and 12.2.2, with status VALID and the terse description "Retrofitted," indicating the view was reconstructed as part of the 11i-to-R12 (or R12-to-12.2) upgrade path rather than being purpose-built for the R12 data model. Functionally, the view joins Kanban pull sequence rows in MTL_KANBAN_PULL_SEQUENCES to their owning organization and, where applicable, to the source organization that replenishes the Kanban. The inclusion of SOURCE_ORGANIZATION_CODE and the source organization name makes the view particularly valuable for reporting across organization boundaries, which is where the user's search term, "source_organization_code," maps directly. Unlike many inventory inquiries that show only the consuming organization, this view surfaces both the destination and the source side of the replenishment relationship.

Underlying Base Objects

The documented base objects are FND_GLOBAL (package), HR_ALL_ORGANIZATION_UNITS, MTL_ITEM_LOCATIONS, MTL_KANBAN_PULL_SEQUENCES, MTL_PARAMETERS, MTL_SYSTEM_ITEMS, PO_VENDORS, PO_VENDOR_SITES_ALL, and WIP_LINES. The view text confirms an inner core built on MTL_KANBAN_PULL_SEQUENCES (aliased MKP) joined to MTL_PARAMETERS MP1 for the owning organization code, MTL_SYSTEM_ITEMS MSI for item validation, and HR_ALL_ORGANIZATION_UNITS HOU1 for the owning organization name. Source-side joins to MTL_PARAMETERS MP2, HR_ALL_ORGANIZATION_UNITS HOU2, and MTL_ITEM_LOCATIONS MIL2 are outer joins against SOURCE_ORGANIZATION_ID and SOURCE_LOCATOR_ID, which is why SOURCE_ORGANIZATION_CODE and the source name can be null for intra-org, supplier, or WIP-line replenishment. The WHERE clause restricts rows to SOURCE_TYPE IN (1, 3), covering intra-organization and inter-organization replenishment, and to KANBAN_PLAN_ID = -1, which denotes the active Kanban definition rather than a specific plan run. FND_GLOBAL supplies the security context through the '_SEC:MKP.ORGANIZATION_ID' predicate. PO_VENDORS, PO_VENDOR_SITES_ALL, and WIP_LINES appear in the UNION'ed branches that handle supplier and WIP-line sources, matching the NULL SUPPLIER_NAME, SUPPLIER_SITE_CODE, and WIP_LINE_CODE placeholders in the first branch.

Key Columns

Common Use Cases and Queries

The view is most useful for reporting that must correlate a Kanban pull sequence in one organization with the source organization that replenishes it, a pattern common in inter-org Kanban setups.

  • Identify all inter-organization Kanban flows and their supplying organizations.
  • Audit Kanban sizing (card count, Kanban size, MOQ, allocation percent) against safety stock days and replenishment lead time.
  • Reconcile pull sequence configuration across the definition and the source side before running planning or replenishment.

A representative query is:

  • SELECT pull_sequence_id, inventory_item_id, organization_code, source_organization_code, source_subinventory, number_of_cards, kanban_size FROM invfv_kanban_location_items WHERE source_organization_code IS NOT NULL ORDER BY organization_code, source_organization_code;

Because the view enforces organization security via FND_GLOBAL, results are naturally scoped to the operating unit and organization context of the session. When SOURCE_ORGANIZATION_CODE is required but absent, verify that the pull sequence SOURCE_TYPE is 1 or 3 and that KANBAN_PLAN_ID equals -1; supplier and WIP-line sources will return null source organization values and should be filtered or joined to PO_VENDORS or WIP_LINES instead.