Results for “auto_request”

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

Overview

MTL_KANBAN_PULL_SEQUENCES is an Oracle Inventory (INV) table that stores the pull sequence definitions used by the Kanban replenishment feature in Oracle E-Business Suite 12.1.1 and 12.2.2. A pull sequence describes how material is replenished at a specific point of use, capturing the relationship between an item, its organization, the supplying subinventory or supplier, and the replenishment parameters that drive card sizing and card counts. It is the master definition layer for Kanban planning; the individual cards that execute that plan are held in a separate, dependent table.

From a Data Vault modeling perspective, the metadata classification is satellite-leaning. The table behaves largely as a descriptive satellite keyed by a surrogate identifier, holding changing attributes about a recognized business entity (item plus organization plus plan plus subinventory), rather than acting as a pure hub or a pure link. Practitioners modeling INV for analytical purposes may wish to separate the durable business key from the measured attributes accordingly.

Key Information Stored

The table is documented with 72 columns. The primary key, MTL_KANBAN_PULL_SEQUENCES_PK, is the surrogate PULL_SEQUENCE_ID. Business-key candidates are captured by two unique indexes: MTL_KANBAN_PULL_SEQUENCES_U1 on PULL_SEQUENCE_ID, and MTL_KANBAN_PULL_SEQUENCES_U2 on the composite of INVENTORY_ITEM_ID, ORGANIZATION_ID, KANBAN_PLAN_ID, SUBINVENTORY_NAME, and LOCATOR_ID. The U2 index is effectively the natural key identifying a pull sequence within a plan.

• PULL_SEQUENCE_ID — surrogate primary key and the join column to Kanban cards.
• INVENTORY_ITEM_ID, ORGANIZATION_ID — the item and inventory organization being replenished.
• SUBINVENTORY_NAME, LOCATOR_ID — the pull point of use within the organization.
• KANBAN_PLAN_ID — the Kanban plan under which the sequence is defined.
• SOURCE_TYPE — indicates the replenishment source (for example supplier, inter-org, or internal subinventory).
• SUPPLIER_ID, SUPPLIER_SITE_ID — supplier sourcing details when the source is external.
• SOURCE_ORGANIZATION_ID, SOURCE_SUBINVENTORY, SOURCE_LOCATOR_ID — the supplying location for internal or inter-org replenishment.
• WIP_LINE_ID — the production line where the sequence is applied, where applicable.
• KANBAN_SIZE, FIXED_LOT_MULTIPLIER, MINIMUM_ORDER_QUANTITY — replenishment quantity drivers.
• NUMBER_OF_CARDS, FUTURE_NO_OF_CARDS, NO_OF_TEMP_CARDS, NO_OF_TEMP_CYCLES — card counts and temporary card logic.
• REPLENISHMENT_LEAD_TIME, SAFETY_STOCK_DAYS, REPLENISHMENT_TYPE — timing and method of replenishment.
• AVG_DEPENDENT_DEMAND, AVG_INDEPENDENT_DEMAND — demand inputs used in sizing calculations.
• CALCULATE_KANBAN_FLAG, ALLOCATION_PERCENT, AGGREGATION_TYPE — calculation and aggregation controls.
• INV_HEALTH_STATUS, PLANNING_UPDATE_STATUS, LAST_IMPLEMENTED_PLAN — status and plan lifecycle tracking.
• PLAN_START_DATE, PLAN_END_DATE, TEMP_EXPIRY_DATE — planning horizon and expiry dates.

Common Use Cases and Queries

Typical reporting scenarios include identifying all active pull sequences for an item and organization, reviewing replenishment parameters before a plan update, and reconciling card counts against defined sequences. A basic query joins the item master to resolve the item number:

• SELECT kps.pull_sequence_id, msi.segment1, kps.organization_id, kps.subinventory_name, kps.number_of_cards FROM mtl_kanban_pull_sequences kps, mtl_system_items_b msi WHERE kps.inventory_item_id = msi.inventory_item_id AND kps.organization_id = msi.organization_id;
• Filter by KANBAN_PLAN_ID to report all sequences within a specific plan.
• Join to MTL_KANBAN_CARDS on PULL_SEQUENCE_ID to compare defined card counts with issued cards.
• Query SOURCE_TYPE and SUPPLIER_ID to analyze supplier-sourced versus internally sourced replenishment.

Related Objects

The table participates in a well-defined set of foreign key relationships that support both the Kanban process and supporting master data.

• MTL_KANBAN_CARDS — references this table on PULL_SEQUENCE_ID; holds the individual cards generated from each sequence.
• MTL_KANBAN_CARD_PRINT_TEMP — also references PULL_SEQUENCE_ID for card printing.
• MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID for item validation.
• MTL_SECONDARY_INVENTORIES — joined on SUBINVENTORY_NAME and SOURCE_SUBINVENTORY for subinventory validation.
• WIP_LINES — joined on WIP_LINE_ID for production line linkage.
• PO_VENDORS and PO_VENDOR_SITES_ALL — joined on SUPPLIER_ID and SUPPLIER_SITE_ID for supplier sourcing.
• MTL_PARAMETERS — joined on ORGANIZATION_ID for organization defaults.
• MTL_INTERORG_PARAMETERS — joined on ORGANIZATION_ID and SOURCE_ORGANIZATION_ID for inter-org transfers.
• MRP_KANBAN_PLANS — referenced via KANBAN_PLAN_ID.