Chapter 5 Outbound Processing

Wave Management in EWM

• Warehouse request items are grouped under waves to control warehouse activities like picking or posting changes.
• These groupings are processed together to create warehouse tasks, which are then forwarded to create warehouse orders for picking or posting changes.
• Waves can be created manually using the shipping cockpit or automatically when an outbound delivery order is created.
• Waves are automatically created via PPF action after the outbound delivery order is created, either immediately or automatically via report RSPPFPROCESS.
• To perform automatic wave assignment with wave templates, wave templates and conditions for wave template assignment need to be set up.
• Waves can be processed with statuses like locked, unlocked, deleted, and merged. Splitting waves and releasing is also possible.
• Wave templates have attributes for capturing dates and times, such as wave completion dates, pick start and completion dates, and pack start and completion dates.
• A wave template is assigned a factory calendar to determine valid days for the wave completion date.
• A wave template uses the release method to determine automatic, manual, or immediate release after wave creation.
• A wave template contains control parameters used to create waves for a warehouse request.
• Warehouse request items are grouped into waves based on settings in the wave template.
• Wave templates are determined using a condition technique.
• Wave template requires dates for Pick start and Pick completion, along with a Wave calendar

Stock Removal Strategies in EWM

• For a stock removal process, the SLED strategy is used based on the expiry date or shelf life of a batch.
• Valid stock removal strategies are FIFO, LIFO, SLED, and partial quantities first.
• FIFO and LIFO work based on the goods receipt date captured in the WDATU and WDATU_DATE fields.
• SLED works on the value in the VFDAT field for the shelf-life expiration of batches.
• Partial quantities first strategy works on the basis of alternate UoMs maintained in the packaging specification.

Decentralized EWM Documents

• An outbound delivery request is replicated from an unchecked or checked SAP S/4HANA delivery document in decentralized EWM.
• Outbound delivery request is generally based on delivery processing related to the creation of sales orders within the SAP CRM application.
• SAP CRM can be configured to suppress the replication of sales documents to the SAP S/4HANA system.
• In SAP S/4HANA, the unchecked delivery is converted to a checked delivery, which is then replicated to the EWM system (outbound delivery request).

Outbound Delivery Order Processing in EWM

• When processing outbound delivery orders in EWM, picking from the stock and packing and staging are involved steps.
• Pick warehouse tasks are created for outbound delivery orders to remove stock from the source bin for picking.
• If the picked stock needs relabeling and repacking, Value Added Services (VAS) is added as part of POSC.
• Picked products are staged and packed or repacked before being loaded onto the truck.
• Outbound delivery in SAP S/4HANA, and an outbound delivery order, are the documents created for the goods issue or outbound process.

EWM and SAP S/4HANA Integration

• It is mandatory to map an SAP S/4HANA document type with an EWM delivery document type.
• When configuring a new document type or item in EWM, it must be mapped to SAP S/4HANA delivery types and item categories.
• This mapping aids in the integration between EWM and SAP S/4HANA.

Warehouse Tasks in EWM

• Warehouse tasks for stock removal for outbound processes in EWM require the warehouse process type, which is assigned to the outbound delivery order.
• Inbound and outbound delivery orders are considered warehouse requests in EWM and are used for further processing.
• To create a pick task, the warehouse process type is assigned to an outbound delivery order.

Direct Outbound Deliveries in EWM

• Direct outbound delivery orders are created in EWM without reference to sales orders or STOs, and are not created for replenishment, or posting inventory differences, or rearrangement processes.
• Direct outbound delivery orders can be created for goods issues to a cost center, for customer pickups, for scrapping, for kit-to-stock, or reverse kitting.

Wave Processing

• Wave statuses can be locked, unlocked, merged, released, split or deleted as required.
• Wave processing is performed via Transaction /SCWM/WAVE, Transaction /SCWM/MON, or the shipping cockpit.

Warehouse Order Creation

• The warehouse order creation process for picking waves begins with a list of warehouse requests.
• The next step involves grouping warehouse requests into waves and then releasing these waves to create warehouse tasks.
• The sequence of wave execution follows how warehouse request items are grouped into a wave.
• When the system releases a wave, warehouse tasks are created, which then determines the warehouse order creation rule from the activity area, which influences the routing.
• Warehouse orders are created according to the warehouse order creation rule defined in Customizing
• Warehouse request items are grouped into waves based on the settings in the wave template.

Automatic Wave Template Assignment

• To assign wave templates automatically, condition technique needs to be maintained.

Delivery Document Header Information

• General data in the delivery document header for inbound and outbound processing, posting changes, and stock transfers includes means of transport and sold-from party.
• The header contains information like the goods receiving and shipping office, weights and volume for the complete delivery, route information from the SAP S/4HANA delivery, means of transport, and overall status of the delivery confirmation.

Wave Processing in Transaction /SCWM/WAVE

• Transaction /SCWM/WAVE can be used to lock waves or release withdrawals.

Stock Removal Indicator Configuration

• Stock removal indicators are configured in EWM and not obtained from the outbound delivery order.
• When creating a picking warehouse task for the EWM product master in an outbound delivery order, the system gets the stock removal indicators for that combination of warehouse, product, and party entitled to dispose.

POSC for Outbound Shipping

• Process-oriented storage control (POSC) for outbound shipping involves picking, VAS, packing, and loading. The deconsolidation step is present for inbound processing.

Storage Type Determination for Pick Warehouse Tasks

• The system attempts to read completely qualified entries with all the parameters and indicators based on the access sequence defined in the configuration to determine the storage type for creating pick warehouse tasks.
• The system attempts to read a completely qualified entry, with all parameters and indicators; then it uses the defined access strategy.
• Parameters are obtained from the delivery, product master data, and packaging specifications.
• The system looks for the access sequence maintained for the combination to determine the stock removal indicator, which contains the information about the storage type search sequence.
• The access sequence is configured as part of the stock removal strategy.

EWM Item Categories

• Valid item categories in EWM include: DLV (standard delivery item), PAC (packing item), RET (return item), TXT (text item), and VAL (value item).

Cartonization Planning

• Cartonization planning can be performed during picking and packing or for outbound delivery orders in EWM.
• Automatic cartonization is used for the documents in outbound delivery orders, waves, and warehouse order creation.
• Cartonization planning uses planned shipping handling units (HUs) as templates for creating shipping HUs for picking and packing in an outbound process.