Maintaining Warehouse Structures and Master Data

Performing Basic Processes in SAP EWM

Operating the Warehouse

Employing Additional Functions in SAP EWM

Processing Batches

Objective

After completing this lesson, you will be able to use batches in inbound and outbound processes in SAP EWM

Batch Management

Note

See the following video to learn more about what batches are, and why they are needed:

Batches are managed centrally as master data in an SAP ERP system. The SAP ERP system distributes batches to all connected SAP EWM systems through the Core Interface (CIF) or through an IDoc, depending on the SAP EWM release. You can also create and change batches in the SAP EWM system. Batch characteristics describe the technical, physical, and/or chemical properties of a batch, and are stored in the classification system.

Note

In an SAP S/4HANA embedded EWM landscape, batches are not distributed and the batches do not exist additionally in EWM as described above. The process in general does look the same, but the batch exists only once.

The image is a flowchart illustrating different configurations of Enterprise Resource Planning (ERP) and Extended Warehouse Management (EWM) systems. The chart is divided into three sections: The top section has ERP linked to EWM (Business Suite) master data distribution connects via CIF (qRFC) The middle section, labeled Master data S/4HANA with embedded EWM, master data is stored in one system. The bottom section shows ERP linked to Decentralized EWM on S/4HANA master data distribution connects via ALE (IDOC).

Note

The image showing the batch distribution is simplified, only showing the distribution from ERP (which is always the leading master system) to EWM. Batches can be created and changed in EWM. But the distribution of new batches or changes in batches from EWM to ERP does not use the same distribution models as from ERP to EWM (EWM always uses qRFC for the distribution).

Batches in EWM

Batch master data is also available in the SAP EWM system, but looks different depending on the SAP EWM system.

In an SAP S/4HANA-based decentralized EWM system, you have the same transactions as in an ERP system. It depends on the SAP S/4HANA release if you can only display, or if you can also create and change batches with the standard transactions (SAP Note 2808143 - Overview: Batch management, decentralized EWM SAP S/4HANA).

In an SCM based decentralized EWM system, you have a separate transaction for the display, maintenance, or creation of a batch. From the SAP EWM Index screen, choose Extended Warehouse Management→Master Data→Product→Maintain Batches for Product.

As described in the previous section, in an SAP S/4HANA embedded EWM, no separate batch exist in EWM.

Batch Level

The batch level, that is, the level on which the batch is uniquely identifiable, can be set in ERP on different levels.

Plant level:
The batch number is unique in connection with the plant and material.
Material level:
The batch number is unique in all plants associated with the material.
Client level:
The batch number is unique in the entire client. A batch number can only be assigned once in the client. You cannot assign the same batch number for different materials.

SAP EWM supports all the different batch levels.

Batches in Inbound Processes

When you receive material that is batch relevant, a batch must be created before the goods receipt can be posted (as the batch is part of the stock information). The batch creation can happen at various times.

The batch can be created before you create the inbound delivery in ERP and directly entered in that inbound delivery. You can also create a batch in ERP during the creation of the ERP inbound delivery (customizing must be set up accordingly).

With an active CIF model, the batch data is immediately distributed and the batch information of the ERP inbound delivery is also available in the SAP EWM inbound delivery.

For an SAP S/4HANA-based decentralized EWM system the distribution is done through an IDoc. While this usually requires the evaluation of change pointers and the scheduling of the transfer of this IDoc, the SAP Note 2881061 - Decentralized EWM: Enhanced Settings for ALE Data Transfer, describes what to implement to overcome this limitation.

Flowchart illustrating a data synchronization process between ERP (Enterprise Resource Planning) and EWM (Extended Warehouse Management) systems. The ERP section, on the left, has two consecutive steps: Step 1 shows the creation of Batch 4711 as a document/master record, followed by Step 3, which generates an Inbound Delivery document containing Batch 4711. This document is transferred to the EWM section on the right, through a bridge labeled CIF/IDoc. In the EWM section, Step 2 shows the reception of Batch 4711 and Step 4 displays the generated Inbound Delivery document, again containing Batch 4711. Yellow arrows interconnect the steps within each system while blue arrows denote the transfer of data from ERP to EWM. The ERP section is blue-bordered, and the EWM section is green-bordered, visually distinguishing them.

Batch Creation in EWM Inbound Delivery

The batch can also be created in SAP EWM. In that case, it is automatically created in the background in ERP using a remote function call.

In a SCM based EWM the transaction /SCWM/WM_BATCH_MAINT can be used to create, change, and display batches. This transaction is not available in an SAP S/4HANA based EWM.

The batch can also be created in SAP EWM in the inbound delivery itself. In this case, in the standard, only the standard characteristics production date, shelf life expiration date, and country of origin can be maintained directly. Other characteristics must be maintained in the batch master record. This can of course be done in ERP. In a SCM based EWM it can be done with the transaction /SCWM/WM_BATCH_MAINT. Batch characteristics can also be changed during quality inspection in SAP EWM, independent if it is SCM or SAP S/4HANA based.

From SAP S/4HANA 2020 FPS01 it is also possible to change or create the batch in the decentralized EWM system with the standard batch transactions.

The image depicts a diagram illustrating the flow of information between an ERP (Enterprise Resource Planning) system and an EWM (Extended Warehouse Management) system with respect to batch creation. The diagram is divided into two sections: ERP on the left in blue and EWM on the right in green. Four steps in the process are highlighted with numbered yellow circles. Step 1 shows an (EWM) Inbound Delivery document with batch 4711 on the EWM side, from which a yellow arrow emerges, pointing to the left (ERP) where batch 4711 is created (step2). Step 2 shows this batch 4711 document/master record on the ERP side. Between Step 2 and Step 3, there is a blue arrow labeled CIF/IDoc moving from the ERP side to the EWM side, indicating that batch 4711 is now created on the EWM side. Step 4 shows an Inbound Delivery document containing batch 4711 now being created on the ERP side, with a thick blue arrow pointing back towards the inbound delivery document from step 1 on the EWM side.

Create Batches in Inbound Processes

This is part 1 of 3 of the exercise:

ExerciseStart Exercise

This is part 2 of 3 of the exercise:

ExerciseStart Exercise

This is part 3 of 3 of the exercise:

ExerciseStart Exercise

Batches in Outbound Processes

You can assign batches to be sold or picked manually at certain points, but it can be done automatically using batch determination, which uses condition technique. This enables you to define your own search strategies by choosing the relevant key fields from the business transaction to search for batches. For example, you choose the combination of customer and material and then specify the criteria for batch selection.

Batch Determination in Sales Orders

The batch can be determined automatically in the sales order. This batch is then copied into the ERP outbound delivery and the SAP EWM outbound delivery order and picking is limited to quants that are part of this batch. However, in a sales order, batch splits are not possible. This means that the system assigns one batch only. If this batch does not have the required quantity, the rest of the sales order is never fulfilled.

Batch Determination in Deliveries

During a batch determination in a delivery, the system always creates a batch split. The system can select as many batches as are required to fulfill the requested quantity, as long as the batch determination criteria are fulfilled. In the case where not enough stock is available in the right batches, the sales order is still open and can be fulfilled later when new batches with the required criteria are available.

Batch Determination with SAP EWM

From a warehouse point-of-view, a batch assigned in the ERP outbound delivery may not be the best choice, because the sort criteria for the batch determination do not reflect any picking strategies. SAP EWM does not have batch determination functionality. However, the interface can be set up so that ERP batch determination in the outbound delivery is only being used to determine the batch determination criteria that needs to be fulfilled, without assigning a batch. These criteria are then passed on to SAP EWM and used to determine the best quant from a warehouse picking strategy, while fulfilling the batch determination requirement.

The image illustrates a process flow diagram showing the integration between ERP (Enterprise Resource Planning) and EWM (Extended Warehouse Management). On the left side, under the ERP section, there are two rectangles labeled Batch determination. Each rectangle points with an arrow to a document labeled Outbound Delivery, with one document indicating Batch 4711 and the other Colour: Red. From the Outbound Delivery documents, arrows point to the right side, under the EWM section, where there are two documents labeled Outbound Delivery Order. The documents maintain the same batch and color information, Batch 4711 and Colour: Red, respectively. Arrows from the Outbound Delivery Order documents lead to yellow rectangles on the right, labeled Warehouse Task, which both bear the inscription Batch 4711. The diagram is visually separated with ERP content on a blue background and EWM content on a green background.

Summary

Batches are used to manage legal requirements, quality tracking needs, or production specifications for a batch of one product. A batch describes a products that have been produced under the same conditions, and its data is managed centrally in SAP ERP, distributed to SAP EWM systems.
For inbound processes the batch information can be distributed from SAP ERP into SAP EWM via the inbound delivery. The batch information can also be maintained directly in SAP EWM during receipt of the material. SAP EWM will then ensure that the batch information is also distributed into the corresponding document in SAP ERP.
For outbound processes a specific batch can be requested in the outbound delivery in SAP ERP. SAP EWM can also determine the batch for the outbound delivery order based on a batch determination strategy applied to the sales order in SAP ERP.

Select Batches in Outbound Processes

This is part 1 of 2 of the exercise:

ExerciseStart Exercise

This is part 2 of 2 of the exercise:

ExerciseStart Exercise

Next lesson