Search Results mtl_kanban_pull_sequences_v




Overview
Explore in AI Chat

Overview

MTL_KANBAN_PULL_SEQUENCES_V is a public Oracle EBS view owned by the APPS schema and classified under the INV (Inventory) product. It exposes the kanban pull sequence configuration that drives replenishment of kanban-controlled items across an organization. A pull sequence defines how a kanban card is replenished when it is emptied, specifying the source type (for example, intra-org transfer, supplier, or work in process), the source organization, subinventory, and locator, and the sizing rules used to determine card quantity. In Oracle EBS 12.1.1 and 12.2.2 the view is treated as retrofitted, meaning it is a compatibility layer over the base table rather than the primary data entry mechanism; the base table MTL_KANBAN_PULL_SEQUENCES continues to hold the authoritative row data.

The view enriches the plain pull sequence record with denormalized descriptive attributes drawn from adjacent setup entities, so callers do not need to join to item master, subinventory, organization, and lookup tables themselves. This makes it suitable for reporting, extracts, and programmatic consumption of kanban definitions. Because it is a view and not a table, it is read-only; any insertion or update must target the base table through the appropriate Inventory forms or APIs.

Underlying Base Objects

The ETRM documentation lists the following referenced objects: HR_GENERAL (package), HR_ORGANIZATION_UNITS (view), HR_SECURITY (package), MFG_LOOKUPS (view), MTL_KANBAN_PULL_SEQUENCES (synonym), MTL_PARAMETERS (synonym), MTL_SECONDARY_INVENTORIES (synonym), MTL_SYSTEM_ITEMS (synonym), PO_VENDORS (view), and WIP_LINES (synonym).

MTL_KANBAN_PULL_SEQUENCES supplies the core pull sequence attributes and is the driving table. MTL_SYSTEM_ITEMS provides item-level location control flags and subinventory/locator restriction codes for the kanban item. MTL_SECONDARY_INVENTORIES is referenced twice to describe the destination subinventory and, separately, the source subinventory locator type. MTL_PARAMETERS supplies organization-level locator control, negative inventory receipt control, and the organization code. HR_ORGANIZATION_UNITS (guarded by HR_SECURITY and HR_GENERAL) supplies the source organization name. MFG_LOOKUPS decodes the source type into a meaningful value, and PO_VENDORS and WIP_LINES support the supplier and WIP line identifiers exposed by the view.

Key Columns

Common Use Cases and Queries

The most frequent use is reporting on kanban pull sequences for a given item or organization, particularly to audit which sequences have automatic recalculation enabled. The following query returns all sequences with the calculate kanban flag set, joined to organization context.

SELECT pull_sequence_id, organization_id, inventory_item_id, subinventory_name, source_type_meaning, calculate_kanban_flag, kanban_size, number_of_cards FROM apps.mtl_kanban_pull_sequences_v WHERE calculate_kanban_flag = 'Y' AND organization_id = :org_id ORDER BY inventory_item_id, pull_sequence_id;

Another common scenario is reconciling source and destination control settings to determine whether users may override the source subinventory or locator at replenishment time.

SELECT pull_sequence_id, inventory_item_id, source_subinventory, source_item_restrict_sub, source_item_restrict_loc, source_org_locator_control FROM apps.mtl_kanban_pull_sequences_v WHERE source_type = 1;

Because SUPPLIER_NAME and WIP_LINE_CODE are NULL in the view text, queries that require those descriptions must join to PO_VENDORS or WIP_LINES on SUPPLIER_ID and WIP_LINE_ID respectively. Reports should also prefer ORGANIZATION_ID filters, since the view is not inherently partitioned by operating unit and relies on HR security for organization visibility when HR_ORGANIZATION_UNITS is accessed.