Demonstrating Wave Management

Objective

After completing this lesson, you will be able to examine wave management

Wave Management

Introduction

Note

See the following video to learn more about the purpose of a wave in SAP Extended Warehouse Management:

Wave Items

The wave item information results from the outbound delivery item that is assigned to.

Flowchart illustrates the distribution of various WR items into waves from different categories. WR 100 includes WR item 10, WR item 20, and WR item 30, all leading to Wave 1, depicted in magenta. WR 101 contains WR item 10 guiding to Wave 1, WR item 20 and WR item 40 steering to Wave 2, represented in green, and WR item 30 directing to Wave 2. WR 102 entails WR item 10 linking straight to Wave 3, shown in orange. Each WR category is color-coded: WR 100 in blue, WR 101 in turquoise, and WR 102 in yellow.

A wave is created by combining warehouse request items from one or from different warehouse requests. The warehouse requests and the warehouse request items do not need to have anything in common or any relationship for this - but of course, the idea of the wave is to optimize and speed up the picking process, so certain fields, like the route, or the ship-to-party, are usually the same.

Wave Templates

Warehouse request items are grouped into waves based on settings in the wave template.

The wave template is SAP EWM master data. It consists of attributes that define how warehouse request items are processed. With a wave template, you can reuse the same wave attribute for different warehouse request items that have the same conditions.

A wave template is made up of:

  • Release method. Possible values are: Automatic, Immediate, and Manual.

  • Wave type. Different wave types enable specific monitoring in the Warehouse Management Monitor.

  • Wave category. You can use this as a filter for warehouse order creation rules.

  • Date- and time-related fields. These are used to determine wave start and completion dates, and times, for example.

  • Capacity profile. This is used for defining capacity limits.

  • Calendar. This is used for defining workdays.

After a wave template is created, it can be applied manually during manual wave creation or it can be used automatically during warehouse request document processing.

Automatic Wave Assignment

You can create waves manually, but you can automate the assignment of warehouse request items to waves. SAP EWM uses the condition technique to determine wave templates. This enables SAP EWM to determine which wave template corresponds to data from the header, item, or split item of a warehouse request.

The system then uses the planned completion time of the warehouse request items to find the wave option with the fitting wave completion-time. The system creates a wave with the option that has a wave completion-time not later than the planned completion time of the warehouse request item.

Flowchart depicting the process of automatic wave assignment for warehouse request items. On the left, there is a yellow column labeled Wave Templates with options including T1, T2, T3, and T... Each template has options listed underneath. Arrows on the right indicate the process flow: items go through Automatic Wave Assignment with Condition Records listed underneath, resulting in items being sorted into Wave 1, Wave 2, Wave 3, and additional waves.

Automatic wave assignment is triggered by a customizing setting in the warehouse process type. A warehouse process type is assigned to every warehouse request item.

Additionally you have the following options to create waves:

  • Schedule the report /SCWM/R_WAVE_PLAN_BACKGROUND with predefined variants. In this case no condition records are required.
  • You can manually or automatically create waves with reference to a transportation unit. This way you can create waves for items which are leaving the warehouse on the same truck.

Wave Processing

After waves have been created, they can be processed in a number of ways:

  • Waves can be locked or unlocked. This function allows you to block and unblock a wave from further processing.

  • Waves can be merged.

  • Waves can be released. This action creates warehouse tasks and subsequent warehouse orders for the warehouse request items in a wave.

  • Waves can be deleted. This action removes all warehouse request items from a wave.

In addition to these activities, the data associated with wave management can be viewed in the Warehouse Management Monitor. All activities that can be started by wave processing can also be started from the Warehouse Management Monitor.

Another option is to simulate the wave release. This gives the warehouse manager a better understanding of the workload which will be created by the wave release. When it becomes clear that the warehouse tasks need to be processed soon, it is possible to release the wave directly from the simulation.

Summary

  • In SAP EWM, wave management involves grouping warehouse request items into a "wave". By releasing a wave, warehouse tasks are created in order to initiate the warehouse processes.
  • Waves can be created manually or automatically, combining items from various warehouse requests. SAP EWM uses condition records to determine the wave template for automated wave creation.
  • Once created, waves can be maintained in several ways, such as being locked, merged, released, or deleted. The Warehouse Management Monitor allows viewing and managing these activities, including simulating wave release to understand the resulting workload.

How to Use Wave Management

This is part 1 of 2 of the demonstration:

This is part 2 of 2 of the demonstration:

Perform Wave Processing

This is part 1 of 2 of the exercise:

This is part 2 of 2 of the exercise: