Thursday, 27 February 2025
  0 Replies
  33 Visits
0
Votes
Undo
  Subscribe

For example, the preference might be to pick stock from floor-level bins first.

Introduction

In this blog, I will cover the features in SAP EWM that assist operators in picking efficiently and optimizing the picking process. We will explore the RF features for sorting warehouse tasks, how WTs can be sorted based on business requirements when a WO is generated using WOCR, review the available enhancement options, and discuss best practices for developing custom RF transactions and picking labels

 

Features in RF Picking transactions

Let's consider a scenario where you have bulk bins with mixed SKUs. An operator needs to pick items from these bins for customer orders. We want one operator to handle the entire order, so a single Warehouse Order (WO) with multiple tasks is created. The operator collects the picking label and starts the picking operation.

If the RF gun suggests a different product as the first task, the operator can navigate to the desired product by clicking F4 - Warehouse Task (WT) list.

The RF gun displays all WTs in the WO, and the operator can choose the WT by looking at the product code and continue to confirm

The same screen allows reversing the sequence of WTs using F2 RvSeq. The operator can sort tasks in ascending or descending order

Refer Function module /SCWM/RF_PICK_WHO_TO_SORT

 

Pick Sequence

In a large distribution center (DC), an operator might need to pick 50+ products for an order and build a pallet while picking. The operator walks through several aisles, picks cartons from multiple bins, and finally drops the pallet at the staging area.

The DC must adopt a specific 'Pick Sequence', which refers to the order in which items are picked to fulfill customer orders. This sequence optimizes the picking process, reducing time and effort. The pick sequence can be based on:

  • Warehouse Layout: The physical arrangement of items.
  • Item Location: Specific locations within the warehouse.
  • Item Characteristics: Size, weight, and other attributes.

 

Warehouse Order Creation Rule - Sort Rules

If the DC wants to sequence picks based on the warehouse layout, each bin will be allocated a bin sort sequence number. This number can be generated automatically using /SCWM/SBST.

If a specific sequence is needed, bin sorting can be manually uploaded using /SCWM/SRTUP - Load Storage Bin Sorting. This is a critical activity performed after the bin load into production systems but can be changed later.

For example, the preference might be to pick stock from floor-level bins first. ( Floor bin in Stack 1 & 2 must be picked first and so bin sorting sequence is aligned accordingly Seq 1 , 2, 3, 4)

When a WT is created, it stores the Sort Sequence allocated to the bin in the attribute PATHSEQ. This can be used in the WO Sort rule as part of the Warehouse Order Creation Rule (WOCR).

You can choose the Sort Order as either Ascending or Descending, starting the picking from Aisle 1 or Aisle 2.

Based on PATHSEQ and the Sort rule (PIPA), EWM updates WHOSEQ in the WT, and tasks are sequenced in RF picking transactions. For example, if the bin sort sequence is 1, there are 10 tasks to be picked from the bin, sequenced from 1 to 10.

SAP provides 40 fields to sort WTs when building the warehouse order (Inbound WO / Warehouse Order Outbound Sort). These fields can be used to meet business requirements.

 

Custom Warehouse Order Sort Rules:

If the business requirements cannot be met using the provided 40 fields, custom enhancements are needed.

For example, if an operator needs to pick 50+ products, you might want the system to propose heavier products (over 10 KG) to be picked first to form the pallet base. Products under 10 KG should be picked based on the warehouse layout (pick path sequence). Such requirements cannot be achieved using standard Sort rules.

SAP provides BADI /SCWM/EX_WHO_SORT to customize based on complex requirements. The Warehouse task table CT_TO needs to be sorted based on customer requirements in this BADI. When control moves out of the BADI, SAP standard logic assigns WHOSEQ to CT_TO, which is sorted inside the BADI.

Best Practice:

The standard SAP program sorts warehouse tasks by the WHOSEQ field in RF picking transactions. When developing custom RF transactions, Picking Lists, and Picking Labels, always sort based on WHOSEQ. If programmed to use Bin sorting sequence (PATHSEQ), tasks will not display in the expected sorting sequence though WHOSEQ is built correctly.

 

Conclusion:

SAP EWM offers a robust set of features that significantly enhance the efficiency of warehouse picking operations. By leveraging RF picking transactions, operators can navigate and sort warehouse tasks to meet specific business requirements. The ability to customize task sorting through enhancements like BADI /SCWM/EX_WHO_SORT ensures that even the most complex picking scenarios can be handled effectively

Ayhan Akkaya set the post as Normal priority — 17 hours ago
Ayhan Akkaya set the type of the post as  Blue Print/Consulting — 17 hours ago
Ayhan Akkaya labelled the post as KT - Document — 17 hours ago
There are no replies made for this post yet.

Bottom menu module

SAP is registered trademark of SAP AG.
EWMWIKI.COM is not affiliated to SAP AG or any of its subsidiaries.