How to Split a Storage Unit (SU) in SAP WM Using Function Modules

In warehouse management, efficiently organizing and splitting storage units (SUs) is crucial for optimizing space and streamlining operations. SAP's Warehouse Management System (WMS) provides powerful tools to handle these tasks, including function modules that allow you to split storage units programmatically.

Whether you're dealing with stock transfers, replenishment, or simply reorganizing storage bins, knowing how to split an SU using function modules can save time and reduce manual errors. In this blog post, we’ll explore:

  • What a Storage Unit (SU) is and when splitting is necessary
  • Key function modules used for splitting SUs in SAP WM
  • A  step-by-step guide to executing the split process

By the end of this guide, you'll have a clear understanding of how to automate and execute SU splits efficiently in your SAP system. Let’s dive in!

Storage Unit:

In SAP Warehouse Management (WM), a Storage Unit (SU) is a physical or logical grouping of materials stored together in a warehouse. It can be a:

  • Pallet
  • Container
  • Carton
  • Bundle

An SU is identified by a unique Storage Unit Number (LENUM) and is used to simplify stock handling, movement, and tracking. Instead of managing individual items, warehouse operators can move, pick, or put away entire storage units, improving efficiency.

When is Splitting a Storage Unit Necessary.?

1. Partial warehouse stock
  • When only a portion of the stock from an SU is needed (e.g., picking 10 boxes from a pallet of 50).

  • The remaining stock stays in the original SU, while the removed quantity is assigned to a new SU.
2. Stock Reorganization
  • If an SU contains mixed materials that need to be separated for better inventory management.
  • Example: A pallet with different product variants must be split into individual SUs for accurate tracking.
3. Quality Inspection or Blocked Stock
  • If some items in an SU fail inspection and must be quarantined, the SU is split to isolate defective stock.
  • The good stock remains in the original SU, while the blocked stock moves to a new SU.
4. Optimizing Storage Space
  • When an SU is too large for a new storage bin, it can be split into smaller SUs to fit available space.
5. Cross Docking or Replenishment
  • If an SU is received but needs to be distributed to multiple destinations, splitting allows for efficient allocation.

Splitting SU using Function Module (FM: L_TO_CREATE_SINGLE)

Case 1: Businesses prefer manual confirmation of Transfer Orders (TO) only after the stock has been physically placed in the destination bin. To achieve this, the I_SQUIT field should be left blank (not set to auto-confirm).

Source Bin Details:

  • Warehouse: 101
  • Storage Type: 122
  • Storage Bin: AC01011
  • SU Number: 1000000006
  • Split Qty: 2 EA

Destination Bin Details:

  • Warehouse: 101
  • Storage Type: 118
  • Storage Bin: AB01012

Step 1: Check Stock Details (Transaction: LX02/LS26/LS25)

Leelamohan_0-1744525005854.png

Step 2: Executing function module (Transaction: SE37)

Leelamohan_1-1744525135205.png

Fill details warehouse, Mvt. type, Material, Plant, Location, Split Qty, Source bin details, Destination bin details etc.

Leelamohan_2-1744525478200.png

Leelamohan_3-1744525590184.png

Once filled, execute the FM to generate Transfer Order

Leelamohan_4-1744525631587.png

TO 1010000070 created

Step 3: TO Confirmation (Transaction: LT12)

Leelamohan_5-1744525681874.png

Save the TO to confirm.

Step 4: Check stock (Transaction: LX02/LS25/LS26)

Leelamohan_6-1744525749536.png

New SU 1000000015 with 2 EA created in destination bin.

 

Case 2: If the business requirement is to confirm the Transfer Order (TO) immediately after generation, then the I_SQUIT field must be set to "X".

Step 1: Fill respective details in the function module as mentioned

Leelamohan_7-1744526061075.png

Leelamohan_8-1744526070897.png

Once filled, execute the FM to generate Transfer Order

Leelamohan_9-1744526098432.png

TO 1010000071 created

Since you check I_SQUIT field as "X", TO confirmed immediately after TO creation

Leelamohan_11-1744526184048.png

Step 2: Check stock (Transaction: LX02/LS25/LS26)

Leelamohan_12-1744526225178.png

New SU 1000000016 with 2 EA created in destination bin.

Refer below links to know more about warehouse related blogs;

Material Staging through MF60 - WM to IM Managed Location

Material Staging in Production Supply Area-WM/PP Integration

Storage Unit Management with Identification and Pick Points in WM

 

Regards,

Leelamohan Mannem



from New blog articles in SAP Community https://ift.tt/DzuiaLf
A.A.Sumudu Ranasinghe

Department of Industrial Information Technology. Uva Wellassa University.

Post a Comment

Previous Post Next Post