4/3/25, 7:52 PM

Extended Warehouse Management (EWM)

Generated on: 2025-04-03 19:52:02 GMT+0000

SAP S/4HANA | 2023 Latest

Public

Original content: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/9832125c23154a179bfa1784cdc9577a?locale=en-

US&state=PRODUCTION&version=2023.003

Warning

This document has been generated from SAP Help Portal and is an incomplete version of the official SAP product documentation.
The information included in custom documentation may not reflect the arrangement of topics in SAP Help Portal, and may be
missing important aspects and/or correlations to other topics. For this reason, it is not for production use.

For more information, please visit https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit SAP Help Portal. 1
 4/3/25, 7:52 PM

Migration from LE-WM

This section contains information on the functions available to migrate data from an LE-WM system to Extended Warehouse
Management (EWM). The following features are available:

Warehouse Product Migration

Storage Bin Migration

Stock Migration

Physical Inventory Completeness Migration

Map Storage Unit Type to Packaging Material

Map Warehouse Management Unit of Measure to Packaging Material

Goods Receipt

Use
Putaway enables you to display your complex putaway process steps and includes the following functions:

Unloading

Deconsolidation

Final Putaway

It takes into account your warehouse arrangement (for example, putaway using identification points in a high rack storage area) as
well as the process-oriented rules and process flows defined by you (for example, repacking). Extended Warehouse Management
(EWM) contains putaway strategies to simplify the search for appropriate storage bins.

You can put away your products directly or through storage control.

You can only execute complex putaway processes by using handling units.

Prerequisites
You have defined the following basic settings in Customizing for Extended Warehouse Management:

Basic settings are, for example:

Customizing Activity Navigation Path

Storage types, storage area, storage bins Customizing for EWM under Master Data:

⇒ Define Storage Type

⇒ Define Storage Section

⇒ Storage Bins

This is custom documentation. For more information, please visit SAP Help Portal. 2
 4/3/25, 7:52 PM

Customizing Activity Navigation Path

Activity Areas Customizing for EWM under Master Data Activity Areas
Define Activity Areas

Activities Customizing for EWM under Master Data Activity Areas

Activities Define Activity Areas

If required, work centers, for example, for deconsolidation For more information about defining putaway steps, see
Customizing for EWM under Master Data Work Center
Define Work Center .

Doors Customizing for EWM under Master Data Warehouse Door

Define Warehouse Door

Staging areas Customizing for EWM under Goods Issue Process Define
Staging Areas

You have displayed your putaway steps in the system.

For more information about defining putaway steps, see Customizing for EWM under Cross-Process Settings
Warehouse Task Layout-Oriented Storage Control or Process-Oriented Storage Control.

All required processes are fully integrated. The system updates, for example, the inbound delivery in the warehouse
activities.

Process
1. The process begins when SAP ERP receives an advanced shipping notification from an external system (for example, SAP
CRM) for a planned inbound delivery.

2. SAP S/4HANA uses this advanced shipping notification to create an inbound delivery, and distributes it to EWM.

3. EWM uses the data from this inbound delivery to create a warehouse request.

This warehouse request is the starting point for the putaway process.

If you reject the inbound delivery in EWM, EWM sets the planned delivery quantity to zero and notifies the SAP S/4HANA
system. EWM ends the inbound delivery and sets the status of the warehouse request to Completed.

 Note
For more information, see Warehouse Request of the Returns Type.

Result

EWM uses the warehouse request to create one or more warehouse tasks (WTs) for the putaway. You can use it to put away the
products.

Goods Issue

Use

A goods issue from Extended Warehouse Management (EWM) is a physical departure of products from your warehouse. With a
goods issue posting, you reduce the stock in the warehouse. You can use a goods issue to indicate goods deliveries to your

This is custom documentation. For more information, please visit SAP Help Portal. 3
 4/3/25, 7:52 PM
customers.

A warehouse request goods issue allows you to display your complex stock removal process steps and includes the following
functions:

Storage Bin Determination for Stock Removal

Stock Removal

Packing at the Work Center

Loading and Unloading

When you display the goods issue process using a warehouse request, you can execute the warehouse-internal processes that
precede the actual goods issue, such as picking or packing, within the warehouse before you trigger the actual goods issue posting.

The goods issue takes into account your warehouse arrangements, such as stock removal using pick points from a high rack
storage area, as well as the process-oriented rules and procedures defined by you, such as packing during warehouse task
confirmation. To simplify the search for appropriate stock, EWM offers you Stock Removal Strategies.

You can remove your products from stock either directly or by using Storage Control.

You can only execute complex stock removal processes by using handling units.

You can use the warehouse request to automatically trigger the goods issue processing. To do this, you use the warehouse task as
the main document upon which you display all goods movements in EWM.

For more information, see Warehouse Request of the Type Inbound Delivery or Outbound Delivery Order.

Prerequisites

The data for the warehouse request for outbound delivery in EWM is complete.

The warehouse request is relevant for picking.

For examples of basic settings, see the prerequisites information under Goods Receipt.

You have defined the following basic settings in Customizing for EWM:

A stock removal strategy under Goods Issue Process Strategies Define Stock Removal Strategy .

A stock removal control indicator under Goods Issue Process Strategies Define Stock Removal Control Indicator .

Process
1. EWM receives a goods issue request from another system, for example an SAP system.

2. EWM creates a warehouse request of the type outbound delivery order, which is the starting point for the goods issue.

3. EWM recognizes, on the item level of the warehouse request, which delivery items are relevant for stock removal with EWM.

For more information, see Generation of Warehouse Request of Outbound Delivery Order Type.

The availability check for the goods issue takes place on the level of the prestored components. EWM does not carry out an
independent availability check, but instead assumes a purely execution function.

4. You create a warehouse task for picking from your warehouse for the warehouse request.

This is custom documentation. For more information, please visit SAP Help Portal. 4
 4/3/25, 7:52 PM
5. When you create a warehouse task, the system creates corresponding warehouse orders. These warehouse orders group
the warehouse tasks in accordance with the rules defined in Customizing. This means that you receive individual work
packages that a worker is to carry out at a certain time (see Warehouse Order Creation).

You can create the warehouse task directly or let EWM create it automatically.

EWM can create warehouse tasks in the following manner:

By default, directly through the release of a wave

Automatically, using a Post Processing Framework (PPF) action

You can create the warehouse tasks manually.

For more information, see Creation of Warehouse Tasks for Warehouse Request, Creation of Warehouse Tasks for Stock
Removal, or Wave Management.

You can take into account batch information when creating warehouse tasks for picking.

6. If you have not determined the batches to be picked in the warehouse request, and you want to pick one or more batches to
cover the required quantity completely, you must verify these batches to the outbound delivery. In doing so, you create a
new warehouse request item for each batch.

7. You either print the warehouse request with the warehouse tasks as a list, or you print all individual documents at once. If
you remove the goods from the determined source storage bins to the goods issue interface, you can use this printout as
the picking document.

For more information, see Printing Warehouse Orders and Warehouse Tasks.

8. Once you have completed the picking, you confirm the warehouse tasks.

9. You carry out further goods issue activities, such as packing or loading.

For each goods issue activity, EWM creates a separate warehouse task, which you confirm after you have completed the
physical activity.

With this confirmation, you confirm that you have brought the goods to the goods issue interface.

This records any stock differences between the required and the picked quantity.

For more information, see Handling Differences When Picking for Warehouse Request.

10. You post the goods issue for the warehouse request.

EWM updates the activity status when a step of the warehouse task processing has been completed. You can inform
yourself about the outbound delivery status during the entire goods issue process.

For more information, see Creation of Warehouse Tasks for Warehouse Request.

Using Storage Control

For more information about goods issue processes using storage control, see Storage Control, Layout-Oriented Storage Control, or
Process-Oriented Storage Control.

Result

EWM reduces the storage bin stock in the source storage bin by the picked product quantity and posts this quantity to the
destination storage bin.

Cartonization Planning
This is custom documentation. For more information, please visit SAP Help Portal. 5
 4/3/25, 7:52 PM

Use

You can use cartonization planning to improve the creation of shipping handling units (HUs) based on information from product
master data and outbound delivery orders, such as quantities, volume, and weight. Cartonization planning results in the creation of
planned shipping handling units (PSHUs) that you can use as templates for creating shipping HUs during picking or packing.

A PSHU is an object similar to a shipping HU, describing a packaging material and the items it contains. In contrast to a shipping
HU, a PSHU does not physically exist in the warehouse and is only used to plan shipping HUs. You can create PSHUs manually or
automatically in cartonization planning. You can create nested PSHUs for cartonization planning of deliveries where HUs are
packed into larger HUs.

Automatic cartonization planning uses algorithms to create PSHUs. Algorithms are defined as implementations of the Business
Add-In BAdI: Cartonization Planning Algorithm. The default implementation aims at minimizing the number of HUs. The default
algorithm uses a heuristic approach. It is not an optimization. For more information, see Customizing for Extended Warehouse
Management under Business Add-Ins (BAdIs) for Extended Warehouse Management Goods Issue Process Cartonization
Planning BAdI: Cartonization Planning Algorithm .

To use this feature, you must activate the business function EWM, Essential Foundation Functions (SCM_EWM_FND).

Prerequisites
Prerequisites for Cartonization Planning

Features

Cartonization planning can take place automatically, with the system using algorithms to create PSHUs. For more information, see
Automatic Cartonization Planning.

Automatic cartonization planning has the following variants:

Cartonization Planning for Outbound Delivery Orders

Cartonization Planning for Waves

Cartonization Planning During Warehouse Order Creation

You can test automatic cartonization planning with different algorithms. For more information, see Maintenance of Planned
Shipping Handling Units.

The system uses PSHUs as templates for creating shipping HUs during picking or packing. For more information, see the following:

Picking with Cartonization Planning

Packing with Cartonization Planning

You can monitor, change, or delete PSHUs. For more information, see the following:

Monitoring of Planned Shipping Handling Units

Maintenance of Planned Shipping Handling Units

Deletion of Planned Shipping Handling Units

Example

This is custom documentation. For more information, please visit SAP Help Portal. 6
 4/3/25, 7:52 PM
Sample Use Cases for Cartonization Planning

Prerequisites for Cartonization Planning

For cartonization planning, the following prerequisites must be met:

For the determination of process profiles for cartonization planning, you have carried out the following Customizing
activities:

Define Process Profiles for Cartonization Planning

Determine Process Profiles for Cartonization Planning

For more information, see Customizing for Extended Warehouse Management under Goods Issue Process
Cartonization Planning .

For the determination of algorithm profiles for cartonization planning, you have carried out the following Customizing
activities:

Define Algorithm Profiles for Cartonization Planning

Define Access Sequence of Algorithm Profiles

For more information, see Customizing for Extended Warehouse Management under Goods Issue Process
Cartonization Planning .

For the determination of algorithm profiles for cartonization planning, you have also made your settings on the launchpad
under Extended Warehouse Management Settings Determine Algorithm Profiles for Cartonization Planning .

To execute automatic cartonization planning, you have at least one active implementation of the Business Add-In (BAdI)
method EXECUTE.

For more information, see Customizing for Extended Warehouse Management under Business Add-Ins (BAdIs) for
Extended Warehouse Management Goods Issue Process Cartonization Planning BAdI: Cartonization Planning
Algorithm .

You have defined number ranges for the identification of planned shipping handling units (PSHUs).

For more information, see Customizing for Extended Warehouse Management under Goods Issue Process
Cartonization Planning Define Number Ranges for Identification of PSHUs .

For the determination of packaging materials for cartonization planning, you have done the following:

You have defined condition types for packaging specifications for cartonization planning. You can use the standard
condition type 0CAP with access sequence 0CAP.

For more information, see Customizing for SCM Basis under Pack Packaging Specification Determination of
Packaging Specifications Define Condition Types .

You have created and activated packaging specification with condition types for cartonization planning on the
launchpad for Extended Warehouse Management under Master Data Packaging Specification Maintain
Packaging Specification .

You have defined a determination procedure for cartonization planning.

For more information, see Customizing for SCM Basis under Pack Packaging Specification Determination of
Packaging Specifications Define Determination Procedure .

You have selected a determination procedure for cartonization planning in your warehouse.

This is custom documentation. For more information, please visit SAP Help Portal. 7
 4/3/25, 7:52 PM
For more information, see Customizing for Extended Warehouse Management under Goods Issue Process
Cartonization Planning Configure Cartonization Planning on Warehouse Number Level .

The following prerequisites are optional:

To modify the standard grouping of outbound delivery order items before executing the cartonization planning algorithms,
you have implemented the BAdI method GROUP_ITEMS.

For more information, see Customizing for Extended Warehouse Management under Business Add-Ins (BAdIs) for
Extended Warehouse Management Goods Issue Process Cartonization Planning BAdI: Pre- and Postprocessing of
CAP Algorithms .

To modify the result of the cartonization planning algorithms, you have implemented the BAdI method
ADJUST_CAP_RESULT.

For more information, see Customizing for Extended Warehouse Management under Business Add-Ins (BAdIs) for
Extended Warehouse Management Goods Issue Process Cartonization Planning BAdI: Pre- and Postprocessing of
CAP Algorithms .

Planned Shipping Handling Unit

Definition
An object similar to a shipping handling unit (HU), describing a packaging material and the items it contains. In contrast to a
shipping HU, a planned shipping HU does not physically exist in the warehouse and is only used to plan shipping HUs. Planned
shipping HUs are created manually or automatically in cartonization planning. They are used for the creation of shipping HUs
during picking or packing.

The planning is carried out based on the quantity in the unit of measure (UoM) as specified in the outbound delivery item,
regardless of whether the base unit of measure (BUoM) or an alternative unit of measure (AUoM) has to be handled. If the
outbound delivery item quantity is given in the BUoM, but the stock for the product is mostly stored with a special AUoM, the
system uses the stock-specific UoM (SUoM) maintained in the product master data to carry out the cartonization planning for an
entire quantity of this SUoM .

Use
The system can create planned shipping HUs in automatic cartonization planning. For more information, see Automatic
Cartonization Planning.

You can also create and change planned shipping HUs manually. For more information, see Maintenance of Planned Shipping
Handling Units.

Structure

A planned shipping HU is identified by a 18-digit number with the prefix $_.

For more information, see Customizing for Extended Warehouse Management under Goods Issue Processes Cartonization
Planning Define Number Ranges for Identification of PSHUs . Note that the system does not generate identification numbers
for planned shipping HUs that are used in transit warehousing and that are sent from an external system, for example, package
items from freight documents in SAP Transportation Management. For more information, see Differences Between Standard
Warehousing and Transit Warehousing.

A planned shipping HU contains the following elements:

This is custom documentation. For more information, please visit SAP Help Portal. 8
 4/3/25, 7:52 PM
Planned shipping HU header

Planned shipping HU item

Additional planned shipping HU identifier

Reference document

Integration
The system uses planned shipping HUs as a template for creating shipping HUs during either picking or packing. For more
information, see the following:

Handling Unit (HU)

Picking with Cartonization Planning

Packing with Cartonization Planning

Automatic Cartonization Planning

Use

You can use this process to have the system automatically create planned shipping handling units (PSHUs) according to
algorithms defined as implementations of the Business Add-In BAdI: Cartonization Planning Algorithm. The default
implementation /SCWM/EI_CAP_MIN_HUS aims at minimizing the number of handling units (HUs). The default algorithm uses a
heuristic approach. It is not an optimization. For more information about the default implementation, see Customizing for
Extended Warehouse Management under Business Add-Ins (BAdIs) for Extended Warehouse Management Goods Issue
Process Cartonization Planning BAdI: Cartonization Planning Algorithm .

Process
Automatic cartonization planning runs as follows:

1. For each newly created or changed outbound delivery order item, the system determines a process profile for cartonization
planning and assigns it to the delivery item.

2. You can trigger automatic cartonization planning in one of the following ways:

Cartonization Planning for Outbound Delivery Orders

Cartonization Planning for Waves

Cartonization Planning During Warehouse Order Creation

For more information about how to test automatic cartonization planning with different algorithms, see Maintenance of
Planned Shipping Handling Units.

3. The system groups outbound delivery order items that are to be packed together.

During cartonization planning, the system processes each group independently of other groups. Delivery items from
different groups are not planned to be packed together in the same HU. The grouping depends on the following criteria:

Algorithm profile for cartonization planning

Consolidation group

This is custom documentation. For more information, please visit SAP Help Portal. 9
 4/3/25, 7:52 PM
Activity area

Wave (in the case of cartonization planning for waves only)

4. The system can modify the grouping of outbound delivery order items.

This is an optional step. For more information, see Customizing for Extended Warehouse Management under Business
Add-Ins (BAdIs) for Extended Warehouse Management Goods Issue Process Cartonization Planning BAdI: Pre- and
Postprocessing of CAP Algorithms .

5. The system executes the cartonization planning algorithms to create PSHUs.

6. The system can modify the result of cartonization planning algorithms.

This is an optional step. For more information, see Customizing for Extended Warehouse Management under Business
Add-Ins (BAdIs) for Extended Warehouse Management Goods Issue Process Cartonization Planning BAdI: Pre- and
Postprocessing of CAP Algorithms .

Result

Automatic cartonization planning results in the creation of PSHUs that the system can use as templates for creating shipping HUs
during picking or packing – depending on the process profiles of the outbound delivery items. For more information, see the
following:

Picking with Cartonization Planning

Packing with Cartonization Planning

You can also monitor, change, or delete automatically created PSHUs. For more information, see the following:

Monitoring of Planned Shipping Handling Units

Maintenance of Planned Shipping Handling Units

Deletion of Planned Shipping Handling Units

Cartonization Planning for Outbound Delivery Orders

Use

You can use this function of automatic cartonization planning to have the system create planned shipping handling units (PSHUs)
for outbound delivery orders based on predefined algorithms.

Features
Selection of Outbound Delivery Orders for Cartonization Planning

You can select outbound delivery orders by the following criteria:

Organizational data: warehouse number

Time range for planned goods issue start

Time range for planned start of departure from yard

Document data

This is custom documentation. For more information, please visit SAP Help Portal. 10
 4/3/25, 7:52 PM
Partner data

Selection of Outbound Delivery Order Items for Cartonization Planning

When you start cartonization planning for outbound delivery orders, the system selects outbound delivery order items that fulfill
the following criteria:

The delivery item has the status Blocked (Unchecked Item) with an initial value, which means that the item is not blocked.

The delivery item has the status Goods Issue with value Not Started.

The delivery item has a process profile for cartonization planning in which the Create Planned Shipping HUs for Outbound
Delivery Orders checkbox is selected.

For more information, see Customizing for Extended Warehouse Management under Goods Issue Process
Cartonization Planning Define Process Profiles for Cartonization Planning .

Execution of Cartonization Planning in Case of Existing PSHUs

If a previous cartonization planning already created PSHUs, you can influence the execution of cartonization planning by using the
Exclude Items with Existing PSHUs checkbox. For more information, see the field help in the system.

Execution Mode

Besides creating PSHUs, you can also use this function in the following execution modes:

Simulation

In simulation mode, you can test cartonization planning without creating PSHUs in the database.

Deletion

If you have already carried out cartonization planning, you can delete the existing PSHUs before starting cartonization
planning for outbound delivery orders. For more information about other ways of deleting PSHUs, see Deletion of Planned
Shipping Handling Units.

Application Log

You can activate the application log to store information about the execution of cartonization planning.

Activities
To start cartonization planning for outbound delivery orders, execute the transaction on the launchpad under Extended
Warehouse Management Work Scheduling Cartonization Planning Cartonization Planning - Outbound Delivery Order or
schedule the report /SCWM/R_CAP_BACKGROUND.

More Information
Outbound Delivery Order

Cartonization Planning for Waves

Use

This is custom documentation. For more information, please visit SAP Help Portal. 11
 4/3/25, 7:52 PM
You can use this function of automatic cartonization planning to have the system create planned shipping handling units (PSHUs)
for waves based on predefined algorithms.

Features
Selection of Waves for Cartonization Planning

You can select waves by the following criteria:

Organizational data: warehouse number

Wave cutoff date and time

Wave number

Selection of Outbound Delivery Order Items for Cartonization Planning

When you start cartonization planning for waves, the system selects outbound delivery order items that fulfill the following criteria:

The delivery item is assigned to the selected wave.

In case of split items, the split item is assigned to the selected wave.

The delivery item has a process profile for cartonization planning in which the Create Planned Shipping HUs for Waves
checkbox is selected.

For more information, see Customizing for Extended Warehouse Management under Goods Issue Process
Cartonization Planning Define Process Profiles for Cartonization Planning .

Execution of Cartonization Planning in Case of Existing PSHUs

If a previous cartonization planning already created PSHUs, the system calculates for each selected outbound delivery order item
how much quantity is not packed into PSHUs yet and is thus still available for cartonization planning. For each delivery item, the
system then compares the unpacked quantities with the selected quantities:

If the unpacked quantities are smaller than the selected quantities, the system cancels cartonization planning and does not
create further PSHUs for the selected delivery items. See Example 1 below.

If the unpacked quantities are equal or larger than the selected quantities, the system carries out cartonization planning
and creates further PSHUs for the selected delivery items. See Example 2 below.

Grouping of Outbound Delivery Order Items

Before executing the algorithms, the system groups outbound delivery order items that are to be packed together. During
cartonization planning, the system processes each group independently of other groups. Delivery items from different groups are
not planned to be packed together in the same PSHU. In cartonization planning for waves, the standard system uses wave numbers
as one of the grouping criteria. As a consequence, the system does not assign delivery items of different waves to the same PSHU.

To modify the standard grouping of outbound delivery order items before executing the cartonization planning algorithms, you
need to implement the Business Add-In (BAdI) method GROUP_ITEMS.

For more information, see Customizing for Extended Warehouse Management under Business Add-Ins (BAdIs) for Extended
Warehouse Management Goods Issue Process Cartonization Planning BAdI: Pre- and Postprocessing of CAP Algorithms .

Execution Mode

Besides creating PSHUs, you can also use this function in the following execution modes:

This is custom documentation. For more information, please visit SAP Help Portal. 12
 4/3/25, 7:52 PM
Simulation

In simulation mode, you can test cartonization planning without creating PSHUs in the database.

Deletion

If you have already carried out cartonization planning, you can delete the existing PSHUs before starting cartonization
planning for outbound delivery orders. For more information about other ways of deleting PSHUs, see Deletion of Planned
Shipping Handling Units.

Application Log

You can activate the application log to store information about the execution of cartonization planning.

Activities

To start cartonization planning for waves, execute the transaction Cartonization Planning - Wave on the launchpad under
Extended Warehouse Management Work Scheduling Cartonization Planning or schedule the report /SCWM/R_CAP_WAVE.

Example
Example 1

In the following example, there are three waves, which contain delivery items of two outbound delivery orders. All delivery items are
split except for delivery item 10 of outbound delivery order 2. Some split items are also assigned to different waves.

You start cartonization planning for wave 1 and 2, but not for wave 3.

The following table shows the selected data:

Selected Wave Wave Item Outbound Delivery Item Split Item Quantity
Delivery Order

Yes 1 10 1 10 1 5

No 3 10 1 10 2 5

Yes 1 30 1 20 1 11

Yes 2 10 1 20 2 9

Yes 2 20 2 10 0 30

Yes 2 30 2 20 1 25

Yes 2 40 2 20 2 15

A previous cartonization planning has created two PSHUs with the following data:

PSHU Outbound Delivery Order Delivery Item Quantity

1 1 10 5

2 1 20 1

This is custom documentation. For more information, please visit SAP Help Portal. 13
 4/3/25, 7:52 PM
In this example, the system does not create PSHUs for the selected waves because there is not sufficient unpacked quantity for
delivery item 20 of outbound delivery order 1. The affected delivery item is divided into two split items with a quantity of 11 and 9.
Each split item is assigned to a different wave: wave 1 and wave 2. Both waves are selected. So both split items are relevant and
therefore a quantity of 20 (11 plus 9) must be unpacked. However, since there is an existing PSHU item with one packed quantity
and the original requested quantity of the delivery item was 20, the remaining quantity is not sufficient so the system cannot
create new PSHUs.

Example 2

In this example, there are three waves that contain two delivery items of the same outbound delivery order. Both delivery items are
split.

You start cartonization planning for wave 1 and 2, but not for wave 3.

The following table shows the selected data:

Selected Wave Wave Item Outbound Delivery Item Split Item Quantity
Delivery Order

Yes 1 10 1 10 1 5

No 3 10 1 10 2 5

No 3 20 1 20 1 11

Yes 2 10 1 20 2 9

A previous cartonization planning has created two PSHUs with the following data:

PSHU Outbound Delivery Order Delivery Item Quantity

1 1 10 5

2 1 20 11

Two different PSHUs exist for the delivery items of this example: Delivery item 10 has an already packed quantity of 5 and delivery
item 20 has an already packed quantity of 11. Even if there are already packed quantities for a delivery item, no exception is thrown
and new PSHUs are created, because the remaining quantity is sufficient for the selected wave items. Delivery item 10 contains a
quantity of 10. Five of them are already packed, but the remaining quantity of five is not smaller thus enough to pack the selected
quantity of five. Delivery item 20 contains a quantity of 20. Eleven of them are already packed, but the remaining quantity of nine is
not smaller and thus enough to pack the selected quantity of 9.

More Information

Wave Management

Cartonization Planning During Warehouse Order Creation

Use
You can use this function of automatic cartonization planning to have the system create planned shipping handling units (PSHUs)
for pick-warehouse tasks during warehouse order creation. The system uses the PSHUs as templates to create shipping HUs
during either picking or packing.

This is custom documentation. For more information, please visit SAP Help Portal. 14
 4/3/25, 7:52 PM

Prerequisites

To enable the use of a warehouse order creation rule for cartonization planning, you have selected the CAP Compatibility checkbox
of the rule. For more information, see Customizing for Extended Warehouse Management under Cross-Process Settings
Warehouse Order Define Creation Rule for Warehouse Orders .

More Information
Picking with Cartonization Planning

Packing with Cartonization Planning

Maintenance of Planned Shipping Handling Units

Use

You can use this function of cartonization planning to carry out the following tasks:

Display the result of a previous cartonization planning

Change the result of a previous cartonization planning manually to handle exceptional situations, for example, if pick denial
reduced the delivered quantity or delivery items are to be shipped with other transportation units

Simulate or carry out automatic cartonization planning for selected unpacked outbound delivery items, for example, to test
different algorithms

For more information about automatic cartonization planning, see Automatic Cartonization Planning.

Prerequisites

You have specified a work center layout for cartonization planning.

For more information, see Customizing for Extended Warehouse Management under Master Data Work Center
Specify Work Center Layout .

You have selected a work center layout for your warehouse number.

For more information, see Customizing for Extended Warehouse Management under Goods Issue Process
Cartonization Planning Configure Cartonization Planning on Warehouse Number Level .

Features
Selection of Outbound Delivery Items and Planned Shipping Handling Units

You can use the following selection criteria:

Organizational data: warehouse number

Planned shipping handling unit (PSHU)

If you want to display a single PSHU, enter its ID. The ID must start with the prefix $_ followed by a number. You can skip the
leading zeros.

 Example

This is custom documentation. For more information, please visit SAP Help Portal. 15
 4/3/25, 7:52 PM
To select PSHU $_000000000000001234, enter $_1234.

Outbound delivery orders and delivery items

Status

Waves

Partners: ship-to parties and carriers of the outbound delivery orders

Shipments: vehicles and transportation units

From the selection, you can exclude unpacked delivery items for which you have already posted a goods issue.

Application Log

You can activate the application log to store information about the execution of cartonization planning.

Activities

To maintain PSHUs, on the launchpad, choose Extended Warehouse Management Work Scheduling Cartonization Planning
Maintain Planned Shipping HUs .

On the selected delivery items, you can carry out the following activities:

Create PSHUs

Repack PSHUs

Repack products

Change PSHUs

Display stock data

Start automatic cartonization planning

Select an unpacked delivery item with an open quantity greater than zero and choose Automatic Cart. Planning. The
system automatically determines the algorithm profile for cartonization planning.

Simulate automatic cartonization planning

Select an unpacked delivery item with an open quantity greater than zero and choose Test Cart. Planning. You can manually
select the algorithm profile for cartonization planning.

Monitoring of Planned Shipping Handling Units

Use
After the execution of cartonization planning, you can monitor the created planned shipping handling units (PSHUs) in the
warehouse management monitor.

Prerequisites
For more information about the settings required for the navigation to the Display Planned Shipping Handling Unit screen, see the
prerequisites of Maintenance of Planned Shipping Handling Units.

This is custom documentation. For more information, please visit SAP Help Portal. 16
 4/3/25, 7:52 PM

Features

You can use the SAP standard monitor node Planned Shipping Handling Unit to display and review selected PSHUs. You can use
any of the following data as selection criteria:

Document or wave

Partner

Shipment

For each selected PSHU, the monitor displays the relevant header data. Additionally, it displays the relevant data of delivery items
packed into the selected PSHU. If a value is not unique, for example, different TUs are assigned, the monitor displays the value ***.

The SAP standard layout Planned Shipping HU Aggregation (0/PSHU_AGGR) displays the following:

Summary of the gross weight and volume per HU type and carrier

Summary of the overall gross weight and volume

 Note
The layout variant is not visible by default. To use it, you have to select it or set it as default.

Activities
To display PSHUs in the SAP standard monitor with standard layout for PSHU aggregation, perform the following steps:

1. On the launchpad, choose Extended Warehouse Management Monitoring Warehouse Monitor .

2. Enter the standard SAP monitor of your warehouse number.

3. In the node hierarchy tree on the left-hand side, choose Outbound Documents Planned Shipping Handling Units .

4. Execute a search for PSHUs.

The system displays the selected PSHUs in a list view on the right-hand side.

5. In the right-hand screen area, choose Choose Layout ... Manage Layouts .

The system displays the list of layouts.

6. Set the layout Planned Shipping HU Aggregation (0/PSHU_AGGR) as default by double-clicking it.

7. Save your setting and exit the layout management screen.

8. After selecting a PSHU displayed in the list view, you can do the following:

Change to form view

Navigate to the Display Planned Shipping Handling Units screen to display the selected PSHU

More Information
Warehouse Management Monitor

Picking with Cartonization Planning

This is custom documentation. For more information, please visit SAP Help Portal. 17
 4/3/25, 7:52 PM

Use

In cartonization planning, the system can use planned shipping handling units (PSHUs) as templates for creating pick handling
units (HUs), which you can then use as shipping HUs.

Prerequisites

For picking with cartonization planning, the following prerequisites must be met:

You have created PSHUs for warehouse tasks during warehouse order creation. For more information, see Cartonization
Planning During Warehouse Order Creation.

You have defined warehouse order creation rules for picking from the activity areas. For more information, see Customizing
for Extended Warehouse Management under Cross-Process-Settings Warehouse Order Define Creation Rule for
Warehouse Orders .

So that the packing profile in the warehouse order creation rule creates the pick-HUs, you have selected the Create HUs
and the Assign WTs to HUs checkboxes in the packing profile. For more information, see Customizing for Extended
Warehouse Management under Cross-Process-Settings Warehouse Order Define Packing Profile for Warehouse
Order Creation .

You have defined a start and end bin for the activity area. If you use a pick point, the bin of the pick point is the starting bin
of the activity area. See the launchpad for Extended Warehouse Management under Master Data Storage Bin Define
Start and End Bin - Activity Area .

Features
Creation of Planned Shipping Handling Units

Picking only works with cartonization planning for warehouse tasks during warehouse order creation. For more information, see
Cartonization Planning During Warehouse Order Creation and Sample Use Cases of Cartonization Planning.

Picking at a Pick Point

Picking with cartonization planning is also possible when using pick points. For more information, see Pick Point.

However, the system can only propose pick-HUs on the basis of PSHUs if you confirm all HU-warehouse tasks for moving stock to
the pick point together, and if you carry out picking at the pick point using radio frequency (RF) instead of using the work center.
For more information, see Picking at a Pick Point Using Radio Frequency.

Two-Step Picking

In two-step picking, the warehouse tasks for withdrawal have no reference to outbound delivery orders. For this reason, you cannot
use picking with cartonization planning in the withdrawal step. However, you can use picking with cartonization planning in the
allocation step. For more information, see Two-Step Picking.

More Information
Picking

Packing with Cartonization Planning

Use
This is custom documentation. For more information, please visit SAP Help Portal. 18
 4/3/25, 7:52 PM
In packing with cartonization planning, the system uses the planned shipping handling units (PSHUs) as templates for proposing
packaging materials or destination handling units (HUs) for shipping HUs while packing at the work center or using radio frequency
(RF).

Prerequisites

You have implemented the Business Add-In BAdI: Destination HUs and Packaging Materials from PSHUs or are using the default
implementation.

For more information, see Customizing for Extended Warehouse Management under Business Add-Ins (BAdIs) for Extended
Warehouse Management Master Data Work Center Adjust User Interface for Work Center .

Features
The destination HUs or packaging materials proposed by the system depend on the implementation of the BAdI: Destination HUs
and Packaging Materials from PSHUs. The default implementation /SCWM/ESI_WRKC_UI_POHU aims at emptying the pick-HUs
as soon as possible. You can also implement the BAdI in a way that the shipping HUs become completely packed as soon as
possible.

More Information

Packing at the Work Center

Packing Using Radio Frequency

Deletion of Planned Shipping Handling Units

Use

You can delete obsolete planned shipping handling units (PSHUs) by using the transaction Delete Planned Shipping HUs.

 Recommendation
We recommend that you delete obsolete PSHUs regularly.

 Note
Using the transaction Delete Planned Shipping HUs, you can only delete a PSHU if all its related outbound delivery order items
fulfill the selection criteria. If you want to delete a PSHU that contains delivery items not fulfilling your selection criteria, you
have to use the transaction Cartonization Planning - Outbound Delivery Order or Cartonization Planning - Wave in execution
mode Deletion of PSHUs. These transactions also offer further criteria to select PSHUs for deletion. For more information, see
Cartonization Planning for Outbound Delivery Orders or Cartonization Planning for Waves.

 Note
You can also delete PSHUs before wave creation with the report /SCWM/R_WAVE_PLAN_BACKGROUND. To do so, select the
Delete Planned Shipping HUs checkbox in the report.

Features

This is custom documentation. For more information, please visit SAP Help Portal. 19
 4/3/25, 7:52 PM
Selection

In transaction Delete Planned Shipping HUs, you can select PSHUs for deletion by the following criteria:

Organizational Data

You have to select the warehouse number in which you want to delete PSHUs.

Selection of Planned Shipping Handling Units

You have to select PSHUs with or without related outbound delivery orders.

With Outbound Delivery Orders

You can select PSHUs by the status of their related outbound delivery orders. You can use one of the following
options:

Goods Issue Status

You can select PSHUs by specifying the minimum number of days since goods issue posting for their related
outbound delivery order items. The default number of days since goods issue posting is 30.

Goods Issue Status

You can select PSHUs by specifying the date range of goods issue posting for their related outbound delivery
order items.

Archiving Status

You can select PSHUs whose related outbound delivery orders have been already marked for archiving.

Without Outbound Delivery Orders

You can select PSHUs whose related outbound delivery orders have already been deleted.

Technical Settings

You can make the following technical settings:

Package Size for Processing

To avoid errors due to maximum runtime and also memory or lock overflows, the system can process data in packages. You
can define the package size by defining the maximum number of the highest-level PSHUs in a package. The default package
size is 5000.

The system processes each package independently. If the processing of one package stops due to an error, this does not
stop the execution of the transaction as the system can process the remaining packages.

Simulation

If you execute the transaction in simulation mode, the system selects PSHUs without actually deleting them and displays
the result in the application log.

Application Log

The system stores the results of the execution in the application log, which contains information about the selected PSHUs as well
as about their related outbound delivery orders if any.

Activities

This is custom documentation. For more information, please visit SAP Help Portal. 20
 4/3/25, 7:52 PM
To delete obsolete PSHUs, on the launchpad, choose Extended Warehouse Management Work Scheduling Cartonization
Planning Delete Planned Shipping HUs or schedule the report /SCWM/R_CAP_DELETE.

 Recommendation
To check your selection of PSHUs, we recommend that you first run the report in simulation mode.

Example
You use cartonization planning in your outbound process. You post goods issue for all items of an outbound delivery order on the
same day or latest one day later. Once you have posted the goods issue, you do not need the PSHUs any longer. However, for
monitoring reasons you want to keep them for two weeks. After two weeks you want to delete them so that the database for the
PSHUs does not contain obsolete entries. To delete the obsolete PSHUs regularly, you schedule the report
/SCWM/R_CAP_DELETE as a background job. In the report, you enter the warehouse number and the following selection criteria:

You select With Outbound Delivery Orders.

You select Goods Issue Status and enter 14 as the minimum number of days since goods issue posting.

Since you expect a large amount of PSHUs to be deleted, you use the standard package size.

Sample Use Cases of Cartonization Planning

Use
You can use cartonization planning, for example, in the following ways:

Use case 1: Picking with automatic cartonization planning for warehouse tasks during warehouse order creation

In this use case you work with waves. The system automatically creates planned shipping handling units (PSHUs) for
warehouse tasks during warehouse order creation. The system uses the PSHUs as templates for creating pick-handling
units (pick-HUs), which you use as shipping handling units (shipping HUs).

Use case 2: Packing with automatic cartonization planning for waves

In this use case you work with waves. The system automatically creates PSHUs for waves. The system uses the PSHUs as
templates for proposing packaging materials or destination HUs during packing at the work center or using radio frequency
(RF).

Use case 3: Packing with automatic cartonization planning for warehouse tasks during warehouse order creation

In this use case you work with waves. The system automatically creates PSHUs for warehouse tasks during warehouse
order creation. The system uses the PSHUs as templates for proposing packaging materials or destination HUs during
packing at the work center or using RF.

Use case 4: Packing with automatic cartonization planning for outbound delivery orders

In this use case, you work without waves. The system automatically creates PSHUs for outbound delivery orders. The
system uses the PSHUs as templates for proposing packaging materials or destination HUs during packing at the work
center or using RF. This enables early planning of shipping HUs.

Combination of use case 1 and 4

In this use case, you work without waves. The system automatically creates PSHUs for outbound delivery orders. After you
have reserved transportation capacity based on your early cartonization planning, you monitor the PSHUs and decide to
delete them. You repeat cartonization planning to execute picking with cartonization planning using up-to-date data. The

This is custom documentation. For more information, please visit SAP Help Portal. 21
 4/3/25, 7:52 PM
process then runs as in use case 1 but without waves. The system automatically creates PSHUs during warehouse order
creation. The system uses the PSHUs as templates for creating pick-HUs, which you use as shipping HUs.

 Note
In use case 4 and its variant, the usage of waves is possible but it does not influence the creation of PSHUs.

Features

The following table lists the features used in each use case:

Feature Use Case 1 Use Case 2 Use Case 3 Use Case 4 Combination of Use
Case 1 and 4

Creation of wave X X X – –

See Wave
Management.

Cartonization – – – X X
Planning for
Outbound Delivery
Orders

Deletion of Planned – – – – X
Shipping Handling
Units

Cartonization – X – – –
Planning for Waves

Cartonization X – X – X
Planning During
Warehouse Order
Creation

Picking with X – – – X
Cartonization
Planning

Packing with – X X X –
Cartonization
Planning

Configuring Package Building

You can use this function to create packages when you build planned shipping handling units (PSHUs) for outbound delivery
orders.

Prerequisites
You have made the settings for package building (see Package Building). Use the following transactions:

To make changes to the master data, use the transaction Change Material (MM02)

This is custom documentation. For more information, please visit SAP Help Portal. 22
 4/3/25, 7:52 PM
Make further settings using the transaction Package Assignment (/SCWM/CAP_PB_PKG_ASS)

 Recommendation
For detailed documentation on how to set up and use package building, please refer to SAP Note 2581421 .

Context
You enter the maximum quantity of a product that the system can put into a package for this product. The dimensions of your
packages, such as size and weight, depend on the settings you make in your master data and the transaction Package
Assignment. Packages are created automatically when you build PSHUs for outbound delivery orders.

This Customizing activity is one of the options available to you for cartonization planning, along with the Customizing activities
Define Algorithm Profiles for Cartonization Planning and Define Process Profiles for Cartonization Planning. For more
information, see Prerequisites for Cartonization Planning.

Procedure
1. Determine the process profiles for cartonization planning in Customizing for Extended Warehouse Management in the
following activities under Goods Issue Process Cartonization Planning :

Define Process Profiles for Cartonization Planning

Determine Process Profiles for Cartonization Planning

2. Define a package building profile in Customizing for Extended Warehouse Management under Goods Issue Process
Cartonization Planning Package Building .

3. Determine the algorithm profiles for cartonization planning in Customizing for Extended Warehouse Management in the
following activities under Goods Issue Process Cartonization Planning :

Define Algorithm Profiles for Cartonization Planning

Enter SAP2 as the algorithm for cartonization planning in the node Define Algorithm

Define Access Sequence of Algorithm Profiles

4. Make further settings for the algorithm profiles in the launchpad under Extended Warehouse Management Settings
Determine Algorithm Profiles - Cartonization Planning .

Enter an algorithm profile that uses the algorithm SAP2.

Enter a package building profile.

5. Define settings for the products to be packed using package building on the launchpad under Extended Warehouse
Management Settings Assign Packaging Materials to Products .

Package Building
You can use this function to create packages out of products.

Use

Package building is performed with the Supply Chain Execution (SCE) package builder in SCM Basis. In the unified package
building profile, you need to select package building with the package builder as the unified package building engine.

During package building, the system bundles products into packages based on specific constraints, while also keeping the total
number of packages to a minimum. The system can also specify the exact position and orientation of each product item.

This is custom documentation. For more information, please visit SAP Help Portal. 23
 4/3/25, 7:52 PM
You can define these constraints for different combinations of product, business partner, equipment, and location. If several
constraints apply, the system always uses the most specific constraint. For more information, see Determination of Package Type
Assignments.

You can use the constraints that you define within this function to create packages in Transportation Management (TM) and in
Extended Warehouse Management (EWM).

For more information about creating packages in TM, see http://help.sap.com/s4hana under Product Assistance Enterprise
Business Applications Supply Chain Transportation Management (TM) Planning Unified Package Building Unified
Package Building in TM .

For more information about creating packages in EWM, see http://help.sap.com/s4hana under Product Assistance Enterprise
Business Applications Supply Chain Extended Warehouse Management (EWM) Goods Issue Cartonization Planning
Configuring Package Building .

Prerequisites

You have defined product master data. For more information, see Defining Product-Specific Master Data.

You have defined package type assignments. For more information see Defining Package Type Assignments.

You have defined a unified package building profile and indicated Package Building as the unified package building engine
you want to use. For more information, see Unified Package Building Profile.

If you want to use mixed package building, you have optionally defined a product relationship profile in the Change Product
Relationship Profile app. In this profile, you can define incompatibilities and stacking rules. Moreover, you can define the
sequence in which the products are to be packaged.

If you want to use detailed mixed package building, you have done the following:

You have optionally defined a profile for the package building optimizer. This profile contains technical settings like
runtimes, dump and trace levels. To define this profile, enter view /SCMB/V_PB_OPT in transaction SM30.

You have optionally defined a rule profile for the package building optimizer. This profile allows you to select
predefined rules and define values and priorities. To define this profile, enter view cluster /SCMB/VC_PB_OPTRP in
transaction SM34. For more information, see Rule Profile for the Package Building Optimizer.

You have optionally defined a product orientation profile. In this profile, you define how a product can be positioned
in a package. To define this profile, enter view /SCMB/V_MAT_ORNT in transaction SM30.

Features

When creating packages, the system can split the quantity of a product using the following criteria:

Quantity per package

Maximum height of the package

Maximum weight of the package

If different products are to be packaged, the system considers the lowest maximum height and the lowest maximum weight for a
product or a packaging material. For example, if each product has a different maximum height, the system uses the lowest
maximum height.

The system creates mixed packages based on one of the following consolidation types:

Volume

This is custom documentation. For more information, please visit SAP Help Portal. 24
 4/3/25, 7:52 PM
Layer definitions

Incompatibilities, stacking rules, and product orientations (based on these values, the system determines the exact
positions of each product item in the package (detailed mixed package building))

The result of package building is different types of packages:

Packages that contain only a single type of product

Mixed packages that contain several different products

Packages that consist of several layers

The layers within a package can also contain different products, which results in mixed layers.

Nested packages, that is a package in another package

For example, you can plan 24 cans in one box and 100 boxes in ten layers on one pallet.

Full packages or incomplete packages

Incomplete packages provide room for further consolidation.

Flat or uneven packages

Flat packages are a prerequisite for stackability.

These package types can be combined. For example, the result of package building can be an incomplete, uneven mixed package
with mixed layers.

You can simulate the package building. For more information, see Test Cockpit for Unified Package Building.

You can check whether you have defined your package building constraints in a consistent way. For more information, see
Consistency Check of Package Building Constraints.

For more information about best practices and the processing logic, see SAP Note 2581421 .

 Note
You can use the Business Add-In BAdI: Package Building (/SCMB/EX_PACKAGE_BUILDER) to change the standard settings of
package building.

Example

You have 105 laptops and 117 mini hi-fi systems. 90 laptops and 80 mini hi-fi systems form a complete package, while 10 laptops
and 16 mini hi-fi systems form one layer. If you allow mixed packages to be created with mixed layers, the system plans to put the
remaining 15 laptops and 37 mini hi-fi systems in a mixed package with one layer consisting of 10 laptops, two layers each
consisting of 16 mini hi-fi systems, and one mixed layer consisting of 5 laptops and 5 mini hi-fi systems.

Related Information
Detailed Mixed Package Building
Unified Package Building

Defining Product-Specific Master Data

This is custom documentation. For more information, please visit SAP Help Portal. 25
 4/3/25, 7:52 PM
In the master data of a product, you define product-specific attributes that the system considers when creating packages.

Procedure
To create a product, in the command field enter MM01.

On the Additional Data Units of measure view, define the following:

Dimensions (length, width, height) of the product

Weight of the product

Definitions for full packages, that is, the product quantity that fits into one package as well as the height and weight
of the package

Definitions for full layers, that is, the product quantity that fits into one layer as well as the height and weight of the
layer

Maximum stacking factor (see Stacking Factor)

Maximum top load, that is, the maximum weight that you can place on top of a full package of this product

A conversion factor between the base unit of measure and the unit of measure for normalized quantity (see
Determination of Normalized Load Consumption Quantities).

Layer definitions are typically used for mixed packages. If you do not define any layer definition for your product, the system
creates packages based on the available volume of the packaging material.

You can define multiple layer and package definitions for a product. To do so, you need to define packaging-specific units of
measure in Customizing for SAP NetWeaver under General settings Check Units of Measurement . In the Change
Package Type Assignment app, you can indicate in which cases these different layer and package definitions are to be used.
For example, you can use different layer definitions for different business partners.

On the Sales: General/Plant view, define the following:

Maximum level (that is the filling level for volume-based mixed package building)

Stackability factor (see Stacking Factor)

Allowed packaging volume (for packaging materials only)

It is used to calculate the maximum height:

Max. height = all. pack. volume / ((max.) length * (max.) width)

The maximum height is needed to calculate the capacity volume, which is the main volume considered during
package building:

Capacity volume for closed packages = (max.) height * (max.) length * (max.) width

Capacity volume for open packages = (max. height – height of packaging material) * (max.) length * (max.) width

In addition, the existing maximum height values defined in the material master data and the Change Package Type
Assignment app need to be considered and the minimum is taken into account.

Closed (closed packaging material)

On the WM Packaging view, define settings for the packaging material. Note that these settings are only relevant if the
physical attributes of the packaging material are to be taken into account during package building. In this case, you need to
define a product for the packaging material and define the following settings:

Maximum height and weight

Note that these are global limits that apply for your entire company, for example. You can set lower limits, for
example on a product-specific basis, in the Change Package Type Assignment app.

On the WM Packaging view, define settings for package building:

A reference product for package building

This is custom documentation. For more information, please visit SAP Help Portal. 26
 4/3/25, 7:52 PM
A product orientation profile

The shape of the product

Thresholds for overhang, and absolute height

For more information, see the system documentation and SAP Note 2581421 .

Related Information
Defining Package Type Assignments

Stacking Factor
The stacking factor defines how products and packages, for example pallets, can be stacked.

The following logic applies:

A stacking factor of zero or an initial field means that the product or package can be stacked an infinite number of times on
itself.

A stacking factor of one means that the product or package can't be stacked on itself.

A stacking factor greater than one, such as six, means that the product or package can be stacked up to six times on itself.

On the Additional Data Units of measure view of the product master data, you can define a maximum stacking factor per
base unit of measure. If, for example, you define a maximum stacking factor of six for the alternative unit of measure of the product
(for example PC (Piece) or EA (Each)), it means that the product can be stacked up to six times on itself. This is taken into account
during detailed mixed package building. Detailed mixed package building also takes into account maximum stacking factors that
you have defined for reference products.

The maximum stacking factor that you define for the alternative unit of measure of the packaging material (for example PAL
(Pallet)) is determined in package building and taken into account during load planning and load consolidation. If you want the
packaging material to be marked as stackable, you need to specify a maximum stacking factor of zero or greater than one.

For closed packaging, only the stackability of the packaging material is relevant, the stackability of the products within the
packaging material does not matter. For example, a pallet cage is considered as the outer packaging and thus the system checks
the maximum stacking factor that you defined for the pallet cage and takes it into account during load planning and load
consolidation. If a product is packaged in a carton, the stackability of the carton is relevant for detailed mixed package building
since the carton will be packaged further.

If an open package, such as a pallet, contains layers only (no matter if these layers consist of the same product or different
products), the system takes into account and applies the maximum stacking factor (Units of measure view) that you have defined
for full packages of the contained products or the stackability factor (Sales: General/Plant view) that you have defined on product
header level. This is valid for layer-based mixed package building (embedded and based on detailed mixed package building).

 Note

If you have defined a stackability factor, the maximum stacking factor is not considered anymore.

An open package is only stackable if all contained products are stackable.

Defining Package Type Assignments

This is custom documentation. For more information, please visit SAP Help Portal. 27
 4/3/25, 7:52 PM
By defining package attributes, for example the packaging material, you specify what kind of packages the system is to create for
your products.

Context

You have the following options:

You define package attributes for multiple different combinations of product, business partner, location, contained material,
and equipment.

You define package attributes for multiple different combinations of business partner, location, and equipment.

You define an exclusive package for a business partner.

You define alternative packaging materials and the sequence in which they are to be used. This allows you to define the
packaging material depending on the product quantity.

 Note
If you define more specific attributes for a specific product (first option), the system considers these attributes and ignores the
more global attributes (second option).

You can define the following package attributes:

Packaging material and package type

Limits to be applied, for example, the maximum height and weight of the package

Note that the lowest limits (that is, the maximum height of the (mixed) package, the maximum weight of the (mixed)
package, and the maximum number of products) of all affected product items are considered.

Product-specific attributes, for example, a separation material or if mixed packages and mixed layers are to be created

In the Packaging Material field, you enter the product ID of the packaging material that you defined in the product master data.
This packaging material is used for full packages and mixed packages unless you have specified an additional product ID in the
Packaging Material (Mixed) field. In this case, all remaining product items are packaged in mixed packages using this additional
packaging material.

The package type can be either the packaging material, or the unit of measure, or both. You can enter the packaging material, or
the package type, or both:

If you only enter the packaging material and not the package type, the system uses the base unit of measure that you
defined in the product master data.

If you only enter the package type and not the packaging material, the weight and dimensions that you defined in the
product master data are not considered. The system only considers limits that you specify in this transaction.

If you enter both a packaging material and a package type, the system overrides the base unit of measure that you defined
in the product master data with the package type that you specify in this transaction.

If you want the system to create layers, you have to indicate a unit of measure for layers. If you do not indicate such a unit of
measure, the system creates packages based on your settings in the unified package building profile (either volume-based package
building or detailed mixed package building).

Some of these attributes can also be defined in the unified package building profile. However, the parameters in the unified
package building profile are global parameters and are taken into account only if you have not defined more specific attributes
here.

This is custom documentation. For more information, please visit SAP Help Portal. 28
 4/3/25, 7:52 PM
For more information about the individual attributes, see the system documentation.

For more information about best practices and the processing logic, see SAP Note 2581421 .

To define package attributes, you need to do the following:

Procedure
1. Open the Change Package Type Assignment app from the launchpad.

2. Define the package attributes.

Note that you have to define attributes on the Product-BP-Location tab page. The other tab pages are optional.

Related Information
Unified Package Building Profile
Determination of Normalized Load Consumption Quantities

Determination of Package Type Assignments

During package building, the system determines package type assignments to decide how to best package a product.

The system always uses the most specific value that it can find for a parameter.

To determine this value, the system does the following:

1. The system checks if you have defined a value for a specific parameter on the Product-BP-Location tab page. On this tab
page, you define product-specific package attributes for different combinations of key fields, that is, product, business
partner, location, contained material, as well as equipment type and group.

2. If the system does not find a value or if you selected Undefined for the parameter on the Product-BP-Location tab page, the
system looks for a value on the BP-Location tab page. On this tab page, you define product-independent package attributes
for different combinations of key fields, that is, business partner, location, as well as equipment type and group.

3. If the system does not find a value for the parameter on the BP-Location tab page either, it uses the initial value (0).

If you also selected Undefined for the parameter on the BP-Location tab page, the system checks if you made a global
setting for the parameter in the unified package building profile.

4. If the system has found a package type assignment in one of the previous steps, it tries to find alternative packaging
materials for the corresponding key fields by applying the sequence defined on the Alternative Packaging Materials tab
page.

5. On the BP tab page, the system checks if you indicated that an exclusive package is to be built for the business partner.

 Recommendation
Please use placeholder (*) for the key fields very carefully. For products and locations, we recommend that you use reference
products for package building and location hierarchies instead. For the contained material, you can't use placeholders.

If several products are to be packaged in the same way, we recommend that you define reference products for package
building. You define reference products for package building in the product master data.

If the same attributes apply for a large number of locations, we recommend that you define a location hierarchy in the
unified package building profile.

This is custom documentation. For more information, please visit SAP Help Portal. 29
 4/3/25, 7:52 PM

 Note

The key fields Equipment Type and Equipment Group allow you to indicate the resource to which the product is
assigned.

You can use these fields if the way a product is packaged depends on the resource with which it is going to be
transported. For example, if you need to transport frozen goods, placing them on a pallet would be fine if the resource is
a refrigerated truck. If the resource is a regular truck, however, you would need to package the goods into a refrigerated
compartment.

Related Information
Defining Product-Specific Master Data
Defining Package Type Assignments
Unified Package Building Profile

Determination of Normalized Load Consumption Quantities

During package building, the system determines normalized load consumption quantities (normalized quantities, NLQ) to get
accurate values regarding the load consumption of products and unit of measures (UoM) in top-level packages (that is, the outer
packaging). Based on these values, vehicle scheduling and routing optimization is able to choose the most suitable resources later
in the process.

To determine the normalized quantity for each product and UoM, the system does the following:

1. The system first checks if a value is available for each product and UoM in the Normalized Quantity field of the Define
Normalized Quantity app. These values can have the following source:

You have entered the values manually.

You have determined NLQs with the Determine Normalized Quantity Based on Randomized Data app. The results
are copied in this field automatically. For more information, see NLQ Determination Based on Randomized Data.

You have determined NLQs with the Determine Normalized Quantity Based on Documents app. The results are
copied in this field automatically. For more information, see NLQ Determination Based on Documents.

You have uploaded a spreadsheet that contains the values.

2. If the system finds an NLQ for a product and UoM, it multiplies this value with the planned quantity indicated in the freight
unit item for this product.

The system saves the results for all products in the freight unit items. In addition, it displays the sum of the normalized
quantities of all items on header level of the freight unit.

3. If the system does not find an NLQ in this field, it checks the product master data. If it finds a conversion factor between the
base UoM and the UoM for normalized quantity for a product and UoM, it uses this conversion factor to determine the
normalized quantity for this product.

4. If you have not defined conversion factors in the product master data, the system does not determine normalized quantities
during package building.

 Note

This is custom documentation. For more information, please visit SAP Help Portal. 30
 4/3/25, 7:52 PM
The system only determines normalized quantities if you have defined a UoM for normalized quantity in your unified
package building profile.

In step 2 and 3, if the system finds an NLQ for a product and UoM, it uses this value. If it does not find an NLQ, it
continues to search from bottom to top in the product hierarchy, starting with the reference product at the lowest level.

Related Information
Reference Products for Package Building
Use of Normalized Quantities and Capacities

NLQ Determination Based on Randomized Data

Use

You can use this report to determine a value for the normalized load consumption quantity (normalized quantity, NLQ) per product
and unit of measure (UoM) by using a statistical approach. This value indicates how much space (footprint) a single product
consumes in a top-level package (that is, the outer packaging).

The report determines this value in the following way:

1. Based on your selection, the report creates SPBUs (that is, units created by separate package building) with a random
number of product items that contain a random quantity of products. Each SPBU represents a transportation demand, that
is, a set of goods that are transported together across the entire transportation chain within a specific period of time (for
example, one delivery day).

2. The report creates one CPBU (that is, a unit created by capacity-document-based package building) with an infinite
capacity for all product items of these SPBUs. The CPBU represents a transportation order.

3. The report performs package building based on this CPBU and builds the best possible packages.

4. Based on the package building results, the report calculates a value for the normalized quantity for each product.

5. The report repeats step 1-3 as many times as you have indicated (number of calculation runs).

6. By evaluating the values calculated during these calculation runs, the report determines a unique weighted value for the
normalized quantity per product.

Prerequisites
You have defined dimensions for your products.

We recommend that you check the consistency of your package building constraints before you run this report. For more
information, see Consistency Check of Package Building Constraints.

For more information about prerequisites for package building, see Package Building.

Features

Selection

You need to indicate the following:

This is custom documentation. For more information, please visit SAP Help Portal. 31
 4/3/25, 7:52 PM
A UoM for the normalized quantity

A unified package building profile

The number of calculation runs

The level on which normalized quantities are to be determined (on product level or reference product level, or both)

We recommend that products belonging to the same reference product have the same dimension.

The number of SPBUs, that is, the number of transportation demands (average and standard deviation)

The number of items to be created per SPBU (average and standard deviation)

The update mode, that is whether the system is to save the results or run the report in simulation mode (default setting)

The input mode, that is whether the report is to run based on the input options or based on a spreadsheet upload

At least one input option. For each input option, you can indicate the following:

A product or reference product

The absolute frequency of the product (the relative frequency is determined by the system)

A product quantity per item (average and standard deviation)

By indicating more than one input options, you can influence the weighting of specific products related to one SPBU.

When you execute the report, the NLQ determination screen is displayed:

On the left, you can change the input data, for example, you can exclude certain products or change the quantities, and then
execute or schedule the NLQ determination.

On the right, the normalized quantities are displayed.

Outputs

The report determines a value for the normalized quantity for each product, which is saved in the Normalized Quantity field of the
Define Normalized Quantity app, if you have indicated that the system is to save the results.

If you have executed the report in simulation mode, you can save the results by selecting Update Selected Normalized Quantities.

If the Define Normalized Quantity app already contains entries for combinations of product number and UoM for the normalized
quantity, these entries are overwritten.

Activities

To start the report, open the Determine Normalized Quantity Based on Randomized Data app from the launchpad.

On the selection screen, choose Program Execute in Background to execute the report in the background. Note however,
that this is not supported if the input is based on spreadsheet upload. You need to execute the report based on spreadsheet upload
if you have more than five input options. On the NLQ determination screen, you can then schedule the NLQ determination for
execution in the background.

We recommend that you check afterwards whether the normalized quantities n your business documents are up to date. For more
information, see Check Normalized Quantities in Business Documents.

Related Information

This is custom documentation. For more information, please visit SAP Help Portal. 32
 4/3/25, 7:52 PM
Determination of Normalized Load Consumption Quantities
Unified Package Building Profile
Defining Package Type Assignments

Detailed Mixed Package Building

You can use this function to create mixed packages for products.

Prerequisites

You have installed the package building optimizer. For more information, see SAP Note 1686826 .

In your unified package building profile in Customizing, you have selected Detailed Mixed Package Building in the Mixed
Package Building Mode field. By doing so, additional fields are made editable, which allow you to make further settings. To
define a unified package building profile, enter view /SCMB/V_PB_PROFX in transaction SM30.

Use
During package building, the package building optimizer creates mixed packages for products taking into account the constraints
you have defined. Moreover, it determines the exact position of each product item and its orientation.

The package building optimizer takes into account the following constraints:

Unified package building profile (settings for detailed mixed packaging)

Package type assignments

Note that the lowest limits (that is, the the maximum height of a (mixed) package, the maximum weight of a (mixed)
package, and the maximum number of products) of all affected product items are considered.

Product-specific master data (settings for package building)

Product orientation profile

Product relationship profile

Profile for the package building optimizer

Rule profile for the package building optimizer

Related Information
Package Building
Defining Product-Specific Master Data
Defining Package Type Assignments
Unified Package Building Profile
Rule Profile for the Package Building Optimizer

Reference Products for Package Building

You can define reference products to simplify the process of defining package building attributes.

This is custom documentation. For more information, please visit SAP Help Portal. 33
 4/3/25, 7:52 PM
If you have a group of products that need the same packaging attributes, you can define the attributes once for a reference product
and then assign the reference product to each product of the group. By doing so, all of the products inherit the attributes of the
reference product.

The following attributes can be defined for reference products:

Definitions for full packages

Definitions for full layers

Package type assignments

Incompatibilities

Stacking rules

Consolidation sequence

 Note
You define full packages and full layers in the product master data. You define incompatibilities, stacking rules, and the
consolidation sequence in the product relationship profile.

When creating packages, the system first tries to create full packages with one product. If this is not possible, the system adds
other products from the group with the same reference product.

You can define reference products on more than one level.

 Note
If you want to change the reference product for multiple products, we recommend to use the test cockpit for unified package
building. For more information, see Test Cockpit for Unified Package Building.

Related Information
Defining Package Type Assignments
Defining Product-Specific Master Data
Unified Package Building Profile

Rule Profile for the Package Building Optimizer

SAP offers a number of predefined rules that you can use for detailed mixed package building. For each rule, you can indicate a
value and a level. Indicating levels allows you to define a hierarchy between several rules.

Rule Number Rule Description Explanation

1110 Minimize height difference on capacity (in With this rule, you can minimize the height
mm) differences of the surface of the package.
This objective is defined as standard
deviation of the heights of the different
cartonized or non-cartonized products that
form the surface of the package, weighted
by the sizes of these individual product
surfaces.

This is custom documentation. For more information, please visit SAP Help Portal. 34
 4/3/25, 7:52 PM

Rule Number Rule Description Explanation

You can indicate the deviation from the

standard deviation that the package
building optimizer is to reach. This value is
considered as a threshold, that means, all
height differences above are penalized. It is
always measured in millimeter.

3010 Minimize distance of center of mass from With this rule, you can minimize the
capacity center distance between the center of mass of the
load (that is, the products) and the center
of a package, for example, a pallet.

You can indicate a threshold value that

defines the maximum deviation above
which the package building optimizer
penalizes distances.

3020 Minimize height of center of mass on With this rule, you can minimize the height
capacity distance between the center of mass of the
load (that is, the products) and the bottom
side of a package, for example a pallet.

You can indicate a threshold value that

defines the maximum deviation above
which the package building optimizer
penalizes height distances.

Note that these rules only apply to top-level packages, that is, to the outer packaging.

Consistency Check of Package Building Constraints

With this report, you can check whether you have defined your package building constraints in a consistent way.

Use

Package building takes into account a wide range of constraints, such as master data and various profiles. When package building
is complete, you might wonder why the system has built packages in a certain way. This report lets you check your constraints to
discover any potential inconsistencies.

A number of individual checks are available. They are grouped in predefined categories, such as:

Products

Package type assignments

Normalized quantities

Integration

By selecting Open Ref. Mat. Hierarchy (Up) (Open Reference Material Hierarchy (Up)) in the check results area, you can directly
open the test cockpit for unified package building and analyze the product hierarchy. For more information, see Test Cockpit for
Unified Package Building.

This is custom documentation. For more information, please visit SAP Help Portal. 35
 4/3/25, 7:52 PM

Features

Selection

To run the report, you need to select the following:

A product, a reference product, or a range of products

One or several check categories

Moreover, you can specify how the output should look. You can indicate whether the report is to focus on products or checks and
whether successful check results are to be displayed as well. Note that you can change these output settings on the consistency
checks screen after you have executed the checks.

When you execute the report, the consistency checks screen is displayed:

On the left, you can select the individual checks and execute them.

On the right, the check results are displayed.

Output

The check results are displayed according to your output settings. A red check result indicates a critical inconsistency that might
lead to a package building run failure. A yellow check result indicates that the system might not build the packages as you expect it.

From the check results area, you can directly open the following:

Product master

Test cockpit for unified package building (see Integration)

Package type assignment transaction

Activities

Enter transaction code /SCMB/CHECK_PB_CONS in the command field to start the report /SCMB/CHECK_PB_DEFINITIONS.

On the selection screen, choose Program Execute in Background to execute the report in batch mode. The system executes
all checks of the categories, which you selected.

Related Information
Defining Package Type Assignments
Defining Product-Specific Master Data

Stock Removal

Use
The stock removal process includes the picking of goods from storage bins in the warehouse and preparing them at the destination
storage bin. If you use Extended Warehouse Management (EWM) for warehouse management, create a warehouse task for all
stock movements. You use stock removal transfer orders to execute stock removals. EWM groups stock removal warehouse tasks
to warehouse orders. You use the printed warehouse order as a pick list for the stock removal.

This is custom documentation. For more information, please visit SAP Help Portal. 36
 4/3/25, 7:52 PM
EWM contains stock removal strategies to simplify your search for the correct product to be removed from stock. According to the
stock removal strategy, EWM selects the storage type and exact storage bin from which you can pick the product that is to be
removed from stock.

Regardless of how you organize stock removals in your company, you can configure EWM in such a way that the stock removal
activities are performed in one of the following ways:

If EWM creates a warehouse request: automatically, using a Post Processing Framework action.

Regularly at set times, using the automatic wave scheduling.

For more information, see Automatic Wave Assignment.

Process
1. The warehouse request is a request for EWM to remove goods from stock.

For more information, see Warehouse Req. - Type Inbound Del. or Outbound Del. Order.

When EWM creates a warehouse request, you can trigger the picking of goods in EWM automatically. In so doing, EWM
creates one or more warehouse task items for each item in the warehouse request.

EWM automatically transfers the information concerning the picking status to the warehouse order. You then have access to
the current data concerning the processing status in the warehouse.

2. You create a warehouse task for the warehouse request.

3. You use a printed warehouse request as the pick list.

The warehouse request contains the corresponding warehouse tasks.

4. You confirm the warehouse task. In so doing, you confirm in EWM that the physical removal of goods is concluded. The
product that is to be removed from stock is then found at the destination storage bin defined in the warehouse task.

At the same time, EWM transfers the picked quantity directly to the corresponding items in the warehouse request.

In addition, EWM reduces the storage bin stock in the source storage bin by the picked product quantity and posts this
quantity to the destination storage bin.

Example
The following graphic clarifies the process of stock removal from the EWM-managed warehouse using a warehouse request:

This is custom documentation. For more information, please visit SAP Help Portal. 37
 4/3/25, 7:52 PM

To remove the product from stock, you create a warehouse task for a warehouse request to the outbound delivery order. EWM can
create more than one warehouse task from one item in the warehouse request. This is the case, for example, if you have to pick the
product for item 2 of the warehouse request from three different source storage bins to remove the product quantity specified in
the warehouse request. Item 2 of the warehouse request results in the three warehouse tasks 2, 3, and 4. You use warehouse tasks
2 and 3 to move the products from storage type 1 to the goods issue zone, and you use warehouse task 4 to move products from
storage type 2 to the goods issue zone.

Creation of Warehouse Tasks for Stock Removal

Use

Extended Warehouse Management (EWM) creates warehouse tasks for stock removal based on a warehouse request of the type
outbound delivery order, so that you can remove products from stock.

EWM uses a warehouse task to specify the following for the stock removal:

The source storage types, sections, and bins

The path to the destination storage type

Prerequisites
If you want EWM to automatically group warehouse tasks into warehouse orders, you must have made the settings in Customizing
for warehouse order creation.

For more information, see the Customizing for EWM under Cross-Process Settings Warehouse Order .

Features

This is custom documentation. For more information, please visit SAP Help Portal. 38
 4/3/25, 7:52 PM
EWM can create warehouse tasks for an outbound delivery in the following ways:

By default, EWM creates warehouse tasks for an outbound delivery when you release a wave, or when EWM releases
a wave.

EWM automatically creates warehouse tasks for an outbound delivery, using an action from the Post Processing
Framework (PPF).

You create the warehouse tasks manually.

When EWM creates a warehouse task for a warehouse request, it uses stock removal strategies to determine the storage
bin. For more information, see Storage Bin Determination for Stock Removal.

When EWM creates a warehouse task, it uses direct or combined storage control to determine whether you should remove a
handling unit from stock directly or by using interim storage bins.

The warehouse task reflects the direct or combined storage control.

EWM automatically groups warehouse tasks according to your Customizing settings for warehouse orders. For more
information, see Warehouse Order Creation.

EWM uses layout-oriented and process-oriented storage control, according to your Customizing settings. For more
information, see Process-Oriented Storage Control and Layout-Oriented Storage Control.

In the warehouse task, EWM specifies various activities for you to perform (for example, packing) according to your
Customizing settings.

Activities

If you have made settings in Customizing for the PPF action to create warehouse tasks for stock removal, EWM
automatically creates the warehouse task for stock removal.

For more information, see the Customizing for EWM under Cross-Process Settings Delivery Processing Actions Use
Assistant to Create Actions .

By default, you or EWM create warehouse tasks by releasing a wave.

After a wave is generated, it can be released immediately, either automatically or manually depending on the release
methods you have defined for the wave or wave template. For more information, see Processing of Waves.

If you want to create a warehouse task manually, on the launchpad, choose Extended Warehouse Management Work
Scheduling Create Warehouse Task for Warehouse Request Create Warehouse Tasks - Outbound Delivery Order .

If you create warehouse tasks for a delivery for loading, and then want to post the goods issue, on the launchpad, choose
Extended Warehouse Management Shipping and Receiving Load Transportation Units .

When EWM creates a warehouse task for an outbound delivery order, it simultaneously updates this warehouse request
(outbound delivery order). The system carries out this update by inserting a document flow entry. The system updates the
quantity for Picking Planned. If the quantity update leads to a change in status, the system also updates this change in the
warehouse request.

 Example
You have an outbound delivery order of 100 pieces of a product. EWM automatically creates three warehouse tasks
(WT1, WT2, and WT3) for the entire quantity, based on the stock determination.

Following creation of the warehouse tasks, the warehouse request status Picking Planning changes to Completed.

If the system does not create warehouse tasks for the entire quantity, the Picking Planning status is set to Partially
Completed.

This is custom documentation. For more information, please visit SAP Help Portal. 39
 4/3/25, 7:52 PM
The following table provides an overview of the Picking Planning status in the warehouse request.

Goods Issue Process Delivery Item Warehouse Task Warehouse Request Status
Picking Planning
Product description

P-01 10 WT1 for 10 pieces Partially Completed

P-01 20 WT2 for 30 pieces Partially Completed

P-01 30 WT3 for 60 pieces Completed

Stock Removal Path Determination

Use

You can use this function to specify a stock removal path for each activity in the activity area. When Extended Warehouse
Management (EWM) creates a warehouse task (WT), it specifies this stock removal path. During definition of stock removal paths,
you can assign more than one stock removal path, or you can allow activity areas to overlap. However, only one stock removal path
is active for each WT.

Integration

Specification of the stock removal path is integrated into WT processing, which means that EWM sorts the WTs according to the
stock removal path.

Prerequisites
You have defined the storage bin types, descriptions, and structure.

For more information, see Customizing for EWM under Master Data Storage Bins .

You have defined activity areas and categories, have assigned storage bins to the activity areas, and have specified the
sorting sequence of the activity areas.

For more information, see Customizing for EWM under Master Data Activity Areas .

You have assigned an activity to a warehouse process type.

For more information, see Customizing for EWM under Cross-Process Settings Warehouse Task Define Warehouse
Process Type .

Features

If EWM has grouped several WTs into a warehouse order, then it sorts the WTs based on the warehouse order. This is regardless of
which products or HUs are on the storage bins.

If you use radio frequency devices, you can skip a source storage bin proposed by EWM. The system places this source storage bin
at the end of the RF display.

For example, you cannot gain access to a source storage bin because a colleague is currently removing products from it. You skip
the source storage bin proposed by EWM and process the next one.

This is custom documentation. For more information, please visit SAP Help Portal. 40
 4/3/25, 7:52 PM

Activities

For your stock removal, you create, or EWM creates, the necessary WTs for the warehouse request for the outbound delivery order.
In so doing, the system determines the stock removal path according to your settings in Customizing and saves this information in
the WT. On the radio frequency device, the system shows the destination storage bins in this predefined sequence.

Picking

Use

You can use picking to remove goods from your warehouse for a warehouse request.

EWM creates the corresponding warehouse tasks for the warehouse request and assigns them to one or more warehouse orders.
You can use the warehouse order as the pick list.

Process

1. You create, or EWM creates, the warehouse tasks for the warehouse request. In doing so, EWM uses stock determination to
find the required stock. If the full amount of requested stock isn't available, a pick denial may be triggered.

For more information, refer to these pages:

Creation of Warehouse Tasks for Stock Removal

Storage Bin Determination for Stock Removal

Pick Denial

2. EWM allocates the individual warehouse tasks to a warehouse order and builds work packages for the individual warehouse
workers. In this way, EWM determines the stock removal path.

For more information, see Warehouse Order Creation and Stock Removal Path Determination.

3. You can process and confirm the warehouse task as follows:

a. You can print the individual warehouse order and process it. You can also process the warehouse orders using radio
frequency devices.

For more information, see Printing Warehouse Orders and Warehouse Tasks and Work Processing Using Radio
Frequency.

b. You can pack products during the picking process.

For more information, see Pick-and-Pack During Picking.

c. You can carry out a partial picking or a complete picking.

For more information, see Partial Picking.

d. You can enter differences that arise during picking. If there is a shortage of stock, you can execute a bin denial, which
then triggers a pick denial.

For more information, see Handling Differences When Picking for Warehouse Request and Pick Denial.

Result

This is custom documentation. For more information, please visit SAP Help Portal. 41
 4/3/25, 7:52 PM
EWM has created the corresponding warehouse tasks for the warehouse request. You have removed the products from your
warehouse, transferred them to the goods issue zone or packing station, for example, and confirmed the associated warehouse
tasks.

Pick-and-Pack During Picking

Use

You can generate pick-handling units (pick-HUs) into which you can pack products during picking. Extended Warehouse
Management (EWM) assigns the pick-HU to a warehouse task. You transfer, or the system transfers, the pick-HUs to the delivery.
You do not need to execute any further packing for the delivery.

Prerequisites

You have created a product that is a packaging material.

On the launchpad, choose Master Data Product Maintain Product .

You have defined a packaging material.

In Customizing for EWM, select Cross-Process Settings Handling Units Basics Define Packaging Material .

In Customizing, determine which steps you want to execute automatically using EWM.

 Note
For more information about making settings in Customizing for the individual steps, see the Activities section below.

For more information about packaging materials, see Packaging Materials.

Features

In Customizing for the creation of a warehouse order, you can make settings for which packaging material the system should
propose for picking. When EWM creates a warehouse order, you can set the packing proposals for any number of combinations of
warehouse order, activity area, and movement type, as follows:

Automatic creation and assignment of pick-HUs

When EWM creates a warehouse order, it automatically creates one or more pick-HUs with the specified packaging
material. It assigns the pick-HUs to the warehouse tasks in the warehouse order (optional). When you confirm the
associated warehouse tasks, you can manually change the pick-HUs and their assignments to the warehouse tasks.

Automatic proposal of packaging materials

When EWM creates a warehouse order, it automatically proposes the number of pick-HUs with the required packaging
material. When you confirm the warehouse tasks for the warehouse order, you can confirm the proposals for the packaging
materials and manually create your own pick-HUs.

Manual creation and assignment of pick-HUs during warehouse task confirmation

EWM does not create any pick-HUs, nor does it determine a packaging material. You can create the pick-HUs manually.
When you confirm the warehouse task, you can manually assign the pick-HUs to the warehouse task.

For more information about packing, see Packing During Warehouse Task Confirmation.

Warehouse Task Item Split for Pick-HUs

This is custom documentation. For more information, please visit SAP Help Portal. 42
 4/3/25, 7:52 PM
If you determine during picking of the warehouse task items that the pick-HU is too small for the entire item quantity, you can split
the warehouse task item and pick in a newly-created pick-HU. In other words, you can execute a partial picking.

Activities

If you want EWM to automatically create and assign the pick-HUs, in Customizing for EWM, choose Cross-Process
Settings Warehouse Order Define Packing Profile for Warehouse Order Creation .

Define a packing profile.

If you want EWM to automatically create pick-HUs, select Create HUs.

If you want EWM to automatically assign pick-HUs to the warehouse tasks in the warehouse order, choose Assign
HUs to WTs.

If you want EWM to automatically propose the number of pick-HUs with the required packaging material, then in
Customizing for EWM, choose Cross-Process Settings Warehouse Order Define Packing Profile for Warehouse
Order Creation , and define a packing profile without choosing Create HUs or Assign HUs to WTs.

If you want to manually create and assign pick-HUs, you do not define a packing profile in Customizing for EWM.

 Note
For more information about the packing profile, see Customizing for EWM under Cross-Process Settings Warehouse
Order Define Packing Profile for Warehouse Order Creation .

Partial Picking

Use

In a partial picking, Extended Warehouse Management (EWM) creates a warehouse task for a warehouse request item, even though
it can't completely fulfill all items for the warehouse request.

 Note
By default, EWM executes partial picking.

If the available quantity in the warehouse isn't sufficient to fulfill all warehouse request items, you can prevent the creation of a
warehouse task.

Prerequisites

If you want to execute a complete picking, you've made the settings for complete picking for a warehouse request item. For more
information, see Customizing for EWM under Cross-Process Settings Warehouse Task Define Warehouse Process Type .

Features

You use the standard setting (partial picking) so that EWM creates a warehouse task even though it can't completely fulfill all the
warehouse request items.

You use the complete picking as follows:

This is custom documentation. For more information, please visit SAP Help Portal. 43
 4/3/25, 7:52 PM
To ensure that EWM doesn't create a warehouse task during a background processing function, such as wave release or
actions triggered by the Post Processing Framework (PPF).

To ensure that EWM warns you that the required quantity can't be fulfilled and that a complete picking is required. You can
cancel the creation of the warehouse task or save the warehouse task that you've created internally but haven't saved or
canceled yet.

 Example
You created an outbound delivery with two products of 50 pieces each. After you created the outbound delivery, you
removed from the warehouse 10 pieces of the product in the second outbound delivery item, so that only 40 pieces
remain. If you create a warehouse task for this outbound delivery, the system notifies you that it can't completely fulfill
the picking requirements.

Activities

The following table provides an overview of the possibilities in partial picking:

Partial Picking Is Allowed Procedure Result

EWM automatically adjusts the outbound In Customizing for EWM, choose Cross- EWM transfers the warehouse task quantity
delivery quantity to the warehouse task Process Settings Exception Handling as warehouse request quantity to the
quantity. Define Exception Codes and choose corresponding items of the warehouse
Delivery Adjustment in Case of request.
Differences. Define the delivery adjustment
in the case of differences.

You manually adjust the outbound delivery On the launchpad, choose Extended EWM transfers the warehouse task quantity
quantity to the picked quantity. Warehouse Management Delivery as warehouse request quantity to the
Processing Outbound Delivery corresponding item of the warehouse
Outbound Delivery Orders . request.

Choose Change Mode and Adjust Delivery

Quantity. Adjust the outbound delivery
quantity to the warehouse task quantity.

You do not adjust, or the system does not Not applicable EWM hasn't completely picked the
adjust, the outbound delivery quantity to outbound delivery yet. You can create
the picked quantity. additional warehouse tasks so that the
system can fill all items of the outbound
delivery.

Pick Denial

Use
You have a warehouse request for an outbound delivery order, a posting change, or a stock transfer, but there is not enough stock
in the warehouse to fulfill one or more of the warehouse request items. A pick denial allows you to post goods issue, even though
you were unable to confirm all of the requested quantity.

The following cases lead to a pick denial:

If Extended Warehouse Management (EWM) can't find stock to fulfill the requested quantity while it is creating a warehouse
task for a warehouse request item, it can't create the warehouse task, or it can only create a warehouse task with a partial
quantity. For more information, see Partial Picking.
This is custom documentation. For more information, please visit SAP Help Portal. 44
 4/3/25, 7:52 PM
If EWM was able to create the warehouse task, but you discover a shortage of stock at the bin, you can use an exception
code to perform a storage bin denial.

Prerequisites

You've activated pick denial at warehouse number level.

For more information, see Customizing for Extended Warehouse Management under Goods Issue Process Pick Denial
Activate Pick Denial at Warehouse Number Level .

You've activated pick denial at warehouse process type level.

For more information, see Customizing for Extended Warehouse Management under Goods Issue Process Pick Denial
Specify Pick Denial at Warehouse Process Type Level .

You've defined your own exception codes for calling exception handling, and have assigned these to the internal exception
codes defined by SAP.

For more information, see Customizing for Extended Warehouse Management under Cross-Process Settings Exception
Handling Define Exception Codes and under Goods Issue Process Pick Denial Assign Internal Exception Codes
to Exception Codes .

 Note
Pick denial won't work if you have specified that warehouse task creation is to be canceled if EWM can't completely fulfill the
requested quantity of the warehouse request, for example, in a Business Add-In (BAdI) such as BAdI: Termination of
Warehouse Task Creation.

Process

1. You want to create a warehouse task. However, EWM can't create a new warehouse task, or it can only create a warehouse
task with a partial quantity. It was not able to find sufficient warehouse stock according to the storage type search sequence
or the overall stock search strategy. Note that the requested stock could be located in another area of the warehouse that
was not searched.

You can create a warehouse task using the user interface for stock removals for the warehouse request (in dialog mode) or
as a background job (background processing mode). You can start a background job, for example, using a Post Processing
Framework action or a wave release.

2. EWM compares the requested quantity with the warehouse task quantity. If the system determines differences, it performs
exception handling according to your Customizing settings. If you've specified an action in Customizing, for example, to
adjust the quantity in the warehouse request to the picked quantity, the system triggers an alert and creates a workflow
task.

You perform, or the system performs, the following actions:

If you create the warehouse task in dialog mode, EWM writes an entry into the application log to inform you that a
pick denial has occurred.

You can proceed as follows:

Accept or manually change the action that is proposed based on your Customizing settings.

The system executes a pick denial and executes a workflow in the background.

Execute the workflow using the action proposed by the system based on your Customizing settings, by
choosing SAP Office Folders Inbox , or delete it and create a new warehouse task, for example if you
still have stock in another storage type.

This is custom documentation. For more information, please visit SAP Help Portal. 45
 4/3/25, 7:52 PM
You can use a BAdI to prevent the pick denial from triggering the exception process when a workflow task is
started. For more information, see Customizing for Extended Warehouse Management under Business
Add-Ins (BAdIs) for Extended Warehouse Management Cross-Process Settings Warehouse Task
Creation of Warehouse Tasks Warehouse Task for Warehouse Request BAdI: Prevention of Pick Denial
Execution in Workflow Task .

If EWM creates the warehouse task in background mode, it automatically triggers a pick denial according to your
Customizing settings and performs any follow-up action in the background.

If you use wave management, EWM also writes an entry into the wave management log to inform you that it couldn't
create a warehouse task, or or that it could only create a warehouse task with a partial quantity.

 Note
If pick denial is triggered for stock transfer items that are assigned to a wave, you can configure your system to remove
the stock transfer item from the assigned wave. This allows picking to be replanned for the stock transfer item, which
can be assigned to different wave.

 Note
You can override the pick denial action if you are working in one of the Create Warehouse Tasks apps for outbound
delivery orders, posting changes, or warehouse requests.

3. EWM sends a message about the pick denial to your enterprise management system, for example, SAP S/4HANA or SAP
ERP, depending on whether you are using EWM in SAP S/4HANA or decentralized EWM.

 Note
EWM doesn't send a message for a direct outbound delivery order. EWM only adjusts the outbound delivery quantity for
the direct outbound delivery order.

Result

EWM has executed the following actions for pick denial:

Adjusted the quantity in the warehouse request to the picked quantity

Sent a message about the pick denial to the enterprise management system, if required

Removed the stock transfer item from its wave, depending on the warehouse process type setting

 Note
For more information about reporting a change to an outbound delivery, see Processing of Outbound Deliveries under
the point Reporting of an outbound delivery change to SAP S/4HANA.

Cancellation of Picking

Use

If you have picked too much, for example, or if you require previously picked stock more urgently for another outbound delivery,
you can cancel an outbound delivery either partially or completely.

Prerequisites

This is custom documentation. For more information, please visit SAP Help Portal. 46
 4/3/25, 7:52 PM
If you want to release stock and simultaneously create a warehouse task (WT) in the background, you need to have performed the
following in the Customizing settings for Extended Warehouse Management (EWM):

You have defined the warehouse process type for the cancellation of picking. For more information, see Customizing for
EWM under Goods Issue Process Cancel Picking Define Warehouse Process Type for Putback .

You have defined the warehouse process type for the cancellation of picking as a default value. For more information, see
the IMG for EWM under Goods Issue Process Cancel Picking Define Warehouse Number Control for Putback .

Features

EWM cancels previously picked stock of warehouse request items (WR items) or handling units (HUs), as well as reserved stock of
WTs. EWM releases the assignment of picked or reserved stock from the WR items, HUs or WTs. This makes the stock freely
available again.

For packed stock, EWM can only release stock for the highest-level HU. In addition, EWM can only release stock for complete HUs.

If EWM releases the assignment of a stock, the system can also create a new WT at the same time. If EWM is creating the WT in the
foreground, the system proceeds as follows:

1. EWM starts by releasing the stock.

2. If the stock is unpacked, EWM then calls the transaction for moving products. If the stock is packed, EWM calls the
transaction for moving HUs.

3. You define the new WT by creating storage bins or the warehouse process type for the new WT, for example.

If EWM is creating the WT in the background, the system releases the stock and simultaneously creates a new WT with the
specified warehouse process type.

On the Warehouse Request Items tab page, EWM gives you information that is relevant for the cancellation of picking for the WR
item. On the Stock tab page, EWM gives you information about the stock, such as where the different stock is located in the
warehouse. On the Open Product WT tab page, EWM displays the open product WTs of the WR items.

Activities
Release Stock From One or More WR Items

You can cancel stock that has already been picked for one or more WR items. To do this, on the launchpad, choose Extended
Warehouse Management Execution Cancel Picking. In the Document Number field for the search, you enter the outbound
delivery that contains the WR item that you want to cancel. EWM shows you all WR items that belong to this outbound delivery. You
can choose between the following options:

You can release the entire picked delivery quantity for a WR item. To do this, on the Warehouse Request Items tab page you
select the WR item that you want to cancel, and then choose Release Stock.

You can cancel the picked delivery quantity of a selected stock in the WR item only. To do this, on the Warehouse Request
Items tab page, select the WR item that contains the corresponding stock. On the Stock tab page you then select the stock
that you want to cancel, and then choose Release Stock.

You can cancel a partial quantity of the picked delivery quantity of a selected stock in the WR item only. To do this, on the
Warehouse Request Items tab page, select the WR item that contains the corresponding stock. In the Cancel Quantityfield
on the Stock tab page, you then specify the delivery quantity that is to be cancelled for this stock.

If you are working with serial number requirement Serial Numbers in Inventory Management, you can do the following:

This is custom documentation. For more information, please visit SAP Help Portal. 47
 4/3/25, 7:52 PM
You first specify the delivery quantity to be cancelled in the Cancel Quantity field and then choose Serial Numbers.
EWM displays the serial numbers corresponding to the cancel quantity. You select the serial numbers that you want
to cancel.

You start by choosing Serial Numbers. EWM displays all the serial numbers for the selected stock. You select the
serial numbers that you want to cancel. EWM automatically calculates the delivery quantity that you have to cancel,
and displays it in the Cancel Quantity field.

Release Stock From One or More HUs

You can cancel stock that has already been picked for one or more HUs. To do this, on the launchpad, choose Extended
Warehouse Management Execution Cancel Picking. In the Handling Unit Identification field for the search, you enter the
HU that you want to cancel.

You can release the entire picked delivery quantity for an HU. To do this, on the Handling Unit tab page you select the HU
that you want to cancel, and then choose Release Stock.

If you have packed multiple stocks into an HU, EWM displays the corresponding information on the Stock tab page.
However, you cannot edit this data.

If you want to cancel a partial quantity of an HU only, you first have to repack the HU. To do this, on the Handling Unit tab
page choose Repack HU (see Packing in the Work Center).

Cancel WTs From One or More WR Items

You can cancel stock that has already been reserved for one or more WTs. To do this, on the launchpad, choose Extended
Warehouse Management Execution Cancel Picking. In the Document Number field for the search, you enter the outbound
delivery that contains the WR item whose WT you want to cancel. EWM shows you all WR items that belong to this outbound
delivery. You can choose between the following options:

You can cancel the entire reserved delivery quantity for a WR item. To do this, on the Warehouse Request Items tab page
you select the WR item whose WTs you want to cancel, and then choose Cancel WT. EWM then cancels all WTs that belong
to the selected WR item.

You can cancel the reserved delivery quantity of a selected WT in the WR item only. To do this, on the Warehouse Request
Items tab page, select the WR item that contains the corresponding WT. On the Open Product WT tab page you then select
the WT that you want to cancel, and then choose Cancel WT. EWM then cancels the selected WTs only.

Cancel WTs From One or More HUs

You can cancel stock that has already been reserved for one or more HUs. To do this, on the launchpad, choose Extended
Warehouse Management Execution Cancel Picking. In the Handling Unit Identification field for the search, you enter the
HU that you want to cancel. On the Handling Unit tab page, you choose the corresponding HUs and then choose Cancel WT. EWM
then cancels all open WTs that belong to these HUs.

Release Stock and Create WT Simultaneously (WR Item or HU)

Corresponding to the above descriptions for releasing stock for WR items and HUs, EWM can simultaneously release stock and
create new WTs (either in the foreground or in the background). To do this, follow the descriptions above for releasing stock.
However, instead of choosing Release Stock, you choose Release Stock + Create WT.. You then select either Release Stock + WT
in Foreground or Release Stock + WT in Background from the dropdown box.

Further Options

If you want to integrate cancel picking into your own UIs, you can use the API /SCWM/IF_API_CANCEL_PICKING. See the
interface information in the system.

This is custom documentation. For more information, please visit SAP Help Portal. 48
 4/3/25, 7:52 PM

Pick by Cart
You can use pick by cart to pick multiple orders with a pick cart in a single trip through the warehouse.

With this app, you can improve customer satisfaction in the following ways:

To improve picking efficiency

To reduce human errors

To reduce the cost of warehouse operations

Key Features
Enable to pick multiple orders in a single trip

Graphically display handling units (HUs) and their logical positions on a pick cart

Employ intuitive Fiori user interface

Provide up-to-date picking relevant information

Support scanning

Pick serial-number and batch managed products

Configure notification sounds for messages

Pick products for warehouse orders of a specific queue

Additional Details

You can use the Pick by Cart app only for warehouse orders with planned HUs.

The process of this app contains the following steps:

In the preparation step, you put pick-HUs in the logical positions of a pick cart for the subsequent pick and unloading tasks.

In the pick step, you pick products for destination HUs. A pick step contains pick tasks grouped together for picking
products with the same attributes, for example, the same source bin.

In the unloading step, you unload HUs at their destinations. An unloading step can contain several HUs grouped together
because of the same destination bin.

For more information about a how-to guide, see 3004810 .

Supported Device Types

Desktop

Tablet

Constraints

Currently, the Pick by Cart app does not support the picking of catch-weight managed products.

Related Information
App Extensibility: Pick by Cart

This is custom documentation. For more information, please visit SAP Help Portal. 49
 4/3/25, 7:52 PM

Pick by Cart Video

Open this video in a new window

App Extensibility: Pick by Cart

Business Add-Ins (BAdIs)

The following BAdI is available for extensibility purposes:

BAdI: Data Retrieval for Product Detail View (/SCWM/EX_PBC_MAT_PIC) in Customizing for Extended Warehouse
Management under Business Add-Ins (BAdIs) for Extended Warehouse Management Goods Issue Process Pick
Cart .

You can use this BAdI to change the product detail view by adding a product picture for a pick step in the Pick by Cart app.

BAdI: Notification Sounds for Messages (/SCWM/EX_PKODLV_MSG_AUDIO) in Customizing for Extended Warehouse
Management under Business Add-Ins (BAdIs) for Extended Warehouse Management Cross-Process Settings .

You can use this BAdI to retrieve the audio URIs of the notification sounds for your messages.

Processing of Non-Picking-Relevant Delivery Items

Purpose

You can use the processing of non-picking-relevant delivery items to remove goods from your warehouse for a warehouse request
of the type outbound delivery order. However, in contrast to picking, Extended Warehouse Management (EWM) does not generate
any warehouse tasks for the warehouse request or any warehouse orders.

Prerequisites

This is custom documentation. For more information, please visit SAP Help Portal. 50
 4/3/25, 7:52 PM
The goods movement bin in the warehouse request from which you are booking out the stock for the goods issue must
contain a valid storage bin in which a sufficient quantity of the product is available.

You use an item type that does not contain any of the following status types in the status profile:

Planning Picking

Picking

For more information, see the Implementation Guide (IMG) for EWM under Cross-Process Settings Delivery
Processing Status Management Define Status Profiles.

Process

1. You or EWM create the warehouse request for an outbound delivery order. Either ERP distributes an outbound delivery to
EWM and EWM automatically generates a corresponding warehouse request, or you manually generate the warehouse
request in EWM as a direct outbound delivery order.

You specify all the relevant stock attributes of the product (for example, the stock type) and a goods movement bin in the
warehouse request.

If you have configured goods movement bin determination, EWM automatically suggests a goods movement bin. On
the SAP Easy Accessscreen, choose Extended Warehouse Management Settings Determine Goods
Movement Bin. EWM also uses the settings that you specify here to process inbound deliveries that are not
relevant to putaway.

If you generate the warehouse request manually, choose one of the following options:

You specify the items with their stock attributes and quantities on the Items tab page.

On the HU tab page, you choose the Create and Save pushbuttons and specify a handling unit (HU) and an
item type. Then EWM automatically creates the corresponding items with their stock attributes and
quantities.

2. You remove the products from your warehouse and perform any other relevant goods issue steps, for example, loading for
transportation.

3. You post the goods issue for the outbound delivery order.

Result

EWM has generated a warehouse request for an outbound delivery order. You have removed the products from your warehouse,
posted the goods issue (for example in sell from stock) or performed additional goods issue activities, and have then posted goods
issue.

Storage Control

Use

You can use the process-oriented as well as layout-oriented methods for storage control. The goal of storage control is to display
your complex putaway, stock removal process steps, and warehouse-internal movements based on your processes or your layout
data. During putaway, stock removal, or warehouse-internal movements, an individual process step can be executed on single level
basis or on multi level basis (that is, through intermediate storage types).

You can combine the process-oriented storage control with the layout-oriented storage control. Here, Extended Warehouse
Management (EWM) always executes the process-oriented storage control first. The layout-oriented storage control then checks

This is custom documentation. For more information, please visit SAP Help Portal. 51
 4/3/25, 7:52 PM
whether the sequence of putaway process steps is possible in layout view, and if required, adjusts the flow of the putaway, stock
removal, or warehouse-internal movement.

 Example
Based on the process-oriented storage control, EWM determined the following putaway process flow:

Unloading at door

Checking the quality

Executing value-added services

Putaway in high rack storage area

The layout-oriented storage control determines that a direct putaway in the high rack storage area is not possible and that the
putaway must occur with the use of an identification point.

Unloading at door

Identification of goods at the ID point

Putaway in high rack storage area

Integration

EWM uses the delivery to determine, via delivery type and delivery item among others, the warehouse process type. This contains
the procedure, in other words, the putaway or stock removal process with different activities. EWM transfers this operation to the
handling unit to be put away or removed from stock. The handling unit thus contains the information concerning what process
steps are required for the putaway, stock removal, or warehouse-internal movement.

Prerequisites

You have defined the following in Customizing for the putaway:

Parameters that specify the work station determination for the next function within the goods receipt process

The following parameters are possible:

Source Storage Type

Destination activity area or destination storage type

Warehouse Process Type

Handling Unit Type

Determination of the warehouse process type, using the delivery type and delivery item type, among others.

Features

For information about the features of storage control, see Process-Oriented Storage Control and Layout-Oriented Storage Control.

Process-Oriented Storage Control

This is custom documentation. For more information, please visit SAP Help Portal. 52
 4/3/25, 7:52 PM

Use

You use this type of storage control to map complex putaways, stock removals, and warehouse-internal movements. In doing so,
you combine your storage process steps into one storage process. You can also trace the status of the individual process steps.

 Note
Process-oriented storage control only operates with handling units.

Integration

For information about integration, see Storage Control.

Prerequisites

For information about the prerequisites, see Storage Control.

Features
You define the process steps for your complex storage process.

A process step is, for example, unloading or deconsolidating. Extended Warehouse Management (EWM) recognizes internal
process steps predefined by SAP and external steps that you can define yourself. Your external process steps can base themselves
on internal ones.

In addition, internal or external process steps can be simple, such as unloading, or combined, such as deconsolidating.

For more information, see Direct and Combined Storage Control (Putaway).

The process steps for the Deconsolidating process predefined by SAP can be dynamic.

Activities
For Customizing of process-oriented storage control, in Customizing for EWM, choose Cross-Process Settings Warehouse
Task Define Process-Oriented Storage Control .

Direct and Combined Storage Control (Stock Removal)

Use

If you want to execute a direct stock removal, you do not have to define anything in process-oriented storage control.

If you want to define complex stock removal processes, you have to use combined process-oriented storage control. Extended
Warehouse Management (EWM) uses this during creation of a warehouse task to determine the intermediate storage types (for
example, packing station).

For information about integration and the prerequisites, see Storage Control.

Features

This is custom documentation. For more information, please visit SAP Help Portal. 53
 4/3/25, 7:52 PM
Direct Storage Control for Stock Removal

If EWM determines that you are to pick a handling unit (HU) directly, it creates a warehouse task for this HU that determines the
way from the source storage type to the destination storage type. For more information about updating the status, see Updating
the Outbound Delivery Order in the GI Process.

The following graphic shows you the relationship between direct putaway and creation of warehouse tasks.

Combined Storage Control for Stock Removal

If EWM determines that you are to pick a HU from stock using one or more intermediate storage types, it creates one warehouse
task per route section for this HU.

One warehouse task that describes the route from source storage type to intermediate storage type

Irrespective of your settings in Customizing, SAP ERP also creates a warehouse task per product contained in the HU.

Based on your settings in Customizing, one warehouse task from the intermediate storage type to the next intermediate
storage type, or to the final destination storage type

You can carry out different activities at the intermediate storage types. For example, in a stock removal process, at an intermediate
storage type, you can distribute HUs containing different products to stock removal HUs.

In combined stock removal, you can determine the final destination storage type either right at the beginning of your stock removal
process, or later.

EWM manages the intermediate storage types in the same way as standard storage types. For example, you can break these down
into storage sections and storage bins.

For more information about updating the status, see Updating the Outbound Delivery Order in the GI Process.

This is custom documentation. For more information, please visit SAP Help Portal. 54
 4/3/25, 7:52 PM
The following graphic shows you the relationship between combined stock removal and creation of warehouse tasks.

Updating the Outbound Delivery Order in the GI Process

Use

Extended Warehouse Management (EWM) updates the outbound delivery order corresponding to the goods issue (GI) activities.

Features

EWM updates the outbound delivery order for the following GI processes:

Unpacked stock

1. You or EWM generate the first product warehouse task (WT).

EWM sets the status Picking Planning in the outbound delivery order.

2. You confirm the first product WT for picking.

This is custom documentation. For more information, please visit SAP Help Portal. 55
 4/3/25, 7:52 PM
EWM sets the status Picking in the outbound delivery order. If the destination location in the product WT is a storage bin at
the door or a transportation unit (TU), EWM sets the status Unloading in the outbound delivery order.

Packed stock

1. You or EWM generate the first product WT.

EWM sets the status Picking Planning in the outbound delivery order.

2. You confirm the first product WT for picking.

EWM sets the status Picking in the outbound delivery order.

3. You pack the stock.

4. You or EWM generate the related loading warehouse task (loading WT), meaning the destination location corresponds to a
bin at the door or to a TU.

5. You confirm the loading WT.

EWM sets the status Loading in the outbound delivery order.

Layout-Oriented Storage Control

Use

You can use the layout-oriented storage control if stock movements in your warehouse do not travel from a source storage bin to a
destination location directly, but rather travel via an intermediate storage bin.

 Note
The layout-oriented storage control only operates with handling units.

The following scenarios do not need handling units to trigger the process, but they still require HUs to run the process.

In the identification point scenario, the initial warehouse task for the process can be created without an HU. However,
you have to specify the destination HU when you confirm the warehouse task .

In the pick point scenario, the pick task can be created without entering a source HU. The system determines the
required HU during the warehouse task creation and saves it in the picking warehouse task. The system also creates an
HU warehouse task to bring the source HU to the pick point.

You use layout-oriented storage control in the material flow system to define conveyor segments. For more information, see
Material Flow System (MFS).

Prerequisites

For more information about the prerequisites, see Storage Control.

Features

For layout-oriented storage control, you define external warehouse process steps for your warehouse, including identification
points and pick points.

This is custom documentation. For more information, please visit SAP Help Portal. 56
 4/3/25, 7:52 PM

 Example
For example, you have a high rack storage area. If you want to move a product pallet from storage bin A (goods receiving area)
to storage bin B (high rack storage area), the system should execute a contour and weight check to ensure that the product
pallet can be put away in the high rack storage area safely. For this activity, Extended Warehouse Management (EWM) splits the
warehouse order into two: one from storage bin A to identification point I, and a second from identification point I to storage bin
B.

You can move your goods using a pick point during picking.

Procedure

For Customizing of layout-oriented storage control, in Customizing for Extended Warehouse Management, choose Cross-
Process Settings Warehouse Task Layout-Oriented Storage Control .

Stock Determination

Use
You use stock determination to apply stock removal strategies during picking and stock transfers, based on predefined settings in
Customizing. Based on the recorded product requirements, Extended Warehouse Management (EWM) determines in which
sequence, from which storage types, and from which stock you are to remove the required product.

EWM executes stock determination during creation of the warehouse task. During stock determination, EWM considers own stock,
consignment stock, and, in the case of internal movements, different stock types.

Prerequisites

You've set stock determination groups in Customizing for Extended Warehouse Management under Cross-Process Settings
Stock Determination Maintain Stock Determination Groups , and have saved these groups in the product master so EWM can
execute stock determination for a product.

You've set a stock determination strategy that the system uses to reduce stock in Customizing for Extended Warehouse
Management under Cross-Process Settings Stock Determination Configure Stock Determination . You also define a
valuation, which allows you to prioritize stock with different owners or with different stock types differently.

For more information about Customizing for stock determination, see Customizing for Extended Warehouse Management under

Cross-Process Settings Stock Determination Maintain Stock Determination Groups

Cross-Process Settings Stock Determination Configure Stock Determination

Features
In EWM, stock determination occurs in the background during creation of warehouse tasks.

You can define the following stock determination strategies:

Stock Determination Has Priority

During stock removal, EWM considers the stock characteristics Owner and Stock Type as defined by you for the warehouse
number. EWM uses the stock removal sequence to check the existing stock for the corresponding stock.

This is custom documentation. For more information, please visit SAP Help Portal. 57
 4/3/25, 7:52 PM
The stock removal sequence arises from prioritizing individual stock according to the valuation you've defined. EWM first
searches through existing stock according to the stock characteristics that have the highest number of points. If the
required stock is larger than the stock found, EWM searches the existing stock according to the stock characteristics that
have the next highest number of points. EWM continues this process until it finds enough stock for the required stock, or it
notifies you that it can only find a portion of the required stock.

EWM Has Priority

During stock removal, EWM considers all allowed stock, regardless of the stock characteristic of the warehouse number. It
stores the required quantities and in so doing, only considers the stock removal rule defined in EWM, such as FIFO (First In,
First Out). In this case, EWM removes the oldest quantity from stock, irrespective of whether this is own stock or
consignment stock. You can also use the stock determination’s number of points as the sort criteria in the stock removal
rule, so, for example, the stock found per storage type is removed from stock according to a descending number of points.

Activities

In Customizing for Extended Warehouse Management under Cross-Process Settings Stock Determination Maintain Stock
Determination Groups , define the stock determination strategy (Stock Determination Has Priority or EWM Has Priority) for the
stock determination group.

Example

You define a stock determination strategy that you use during replenishment activities to firstly remove own stock (owner GLENN)
and then to remove consigned stock for owner SMITH (owner SMITH). To do this, you define the following in Customizing for
Extended Warehouse Management:

Maintain Stock Determination Groups

You define the stock determination group 01 for warehouse 001, using the stock determination strategy Stock
Determination Has Priority.

Configure Stock Determination

Warehouse Party Activity Stock Current Stock Inbound Permitted Valuation

Number Entitled Determination Number Characteristic Value Value
to Group
Dispose

001 GLENN Replenishment 01 1 Owner GLENN GLENN 100

001 GLENN Replenishment 01 2 Owner GLENN SMITH 10

The system uses your stock determination strategy to search for the stock determination group 01.

If you've specified the strategy Stock Determination Has Priority for the stock determination group 01, EWM first searches
the warehouse for own stock according to the stock removal strategy. If EWM can't fulfill the required quantity for the
warehouse task, it also searches for stock from owner SMITH and uses stock found here as well to fulfill the warehouse
task’s required quantity.

If you've specified the strategy EWM Has Priority for the stock determination group 01, EWM searches the warehouse for
own stock and for stock from owner SMITH, according to the stock removal strategy. You define the stock removal
sequence by using the storage type search sequence and the stock removal strategy, such as FIFO. You've made settings in
Customizing for stock determination to define valuation points for the individual owners, and thus have prioritized stock
from one of the owners. You can use this prioritization to sort stock for a storage type or storage type group.

This is custom documentation. For more information, please visit SAP Help Portal. 58
 4/3/25, 7:52 PM

Storage Bin Determination for Stock Removal

Storage bin determination for stock removal determines storage bins and stock for stock removals and internal movements. Here,
for example, the system uses parameters from the product master that you've defined manually or those that the system has
determined in slotting (see Slotting).

You can define the business strategy according to which the storage bin determination for stock removal is to run, for example,
FIFO (First In, First Out). You make the settings for these stock removal strategies in Customizing.

Storage bin determination for stock removal occurs automatically when warehouse tasks are created.

Prerequisites

You have defined a stock removal rule in Customizing for Extended Warehouse Management under Goods Issue Process
Strategies Specify Stock Removal Rule .

You have defined a storage type search sequence in Customizing for Extended Warehouse Management under Goods
Issue Process Strategies Specify Storage Type Search Sequence .

You have assigned the storage type search sequence in Customizing for Extended Warehouse Management under Goods
Issue Process Strategies Determine Storage Type Search Sequence for Stock Removal .

You have assigned the stock removal rule to the storage type in Customizing for Extended Warehouse Management under
Master Data Define Storage Type .

Alternatively, you can assign the stock removal rule under Goods Issue Process Strategies Determine Storage Type
Search Sequence for Stock Removal .

Features

Determination of Stock Removal Search Sequence and Stock Removal Rule

The stock removal search sequence contains information about the storage types in which the system is to search for stock and
the order in which it is to sort the stock found. The stock removal rule specifies the order in which the system is to sort the
individual quants.

The system determines the stock removal search sequence on the basis of the parameters from the warehouse task.

In Customizing, you can link a stock removal rule to a stock removal search sequence. This means that the stock removal rule is
fixed for all storage types belonging to the stock removal search sequence. If you have not linked the stock removal rule and the
stock removal search sequence to one another, the system uses the stock removal rule that you have defined for the storage type
or the storage type group. If you enter the storage type or the storage type group manually, the system calls the determination of
stock removal search sequences to determine the stock removal rule.

You can use the Business Add-Ins (BAdIs) in the /SCWM/ES_CORE_RMS enhancement spot to make changes to the result.

Determination of Storage Type or Storage Type Group

The system uses the stock removal search sequence that was found to determine the storage type or the storage type group in
which it is to search for stock.

Selection of Quants

The system uses the storage type or the storage type group that was found to select the stock.

This is custom documentation. For more information, please visit SAP Help Portal. 59
 4/3/25, 7:52 PM
You can use the BAdIs in the /SCWM/ES_CORE_RMS enhancement spot to make changes to the result.

Sorting the Quants

The system uses the stock removal rule that was found to sort the stock that was determined. You can use the BAdIs in the
/SCWM/ES_CORE_RMS enhancement spot to make changes to the result.

For customer-defined packing and picking (see Customer-Defined Packing and Picking), the system uses a fallback
implementation of BAdI: Filtering and/or Sorting of Quants to filter and sort available stock for relevant outbound delivery order
items according to the following logic:

Filtering

The system considers items packed into handling units (HUs) only.

The HUs must have a reference to the sales document item that the outbound delivery order item refers to, or no
reference to a sales document item. The system doesn't consider HUs with a reference to a different sales document
item.

The HUs must have a reference to the default packing instruction / packaging specification or alternative packing
instruction / packaging specification that was determined for the outbound delivery order item (see Creation of
Warehouse Tasks for Warehouse Request).

Sorting

Sales document and default packing instruction or packaging specification

No sales document and default packing instruction or packaging specification

Sales document and alternative packing instruction or packaging specification

No sales document and alternative packing instruction or packaging specification

 Note

BAdI: Filtering and/or Sorting of Quants can overrule the stock removal rule.

The system also considers other factors influencing stock selection (such as blocked bins).

As this is a fallback BAdI implementation, you can change the logic by providing your own BAdI implementation.

If essential, you can ignore the requirement to have a suitable packing instruction or packaging specification on HU level
by selecting the Ignore PI/PS checkbox in the Create Warehouse Tasks – Outbound Delivery Order app.

The system can then select stock from HUs just with the same sales document.

Selection of a Quant

The system chooses the first quant that was found, and checks it. If it cannot use this quant, for example, because the quantity is
insufficient or the storage bin is locked for stock removal, the system takes the next quant, and so on.

Work Center Determination in Goods Issue

Use

In Extended Warehouse Management (EWM), you can have the system determine a work center in goods issue. You can specify
various criteria for this determination.

This is custom documentation. For more information, please visit SAP Help Portal. 60
 4/3/25, 7:52 PM

Prerequisites

In Customizing for EWM, you have set the Determine WkCtr indicator in the used warehouse order creation rule, under Extended
Warehouse Management Cross-Process Settings Warehouse Order Define Creation Rule for Warehouse Orders .

Features

You can define the following criteria for the determination:

Warehouse number

Route

Activity area

Consolidation group

If you have set the indicator Determine WkCtr in the used warehouse order creation rule, EWM uses your criteria during warehouse
order creation . You can specify any number of criteria for the determination. EWM first attempts to find a work center matching
your criteria. If it cannot find a work center, it uses the optimization that you have specified in Customizing for EWM under
Extended Warehouse Management Master Data Work Center Optimize Work Center Determination in Goods Issue .

You also specify at least the storage bin for the work center determination. You can also specify the storage type or storage section.

If you specify the storage type or storage section, the storage type must have the storage type role Work center . If you only
specify a storage type, this has to have the putaway rule Consolidation Group . EWM checks these settings when you save
your details.

If you do not specify a storage type or storage section, EWM determines these values when you save your details.

Activities

On the launchpad, choose Extended Warehouse Management Master Data Work Center Determine Work Center - Goods
Issue.

Result

EWM analyzes the details that you enter here. EWM assigns the determined destination data storage type, storage section and
storage bin to the warehouse tasks that it bundles using the warehouse order creation rule used here. This enables you to have the
system determine a special work center for packing, depending on the route, for example.

Replenishment Control

Use

You use replenishment control to fill up a picking area in accordance with the demand for products that you pick in this area.

The data can come from the following sources:

Slotting

Calculation of the minimum quantity and the maximum quantity as well as the minimum replenishment quantity at storage type
level or at fixed storage bin level

This is custom documentation. For more information, please visit SAP Help Portal. 61
 4/3/25, 7:52 PM
Open warehouse requests in accordance with selection

Manually entering the minimum and maximum quantity as well as the minimum replenishment quantity

Prerequisites

You have executed the following in Customizing under Extended Warehouse Management Internal Warehouse
Processes Replenishment Control Activate Replenishment Strategies in Storage Types:

You have activated the required replenishment strategy.

If you want to work with picker-directed replenishment, you have set the Pckr-Drvn Repl. indicator for direct
replenishment and have, optionally, restricted storage types.

If the system is to automatically create a warehouse task when executing replenishment, you have set the WT
Immed. indicator. Otherwise, the system creates a warehouse request or changes an existing warehouse request.

You have defined a stock removal control indicator for the warehouse number in Customizing under Extended Warehouse
Management Goods Issue Process Strategies Define Stock Removal Control Indicator.

You have defined tolerances and replenishment levels (fixed storage bin level or storage type level) in Customizing under
Extended Warehouse Management Master Data Define Storage Type. You have also defined the following:

If you want to work with replenishment at storage type level, you have defined the minimum quantity and the
maximum quantity in the warehouse product master.

If you want to work with replenishment at fixed storage bin level, you have defined fixed storage bins for your
products as well as a minimum and a maximum quantity for each bin in the master data for Extended Warehouse
Management under Storage Bin Assign Fixed Bins .

If the system is to round replenishment quantities, you have defined a minimum replenishment quantity in the warehouse product
master. You can only define the minimum replenishment quantity at storage type level, but the system can also use it at fixed
storage bin level.

You have defined a default stock type for replenishment in Customizing under Extended Warehouse Management
Master Data Define Warehouse Number Control.

Features

The following types of replenishment control are available:

Planned replenishment

You can start planned replenishment either interactively or in the background. The system calculates the replenishment in
accordance with the defined minimum quantity and maximum quantity. Replenishment control is triggered when the stock is less
than the minimum quantity. The system rounds down the replenishment quantity, in other words, the quantity of the warehouse
task or the warehouse request, to a multiple of the minimum replenishment quantity.

Order-related replenishment

You can start order-related replenishment either interactively or in the background. The system calculates the replenishment in
accordance with the quantity of the selected open warehouse requests. Replenishment control is triggered when the stock is less
than the required quantity. The system rounds up the replenishment quantity to a multiple of the minimum replenishment quantity.
The maximum quantity can be exceeded.

Order-related replenishment takes the requested batches of open delivery orders into account when performing the
replenishment.

This is custom documentation. For more information, please visit SAP Help Portal. 62
 4/3/25, 7:52 PM
Automatic replenishment

The system starts automatic replenishment in the background when you confirm a warehouse task. It calculates the replenishment
in accordance with the maximum and minimum quantity. Replenishment control is triggered when the stock is less than the
minimum quantity. The system rounds down the replenishment quantity to a multiple of the minimum replenishment quantity.

Direct replenishment

Direct replenishment is only possible in fixed storage bin scenarios. It is started during a bin denial when an exception code refers
to the internal process code Replenishment . The system calculates the replenishment in accordance with the maximum and
minimum quantity. Here it assumes that the quantity at the storage bin is zero. The system rounds down the replenishment
quantity to a multiple of the minimum replenishment quantity.

Direct replenishment can be performed by the picker (picker-directed replenishment). In this case, a warehouse task is displayed
for the replenishment as the next item to be processed in the picker's warehouse order. As a prerequisite, the system must have
found stock in the permitted storage types. Picker-directed replenishment is only possible in radio frequency scenarios.

 Recommendation
We recommend that you use picker-directed replenishment if the reserve storage area is situated close to the picking area.

Activities

To start planned replenishment or order-related replenishment, on the launchpad, choose Extended Warehouse Management
Work Scheduling Replenish Stock.

Handling Differences When Picking for Warehouse Request

Use

When you confirm a warehouse task, you can get differences between the product quantity requested and the product quantity
available.

 Example
According to the warehouse task for a warehouse request, you are to pick 50 pieces of the product PROD-01 from the storage
bin 02-03-44. However, you find only 45 pieces of the product in the storage bin. You confirm the warehouse task with a
difference of 5 pieces.

Process

You use the following procedure to remove a product from stock:

1. You pick a quantity smaller than the quantity specified on the corresponding warehouse task.

2. You record the quantity difference in the warehouse task by entering the quantity you have actually picked.

3. You confirm the warehouse task difference.

EWM updates the quantity to be picked in the warehouse request.

4. You decide how to proceed as follows:

You pick again for the warehouse request.

This is custom documentation. For more information, please visit SAP Help Portal. 63
 4/3/25, 7:52 PM
You create a further warehouse task for the warehouse request.

After you have confirmed the further warehouse task for the warehouse request, the picking for the
warehouse request is closed completely.

You do not pick again for the warehouse request.

The system uses Adjust Delivery Quantity to equate the delivery quantity with the picked quantity. Through this
adjustment, the pick status changes from Partially Completed to Completed. You can post the delivery for goods
issue.

Result

The warehouse request is completely picked. You can post the goods issue for the warehouse request.

Pickup and Account Assignment

Use

Extended Warehouse Management (EWM) supports goods issue for the pickup. Goods issue for the pickup can be planned or
unplanned.

Integration

If you work with a planned pickup, you generate an outbound delivery in shipping in the Logistics Execution area. Shipping sends
this to EWM. EWM generates a corresponding outbound delivery order. This contains the account assignment information from the
outbound delivery in shipping. You cannot change this account assignment information in EWM.

If you work with an unplanned pickup, you generate a direct outbound delivery order in EWM. EWM transmits this to shipping.
Shipping generates a corresponding outbound delivery that contains the account assignment information from EWM. You can
change the account assignment information in EWM. For more information about direct outbound delivery orders, see direct
outbound delivery order.

You can assign one or more account assignments to a delivery item. When you post goods issue for an outbound delivery with an
account assignment, the product is consumed, and the consumption of the product is debited to this account assignment.

Prerequisites

You have defined the account assignment categories in Customizing for EWM.

If you want to use a particular account assignment category for planned or unplanned goods issues with accounts assigned
in a warehouse number, you have assigned this to a warehouse number. For more information, see Customizing for
Extended Warehouse Management under Goods Issue Process Outbound Delivery Define Account Assignment
Category and Allow in Warehouse Number .

You can also perform planned goods issues with account assignment without setting up account assignment categories. In
this case, the outbound delivery in shipping contains the account assignment information, and the system debits the
account assignment during goods issue.

If you are using decentralized EWM and you want to work with unplanned goods issues, you have retrieved the data of the
relevant account assignment object from the enterprise management system. In the launchpad, choose Extended
Warehouse Management Interfaces ERP Integration Administration of Account Assignment Data .

You have defined a process profile for the pickup in Customizing for EWM.

This is custom documentation. For more information, please visit SAP Help Portal. 64
 4/3/25, 7:52 PM
For more information, see Customizing for Extended Warehouse Management under Cross-Process Settings Delivery
Processing Process Management and Control .

You have defined a status profile for the pickup in Customizing for EWM.

For more information, see Customizing for Extended Warehouse Management under Cross-Process Settings Delivery
Processing Status Management Define Status Profiles .

You have assigned the process profile for the pickup to a document type in Customizing for EWM.

For more information, see Customizing for Extended Warehouse Management under Goods Issue Process Outbound
Delivery Define Document Types for Outbound Delivery Process .

In Customizing for EWM, you have defined your own document and item types for each of your processes, for example,
document type OPIG Outbound delivery order for pickup and item type ODPG Standard item outbound delivery for
pickup.

In Customizing for EWM, you have defined the used document type as relevant for the pickup, in the process profile.

For more information, see Customizing for Extended Warehouse Management under Cross-Process Settings Delivery
Processing Process Management and Control Define Process Profile for Delivery Document Header . EWM only
shows you the documents of the used document types in the input help for direct sales and for goods issue with account
assignment.

For more information, see the documentation for Business Configuration Set (BC Set) /SCWM/DLV_OUTBOUND_DIRODO_1 and
/SCWM/DLV_OUTBOUND_DIRODO_2. On the launchpad, choose Tools Customizing Business Configuration Sets Display
and Maintain BC Sets .

Features
Unplanned pickup

You can create, change, or delete the account assignment information in unplanned outbound delivery orders for the pickup
until goods issue has been posted.

When you create or change a direct outbound delivery order, EWM performs a validation and displays any warning
messages accordingly. The validation checks the type of account assignment category and its uniqueness for each delivery
item. It also checks the type of the existing account assignment object. If you are using more than one account assignment
object for a delivery item, only one account assignment object is permitted to be non-statistical. This is to avoid a duplicate
allocation. The account assignment object always refers to the complete delivery quantity of a delivery item. It does not
consider partial quantities.

Planned pickup

You cannot create, change, or delete the account assignment data in planned outbound delivery orders for the pickup.

To provide you with information, EWM performs a validation when it creates an outbound delivery order. The validation
checks the type of account assignment category and its uniqueness for each delivery item.

If you are using decentralized EWM, you can use the Administration of Account Assignment Data report to request
account assignment data from the enterprise management system periodically.

You can use Business Add-In (BAdI) BAdI: Validation of Account Assignment Data of Delivery Item to implement
additional checks. For more information, see Customizing for Extended Warehouse Management under Business Add-
Ins (BAdIs) for Extended Warehouse Management Cross-Process Settings Delivery Processing Validation Within
Delivery BAdI: Validation of Account Assignment Data of Delivery Item .

EWM prints out the account assignment data on the delivery note (Printing Delivery Notes).

This is custom documentation. For more information, please visit SAP Help Portal. 65
 4/3/25, 7:52 PM
You can specify the print profile to influence the printer selection. On the launchpad, choose Extended Warehouse
Management Delivery Processing Outbound Delivery Outbound Delivery Orders - Pickup . Choose with the
quick info Default Values, and specify a print profile. For more information, see Printer Determination in Delivery Processing
and Print Profile Determination for Invoice Printout.

Activities

If you want to generate or edit direct outbound delivery orders for the pickup, on the launchpad, choose Extended
Warehouse Management Delivery Processing Outbound Delivery Outbound Delivery Orders - Pickup .

If you want to check the account assignment category for a pickup outbound delivery order on the user interface for the
outbound delivery order, on the launchpad, choose Extended Warehouse Management Delivery Processing
Outbound Delivery Outbound Delivery Orders - Pickup . Display a delivery document. Select a delivery item and
choose Expand/Enlarge. EWM displays the details of the item. On the Account Assignments tab page, EWM displays the
account assignment category, for example, cost center, and the account assignment object, for example, 10000.

 Note
If you want to display all outbound delivery orders, not just those that have been marked as relevant for the pickup, you
can use the transaction Outbound Delivery Orders (/SCWM/PRDO). The relevance for pickup is defined in the document
type, for example, OPIG.

Kit to Order

Purpose

With this process, you can have the system automatically assemble kits to order if there is no kitin stock.

The following rules apply to kits:

A kit is always delivered in full to a customer.

The kit header and the kit components are always scheduled for the same date.

All components of a kit must come from the same warehouse (this can be achieved by means of internal transfer between
warehouses).

Kit prices are always calculated at kit header level.

The kit header and kit component have a quantity ratio - defined by the kit structure -to each other. This quantity ratio is
recalculated as soon as there are changes at kit header level or at kit component level.

If the kit is in stock, the SPM goods issue process takes place.

For more information about the SPM Goods Issue Process , see the SAP Library for SAP ECC under Logistics Logistics -
General (LO) SAP Service Parts Management (LO-SPM) Goods Issue Process.

For more information about kit to stock, see Kit to Stock .

Prerequisites

You are using the following systems:

SAP CRM 5.0

This is custom documentation. For more information, please visit SAP Help Portal. 66
 4/3/25, 7:52 PM
For more information, see the SAP Library for mySAP Customer Relationship Management under Components and
Functions Availability Check Availability Check using SAP APO Additional ATP Functions in Service Parts
Management Kits in the Sales Order.

SAP ECC 6.0

For more information about the required Customizing settings, see the SAP Library for SAP ECC under Logistics
Logistics - General (LO) SAP Service Parts Management (SPM) Goods Issue Process Kit to Order Customizing
Settings.

SAP SCM 5.0

Extended Warehouse Management (EWM):

For more information about the required Customizing settings, see the Implementation Guide (IMG) for SCM under
Extended Warehouse Management Goods Issue Process Make Settings forKitting .

Advanced Planning and Optimization (APO):

For more information, see SAP Library for SAP Supply Chain Management (SAP SCM) underSAP Advanced
Planning and Optimization (SAP APO) Global Available-to-Promise (Global ATP) Check Methods Connection
to Production Availability Check for Kits .

Process

1. You create a sales order (SAP CRM)

a. The system triggers the rule-based ATP check in SAP SCM for a requirement from the sales order. The system
determines one or more rules with substitutions. One of the substitutions is a kit.

This is custom documentation. For more information, please visit SAP Help Portal. 67
 4/3/25, 7:52 PM
b. A requirement for a kit originates as an input product from the sales order. The system then triggers the ATP check
in SAP SCM .

c. The system initiates the credit check in SAP ECC.

d. The system performs the price determination and checks for the sales order, as well as checks for foreign trade
determination.

e. The system transfers the data from the sales order to SAP ECC.

For more information about editing sales orders, see the SAP Library for mySAP Customer Relationship
Management under Components and Functions Process Sales Orders .

2. The system performs an ATP check and confirms quantities (SAP SCM-APO)

The system checks whether the kit is in stock. If the kit is not in stock, the production that is activated in the validation rule
creates a kit structure that contains the kit components that the system requires to assemble the kit. The system then
performs the ATP check for the kit components and confirms the quantities for the sales order.

3. The system creates an unchecked delivery (SAP ECC-SPM) without creating an order.

For more information, see the SAP Library for SAP ECC under Logistics Logistics - General (LO) SAP Service Parts
Management (SPM) Goods Issue Process Creation and Update of Unchecked Deliveries.

4. You convert the unchecked delivery to a checked delivery (SAP ECC-SPM).

For more information, see the SAP Library for SAP ECC under Logistics Logistics - General (LO) SAP Service Parts
Management (SPM) Goods Issue Process Conversion of Unchecked to Checked Deliveries.

5. The system performs another ATP check for the various kit components and confirms the quantities from the checked
delivery (SAP SCM-APO)

For more information, see SAP Library for SAP Supply Chain Management (SAP SCM) underSAP Advanced Planning
and Optimization (SAP APO) Global Available-to-Promise (Global ATP) Check Methods Connection to Production
Availability Check for Kits .

6. EWM creates a warehouse request for the outbound delivery (SAP SCM-EWM).

When it receives notification from SAP ECC, EWM uses the checked delivery to automatically create an outbound delivery
order, that is, a warehouse request for an outbound delivery.

For more information, see Generating a Warehouse Request of Type Outbound Delivery Order .

7. You pick the outbound delivery order (SAP SCM-EWM).

For more information, see Generating a Warehouse Request of Type Outbound Delivery Order .

8. The system changes/confirms the outbound delivery (SAP ECC-SPM)

The system changes the delivery if quantity shortages are reported by EWM and then confirms the delivery.

The system confirms the delivery if exact delivery fulfillment is reported by EWM.

For more information, see the SAP Library for SAP ECC under Logistics Logistics - General (LO) SAP Service
Parts Management (SPM) Goods Issue Process Processing of Checked Deliveries.

9. The system posts the goods issue for the kits (SAP ECC-SPM).

For more information about posting goods issue, see the SAP Library for SAP ECC under Logistics Logistics - General
(LO) SAP Service Parts Management (SPM) Goods Issue Process Transfer Posting for Kits.

10. The system clears ATP-confirmed quantities (SAP SCM-APO).

11. The system updates the stock (SAP SCM-APO).

This is custom documentation. For more information, please visit SAP Help Portal. 68
 4/3/25, 7:52 PM
12. The system updates the data in the sales order (SAP CRM).

For more information about editing sales orders, see the SAP Library for mySAP Customer Relationship Management under
Components and Functions Process Sales Orders .

13. The system executes billing (SAP CRM).

Kit

Definition

Describes a piece list that you always deliver in a complete and assembled form.

Use

Extended Warehouse Management (EWM) does not save the kits as master data, instead it receives the information about the
structure of a kit in the form of items of an outbound delivery from the ERP system (see also Kit in the Warehouse Request for the
Outbound Delivery Order ). You can use the structure containing the kit in the outbound delivery in combination with a packaging
specification as a basis for assembling or producing a kit in EWM.

Structure
A kit can consist of the following levels:

Kit header

Kit component

Replaced kit component(optional)

 Note
EWM does not support nested kits, that is, kits in kits.

Integration

EWM supports kits in the kit to order process.

Kitting at a Work Center with a VAS Order

Purpose
You can use this process to create a kit with a value-added service order (VAS order). This provides you with the following VAS
order options:

Working with a special kitting work center

Automatic determination of the kitting work center

Documentation about efforts and status tracking for kitting

This is custom documentation. For more information, please visit SAP Help Portal. 69
 4/3/25, 7:52 PM
Integrating VAS processing into the delivery

You can use an indicator for the item type of the kit header to make the system generate an item for the kit header in the pick-
handling unit (pick-HU). You can print out this HU item in a HU list, display it in the packing transaction, and confirm it to the ERP
system.

In EWM, a kitting instruction can exist in one of the following forms:

As free text from the SAP Customer Relationship Management sales order that forms the basis for the outbound delivery.

As free text that you have created in the warehouse request in EWM.

You can display this text in the work center as additional information.

Prerequisites

You have made all the required settings for kitting in Customizing. For more information, see the Implementation Guide (IMG) for
Extended Warehouse Management (EWM) under Goods Issue Process Make Settings for Kitting.

An outbound delivery with kit items exists in EWM.

You have created a packaging specification for the product of the kit header item as master data, so that you can create a VAS
order. This packaging specification must have a level of the level type Kitting. If you are using process-oriented storage control, you
must assign the corresponding warehouse process step (such as KIT) of the warehouse process used to the kitting level (see also:
Process-Oriented Storage Control).

 Note
Note that a packaging specification (and therefore a VAS order) can only have one level of the type Kitting. You can assign a
packaging material to the kitting level as a proposal for packing the kit.

If the system is to automatically generate an HU item for the kit header in the pick-HU, set the Create Kit Item indicator in
Customizing. For more information about the packing profile, see the Implementation Guide (IMG) for Extended Warehouse
Management (EWM) under Goods Issue Process Outbound Delivery Define EWM-Specific Settings for Item Types.

Process

1. EWM receives an outbound delivery with kit component items from the ERP system.

2. Depending on your Customizing settings, either you manually create a VAS order or you have the system create one
automatically (see also: VAS Order for the Kit Header Item of the Warehouse Reqeust).

3. You generate warehouse tasks for the kit component items in EWM.

4. You pick the kit component into a pick-HU and confirm the warehouse tasks. The kit components are then at the kitting
work center.

If you have set the Create Kit Item indicator in Customizing and are working with pick-HUs, the system generates
the kit header item in the pick-HU. You can then use these items in the work center to repack the entire kit into
another HU.

If you have not set the Create Kit Item indicator in Customizing, you can generate the kit header item in the work
center manually.

5. You assemble the kit in accordance with the kitting instructions where required.

a. You can display the kitting instruction.

This is custom documentation. For more information, please visit SAP Help Portal. 70
 4/3/25, 7:52 PM
b. You can report the work progress in the VAS order.

6. You pack the kit into an HU and generate the HU item for the kit header.

If the ERP system is dependent on an HU item for the confirmation, and you have not set the Create Kit Item indicator in
Customizing, then you must generate the item manually after packing the kits in the work center at the latest. If a transfer posting
of the stock from the kit components to the kit header takes place in the ERP system when processing the goods issue
confirmation from EWM, the ERP system is dependent on this item (see also: Kit to Order).

1. You generate an HU warehouse task to transport the HU to the goods issue zone.

2. You confirm the HU warehouse task.

3. You then post the goods issue for the warehouse request.

If you have set the Create Kit Item indicator, the system uses this HU item in goods issue posting to check whether the
packed kits are complete, meaning the system can therefore post these kits for goods issue.

 Note
The system only performs this check if the indicator is set in the item type of the kit header.

This process allows you to use the following options:

Process-oriented storage control

Integrating the VAS order into storage control

Creating VAS orders based on a packaging specification

This enables you to provide additional steps in the warehouse process, such as loading.

You can also define your own warehouse process steps for packing kits into an HU, such as in the following instances:

If you are not performing this step during kitting, but as an additional step at the same work center.

If you are packing the kits into an HU at a different work center after kitting.

The decision as to whether you map additional steps as a step in the warehouse process only, or as a level of the packaging
specification as well, depends on whether you want to document this step in the VAS order. The system only generates a VAS
activity where you can report effort and consumption of the packaging material if you have mapped this step as a level of the
packaging specification.

Result

You can ship the kit.

VAS Order for the Kit Header Item of the Warehouse Request

Purpose

You can generate value-added service orders (VAS orders) automatically or manually in Extended Warehouse Management ( EWM
), to document and monitor these value-added services.

VAS orders that are generated for a kit header item have a special structure.

This is custom documentation. For more information, please visit SAP Help Portal. 71
 4/3/25, 7:52 PM

Prerequisites

You have made the required settings in Customizing for generating VAS orders automatically or manually. If you want to create a
VAS order for kit items in the delivery, make the settings for the item type of the kit header only. For more information, see the
Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings Value-Added Services
Define Relevance for VAS Order .

An outbound delivery with kit items exists in EWM.

You have defined a packaging specification with a level of type Kitting . Note that a packaging specification (and therefore a VAS
order) can only have one level of the type Kitting .

Process

Automatic Generation

1. You receive an outbound delivery with kit items from the ERP system.

2. EWM checks whether it is to generate a VAS order for the kit header item automatically, and generates it where appropriate.

3. EWM saves the number of the VAS order as a document flow for all kit items of the warehouse request.

4. If you have activated the VAS Order status in the status profile of the item type for the warehouse request item, EWM sets
the VAS Order status of the kit items to one of the following entries:

Generated

If you have defined in Customizing that EWM is to generate the VAS order automatically.

Not Relevant

If you have defined in Customizing that EWM is not to generate the VAS order automatically.

Manual Generation

1. You receive an outbound delivery with kit items from the ERP system.

2. You create a VAS order for the kit header item manually (see also: Create and Edit VAS Orders ).

3. EWM creates the VAS order. When you save the VAS order, EWM saves the number of the VAS order as a document flow for
all kit items of the warehouse request.

4. If you have activated the VAS Order status in the status profile of the item type for the warehouse request item, EWM sets
the VAS Order status of the kit items to Generated .

Result

The system has created a VAS order for the kit header. You can use this VAS order for confirming services in the process Kitting at a
Work Center with a VAS Order .

When you edit the VAS order, EWM changes the VAS Order status of the warehouse request item (see also: Updating the
Warehouse Request Using the VAS Order ).

The VAS order for the kit header has the following special features. For example, you have defined a packaging specification with
the levels Oiling , Kitting , and Packing . The VAS order for the kit header has the following special features:

All activities prior to the kitting activity (such as oiling) and the kitting activity itself have kit component items of the
delivery as their items. This is based on the assumption that you perform all activities prior to assembling the kits and the

This is custom documentation. For more information, please visit SAP Help Portal. 72
 4/3/25, 7:52 PM
kitting activity itself in the kit components.

All activities after the kitting activity (such as packing) have the kit header item as their item. This is based on the
assumption that you perform all activities after assembling the kits in the kit itself.

Kitting at a Work Center Without a VAS Order

Purpose

You can use this process in Extended Warehouse Management (EWM) to create a kit without a value-added service order (VAS
order). Here you can configure a work center where you also pack in such a way that you can confirm generated kits there. This
process is suitable for the following cases:

You do not require detailed documentation of the kitting procedure in EWM.

You are not performing kitting in one special kitting work center, but at a work center where you are also packing.

You can only find information about kitting in the information for the kit in the outbound delivery and in the kitting instruction that
may exist in the form of free text for the warehouse request item of the kit.

You can use an indicator for the item type of the kit header to make the system generate an item for the kit header in the pick-
handling unit (pick-HU). You can print out this HU item in an HU list, display it in the packing transaction, and confirm it to the ERP
system.

In EWM, a kitting instruction can exist in one of the following forms:

As free text from the SAP Customer Relationship Management sales order that forms the basis for the outbound delivery.

As free text that you have created in the warehouse request in EWM.

You can display this text in the work center as additional information.

Prerequisites
You have made all the required settings for kitting in Customizing. For more information, see the Implementation Guide (IMG) for
Extended Warehouse Management (EWM) under Goods Issue Process Make Settings for Kitting.

An outbound delivery with kit items exists in EWM .

If the system is to automatically generate an HU item for the kit header in the pick-HU, set the Create Kit Item indicator in
Customizing . For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under
Goods Issue Process Outbound Delivery Define EWM-Specific Settings for Item Types.

Process

1. EWM receives an outbound delivery with kit component items from the ERP system.

2. You generate warehouse tasks for the kit component items.

3. You pick the kit components into a pick-HU and confirm the warehouse tasks. The kit component items are then in the
packing work center.

If you have set the Create Kit Item indicator in Customizing and are working with pick-HUs, the system generates
the kit header item in the pick-HU. You can then repack these items into other HUs in the work center.

This is custom documentation. For more information, please visit SAP Help Portal. 73
 4/3/25, 7:52 PM
If you have not set the Create Kit Item indicator in Customizing, you can generate the kit header item in the work
center manually.

4. You assemble the kit in the packing work center.

5. You pack the kit into an HU and generate the HU item for the kit header.

6. You generate an HU warehouse task to transport the HU to the goods issue zone.

7. You confirm the HU warehouse task.

8. You then post the goods issue for the warehouse request.

If you have set the Create Kit Item indicator, the system uses this HU item in goods issue posting to check whether the
packed kits are complete, and therefore whether the system can post goods issue for these kits.

 Note
The system only performs this check if the indicator is set in the item type of the kit header.

If the ERP system is dependent on an HU item for the confirmation, and you have not set the Create Kit Item indicator in
Customizing, you must generate the item manually after packing the kits in the work center at the latest. If a transfer
posting of the stock from the kit components to the kit header takes place in the ERP system when processing the
goods issue confirmation from EWM, the ERP system is dependent on this item (see also: Kit to Order ).

Result

You can ship the kit.

Kitting During Picking Without a VAS Order

Purpose

You can use this process in Extended Warehouse Management (EWM) to create a kit during picking. This process is suitable for the
following cases:

You do not require detailed documentation of the kitting procedure in EWM.

You assemble the kits during picking, that is, you do not perform kitting at special work centers.

You can only find information about kitting in the information for the kit in the outbound delivery and in the kitting instruction that
may exist in the form of free text for the warehouse request item of the kit header.

You can use an indicator for the item type of the kit header to make the system generate an item for the kit header in the pick-
handling unit (pick-HU). You can print out this HU item in an HU list, display it in the packing transaction, and confirm it to the ERP
system.

In EWM, a kitting instruction can exist in one of the following forms:

As free text from the SAP Customer Relationship Management sales order that forms the basis for the outbound delivery.

As free text that you have created in the warehouse request in EWM.

You can display this text in the work center as additional information.

This is custom documentation. For more information, please visit SAP Help Portal. 74
 4/3/25, 7:52 PM

Prerequisites

You have made all the required settings for kitting in Customizing. For more information, see the Implementation Guide (IMG) for
Extended Warehouse Management under Goods Issue Process Make Settings for Kitting.

An outbound delivery with kit items exists in EWM.

If the system is to automatically generate an HU item for the kit header in the pick-HU, set the Create Kit Item indicator in
Customizing . For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under
Goods Issue Process Outbound Delivery Define EWM-Specific Settings for Item Types.

 Note
If the ERP system is dependent on an HU item for the kit header in the confirmation of goods issue, you must make this setting.

If a transfer posting of the stock from the kit components to the kit header takes place in the ERP system when processing the
goods issue confirmation from EWM, the ERP system is dependent on this item (see also: Kit to Order ).

Process

1. EWM receives an outbound delivery with kit component items from the ERP system.

2. You generate warehouse tasks for the kit component items.

3. You pick the kit components and assemble the kit, where required in accordance with the kitting instruction.

4. You confirm the warehouse tasks.

If you have set the Create Kit Item indicator in Customizing and are working with pick-HUs, the system generates the kit
header item in the pick-HU. You can then repack these items into other HUs in the work center.

5. You then post the goods issue for the warehouse request.

If you have set the Create Kit Item indicator, the system uses this HU item in goods issue posting to check whether the
packed kits are complete, and therefore whether the system can post goods issue for these kits.

 Note
The system only performs this check if the indicator is set in the item type of the kit header.

Results
You can ship the kit.

Packing at the Work Center

Use

At a work center, you can pack and unpack products into handling units (HU), and HUs into other HUs using the Pack Handling
Units - Advanced and Deconsolidate Handling Units apps. On the initial screen, you select your warehouse number and work
center. You can set filters, including storage bin, HU, or delivery, enabling you to optimize your worklist.

If you use a mouse, you can use simple drag and drop on the left-hand side of the screen to repack entire HUs, or to pack products
into other HUs. You can use a keyboard or a scanner - provided the necessary information is available as a bar code - for the same

This is custom documentation. For more information, please visit SAP Help Portal. 75
 4/3/25, 7:52 PM
purpose in the tabs on the upper right-hand side of the screen.

If your warehouse has enabled the order reduction function, and you scan a canceled product, a message informs you that you
should exclude this product from the outbound process. For more information, see Order Reduction.

You can assign scales that are connected to your work center to transmit the exact weight to the SAP system. You can also assign a
printer for printing HU documents.

You can upload, read, update, or delete attachments to HUs, for example, photos or documents in various file formats or URLs, in
the Pack Handling Units - Advanced app or the Deconsolidate Handling Units app. For more information about using attachments
with HUs, see Attachments.

For information about other available functions at a work center, see Work Center, Kitting at a Work Center with a VAS Order, and
Kitting at a Work Center Without a VAS Order.

Prerequisites

You have made the following settings in Customizing and on the launchpad:

In Customizing, you have created a work center layout and assigned this layout to the work center. You can configure the
packing transactions so that the user only sees the relevant tab pages for packing.

Optionally, you have added a tab page for HU attachments to your work center layout.

For more information, see Customizing for Extended Warehouse Management under Master Data Work Center
Specify Work Center Layout .

In Customizing, you have specified additional information about your work center, for example, which warehouse process
type is used for packing. For more information, see Customizing for Extended Warehouse Management under Master
Data Work Center Define Work Center .

On the launchpad, you have specified which storage bin is assigned to which work center. To do so, choose Extended
Warehouse Management Master Data Work Center Define Work Center Master Data (/SCWM/TWORKST).

Optionally, you have assigned a work center to your terminal so that during packing, the system automatically fills in the
correct warehouse number and your work center. On the launchpad, choose Extended Warehouse Management Master
Data Work Center Define Work Center Master Data (/SCWM/TWORKST).

Optionally, you have assigned scales that are connected with your work center. On the launchpad, choose Extended
Warehouse Management Master Data Work Center Define Scales .

Features
The display is divided into the left and right screen areas. You use the left screen area mainly for navigation, and for quick repacking
of HUs and products using only the mouse. On the right screen area, you can edit or request detailed information about the storage
bins, HUs, products, and warehouse tasks.

When packing at a work center, you can scan the following:

HU identification

Stock identification

Serial number

Product

This is custom documentation. For more information, please visit SAP Help Portal. 76
 4/3/25, 7:52 PM
Warehouse task

Storage bin

You can use the scanned data to perform the following tasks:

Create HUs

Repack HUs

Repack products

Post differences

Change HUs

Deconsolidate HUs

Exclude products from packing

Repack canceled items

You can configure packing at the work center in such a way that the system copies over frequently required data as default values.
You can make these settings in the Control tab.

Activities

There are two packing transactions available for work centers. The input help is restricted, depending on the type of work center, to
the data you have configured in Customizing. You can access the packing transactions for work centers as follows:

1. On the launchpad, open the Pack Handling Units - Advanced app.

2. On the launchpad, open the Deconsolidate Handling Units app.

Enter your warehouse number and work center, if you have not already assigned a work center to your terminal. Further
filters are optional.

Packing Using Drag and Drop

In the area on the left, you can pack, unpack, or repack products or HUs by dragging and dropping them into the HU, storage bin, or
separate HU respectively.

To repack just a partial quantity of a product, carry out the following:

1. Double-click a higher-level node (HU or storage bin) in the area on the left.

2. Choose the Content tab page in the area on the lower right. All the product items of the HU or storage bin are now visible.

3. Enter the quantity that you want to repack in the Partial Quantity field and choose Enter .

4. Drag the item from the area on the right into the target HU or target storage bin in which you want to repack these partial
quantities. To do this, click any cell in this row that is not ready for input. Then drag and drop this cell in the target area.

Repacking Products Subject to Order Reduction

If you are in the Repack Product tab and you start processing a handling unit containing a canceled item, a message informs you of
the order reduction. If you decide to process the order reduction, the usual outbound process is stopped and the system cancels
picking so that the stock is released from the outbound delivery order item. The delivery quantity is reduced and the stock can be

This is custom documentation. For more information, please visit SAP Help Portal. 77
 4/3/25, 7:52 PM
put away again. You should pack the excess stock into a special handling unit and select Return Transfer. For more information, see
Pick Point.

If only some of the outbound delivery order item quantity is subject to order reduction, the process is split. Follow the process
described above for the reduced quantity, and follow the usual outbound process for the remaining, uncanceled quantity, meaning
it is shipped to the customer.

It is not mandatory to follow the order reduction process, as in certain situations it may not be desirable to reverse the outbound
process for an item. You can decide to continue packing and prepare to ship the item to the customer as normal.

Pack Outbound Deliveries

With this app, you can quickly pack products for outbound deliveries. In a warehouse, after picking, you want to pack products and
send them immediately to customers. To achieve this, you can use this app to improve your daily packing efficiency and minimize
human errors.

Key Features
You can use this app to:

Choose different packing modes on the first screen of the app - advanced packing mode or basic packing mode

Create and manage shipping handling units, for example, to change packaging materials

Propose up to six favorite packaging materials for the most frequently used materials

Pack serial number or batch-managed products in the advanced packing mode

Pack products based on sales order or project information

Use an asynchronous way to pack products for better system performance

For example, after packing the first product, you can directly continue to pack the next product without waiting for the
system to confirm the packing action.

Print delivery and handling unit-related documents

Handle exceptions, for example, you can exclude damaged products from packing

Get notifications when a customer cancels or changes an order during the packing

Use access codes to improve packing efficiency, for example, you can configure access codes for frequently used actions

In a separate process, you generate and print bar codes of the access codes for scanning.

Connect to a scale that reads the actual weight and transfers the exact weight to this app

Configure notification sounds for messages

Use a base unit of measure to enter a product quantity when there is an exception

For example, when you partially pack products into a shipping handling unit (HU).

Pack products from an HU, a storage bin, or an outbound delivery order

Additional Information
Packing Modes

This is custom documentation. For more information, please visit SAP Help Portal. 78
 4/3/25, 7:52 PM
The advanced packing mode provides, for example, more detailed product information, visualization of the weight of packed
products, and exception handling.

The basic packing mode provides a simpler and more interactive user interface design. However, you can use some features in the
advanced packing mode but not in the basic packing mode.

Note that you can't pack products from a nested HU.

For more information about a how-to guide, see 3004810 .

Supported Device Types

Desktop

How-To Videos

Pack Outbound Deliveries - How to Use the Basic Packing Mode

Open this video in a new window

Pack Outbound Deliveries - How to Use the Advanced Packing Mode

This is custom documentation. For more information, please visit SAP Help Portal. 79
 4/3/25, 7:52 PM

Open this video in a new window

Feature Comparison Documentation

For a comparison of the features offered by this app and other apps in the area of Extended Warehouse Management, see:

Feature Comparison for Packing

App Extensibility: Pack Outbound Deliveries

You can extend the Pack Outbound Deliveries app according to your business needs for different aspects.

Further Extensibility Entities

Custom Fields

You can create your own fields, using the Custom Fields app with the business context Warehousing: Pack Outbound Deliveries.

Business Add-Ins (BAdIs)

The following BAdIs are available for extensibility purposes:

BAdI: Retrieval of Product Picture URLs (/SCWM/EX_POD_MAT_PIC) in Customizing for Extended Warehouse
Management under Business Add-Ins (BAdIs) for Extended Warehouse Management Master Data Product

You can use this BAdI to retrieve a picture URL for a product. You can then, for example, enter a product and verify the
product with the picture.

BAdI: Notification Sounds for Messages (/SCWM/EX_PKODLV_MSG_AUDIO) in Customizing for Extended Warehouse
Management under Business Add-Ins (BAdIs) for Extended Warehouse Management Cross-Process Settings

You can use this BAdI to retrieve the audio URIs of the notification sounds for your messages.

Product Filtering and Value Retrieval for Custom Fields During Packing (/SCWM/EX_POD_FILTER_ITEMS)

You can use this BAdI to define your own logic to retrieve and filter products that are available for packing. You can also use
this BAdI to append values to the custom fields.

Action Validation During Packing (/SCWM/EX_POD_VALIDATE_ACTION)

You can use this BAdI to decide whether to continue with an action depending on the current packing status of an outbound
delivery order, a storage bin, or a handing unit.

Related Information
Custom Fields
Custom Logic
Pack Outbound Deliveries

This is custom documentation. For more information, please visit SAP Help Portal. 80
 4/3/25, 7:52 PM

Feature Comparison for Packing

The following table compares the features offered by various apps for packing. The column headings contain links to the app
documentation and the app's entry in the SAP Fiori apps reference library.

App Name Pack Handling Units - Pack Outbound Deliveries Pack Warehouse Stock
Advanced

App ID /SCWM/PACK F3193 F3738

Advanced Mode Basic Mode

Create handling units Yes

(HUs)

Repack HUs Yes No

Change HUs Yes No

Deconsolidate HUs for Yes No

putaway

Work with nested HUs Yes No

Cancellation of picking in Yes No

case of an order
reduction

Scan HU identification, Yes

products, or storage bins

Scan stock identification Yes No

or warehouse tasks

Scan delivery documents No Yes No

Use access codes to No Yes

trigger actions for most
frequently used
transactions

Scan and pack a single No Yes No

piece of an order

Pack using drag and Yes No

drop

Use the consolidation Yes No

group to find destination
HUs automatically

Highlight items belong to No Yes No

the same consolidation
group

Repack products for Yes

outbound deliveries

Repack products for Yes No Yes

putaway

This is custom documentation. For more information, please visit SAP Help Portal. 81
 4/3/25, 7:52 PM

App Name Pack Handling Units - Pack Outbound Deliveries Pack Warehouse Stock
Advanced

App ID /SCWM/PACK F3193 F3738

Advanced Mode Basic Mode

Repack products for Yes No Yes

internal movements

Exclude picked products Yes No

from packing

Repack partial quantities Yes

of a product

Repack products with Yes No Yes

serial numbers

The system Yes No

automatically proposes a
packaging material

Work with default and No Yes

favorite packaging
materials

Change the packaging No Yes

material of an HU

Use process-oriented Yes No

storage control

Work with products that Yes No

use catch weight

Assign serial numbers to Yes Yes (Only for products with a serial number requirement on document level)
products or delivery

Work with kits Yes No

Post differences Yes No Yes

Display the HUs in a Yes No

hierarchy, including open
warehouse tasks

Display and change HU Yes Some fields

header fields

Display an overview of Yes No

warehouse tasks created
for an HU

Display the hazardous Yes Supports the following:

substance text and text
Packing instructions
from the delivery for
stock items Handling instructions

Navigate to the delivery Yes No

from an HU or a stock

This is custom documentation. For more information, please visit SAP Help Portal. 82
 4/3/25, 7:52 PM

App Name Pack Handling Units - Pack Outbound Deliveries Pack Warehouse Stock
Advanced

App ID /SCWM/PACK F3193 F3738

Advanced Mode Basic Mode

item

Display details for stock Yes Some details

Import the weight of the Yes No Yes

delivery from a scale

Print forms Yes Using PPF only

Display image of product No Yes

Play a sound in the case No Yes

of entry errors

Related Information
Packing at the Work Center

Scrapping

Purpose
In your warehouse you sometimes find products that are damaged, or that are unusable for some other reason. You often notice
this, for example, during picking or physical inventory. Since you cannot normally sell these products on, you have to scrap them.

You can use this process to create posting change notices for scrapping, and can remove these products from stock and post
goods issue as usual.

Prerequisites
You have defined the following different document types for the posting change process, so that you can begin the
scrapping process:

Document type for scrapping the entire quantity of a product

Document type for scrapping the entire quantity of a product except for a fixed remaining quantity

Document type for scrapping a partial quantity of a product

For more information, see Customizing for Extended Warehouse Management under Internal Warehouse Processes
Delivery Processing Posting Changes Define Document Types for Posting Change Process .

You have defined the warehouse process types for scrapping, in which you enter the work center for scrapping as the
destination storage bin.

For more information, see Customizing for Extended Warehouse Management under Cross-Process Settings
Warehouse Task Define Warehouse Process Type .

You have defined the stock removal strategies for determining the stock to be scrapped.

This is custom documentation. For more information, please visit SAP Help Portal. 83
 4/3/25, 7:52 PM
For more information, see Customizing for Extended Warehouse Managements under Goods Receipt Process
Strategies .

You have defined the work center for scrapping, where you can pack the products to be scrapped together into a collection
container.

For more information, see Customizing for Extended Warehouse Managements under Master Data Work Center .

You have defined a non-picking-relevant document type and item type for the outbound delivery of the scrapping container.

For more information, see Customizing for Extended Warehouse Management under Goods Issue Process Outbound
Delivery Define Document Types for Outbound Delivery Process and Define Item Types for Outbound Delivery
Process.

Process
1. Create the posting change notice for scrapping.

For the entire quantity of a product

For the entire quantity of a product except for a fixed remaining quantity

For a partial quantity of a product (unsaleable or damaged products in the warehouse)

2. Create a warehouse task for scrapping with reference to the posting change notice

3. You can use a stock removal strategy to determine the stock to be scrapped.

You can use different stock removal strategies for the entire quantity of a product and for the entire quantity of a product
except for a fixed remaining quantity.

4. Remove the products to scrap from stock.

You pick these products and confirm the warehouse tasks to the work center for scrapping.

5. You use the packing transaction to pack the products to scrap, and to construct handling units.

6. Use the handling units to create a non-picking-relevant outbound delivery.

7. Post the goods issue for the outbound delivery.

Manage Physical Stock - Products

App ID: F5340

With this app, you can search for and display physical stock that’s in storage bins, listed by product. You can post unplanned goods
issue for consumption and scrapping.

Key Features

You can use this app to do the following:

Use the Search field to search for physical stock by product, product description, or storage bin.

Search for physical stock using various selection criteria, such as product, or handling unit.

Display physical stock in a list.

For products serialized in Inventory Management, display the serial numbers assigned to the physical stock.

This is custom documentation. For more information, please visit SAP Help Portal. 84
 4/3/25, 7:52 PM
Post unplanned goods issue to consume or scrap stock.

Post the goods issue for one stock item or several stock items at the same time.

Post the goods issue for the total quantity or for partial quantities.

Enter account assignments for the goods issue.

Enter a reason for movement for the goods issue.

Add a short text to the goods issue.

For products serialized in Inventory Management, select serial numbers during consumption or scrapping.

For products serialized on warehouse number level, enter serial numbers during consumption or scrapping.

Navigate from the list of physical stock to a detail view to see details for a single stock item.

Navigate to the Manage Warehouse Documents app.

Navigate to other apps for more information about products and storage bins.

Additional Information

You can't use Manage Physical Stock - Products to work with valuation units.

The Special Reference Stock Type filter allows you to filter for sales order stock or project stock only. If you want to filter by work-
in-process (WIP) stock or products, enter the WIP number in the WIP Number filter.

You can display the warehouse documents posted with Manage Physical Stock - Products in the Manage Warehouse Documents
app.

You can also post unplanned consumption or scrapping in the Post Goods Issue – Unplanned app.

You can cancel warehouse documents posted with Manage Physical Stock - Products in Post Goods Issue – Unplanned and
Manage Warehouse Documents. You can cancel warehouse document items in warehouse documents posted with Manage
Physical Stocks - Products in Manage Warehouse Documents.

Supported Device Types

Desktop

Tablet

Feature Comparison Documentation

For a comparison of the features offered by this app and other apps in the area of unplanned goods issue, see Feature Comparison
for Posting Unplanned Goods Issue.

Related Information
Prerequisites for Using Reasons for Movement in Manage Physical Stock - Products and Manage Warehouse Documents
Manage Warehouse Documents
Posting of Unplanned Goods Issue

This is custom documentation. For more information, please visit SAP Help Portal. 85
 4/3/25, 7:52 PM

Prerequisites for Using Reasons for Movement in Manage

Physical Stock - Products and Manage Warehouse Documents
How to configure reasons for movement for the unplanned goods issue.

If you want to use reasons for movement in the Manage Physical Stock - Product or Manage Warehouse Documents apps, you
need to define the reasons for movement, and map the reason codes from Inventory Management to reasons for movement in
Extended Warehouse Management (EWM).

You define the reasons for movement in Customizing for Extended Warehouse Management under Cross-Process
Settings Warehouse Task Define Reasons for Warehouse Movements .

You map the Inventory Management reason codes to reasons for movement in Customizing for Extended Warehouse
Management under Interfaces ERP Integration Goods Movements Map EWM Reason Code to ERP Reason for
Movement .

You create reason codes for Inventory Management in Customizing for Materials Management under Inventory
Management and Physical Inventory Movement Types Record Reason for Goods Movements .

Posting of Unplanned Goods Issue

You can post goods issue for products you want to remove from stock where you did not plan the goods issue and do not have a
reference to outbound delivery orders in Extended Warehouse Management (EWM).

The following goods issue processes are available:

Scrapping

Scrap stock from the scrap zone or directly from any other storage bin in the warehouse without using outbound delivery
orders. You can use an account assignment for the scrapped stock. The goods issue is posted with movement type 551 in
Inventory Management.

Sampling

Post goods issue for sampling purposes without using quality management functions. The sample is destructive, that is, the
goods issue has the same effect as scrapping. You can use an account assignment for the sample. The goods issue is
posted with movement type 333 in Inventory Management.

Stock Correction

Post goods issue due to a stock loss without using physical inventory functions. You can also post a goods receipt due to a
stock gain by entering a negative quantity. This process is available for existing stock only, that is, you cannot create new
quants. The stock correction is posted with movement type 711- 716 in Inventory Management. In Inventory Management
a physical inventory document can be created automatically with the stock correction.

Storage Location

Transfer stock to an Inventory Management storage location not managed by EWM without using outbound delivery orders.
In the case of normal unrestricted-used stock, the goods issue is posted with movement type 411 in Inventory
Management. For other stock types, stock with stock usage, and for sales order stock or project stock, other movement
types are used. The plant of the storage location is determined by the party entitled to dispose.

Consumption

Post goods issue with an account assignment, for example, a cost center, an order, or a WBS element, directly from any
storage bin in the warehouse without using outbound delivery orders. The goods issue is posted with movement types 201,

This is custom documentation. For more information, please visit SAP Help Portal. 86
 4/3/25, 7:52 PM
261, or 291 in Inventory Management.

You can cancel some goods movement documents with the following processes:

Cancel GI Documents

Cancel documents created during the goods issue processes in this app.

Cancel Stock Migration

Cancel documents created by uploads during stock data transfer.

For more information, see Initial Stock Data Transfer.

 Note
An unplanned goods issue can be performed even if you have selected the No GI checkbox in the storage type settings, because
the unplanned goods issue is not an outbound delivery process. For more information, see Customizing for Extended
Warehouse Management under Master Data Define Storage Type .

You can implement checks during unplanned goods issue by using the Business Add-In BAdI: Stock Checks for Goods
Movements. For more information, see Customizing for Extended Warehouse Management under Business Add-Ins (BAdIs) for
Extended Warehouse Management Cross-Process Settings Goods Movement Postings BAdI: Stock Checks for Goods
Movements .

Features
Selection

You can use two different display modes to display the stock: a stock list and a handling unit (HU) list.

If you choose the display mode Display Stock List, enter the location data, product data or HU data to select the stock.

If you choose the display mode Display HU List, enter the location data or the HU data to select the HUs.

In the Processing selection area, select the goods issue process you want to use. For the goods issue process Storage Location,
also enter a storage location. For the goods issue process Cancel GI Documents, also enter the document numbers. For the goods
issue processes Scrapping, Sampling, and Consumption, you can also enter an account assignment.

Using the Post GM Immediately checkbox, you can plan a background job for report /SCWM/RGI_SCRAP (for example, to empty
the scrap zone regularly).

Output

The system displays the quantity that was already posted the Posted Quantity column. On the HU list, the quantity is 1 if the goods
issue was posted for a specific HU.

For the GI process Cancel GI Documents, no list is displayed. The documents are canceled immediately.

Application Log

Depending on the settings of the subobject GI_SCRAP, the system creates an application log for the goods issue. On the
launchpad, choose Extended Warehouse Management Settings Activate Application Log .

Activities

This is custom documentation. For more information, please visit SAP Help Portal. 87
 4/3/25, 7:52 PM
On the launchpad, choose Extended Warehouse Management Execution Post Goods Issue - Unplanned .

From the stock list, you can perform the following functions:

Display a serial number list for a selected line, for products with serial number management.

You can select one or more serial numbers on the serial number list and post a goods issue.

Post goods issue for the total quantity of the selected stock.

Post goods issue for a partial quantity of the selected stock.

A dialog box appears for you to enter a quantity.

From the HU list, you can perform the following activities:

Display a stock list for a selected HU.

You can post a goods issue from the stock list too.

Post goods issue for the HU content.

If you post goods issue for the total contents of the HU, the empty HU can be deleted automatically, depending on the
packaging material type. Note that the HU data is not communicated by the goods movement interface to Inventory
Management.

Feature Comparison for Posting Unplanned Goods Issue

The following table compares the features offered by various apps for posting goods issue without an outbound delivery order. The
column headings contain links to the app documentation and the app's entry in the SAP Fiori apps reference library.

App Name Manage Physical Stock - Manage Warehouse Post Unplanned Goods Issue
Products Documents

App ID F5340 F5341 /SCWM/ADGI

Display physical stock listed by Yes No Yes

product

Scrap stock Yes No Yes

Post goods issue for sample No No Yes

stock

Correct stock for a stock loss No No Yes

without performing a full
physical inventory

Transfer stock to a storage No No Yes

location not managed by
Warehouse Management

Cancel goods issue documents No Yes Yes

one at a time

Cancel multiple goods issue No No Yes

documents together

Cancel stock migration No Yes Yes

This is custom documentation. For more information, please visit SAP Help Portal. 88
 4/3/25, 7:52 PM

App Name Manage Physical Stock - Manage Warehouse Post Unplanned Goods Issue
Products Documents

App ID F5340 F5341 /SCWM/ADGI

Cancel warehouse document No Yes No

items

Consume stock Yes No Yes

Work with batch-managed Yes No Yes

products

Work with serialized products Yes No Yes

Work with valuation units No No Yes

Post goods issue of partial Yes No Yes

quantities for a single stock
item

Post goods issue of partial Yes No No

quantities for multiple stock
items at the same time

Post goods issue of total Yes No Yes

quantities

Post goods issue of partial Yes No No

quantities and total quantities
at the same time

Post goods issue with account Yes No Yes

assignments

Post goods issue with reasons Yes No Yes

for movement

Add short text to goods Yes Yes Yes

movement

Schedule goods issue in the No Yes

background

Display physical stock listed by No No Yes

handling unit (HU)

Post goods issue for HUs No No Yes

Update Delivery in Delivery Management Before Goods Issue

You can update an outbound delivery in Delivery Management (LE-SHP) after picking and packing is completed but before goods
issue is posted.

The Delivery Management outbound delivery is updated at goods issue with information like delivery quantities, batches and batch
splits, and handling units and additional package items for the handling units.

But it's also possible to update the Delivery Management outbound delivery before goods issue. After picking and packing is
completed for an outbound delivery order in Extended Warehouse Management (EWM), you trigger the early update by setting the
This is custom documentation. For more information, please visit SAP Help Portal. 89
 4/3/25, 7:52 PM
shipping readiness status for the outbound delivery order to Ready. Select the Set to Ready for Shipping method in the
warehouse management monitor under Outbound Documents Outbound Delivery Order .

You can use this status update as a condition for other activities. For example, you can use the status update to trigger the printing
of delivery notes in Delivery Management that can then be attached to packed deliveries.

Prerequisites
You've defined the document type and item type that are to be used in the outbound delivery order as follows:

Define a process profile that has the setting Send Update to LE-SHP: Ready for Shipping. This process profile is to be
assigned to the document type.

You can find this setting for the process profile in Customizing for Extended Warehouse Management under Cross-
Process Settings Delivery - Warehouse Request Process Management and Control Define Process Profile for
Document Header .

Define status profiles for the document type and the item type:

For the document type, define a status profile in which the Shipping Readiness (DSH) status type is active and the
Assign Transportation Unit (DTU) status type is inactive.

For the item type, define a status profile in which the Assign Transportation Unit (DTU) status type is inactive.

 Note
It's possible to choose different status profiles for the document type and the item type, but the DTU status type
must be inactive in both.

You can find these settings for the status profiles in Customizing for Extended Warehouse Management under
Cross-Process Settings Delivery - Warehouse Request Status Management Define Status Profiles .

Assign the process profile and the relevant status profile to the document type in Customizing for Extended Warehouse
Management under Goods Issue Process Outbound Delivery Define Document Types for Outbound Delivery
Process .

Assign the relevant status profile to the item type in Customizing for Extended Warehouse Management under Goods
Issue Process Outbound Delivery Define Item Types for Outbound Delivery Process .

Constraints
You can't change the shipping readiness status of an outbound delivery order in the following cases:

There aren't enough warehouse tasks for the delivery quantities in the outbound delivery order.

Picking isn't completed.

Serial numbers for serialized products aren't entered in the outbound delivery order.

This is only relevant for serialization on document level, because serial numbers have to be entered in the outbound delivery
order before it's possible to post goods issue.

 Note
For serialization on stock level, the serial numbers are already recorded during picking.

The outbound delivery order items are only partially packed.

This is custom documentation. For more information, please visit SAP Help Portal. 90
 4/3/25, 7:52 PM

Post Goods Issue

After the early update, you post goods issue for the outbound delivery order.

Correcting a Delivery
If you have to correct an outbound delivery order after the early update, for example, because a handling unit is damaged and must
be replaced, select the Reverse Ready for Shipping method in the warehouse management monitor under Outbound
Documents Outbound Delivery Order . Correct the outbound delivery order, for example, change the quantity or change the
packaging material.

You can also correct an outbound delivery order that is posted goods issue. In the Run Outbound Process - Deliveries app, reverse
goods issue. The ready for shipping status is automatically set to Not Ready. After you correct the outbound delivery order, you
must manually set the ready for shipping status back to Ready to continue.

Related Information
Process Management and Control

Invoice Creation Before Goods Issue

Use
You can define when billing for SAP Customer Relationship Management (CRM billing) or billing for SAP S/4HANA (SAP S/4HANA
billing) is to create an invoice for one single delivery or multiple deliveries.

In the standard system, CRM billing or SAP S/4HANA billing creates the invoice after goods issue. However, if you require the
invoice printout before the end of the loading and transportation process, such as for international transportation, you can create
the current invoice before goods issue posting. You do this by sending an invoice request from Extended Warehouse Management
(EWM) to CRM billing or SAP S/4HANA billing.

You can request an invoice for each delivery or one or more invoices for the contents of a vehicle or transportation unit.

If you want to print invoices for the contents of a vehicle or transportation unit, EWM triggers the invoice printout in CRM
billing or SAP S/4HANA billing by sending the message Print Billing Document.

If you want to create one invoice for each delivery, EWM triggers the creation and invoice printing automatically when it
generates an outbound delivery.

Integration
To be able to create and print invoices, you have performed the following:

If you are using CRM billing, you have connected an SAP S/4HANA and an SAP CRM system.

If you are using SAP S/4HANA billing, you have connected an SAP S/4HANA system.

EWM sends the invoice-relevant data to SAP S/4HANA . SAP S/4HANA copies the data to CRM billing or SAP S/4HANA billing.

The following applies for invoice creation:

In the case of direct outbound delivery orders, the invoice is always created through SAP S/4HANA billing.

This is custom documentation. For more information, please visit SAP Help Portal. 91
 4/3/25, 7:52 PM
In the case of CRM orders, the invoice is always created through CRM billing.

In the case of SAP S/4HANA orders, the invoice is always created through SAP S/4HANA billing.

Prerequisites

If you are using CRM billing, you have set the IBGI (Invoicing Before Goods Issue) indicator in the data relevant to the
business partner. You can override this indicator in the sales order.

For more information, see the SAP Library under SAP CRM Components and Functions Sales Sales Transaction
Sales Orders Additional Functions for Service Parts Management .

If you are using SAP S/4HANA billing, you have set the IBGI (Invoicing Before Goods Issue) indicator in Customizing for SAP
S/4HANA under Logistics Execution Extended Warehouse Management Integration Settings for Billing Determine
Invoicing Before Goods Issue .

You have determined that EWM requests CRM billing or SAP S/4HANA billing for single deliveries and also for groups of
deliveries in accordance with the contents of a vehicle or a transportation unit. If, for example, a vehicle is carrying a delivery
of 50 different regulators, EWM requests at least 50 invoices from CRM billing.

In the launchpad, choose Extended Warehouse Management Interfaces Invoice Before Goods Issue.

In Customizing for EWM, you have defined the following for the document type and item type of the outbound delivery:

You have defined a process profile for the document type of the outbound delivery that allows invoicing before goods
issue. For example, you are using document type OUTB Outbound Delivery Order with process profile
/SCWM/OUT_PRD Outbound Delivery Order Standard for the delivery header, and process profile
/SCWM/OUT_PRD_DLV Outbound Delivery Order Standard Item EWM for the delivery item. For more information,
see IMG for EWM under Goods Issue Process Outbound Delivery Define Document Types for Outbound
Delivery Process .

For more information about the individual process indicators, see the IMG for EWM under Cross-Process Settings
Delivery Processing Process Profile for Delivery Document Header in the field help for the individual process
indicator.

You have defined a process profile for the item types of the outbound delivery that allows invoicing before goods
issue. For example, you use item type ODLV Standard Item Outbound Delivery with process profile
/SCWM/OUT_PRD_DLV Outbound Delivery Order Standard Item.

For more information, see the IMG for EWM under Cross-Process Settings Delivery Processing Process
Control Define Process Profile for Delivery Document Header or Define Process Profile for Delivery Document
Item .

If you do not use routes in the outbound delivery, you can define the following in Customizing for EWM for the document
type of the outbound delivery:

EWM triggers invoice creation and invoice printing automatically when it generates an outbound delivery

You trigger invoice creation and invoice printing manually on the user interface of the outbound delivery later

For the routes that you want to use in the invoice before goods issue process, you have defined one of the following options:

The invoice for the outbound deliveries is to be created individually

The invoice for the outbound deliveries is to be created as a group per transportation unit or per vehicle, or manually
on the user interface for the outbound delivery.

In the launchpad, choose Extended Warehouse Management Interfaces Invoice Before Goods Issue.

Features
This is custom documentation. For more information, please visit SAP Help Portal. 92
 4/3/25, 7:52 PM
For single requests from EWM, CRM billing or SAP S/4HANA billing directly creates single invoices that you cannot change. For
changes, you have to delete the outbound delivery. This automatically cancels the invoice. If you then generate a new outbound
delivery, the invoice is automatically created and printed again.

For group requests from EWM, CRM billing or SAP S/4HANA billing creates one or more invoices for each vehicle or transportation
unit. CRM billing creates corresponding billing due list items. SAP S/4HANA billing does not create any billing due list items. You
can make changes to these deliveries in EWM. If these occur before invoice creation, SAP S/4HANA or SAP CRM updates its
deliveries or the invoice-relevant data in accordance with the input from EWM.

After you have posted the goods issue, you can only trigger the invoice printout from CRM billing or SAP S/4HANA billing.

If more than one vehicle forwards the material for a sales order, you can create related outbound deliveries for each vehicle and
request invoices for them.

Invoice Relevance

With your settings at sales order level or delivery level, you can control the global relevance for invoice creation before goods issue
at delivery item level.

You can determine a print profile after CRM billing or SAP S/4HANA billing has selected the printer. EWM finds the print profile and
informs CRM billing or SAP S/4HANA billing accordingly. For printing single requests, the billing system uses the print profile
found. For the printing of group requests, the billing system uses the profile of the first delivery that was found.

 Note
You must determine the same print profile in CRM billing or SAP S/4HANA billing and EWM, so that CRM billing or SAP
S/4HANA billing can print invoices.

Invoice Cancellation

You cannot change an invoice once it has been created. If, for example, you have loaded a handling unit on to a different
transportation unit and want to change the invoice that has already been created, you have to perform an invoice cancellation.
EWM sends the cancellation for the invoice that was created to CRM billing or SAP S/4HANA billing. You can then request invoice
creation and invoice printing again for the changed shipment document or delivery.

Activities
Among other things, SAP CRM determines whether EWM sends an invoice request for a delivery before the goods issue posting to
CRM billing via SAP S/4HANA , due to the business partner status Invoice Creation Before Goods Issue Posting Allowed . You can
override this setting in the sales order of SAP CRM.

SAP S/4HANA uses the Customizing entries to determine whether the outbound delivery is relevant for the Invoice Before Goods
Issue process. In SAP S/4HANA , you can configure for the sales document type and sales organization the indicator with which
the document items are sent to EWM.

If the IBGI indicator on the delivery item allows invoice before goods issue depending on the route, EWM decides which type of
request it sends to CRM billing or SAP S/4HANA billing for invoice creation and invoice printing:

Single request for an immediate invoice creation and invoice printing

Group request for an invoice creation and invoice printing

If you want to request, print or cancel an invoice for a group request, on the launchpad, choose Extended Warehouse
Management Shipping and Receiving Maintain Vehicles or Maintain Transportation Units. If you are not using a vehicle or
transportation unit in the outbound delivery, on the launchpad choose Extended Warehouse Management Delivery

This is custom documentation. For more information, please visit SAP Help Portal. 93
 4/3/25, 7:52 PM
Processing Outbound Delivery Maintain Outbound Deliveries or Outbound Delivery Orders - Pickup and then choose one of
the following options:

Request Invoice

EWM sends the message Create Invoice to SAP CRM or SAP S/4HANA.

Cancel Invoice

EWM sends the message Cancel Invoice to SAP CRM or SAP S/4HANA.

Print Invoice

EWM sends the message Print Invoice to SAP CRM or SAP S/4HANA.

Get Status

The system requests and displays the status of the invoice creation for the SAP S/4HANA delivery.

Print Profile Determination for Invoice Printout

Purpose
You can use this process to define print profile determination for invoice creation before goods issue in Extended Warehouse
Management (EWM). Here, every goods issue area can have multiple printers for various document types, for example, for freight
lists, bills of lading, or invoices.

EWM always sends the print profile names for invoice printouts to Logistics Execution (LE), irrespective of whether you print from
LE or from SAP Customer Relationship Management (SAP CRM).

Prerequisites

If appropriate, you have defined a print profile in the default values. To do so, on the launchpad, choose Extended
Warehouse Management Delivery Processing Outbound Delivery Outbound Delivery Orders - Pickup. Choose
Default Values and enter a print profile.

If appropriate, you have implemented your own print profile determination in Business Add-In (BAdI)
/SCWM/EX_DLV_PRINT_PROFILE. For more information, see the BAdI documentation.

If appropriate, you have defined one or more print profiles in Customizing for EWM.

For more information, see the Customizing for Extended Warehouse Management, under Goods Receipt Process
Inbound Delivery Print Define Print Profiles for Delivery Processing and Goods Issue Process Outbound
Delivery Print Define Print Profiles for Delivery Processing .

You have defined print profile determination for the goods receipt process or goods issue process in Customizing for EWM.

For more information, see the Customizing for Extended Warehouse Management, under Goods Receipt Process
Inbound Delivery Print Define Print Profile Determination for Goods Receipt Process or Goods Issue Process
Outbound Delivery Print Define Print Profile Determination for Goods Issue Process .

Process

EWM attempts to determine the print profile in the following sequence:

This is custom documentation. For more information, please visit SAP Help Portal. 94
 4/3/25, 7:52 PM
1. EWM checks whether you have specified a print profile in the default values on the user interface for pickup. If so, it uses the
name of this print profile.

2. If EWM cannot find a print profile in step 1, it checks whether you have implemented your own print profile determination in
BAdI /SCWM/EX_DLV_PRINT_PROFILE. EWM uses the name of this print profile.

3. If EWM cannot find a print profile in step 2, it checks whether you have defined a print profile determination for the goods
receipt process or the goods issue process in Customizing for EWM. EWM uses the name of this print profile.

You can define an access sequence for print profile determination. As a result, EWM considers one or more combinations of
different parameters for the print profile, for example, goods receipt office, loading point, and warehouse number.

If EWM cannot determine a print profile, it does not send a print profile name to LE.

If EWM requests a single print from CRM billing, CRM billing uses the print profile that EWM sends. EWM determines this print
profile in the sequence described above.

If EWM requests a grouped print for multiple deliveries from CRM billing, EWM always sends the first print profile that is found by
delivery processing.

For information about invoice relevance, the invoice printout, and invoice cancellation, see Invoice Creation Before Goods Issue .

 Note
If you want to synchronize invoice printing with delivery note printing, you must ensure that EWM determines the printer for
delivery note printing using a print profile (see Printer Determination in Delivery Processing ). This is because EWM only sends
the print profile name to LE and not the printer name.

See also:

Printing Delivery Notes

Consolidation Group

Use
You can use consolidation groups in the outbound process to determine which delivery items can or cannot be picked or packed
together into a handling unit (HU).

Integration
The use of consolidation groups is determined by the setting of the Packing Consolidation checkbox of the outbound delivery
item, which the system takes over from the Order Combination checkbox of the outbound delivery in SAP ERP.

If you use Outbound Processing: Transportation Planning in TM-ERP-EWM or Outbound Processing: Transportation Planning in
EWM-ERP-TM, do not use cross delivery HUs in this process. Either leave the Order Combination checkbox of the outbound
delivery empty in SAP ERP, or create a Business Add-In (BAdI) implementation for BAdI Determine Consolidation Group
(/SCWM/EX_CORE_CONS), which prohibits the packing consolidation in Extended Warehouse Management (EWM). For more
information, see Outbound Processing: Transportation Planning in TM-ERP-EWM and Outbound Processing: Transportation
Planning in EWM-ERP-TM.

Prerequisites

This is custom documentation. For more information, please visit SAP Help Portal. 95
 4/3/25, 7:52 PM
You have made the following settings in Customizing for EWM:

You have defined if you want to work with consolidation groups in the outbound process of your warehouse and if so, what
attributes influence the creation of the consolidation group per outbound delivery item. The attributes that the creation of
the consolidation group can depend on are the following:

Warehouse number

Route

Ship-to party

Priority of the delivery item

For more information, see Customizing for Extended Warehouse Management under Goods Issue Process Define
Consolidation Group .

You have defined number ranges for your consolidation groups and assigned them to the different use cases of
consolidation groups.

For more information, see Customizing for Extended Warehouse Management under the following:

Master Data Define Number Ranges Define Number Range Intervals for Consolidation Group

Goods Issue Process Assign Number Range Intervals to Consolidation Groups

In the Customizing of the work center, you have defined on which of the following levels you want to check the consolidation
group during packing.

Check while repacking products

Check while repacking handling units (HUs) and products

No check

For more information, see Customizing for Extended Warehouse Management under Master Data Work Center
Define Work Center .

Features
During the creation of outbound deliveries, the system determines the consolidation group for each delivery item. Depending on
the setting of the Packing Consolidation checkbox, the system determines the consolidation group in the following way:

If the checkbox is selected, the system tries to find an existing consolidation group from the Maintain Consolidation Group
transaction.

If there is no appropriate consolidation group yet, the system creates a new one and adds it to the Maintain Consolidation
Group transaction for later reuse.

If the checkbox is not selected, the system creates a new consolidation group but does not add it to the Maintain
Consolidation Group transaction. Therefore, the new consolidation group cannot be reused.

After determining the consolidation group for the outbound delivery item, the system transfers it to the corresponding warehouse
tasks.

Depending on the setup of the warehouse order creation rule (for example, on the setting of the value limit), it is possible to group
only warehouse tasks with the same consolidation groups into one warehouse order or to group warehouse tasks with different
consolidation groups into one warehouse order. If you use more than one planned pick-HU within your warehouse order, it is
possible to assign warehouse tasks with the same consolidation group to the same pick-HU, while the corresponding warehouse
order can carry warehouse tasks with different consolidation groups. For more information, see Warehouse Order Creation.

This is custom documentation. For more information, please visit SAP Help Portal. 96
 4/3/25, 7:52 PM
After the confirmation of a warehouse task into the pick HU, the system assigns the consolidation group to the stock. In case of
mixed stock in one pick HU with different consolidation groups, you can execute a repacking at a packing station to consolidate the
stock in terms of packing together only stock with the same consolidation group into one HU.

After the confirmation of a warehouse task into a consolidation group unique HU, the HU carries the information about the
consolidation group as well.

Using Consolidation Groups with Transportation Integration

Transportation integration offers you the following features:

When you change the door and the EWM processing has not yet started, the system can redetermine the consolidation
group with the new door.

To use this feature, you have to maintain a separate consolidation group per door. To do so, on the launchpad, choose
Extended Warehouse Management Master Data Maintain Consolidation Group .

When you or the system change the transportation unit (TU) assignment of a delivery and the EWM processing has not yet
started, the system can redetermine the consolidation group with the new data.

To use this feature, you have to maintain a separate consolidation group for each TU. For more information, see Customizing
for Extended Warehouse Management under Business Add-Ins (BAdIs) for Extended Warehouse Management Goods
Issue Process BAdI: Define Consolidation Group .

Activities

You have to decide if you want to use consolidation groups in the outbound process.

During picking processes, the system checks whether the picking of warehouse tasks with different consolidation groups into a
pick HU is allowed or not.

During processes of repacking stock or HUs with consolidation groups, the system checks whether they are allowed or not.

To start the Maintain Consolidation Group transaction, on the launchpad, choose Extended Warehouse Management Master
Data Maintain Consolidation Group

Example

Example with Order Combination

In Customizing for EWM, you have activated the consolidation group determination for the warehouse number, the ship-to party,
the route, and the priority. In SAP ERP, you have selected the Order Combination checkbox in the outbound delivery. You have
created two outbound deliveries in the system within the same warehouse, for the same ship-to party, on the same route, and with
the same priority. Since the Packing Consolidation is selected, EWM assigns all the items of both deliveries to the same
consolidation group. Therefore, all the warehouse tasks created for all those line items belong to the same consolidation group.
Since all the warehouse tasks have the same consolidation group, you can pick and pack the requested stock into one HU.

Example Without Order Combination

In Customizing for EWM, you have activated the consolidation group determination for the warehouse number, the ship-to party,
the route, and the priority. In SAP ERP, you have not selected the Order Combination checkbox in the outbound delivery. You have
created two outbound deliveries in the system within the same warehouse, for the same ship-to party, on the same route, and with
the same priority. Since the Packing Consolidation is not selected, EWM assigns the two deliveries to unique consolidation groups.
Therefore, the items within one delivery belong to the same consolidation group but the items of the other delivery have a different

This is custom documentation. For more information, please visit SAP Help Portal. 97
 4/3/25, 7:52 PM
consolidation group. This means that you cannot mix the requested stock for the two deliveries into one HU. You can pick and pack
only the items of one delivery together.

Run Outbound Process - Deliveries

Use
With this app, you can monitor the outbound process based on outbound deliveries. The app is optimized for small and medium
warehouses using an outbound process without waves. On the overview screen, you have all relevant information about the
deliveries that are planned for one day or several days. With this information, you create the tasks to trigger the picking process.
You can also post goods issue. If there is an exception, for example, a delay or missing tasks for a delivery, you can navigate to a
second screen in the app to resolve the issue.

Key Features
Find outbound delivery orders

Create tasks for outbound deliveries, with the option to specify the source bin and target quantity

Increase or decrease the delivery item quantity

Adjust the delivery quantity down to the warehouse task quantity, for example, if stock is missing

Release stock from the delivery once it has already been picked

Navigate to the Process Warehouse Tasks - Picking app to work with warehouse tasks

Navigate to the warehouse management monitor to retrieve additional information about handling units

Post goods issue for outbound deliveries

Reverse goods issue

In addition, the app supports the following technical features and options:

This app supports the Attachment Service. You can upload, read, update, or delete files, for example, photos or documents
in various file formats, that are attached to outbound delivery orders or handling units. For more information, see
Attachments.

Supported Device Types

Desktop

Tablet

Relevant Business Catalog

SAP_SCM_BC_EWM_LWC

Feature Comparison Documentation

For a comparison of the features offered by this app and other apps in the area of Extended Warehouse Management, see Feature
Comparison for Outbound Process Apps.

This is custom documentation. For more information, please visit SAP Help Portal. 98
 4/3/25, 7:52 PM

Run Outbound Process - Deliveries: Videos

The following videos explain how to use the functions available in the Run Outbound Process - Deliveries app.

 Note
Captions are available for multiple languages. Simply click the CC button at the bottom right of the video player to see which
languages are supported.

Run Outbound Process - Deliveries: How to Use the Basic Process

You can use this app to monitor and run the outbound process in your warehouse. You can create warehouse tasks for outbound
delivery orders, change delivery item quantities, and post goods issue.

Open this video in a new window

Run Outbound Process - Deliveries: How to Release Stock

You can use this app to release stock after it has been picked, before goods issue. The process is different depending on whether
the stock is unpacked or packed.

This is custom documentation. For more information, please visit SAP Help Portal. 99
 4/3/25, 7:52 PM

Open this video in a new window

App Extensibility: Run Outbound Process - Deliveries

You cannot extend the Run Outbound Process - Deliveries app.

Run Outbound Process - Transportation Units

Use
With this app, you can monitor the outbound process based on transportation units (TUs). The app is optimized for small and
medium warehouses and for an outbound process without waves. On the overview screen, you have all the relevant information
about the TUs that are planned for that day or for a range of days. With this information, you create warehouse tasks to trigger the
picking process. If there is an exception, for example, a delay or missing tasks for a TU, you can navigate to a second screen in the
app to resolve the issue.

Key Features
Find outbound deliveries based on transportation units

Create warehouse tasks for outbound deliveries, with the option of specifying the source bin and the target quantity

Add or change scheduling or staging information

Post goods issue and reverse goods issue

Adjust the delivery quantity down to the warehouse task quantity, for example, because stock is missing

Change delivery item quantity to an amount you specify

Indicate that transportation units have arrived at the checkpoint and departed from the checkpoint

Navigate to the warehouse management monitor to retrieve additional information about the handling units assigned to a
transportation unit

Navigate to the Run Outbound Process - Deliveries app to retrieve additional information about the outbound delivery
order assigned to a transportation unit. For instance, you can investigate a blocked delivery.

Release unpacked stock from the delivery after it has been picked

In addition, the app supports the following technical features and options:

This app supports the Attachment Service. You can upload, read, update, or delete files, for example, photos or documents
in various file formats, that are attached to transportation units. For more information, see Attachments.

Supported Device Types

This is custom documentation. For more information, please visit SAP Help Portal. 100
 4/3/25, 7:52 PM
Desktop

Tablet

Relevant Business Catalog

SAP_SCM_BC_EWM_LWC

Feature Comparison Documentation

For a comparison of the features offered by this app and other apps in the area of Extended Warehouse Management, see Feature
Comparison for Outbound Process Apps Using Transportation Units.

App Extensibility: Run Outbound Process - Transportation Units

You cannot extend the Run Outbound Process - Transportation Units app.

Run Outbound Process - Production

With this app, you can monitor the outbound process based on outbound deliveries destined for production. On the overview
screen, you have all relevant information about the deliveries that are planned for one day or several days. With this information,
you create the tasks to trigger the picking process. You can also post goods issue. If there is an exception, for example, a delay or
missing tasks for a delivery, you can navigate to a second screen in the app to resolve the issue.

Key Features
You can use this app to:

Find outbound delivery orders destined for production. For example, you can filter your search by date, Manufacturing
Order, or Production Supply Area.

Create tasks for outbound deliveries, with the option to specify the source bin and target quantity

Increase or decrease the delivery item quantity

Adjust the delivery quantity to the warehouse task quantity, for example, if stock is missing

Release stock from the delivery after it has been picked

Navigate to the Process Warehouse Tasks - Picking app to work with warehouse tasks

Navigate to the monitor to retrieve additional information about handling units

Post goods issue for outbound deliveries

Reverse goods issue

In addition, the app supports the following technical features and options:

This app supports the Attachment Service. You can upload, read, update, or delete files, for example, photos or documents
in various file formats, that are attached to outbound delivery orders or handling units. For more information, see
Attachments.

This is custom documentation. For more information, please visit SAP Help Portal. 101
 4/3/25, 7:52 PM

Supported Device Types

Desktop

Tablet

Feature Comparison Documentation

For a comparison of the features offered by this app and other apps in the area of Extended Warehouse Management, see Feature
Comparison for Outbound Process Apps.

App Extensibility: Run Outbound Process - Production

You cannot extend the Run Outbound Process - Production app.

Feature Comparison for Outbound Process Apps

The following table compares the features offered by various apps for processing outbound deliveries that do not use
transportation units (TUs). The column headings contain links to the app documentation and the app's entry in the SAP Fiori apps
reference library.

App Name Outbound Delivery Orders Run Outbound Process - Run Outbound Process -
Deliveries Production

App ID /SCWM/PRDO F1704 F5164

Display Outbound Delivery Yes Not applicable

Orders from Procurement

Display Outbound Delivery Yes Not applicable Yes

Orders from Production

Post Full Goods Issue Yes

Reverse Full Goods Issue Yes

Post Partial Goods Issue on Yes No

Handling Unit (HU) Level

Reverse Partial Goods Issue on Yes No

HU Level

Check Reason for Blocked Yes

Outbound Delivery Order

Set or Reverse Transportation Yes No

Planning Status

Set or Reverse In Yard Status Yes No

Reject Outbound Delivery Order Yes No

Print Loading Instruction No Yes

Load Outbound Delivery Order Yes No

This is custom documentation. For more information, please visit SAP Help Portal. 102
 4/3/25, 7:52 PM

App Name Outbound Delivery Orders Run Outbound Process - Run Outbound Process -
Deliveries Production

App ID /SCWM/PRDO F1704 F5164

Reverse Loading of Outbound Yes No

Delivery Order

Create Batch Split Item for Yes No

Outbound Delivery Order Item

Pack Before Goods Issue by Yes

Navigating to Pack Handling
Units

Delete Item from Outbound Yes No

Delivery Order

Create Putaway Warehouse No Yes

Tasks Directly for Outbound
Delivery Order with One Click

Create Additional Outbound Yes No

Delivery Order Items

Create Outbound Delivery Order Yes No

Create Subitems for Outbound Yes No

Delivery Order Items

Integrate with GTS and Yes No

Transportation Management

Maintain Document Address Yes No

Search for Outbound Delivery Orders by Different Selection Criteria

Search by External Reference Yes

Numbers

Search by Consignee Yes

Search by Carrier Yes No

Search by Vendor, Ship-From Yes No

Party, or Ship-To Party

Search by Status Values Yes No

Search by HUs Yes No

Search by Products Yes No

Search by Creation Date or User Yes No

Search by Route Yes

Search by Means of Transport Yes

Search by TU or Vehicle Yes No

Search by Departure Calendar Yes No

This is custom documentation. For more information, please visit SAP Help Portal. 103
 4/3/25, 7:52 PM

App Name Outbound Delivery Orders Run Outbound Process - Run Outbound Process -
Deliveries Production

App ID /SCWM/PRDO F1704 F5164

Search by Route Departure Date Yes

Search by Planned Delivery Yes

Date

Search by All Dates Yes No

Search by Loading Point Yes No

Search by Door Yes

Search by Shipping Condition Yes

Search by Production Supply Yes

Area (PSA)

Search by Bill of Lading, Yes No

Consignment, or Freight Order

Maintain Outbound Delivery Order Header Data

Maintain Route Departure Date Yes No

Maintain Planned Delivery Date No Yes

Maintain Door for All Items No Yes

Maintain Staging Area Data for No Yes

All Items

Maintain All Changeable Data of Yes No

the Outbound Delivery Order
Header

Display Outbound Delivery Order Header Data

Display Number of Items for No Yes

Each Outbound Delivery Order

Display Outbound Delivery Yes

Order Document Type

Directly Display if HUs Exist No Yes

Directly Display if Warehouse No Yes

Tasks Exist

Display Picking Progress in No Yes

Percentage

Display Good Issue Status, Yes

Picking Status, Packing Status,
and Completion Status

Display All Status Values of the Yes No

Outbound Delivery Order
Header

This is custom documentation. For more information, please visit SAP Help Portal. 104
 4/3/25, 7:52 PM

App Name Outbound Delivery Orders Run Outbound Process - Run Outbound Process -
Deliveries Production

App ID /SCWM/PRDO F1704 F5164

Display Planned Delivery Date Yes

Display Route Departure Date Yes

Display Weight and Volume for Yes No

Outbound Delivery Order
Header

Display All Configured Dates of Yes No

the Outbound Delivery Order

Display Loading Point Yes

Display Door Yes No

Display Staging Area Data Yes

Display Shipping Condition Yes

Display TU Number, Means of Yes

Transport, and Route

Display External Reference Yes

Numbers

Maintain Texts of Outbound Yes No

Delivery Order Header

Manage Attachments for No Yes

Outbound Delivery Order
Header

Display PPF Actions of Yes No

Outbound Delivery Order
Header

Display All Data of Outbound Yes No

Delivery Order Header

Maintain Outbound Delivery Order Item Data

Change Delivery Quantity of Yes

Outbound Delivery Order Item

Maintain Gross Weight and Yes

Volume

Adjust Delivery Quantity to Yes

Allow Goods Issue

Maintain Door for Each Item Yes No

Maintain Staging Area Data for Yes No

Each Item

Maintain Serial Numbers Yes No

This is custom documentation. For more information, please visit SAP Help Portal. 105
 4/3/25, 7:52 PM

App Name Outbound Delivery Orders Run Outbound Process - Run Outbound Process -
Deliveries Production

App ID /SCWM/PRDO F1704 F5164

Create Picking Warehouse Tasks Yes No

for Each Item

Create Picking Warehouse Tasks No Yes

for Each Item with Source Bin

Confirm Picking Warehouse No Yes

Tasks for Each Item

Release Unpacked Stock for No Yes

Each Picked Item

Maintain and Display Process Yes No

Codes

Maintain All Changeable Data of Yes No

Outbound Delivery Order Item

Display Outbound Delivery Order Item Data

Display Product and Product Yes

Description

Display Item Number and Main Yes

Item Number

Directly Display if Warehouse No Yes

Tasks Exist

Display All Status Values of Yes No

Outbound Delivery Order Item

Display Good Issue Status and Yes

Packing Status

Display All Configured Dates of Yes No

Outbound Delivery Order Item

Display Delivery Quantity and Yes

Unit of Measure

Directly Display of Open No Yes

Warehouse Task Quantity and
Missing Warehouse Tasks
Quantity

Display Weight and Volume for Yes

Outbound Delivery Order Item

Display All Configured Yes No

Quantities of Outbound Delivery
Order

Display Loading Point of Yes No

Outbound Delivery Order Item

This is custom documentation. For more information, please visit SAP Help Portal. 106
 4/3/25, 7:52 PM

App Name Outbound Delivery Orders Run Outbound Process - Run Outbound Process -
Deliveries Production

App ID /SCWM/PRDO F1704 F5164

Display Staging Area Data of Yes

Outbound Delivery Order Item

Display Staging Bay of Yes No

Outbound Delivery Order Item

Display Door of Each Item Yes No

Display PSA Yes

Display Outbound Delivery Yes No

Order Item Type

Display Warehouse Process Yes No

Type of Outbound Delivery
Order Item

Display Stock Type of Outbound Yes

Delivery Order Item

Display HUs of Outbound Yes No

Delivery Order Item

Display Batch of Outbound Yes

Delivery Order Item

Display Vendor Batch, Best- Yes

Before Date, Production Date,
and Country/Region of Origin of
Outbound Delivery Order Item

Display Document Flow of Yes No

Outbound Delivery Order Item

Maintain Texts of Outbound Yes No

Delivery Order Item

Display Process Codes of Yes No

Outbound Delivery Order Item

Display Change Documents of Yes No

Outbound Delivery Order Item

Display All Data of the Yes No

Outbound Delivery Order Item

Navigate to Other Apps or Sources of Information

Navigate to Warehouse Tasks of Yes

Outbound Delivery Order
Header

Navigate to Warehouse Orders Yes No

of Outbound Delivery Order
Header

This is custom documentation. For more information, please visit SAP Help Portal. 107
 4/3/25, 7:52 PM

App Name Outbound Delivery Orders Run Outbound Process - Run Outbound Process -
Deliveries Production

App ID /SCWM/PRDO F1704 F5164

Navigate to Change Documents Yes

of Outbound Delivery Order
Header

Navigate to Loaded HUs of Yes No

Outbound Delivery Order
Header

Navigate to Handling Units of No Yes

Outbound Delivery Order
Header in the Warehouse
Monitor

Navigate to Handling Units in Yes

Pack Handling Units

Navigate to Outbound Delivery Yes No

Navigate to Warehouse Tasks of Yes

Outbound Delivery Order Item

Navigate to Warehouse Orders Yes No

of Outbound Delivery Order
Item

Navigate to Change Documents Yes No

of Outbound Delivery Order
Item

Navigate to Display Information Yes

about Product

Navigate to Maintain Product No Yes

Navigate to Physical and No Yes

Available Stock in the
Warehouse Monitor

Feature Comparison for Outbound Process Apps Using

Transportation Units
The following table compares the features offered by various apps for processing outbound deliveries using transportation units
(TUs). The column headings contain links to the app documentation and the app's entry in the SAP Fiori apps reference library.

App Name Maintain Transportation Units Run Outbound Process - Transportation

Units

App ID /SCWM/TU F1703

Create TUs Yes No

Display Inbound TUs Yes No

This is custom documentation. For more information, please visit SAP Help Portal. 108
 4/3/25, 7:52 PM

App Name Maintain Transportation Units Run Outbound Process - Transportation

Units

App ID /SCWM/TU F1703

Display TUs without Assigned Outbound Yes

Delivery Orders

Display Outbound TUs Yes

Maintain Assignments of Deliveries to TUs Yes No

Maintain Assignments of Handling Units Yes No

(HUs) to TUs

Work with Yard Management in Extended Yes No

Warehouse Management

Integrate with Dock Appointment Yes No

Scheduling

Delete TUs Yes No

Post Arrival at Checkpoint for TU Yes

Reverse Arrival at Checkpoint for TU Yes No

Post Departure From Checkpoint for TU Yes

Reverse Departure From Checkpoint for TU Yes No

Post Goods Issue for TU Yes

Reverse Goods Issue for TU Yes

Post Arrival at Door and Departure from Yes No

Door

Create Picking Warehouse Tasks for TU No Yes

Create Picking Warehouse Tasks for No Yes

Assigned Outbound Delivery Order Items

Create Picking Warehouse Tasks with No Yes

Manual Source Bin Selection for Assigned
Outbound Delivery Order Items

Create Loading Warehouse Tasks for Yes No

Assigned Outbound Delivery Order Items

Change Delivery Quantity for Assigned No Yes

Outbound Delivery Order Items

Adjust Delivery Quantity for Assigned No Yes

Outbound Delivery Order Items to Picked
Quantity

Confirm Picking Warehouse Tasks for No Yes

Assigned Outbound Delivery Order Items

Release Unpacked Stock for Assigned No Yes

Outbound Delivery Order Items

This is custom documentation. For more information, please visit SAP Help Portal. 109
 4/3/25, 7:52 PM

App Name Maintain Transportation Units Run Outbound Process - Transportation

Units

App ID /SCWM/TU F1703

Set Start Loading and Loading Finished for Yes No

TU

Block and Unblock TU from Processing Yes No

Archive TU Yes No

Generate Outbound Delivery for TU Yes No

Search for TUs by Different Selection Criteria

Search by External Transportation Unit Yes

Number

Search by Internal Transportation Unit Yes No

Number

Search by Carrier Yes

Search by Route Yes

Search by Route Departure Date Yes

Search by Outbound Delivery Order Yes

Number or LE Delivery Number

Search by Means of Transport Yes

Search by Sales Order Yes

Search by Vehicle Data Yes No

Search by Door Yes No

Search by License Plate Yes No

Search by Seal Number Yes No

Search by All Status Values Yes No

Search by HU Yes No

Change TU Data

Change Planned Departure Date (End) Yes

Change Planned Door Yes

Change Carrier Yes

Maintain Attachments for TU No Yes

Maintain Assigned Vehicles Yes No

Maintain Seals Yes No

Display TU Data

This is custom documentation. For more information, please visit SAP Help Portal. 110
 4/3/25, 7:52 PM

App Name Maintain Transportation Units Run Outbound Process - Transportation

Units

App ID /SCWM/TU F1703

Display External and Internal TU Number Yes

Display External Vehicle Number Yes

Display Route Yes

Display Planned Departure Date (End) Yes

Display Planned Date or Time Ranges for Yes No

Arrival and Departure

Display Carrier Yes

Display Means of Transport Yes

Display License Plate Number Yes

Display Consignee of Assigned Outbound No Yes

Delivery Orders when All Outbound Delivery
Orders have the Same Consignee

Display Staging Area Data of Assigned No Yes

Outbound Delivery Orders when All
Outbound Delivery Orders have the Same
Staging Area Data

Display Alternative TU IDs Yes No

Display Door Yes

Display Number of Seals Yes No

Display Seals Yes No

Display Picking Status (Planned or Yes

Executed)

Display Picking in Percentage of Cumulated No Yes

Assigned Outbound Delivery Orders

Display Loading Weight, Loading Volume, Yes

and Maximum Weight

Display Maximum Length, Height, and Yes No

Width

Display Shipping and Receiving Activity Yes

Status with Text

Display Goods Issue Status Yes

Display Assigned Outbound Deliveries

Display Assigned Outbound Delivery Order Yes No

Headers

This is custom documentation. For more information, please visit SAP Help Portal. 111
 4/3/25, 7:52 PM

App Name Maintain Transportation Units Run Outbound Process - Transportation

Units

App ID /SCWM/TU F1703

Display Assigned Outbound Delivery Order Yes

Items

Display Assigned Outbound Delivery Order Yes No

HUs

Display Assigned Vehicles of TU Yes No

Display All Status Values of TU Yes No

Display Outbound Delivery Order Number Yes

of Assigned Outbound Delivery Order Items

Display Item Number of Assigned Outbound Yes

Delivery Order Items

Display Product of Assigned Outbound Yes

Delivery Order Items

Display Delivery Quantity of Assigned Yes

Outbound Delivery Order Items

Display Batch of Assigned Outbound Yes

Delivery Order Items

Display Best-Before Date or Shelf Life Yes

Expiration Date of Assigned Outbound
Delivery Order Items

Display Staging Area Data of Assigned Yes

Outbound Delivery Order Items

Display if Picking Warehouse Tasks Exist for No Yes

Assigned Outbound Delivery Order Items

Display Planned Picking Status of Assigned No Yes

Outbound Delivery Order Items

Display Missing Warehouse Task Quantity of No Yes

Assigned Outbound Delivery Order Items

Display Open Warehouse Task Quantity of No Yes

Assigned Outbound Delivery Order Items

Display Number of Open Warehouse Tasks No Yes

of Assigned Outbound Delivery Order Items

Display Packing Status of Assigned No Yes

Outbound Delivery Order Items

Display Project Stock Sales Order Number No Yes

of Assigned Outbound Delivery Order Items

Display Outbound Delivery Number of Yes No

Assigned Outbound Delivery Order Items

This is custom documentation. For more information, please visit SAP Help Portal. 112
 4/3/25, 7:52 PM

App Name Maintain Transportation Units Run Outbound Process - Transportation

Units

App ID /SCWM/TU F1703

Display Outbound Delivery Item Number of Yes No

Assigned Outbound Delivery Order Items

Display PPF Actions of TU Yes No

Display All Assigned Doors of TU Yes No

Manage Warehouse Documents

With this app, you can search for and display warehouse documents in your warehouse. You can cancel complete warehouse
documents or individual items in a warehouse document. Warehouse documents are goods movement documents for goods
receipt and goods issue. Stock-related information, such as product and storage bin, is taken from the first warehouse document
item. Other information, such as warehouse document status, is aggregated from all items that belong to the same warehouse
document.

Prerequisites
If you want to use reasons for movement, you have performed the actions described in Prerequisites for Using Reasons for
Movement in Manage Physical Stock - Products and Manage Warehouse Documents.

Key Features
You can use this app to do the following:

Use the Search field to search for warehouse documents by the warehouse document number

Filter warehouse documents, for example, by status, product, or storage bin

View the details of warehouse documents and items, for example, account assignment information

Display the serial numbers of items that contain products serialized in Inventory Management

Cancel warehouse documents with the status Confirmed or Partially Canceled

Cancel one or more warehouse document items that have the status Confirmed

Enter a reason for movement when canceling warehouse documents or warehouse document items

Enter a short text when canceling warehouse documents or warehouse document items.

Enter a posting date when canceling warehouse documents posted with the Migration Cockpit

Navigate to other apps for more information about products and storage bins

Note that you may need additional authorizations to use these apps.

Additional Information
You can cancel only warehouse documents created with the following apps in Manage Warehouse Documents:

Manage Physical Stock – Products

This is custom documentation. For more information, please visit SAP Help Portal. 113
 4/3/25, 7:52 PM
Post Goods Issue – Unplanned

Migration Cockpit

You can display warehouse documents created with other apps.

Supported Device Types

Desktop

Tablet

Feature Comparison Documentation

For a comparison of the features offered by this app and other apps in the area of unplanned goods issue, see Feature Comparison
for Posting Unplanned Goods Issue.

Related Information
Manage Physical Stock - Products
Posting of Unplanned Goods Issue

Supply Assignment
Supply Assignment ensures that the supply is assigned to the sales orders according to the changing requirements.

In a supply shortage situation, supply assignment ensures an optimal assignment of supply to the open requirements and
distributes available supply to the respective sales orders. For more information, see Supply Assignment (ARun).

When stock deduction or deallocation happens in Extended Warehouse Management (EWM), sometimes the stock information
isn't synchronized in Inventory Management immediately. To avoid any risk that can happen, for example, supply shortage, you can
specify whether to allow the following actions for products relevant to supply assignment:

Pick more goods than required

Create direct outbound delivery order

You specify this in Customizing for Extended Warehouse Management under Goods Issue Process Supply Assignment
Specify Outbound Settings for Products Relevant to Supply Assignment .

Decentralized EWM
In decentralized EWM based on SAP S/4HANA, you also need to include the supply assignment values in the master data
replication.

You use IDoc MATMAS to replicate the supply assignment values from the enterprise management system to decentralized EWM.

Pack Separately – Ship Together

Pack Separately – Ship Together (PSST) enables you to create grouping rules and use the rules to create PSST groups. A PSST
group comprises outbound deliveries in Logistics Execution (LE) that need to ship together based on the customer's business
rules, even though these items are packed separately. For more information, see Pack Separately – Ship Together (PSST).

This is custom documentation. For more information, please visit SAP Help Portal. 114
 4/3/25, 7:52 PM
You configure PSST groups on the document level of LE outbound delivery. The system replicates the PSST group from LE to
Extended Warehouse Management (EWM). You can then use the PSST group in EWM to filter outbound delivery orders for wave
assignment, packing, and transportation unit assignment.

This is custom documentation. For more information, please visit SAP Help Portal. 115