Results for “bulk_pick_type”

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

Overview

WMS_OP_PLAN_DETAILS is a Warehouse Management (WMS) transactional table in Oracle E-Business Suite that stores the individual line-level details of an operation plan. Where the parent table WMS_OP_PLANS_B defines the overall operation plan header, WMS_OP_PLAN_DETAILS captures the discrete steps, sequencing, and selection criteria that govern how each operation within a plan is executed. It is a core configuration and runtime construct for warehouse task execution, including picking, put-away, replenishment, and cross-docking activities.

The table is owned by the WMS schema and is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2. The documented physical schema lists 49 columns. Based on the heuristic Data Vault classification mined from the foreign key structure, this object is best modeled as a satellite table. It carries descriptive attributes (operation type, sequence, selection criteria) that depend on the parent operation plan, rather than serving purely as a hub or link. This classification is a modeling suggestion derived from the FK topology, not an Oracle-imposed designation.

Key Information Stored

The table is anchored by a surrogate primary key and a small set of business-relevant identifiers and operational attributes:

• OPERATION_PLAN_DETAIL_ID — the surrogate primary key, enforced by WMS_OP_PLAN_DETAILS_PK.
• OPERATION_PLAN_ID — foreign key to WMS_OP_PLANS_B, linking each detail row to its parent plan.
• OPERATION_TYPE and OPERATION_SEQUENCE — define the kind of warehouse operation and its order within the plan.
• ORGANIZATION_ID — the inventory organization context for the operation.
• ZONE_SELECTION_CRITERIA, PRE_SPECIFIED_ZONE_ID, ZONE_SELECTION_API_ID — control how destination zones are determined.
• LOC_SELECTION_CRITERIA, PRE_SPECIFIED_LOC_ID, LOC_SELECTION_API_ID — control how storage locations are selected.
• SUB_SELECTION_CRITERIA and PRE_SPECIFIED_SUB_CODE — govern subinventory-level selection.
• LPN_SELECTION_CRITERIA and LPN_SELECTION_API_ID — govern license plate number (LPN) selection logic.
• ZD_EDITION_NAME — the editioning column; the unique index WMS_OP_PLAN_DETAILS_U1 spans (OPERATION_PLAN_DETAIL_ID, ZD_EDITION_NAME), making this combination the business-key candidate.
• Standard who-columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• Fifteen descriptive flexfield columns (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15) for customer extensions.

Common Use Cases and Queries

Typical usage centers on retrieving the ordered operations for a given plan and understanding how each step selects its zone, location, subinventory, and LPN. A reporting query joining details to plan headers might appear as:

SELECT d.operation_plan_detail_id, d.operation_sequence, d.operation_type, d.organization_id, p.plan_id FROM wms_op_plan_details d, wms_op_plans_b p WHERE d.operation_plan_id = p.operation_plan_id AND d.operation_plan_id = :plan_id ORDER BY d.operation_sequence;

Because operation instances reference this table, tracing execution history is a common pattern. Joining WMS_OP_PLAN_DETAILS to WMS_OP_OPERATION_INSTANCES on OPERATION_PLAN_DETAIL_ID reveals which planned steps were actually instantiated. Operational dashboards frequently aggregate by OPERATION_TYPE and ORGANIZATION_ID, while tuning exercises examine SYSTEM_DISPATCHED, BULK_PICK_TYPE, and DROP_LPN_OPTION to validate dispatch behavior.

Related Objects

• WMS_OP_PLANS_B — parent plan header; joined via OPERATION_PLAN_ID.
• WMS_OP_OPERATION_INSTANCES — runtime instances referencing OPERATION_PLAN_DETAIL_ID.
• WMS_OP_OPERTN_INSTANCES_HIST — historical operation instances keyed to the same detail ID.
• WMS_OP_OPERTN_INSTANCES_ARCH — archived operation instances carrying the same reference.

These relationships make WMS_OP_PLAN_DETAILS the central linkage between plan configuration and executed warehouse operations.