Search Results mtl_inv_picking_rules_pk

Overview

MTL_INV_PICKING_RULES is an Inventory module table owned by the INV schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the picking rule definitions that Oracle Inventory and Oracle Warehouse Management use to determine how material is selected, sorted, and allocated when a picking transaction is generated. Each row represents a named picking rule that governs lot selection, revision control, shelf-life enforcement, subinventory and locator sequencing, and whether partial or single-lot picks are permitted. The table therefore acts as the configuration backbone for outbound material handling strategies across order management, shipping, and warehouse execution flows.

The primary key is MTL_INV_PICKING_RULES_PK, defined on the INV_RULE_ID column. Under a heuristic Data Vault classification, MTL_INV_PICKING_RULES is best modeled as a hub candidate, since INV_RULE_ID serves as the unique business key and is referenced by multiple downstream tables as a foreign key. The rule attributes themselves behave as satellite-style descriptive columns attached to that hub.

Key Information Stored

The documented physical schema contains 56 columns. The most operationally significant are:

• INV_RULE_ID — the surrogate and business key (MTL_INV_PICKING_RULES_PK) uniquely identifying each rule.
• SHELF_DAYS — minimum remaining shelf life required for a lot to be eligible for picking.
• SINGLE_LOT — indicates whether the rule restricts picking to a single lot.
• PARTIAL_ALLOWED_FLAG — controls whether partially available quantities may be picked.
• CUST_SPEC_MATCH_FLAG — enforces customer specification matching during selection.
• LOT_SORT and LOT_SORT_RANK — define lot-level sort criteria and their priority order.
• REVISION_SORT and REVISION_SORT_RANK — govern revision sequencing and priority.
• SUBINVENTORY_SORT and SUBINVENTORY_SORT_RANK — control subinventory selection order.
• LOCATOR_SORT and LOCATOR_SORT_RANK — control locator (bin) selection order.
• WMS_RULE_ID and WMS_STRATEGY_ID — link the rule to Oracle Warehouse Management rule and strategy definitions.
• APPLY_TO_SOURCE — determines whether the rule applies at the source level.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–30 — the standard EBS descriptive flexfield columns.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY and the WHO audit columns — standard concurrency and audit tracking.

Common Use Cases and Queries

Picking rules are typically queried to audit allocation behavior, to resolve why a particular lot or subinventory was chosen, or to replicate rule configurations across organizations. A common pattern joins the rule to WMS strategy data:

• Listing all picking rules with their shelf-life and single-lot constraints for a review of outbound policy.
• Identifying rules that allow partial picks where business policy requires full-lot fulfillment.
• Reporting on lot, revision, subinventory, and locator sort ranks to verify prioritization logic.
• Tracing a picking rule reference back from order management or payment terms tables to confirm configuration lineage.

A representative query selects INV_RULE_ID, SHELF_DAYS, SINGLE_LOT, PARTIAL_ALLOWED_FLAG, LOT_SORT, SUBINVENTORY_SORT, and LOCATOR_SORT from MTL_INV_PICKING_RULES, filtered by the relevant rule identifiers. Because the table is configuration-driven, reporting is usually read-only.

Related Objects

INV_RULE_ID is referenced as a foreign key by several objects across Inventory, Order Management, and Payments:

• OKC_K_LINES_B and OKC_K_LINES_BH (INV_RULE_ID) — contract line rule assignments.
• OKI_SALES_K_HDRS (INV_RULE_ID) — sales contract header references.
• PN_PAYMENT_TERMS_ALL and PN_PAYMENT_TERMS_HISTORY (INV_RULE_ID) — payment terms linkage.
• PN_TERM_TEMPLATES_ALL (INV_RULE_ID) — term template references.

These relationships confirm that the table is a referenced master, reinforcing its classification as a hub-style entity whose INV_RULE_ID drives dependent link and satellite structures.