Sap Help For Idoc WT in Ewm

10/3/2019
SAP Extended Warehouse Management

(SAP EWM)
Generated on: 2019-10-03
SAP Extended Warehouse Management (SAP EWM) | 9.5.0.2
PUBLIC
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the SAP Help Portal.
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20704074&topics=48890776d2b21b5ae10000000a… 1/59
10/3/2019
Warehouse Order Creation

Use
This function groups together warehouse tasks into warehouse orders, according to your settings in Customizing for warehouse
orders (see Warehouse Order), and thus creates optimum work packages for you. For warehouse order creation, you de ne rules
with their relevant criteria. Warehouse order creation is particularly suitable for optimizing processes for picking.
Integration
You assign warehouse orders to warehouse workers in resource management.
Prerequisites
You have de ned the following in Customizing for Extended Warehouse Management (EWM):
Number Ranges for Warehouse Orders
For more information about de ning number ranges for warehouse orders, see Customizing for EWM under Cross-Process
Settings Warehouse Order De ne Number Ranges for Warehouse Order .
Storage Bins
For more information about de ning number ranges for warehouse orders, see Customizing for EWM under Master
Data Storage Bins .
Activity Areas
For more information about de ning number ranges for warehouse orders, see Customizing for EWM under Master
Data Activity Areas De ne Activity Areas .
Source Bins
To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Storage Bin Assign
Start/End Storage Bin for Activity Area .
Features
A wave consists of a number of deliveries. After the wave and wave item have been released (either automatically by EWM or
manually by a user), EWM creates warehouse tasks. EWM joins the warehouse tasks together into warehouse orders, according to
the warehouse order creation rules (WO creation rules) you have de ned. A warehouse order can contain warehouse tasks from
more than one delivery.
You can create locked warehouse orders resulting from the wave release. You cannot initially continue to process these warehouse
orders. You can use a method in the warehouse management monitor (see Warehouse Management Monitor) to release the lock
on the warehouse orders. If you want to release the lock on a warehouse order, you can select the Unlock WO method, for
example, in the warehouse management monitor in the dialog structure under the node Documents Warehouse Order using the
More Methods action menu (see Processing Waves).
When grouping warehouse tasks into warehouse orders, EWM uses the search sequence for WO creation, for example, rst rule A,
then B, then C. EWM works through the WO creation rules in sequence, as you have de ned for each activity area. You can change
the sequence subsequently.
10/3/2019
Filters and limit values control which warehouse tasks and how many warehouse tasks EWM groups together into a warehouse
order.
The individual WO creation rule can contain sorting rules . As soon as EWM applies a WO creation rule, it sorts the warehouse
tasks according to these sort rules.
Since the work packages for the warehouse employee are based on the complete summarization of warehouse tasks into
warehouse orders, then after all user-de ned WO creation rules have been applied, no warehouse tasks must be left over that are
not assigned to a warehouse order. If EWM has applied all the user-de ned WO creation rules for the search sequence, and there
are still unprocessed warehouse tasks, the system uses a remainder rule . This rule creates warehouse orders for the remaining
warehouse tasks. EWM summarizes these warehouse tasks according to the following criteria:
For each activity area
For each queue
For each consolidation group
If you do not de ne your own WO creation rules for the current activity area, then warehouse order creation uses a standard rule .
This rule attempts to group deliveries according to the following criteria:
For each activity area
For each queue
For each delivery
Note
If you generate warehouse tasks that are relevant for the material ow system, EWM automatically uses the WO
creation rule of the material ow system. This rule allows EWM to group a maximum of one warehouse task per
warehouse order.
You can use the following parameters to de ne creation of warehouse orders in detail for your warehouse processes:
Sorting rule
For more information about de ning sorting rules, see Customizing for EWM under Cross-Process Settings Warehouse
Order De ne Sorting Rules for Warehouse Tasks .
Filter
For more information about item lters or subtotal lters, see Filters for Warehouse Order Creation Rules.
Limit value
For more information, see Limit Values for Warehouse Order Creation Rules.
Parameters for packing
You use these parameters to specify the number of handling units for a warehouse order. You specify these parameters in a
packing pro le, which you assign to a packaging speci cation.
For more information about de ning packing pro les, see Customizing for EWM under Cross-Process Settings Warehouse
Order De ne Packing Pro le for Warehouse Order Creation .
Packing mode
Consolidation Group
10/3/2019
During warehouse order creation, the consolidation group in uences which warehouse tasks you are permitted to pack
together. EWM determines the consolidation group in the delivery, and transmits it to the relevant warehouse tasks.
Example
You de ne the maximum number of consolidation groups in a warehouse order as the de nition of a limit value.
You can simulate creation of warehouse orders for your warehouse tasks.
You can de ne control parameters for warehouse order creation. For example, you can activate the log for WO creation for each
warehouse number, activity area or warehouse order creation rule, or specify the number of work processes depending on the
warehouse number.
Activities
EWM creates a list of warehouse requests.
EWM groups the warehouse requests into a wave (for example, a wave pick) and releases it.
EWM starts warehouse order creation, and uses the wave as a basis for creating a suitable number of warehouse tasks.
EWM creates warehouse orders for each warehouse task, according to your Customizing settings, which contain the
relevant warehouse tasks.
For more information about making settings for the sorting rules, lters, limit values, parameters for packing, and
the packing mode, see Customizing for EWM under Cross-Process Settings Warehouse Order
De ne Sort Rules for Warehouse Tasks
De ne Filters for Warehouse Order Creation Rules
De ne Limit Values for the size of a Warehouse Order
De ne Packing Pro le for Warehouse Order Creation, and select an option for Split WT.
De ne Packing Pro le for Warehouse Order Creation, and select an option for Split TO.
Further information regarding setting the consolidation group is available in Customizing for EWM under Goods
Receipt Process Deconsolidation Assign Number Range Intervals to Consolidation Groups or Goods Issue
Process Assign Number Range Intervals to Consolidation Groups .
If you want to simulate warehouse order creation for your warehouse tasks, then on the SAP Easy Access screen choose
Extended Warehouse Management Monitoring Warehouse Management Monitor .
Choose warehouse number 0001, the monitor SAP and Execute.
Open Documents Warehouse Tasks .
In the dialog box, choose the warehouse task status Open and Execute.
Select one or more open warehouse tasks and choose Other Methods Simulate Warehouse Order . The WO
Create Rule dialog box appears.
Enter a warehouse order creation rule.
If you do not make an entry, then EWM executes the warehouse order creation rules according to the search
sequence for warehouse order creation rules.
If you want to de ne control parameters for warehouse order creation, from the SAP Easy Access choose Extended
Warehouse Management Settings Warehouse Order Set Up Control Parameters for Warehouse Order Creation.
10/3/2019
Warehouse Order
De nition
Document that represents an executable work package that a warehouse employee should perform at a speci c time. The
warehouse order consists of warehouse tasks or physical inventory items.
Use
When you move products, in other words you or Extended Warehouse Management (EWM) create warehouse tasks, then EWM
groups these warehouse tasks together into warehouse orders, and makes them available for processing.
When you perform a physical inventory, in other words you create physical inventory items, EWM also groups these physical
inventory items together into warehouse orders.
You can adjust the scope and type of a warehouse order using the warehouse order creation rules that you have de ned in
Customizing.
Note
For more information about warehouse order creation rules, see the Implementation Guide (IMG) for EWM under Cross-
Process Settings Warehouse Order De ne Creation Rule for Warehouse Orders.
Integration
The warehouse groups together warehouse tasks or physical inventory items.
Example
EWM creates warehouse tasks for an outbound delivery with four delivery items. EWM uses warehouse order creation to assign
the resulting four warehouse tasks to a new warehouse order. A warehouse employee receives this warehouse order as a work
package to pick the items listed in the delivery.
Filters for Warehouse Order Creation Rules

De nition
The lter for a warehouse order creation rule decides whether Extended Warehouse Management (EWM) processes a warehouse
task using a creation rule. Warehouse order creation uses the lters on all warehouse tasks that you have not yet assigned to a
warehouse order, and which WO creation should process.
Use
You can de ne two types of lters: Item Filtersand Subtotal Filters.
Item Filter
You de ne item lters, so that EWM checks the individual warehouse task against the lter criteria de ned in your Customizing
settings.
10/3/2019
During processing of a warehouse task, EWM checks whether the given item lter ts. If the lter ts the warehouse task, then
EWM continues processing for the warehouse task. If it does not t, EWM stops processing the warehouse task. EWM checks,
according to your Customizing settings, whether it should use another warehouse order creation rule to check the warehouse task
that has not yet been processed.
For more information about Customizing for lter parameters for warehouse tasks, see the Implementation Guide (IMG) for EWM
under Cross-Process Settings Warehouse Order De ne Filters for Warehouse Order Creation Rules.
Subtotal Filter
You de ne subtotal lters, so that EWM can use the lter criteria de ned in your Customizing settings to compare several
warehouse tasks against a subtotal, containing values you have de ned. During this, EWM works out the subtotal for each
consolidation group. You must have de ned sorting rules with the sort eld DSTGRP (consolidation group), for the warehouse
tasks to process.
For more information about de ning sorting rules, see the IMG for EWM under Cross-Process Settings Warehouse Order De ne
Sorting Rules for Warehouse Tasks.
During processing of several warehouse tasks, EWM checks whether the given item or subtotal lter ts. If the lter ts the
transfer orders, then EWM continues processing for the warehouse tasks. If it does not t, EWM stops processing the warehouse
tasks. In the case of a subtotal lter, this means that EWM does not process the entire group of warehouse tasks for a
consolidation group using the current lter. EWM checks, according to your Customizing settings, whether it should use another
warehouse order creation rule to check the warehouse tasks that have not yet been processed.
For more information about Customizing for lter parameters for warehouse tasks, see the IMG for EWM under Cross-Process
Settings Warehouse Order De ne Filters for Warehouse Order Creation Rules.
Limit Values for Warehouse Order Creation

Rules
De nition
The limit value of a warehouse order creation rule speci es the size of a warehouse order.
Use
During warehouse order creation, Extended Warehouse Management (EWM) compares the warehouse tasks that passed the
checks in the warehouse order creation rule (for example, lter criteria), against the limit values de ned in your Customizing
settings.
As soon as the transfer orders exceed one of the limit values, EWM creates a warehouse order containing all the warehouse tasks
that do not exceed the limit value. EWM creates new warehouse orders for the remaining warehouse tasks. It continues with this
process until it has processed all the warehouse tasks.
For more information about Customizing for limit values for warehouse orders, see the Implementation Guide (IMG) for EWM
under Cross-Process Settings Warehouse Order De ne Limit Values for the Size of a Warehouse Order.
Printing Warehouse Orders and Warehouse

Tasks
10/3/2019
Use
Extended Warehouse Management (EWM) can use this function to automatically print lists during creation of warehouse orders
and warehouse tasks, according to your Customizing settings. These lists contain information about the storage bin to and from
which a warehouse employee should move speci c goods.
You can use this function in the warehouse management monitor, from the user interface for warehouse tasks, to manually print a
warehouse order, which also prints all corresponding warehouse tasks. For example, the rst printout is damaged, or your require
a second printout.
Integration
Printing of warehouse orders and warehouse tasks is based on SAPscript texts and SAP Smart Forms as form templates.
EWM uses the Post Processing Framework (PPF) for message control.
Additionally, EWM uses condition technique in the schedule condition for PPF, in order to determine the printer, the form
type, and the spool parameter.
Note
For more information about the structure and Customizing for the Post Processing Framework, see the SAP Library
under SAP NetWeaver Components SAP Web Application Server Basis Services/Communication Interface (BC-
SRV) SAP Communication: Con guration (BC-SRV) Business Workplace and Services (BC-SRV-OFC) Generic
Business Tools for Application Developers (BC-SRV-GBT) Post Processing Framework (BC-SRV-GBT) .
Prerequisites
You have made the settings in Customizing for PPF :
You have de ned the PPF action de nitions with the relevant processing types.
In Customizing for the PPF action de nition, you have de ned the following data:
Processing time
Scheduling
Determination technique
Rule type
Action merging
You have speci ed the PPF conditions for the de ned PPF action de nitions.
In Customizing for the condition technique, you have de ned the condition tables.
In Customizing, you have de ned your condition tables from the eld catalog, which SAP delivers. You have selected elds
from the eld catalog as key elds. These elds represent the condition under which the condition technique nds the
condition record. If a data record transferred by EWM matches your key elds, then condition technique nds the matching
condition record.
In Customizing, you have de ned condition types, and therefore the access sequence to the condition tables to search.
In Customizing, you have assigned the relevant condition schemas to your condition types.
The condition schema speci es the conditions that you permit for determining data (such as printer, form type) and
speci es the sequence (access sequence) in which condition technique is to consider them.
10/3/2019
In Customizing, you have assigned the condition schema to the application object (warehouse process type, packaging
material type, work center).
In Customizing, you have de ned the condition maintenance group.
The condition maintenance group is required for creating condition records. The condition maintenance group speci es
the condition tables and therefore the key elds.
You have de ned the logical conditions that you want to use in the condition records.
You have de ned warehouse-number-speci c print settings (in particular the spool parameters).
Features
For printing warehouse orders, the following action de nitions are supported in PPF in the application /SCWM/WME in the action
pro le /SCWM/HU. These action de nitions were created for each form type, and thus enable you to simultaneously print several
different documents, for example, printing a warehouse order list and printing individual documents for the warehouse order.
For each action de nition there is also an SAP Smart Forms form. The system only supports printing of SAP Smart Forms. The
following table gives you an overview of the action de nitions and their corresponding SAP Smart Forms forms. The assignment
between action de nition and SAP Smart Forms form is speci ed in the created condition records.
Action De nition Description SAP Smart Forms Form
WO_MULTIPLE Print list for warehouse order with serial /SCWM/WO_MULTIPLE

numbers
WO_SINGLE Print single document for warehouse order /SCWM/WO_SINGLE

with serial numbers
WO_HUSHIP Print shipping label /SCWM/WO_HUSHIP
WO_LOAD Print loading instruction with warehouse /SCWM/WO_LOAD

tasks
WO_UNLOAD Print unloading instruction with warehouse /SCWM/WO_UNLOAD

tasks
During warehouse order creation, transfer order con rmation, and activation of product warehouse tasks, if you attempt to print
during storage control, then you automatically call up PPF. The decision whether to print is dependent on the condition records
that are found in the schedule condition. In the following circumstances, PPF triggers the executing method and therefore printing:
There is a condition record in which the PPF action de nition matches the current PPF action de nition.
The logical condition is entered in the condition record, and is ful lled.
During printing or repeat printing, you can also execute PPF action de nitions for which there are no de ned condition records. In
this case, the system cannot determine the necessary data such as printer, form name, and spool parameters, and you must enter
this data manually.
During printing, PPF writes a determination log and a processing log. Since these logs can become extremely large, you can switch
them on and off. To do this, use parameter /SCWM/WO_PRT_PROT.
Activities
EWM automatically triggers the print run from processing, or you trigger it manually.
EWM calls the PPF and transmits the application data.
10/3/2019
The PPF determines the PPF action de nitions you have de ned in Customizing for the PPF application /SCWM/WME and
the PPF action pro le /SCWM/WO.
The PPF calls the schedule condition that corresponds to the PPF action de nition.
In the schedule condition, the PPF calls determination in the condition technique.
Determination of the condition technique returns the relevant condition record. This determines the printer, spool
parameters, and the SAP Smart Forms form.
PPF reads the current application data.
PPF determines the function module that corresponds to the SAP Smart Form form, and calls up the application data.
PPF saves the action that was executed and the logs that were written.
Manual Assembly of Warehouse Orders

Use
You use this function in the goods receipt process to delete warehouse tasks of different handling units (HUs) from your
warehouse orders, and to group them together in a new warehouse order. This allows you to put away the HUs collectively, and
Extended Warehouse Management (EWM) is able to determine the optimal putaway path.
Prerequisites
You have made sure that putaway warehouse tasks exist and are active for the entire contents of the HU.
If EWM is to generate a single warehouse order for all warehouse tasks that belong to the HUs you have speci ed, you have
made sure that the warehouse activity area and queue for these warehouse tasks are identical (see Warehouse Order
Creation ).
If you want to print warehouse orders using a PPF action, you have scheduled a corresponding PPF action.
Features
This function is optimized so that you can operate it using a hand-held scanner that is installed on a keyboard lter. You can
specify multiple HUs in the entry eld, one after each other. EWM shows you the speci ed HU in the lower part of the screen, and
assigns the HU to a position eld, ascending. For example, you scan three HUs. EWM assigns the HU scanned rst to position one,
the next HU to position two, and the HU scanned last to position three. Make sure that the position of the HU in EWM matches the
physical position of the HU in the resource. When you perform putaway, EWM shows you the position in the Radio Frequency
dialog (RF dialog).
A traffic light shows the status of the warehouse task.
Green means that you have speci ed a valid HU, and that warehouse tasks exist for all products in the HU. EWM has
updated screen content for the total weight and total volume, and increased the number of HUs in the new warehouse
order that is to be created by one.
Red means that you have speci ed an HU, but that no warehouse task exists for at least one of the products in the HU.
EWM does not update the screen content for the total weight and total volume, and does not include the HU in the new
warehouse order that is to be created.
Activities
10/3/2019
On the SAP Easy Access screen, choose Extended Warehouse Management Execution Manually Assemble Warehouse
Orders.
After you have speci ed all the HUs, choose Save . In doing this, EWM deletes all warehouse tasks of the HUs from your
warehouse orders. EWM attempts to generate a warehouse order for all warehouse tasks, and saves the warehouse tasks in
this order.
EWM displays a success message if appropriate. If EWM generates one warehouse order only, you can take the warehouse
order number directly from the message. If EWM generates multiple warehouse orders, the message only contains the
number of warehouse orders. In this case, you can get the warehouse order number from the log.
EWM updates the screen content.
You can print the warehouse order in one of the following ways:
Using a Post Processing Framework action
Manually
Choose Work Center Print Last Warehouse Order .Under Create Action , choose the PPF action you require for
printing warehouse orders (see Printing Warehouse Orders and Warehouse Tasks ).
Pick, Pack, and Pass During Picking

Use
You use this function to coordinate picking, packing, and transportation of products in different activity areas in your warehouse.
For example, you transport products from one activity area to another using a conveyor belt. From an organizational point of view,
an activity area can correspond to an aisle, for which a warehouse worker is responsible. As soon as the warehouse worker has
picked a warehouse order in his area, he passes on the goods.
If you use this function, the system creates a higher-level warehouse order that contains the pick-HUs for all warehouse tasks that
are to be created, which you pick one after the other. The warehouse worker also receives the warehouse order created for his
activity area, together with its warehouse tasks.
Integration
You can use the Pick, Pack, and Pass function most efficiently in a radio frequency (RF) environment. The process ow is the same
as for "standard" RF picking. You only have to make the Customizing settings mentioned in the prerequisites in SAP Extended
Warehouse Management (SAP EWM).
For more information about RF picking, see RF Picking Flow.
Prerequisites
1. In Customizing for SAP EWM, de ne a warehouse order creation with the creation type for the pick, pack, and pass
function. You can choose between a system-controlled or user-controlled creation type.
Choose Extended Warehouse Management Cross-Process Settings Warehouse Order De ne Creation Rule for
Warehouse Orders. .
2. In Customizing for SAP EWM, de ne the determination of the warehouse order creation rule de ned in step 1 by doing one
of the following:
De ne a warehouse process type that contains the warehouse order creation rule de ned above.
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=20704074&topics=48890776d2b21b5ae10000000… 10/59
10/3/2019
De ne the search sequence in Customizing for SAP EWM.
Choose Extended Warehouse Management Cross-Process Settings Warehouse Order De ne Search Sequence
of Creation Rules for Activity Areas. .
3. In Customizing for SAP EWM, de ne a higher-level activity area for your activity areas by selecting the checkbox Merged.
Choose Extended Warehouse Management Master Data Activity Areas Activities De ne Activity Areas .
4. Assign the individual activity areas to the higher-level activity area in the order you require.
Choose Extended Warehouse Management Cross-Process Settings Warehouse Order Join Activity Areas Together. .
5. If you work with the system-controlled method, you have to de ne the source and destination storage bins for each activity
area.
On the SAP Easy Access screen, choose Extended Warehouse Management Master Data Storage Bin Assign Start/End
Storage Bin for Activity Area .
Features
The destination storage bins are different for RF picking using pick, pack, and pass and "standard" RF picking. In pick, pack, and
pass, warehouse workers pass the product from activity area to activity area until it arrives at the actual destination storage bin.
Picking Destination Storage Bin
RF picking Destination storage bin, such as goods issue area
RF picking using pick, pack, and pass Storage bin of activity area from where the product moves to the next activity
area
You can use this function in either a system-controlled or user-controlled way.
System-controlled pick, pack, and pass function
With this setting, the system speci es the sequence for processing the warehouse orders and corresponding pick-HUs.
It creates a higher-level warehouse order that contains all other warehouse orders that have been created. Only the rst
warehouse order in the sequence is active, all other warehouse orders are inactive. The sequence in which the system
orders the warehouse orders corresponds to the sequence that you have de ned in Customizing for the activity areas in
the warehouse order creation rules.
1. During warehouse order creation, the pick-HU determination determines the suitable pick-HUs for all warehouse
tasks of the warehouse order.
2. The system checks the warehouse order type. If you activated the pick, pack, and pass function, the system creates
a higher-level warehouse order that contains multiple warehouse orders sorted by activity area. The system only
passes on the "standard" warehouse orders to resource management in SAP EWM.
User-controlled pick, pack, and pass function
With this setting, the system creates the warehouse orders and the corresponding pick-HUs the same as for the system-
controlled pick, pack, and pass function. However, all created warehouse orders are active, and no sequence for processing
them exists. The user takes a warehouse order that is valid for his or her activity area.
Example
The warehouse workers pick in the three activity areas P1, P2, and P3 in a system-controlled way using pick, pack, and pass.
10/3/2019
1. The system creates a higher-level warehouse order containing seven warehouse tasks for the three activity areas P1, P2,
and P3, and determines the pick-HUs for all warehouse tasks.
2. It then distributes the warehouse tasks across the three activity areas.
3. Each of the three warehouse workers receives their own warehouse order.
4. The warehouse worker takes the pick-HU from the source storage bin of his or her activity area.
5. The worker perfoms picking and puts the pick-HU in the destination storage bin of his or her activity area.
6. The pick-HU is moved from the destination storage bin of the activity area to the source storage bin of the next activity
area.
7. The process is repeated from step 4. When it comes to the nal activity area (P3), the worker puts the pick-HU in the
original destination bin, such as the goods issue area, instead of in the destination storage bin of the activity area.
Interface Between EWM and Non-SAP

Systems
Use
SAP Extended Warehouse Management (SAP EWM) has an interface (EWM-WCU interface) that you can use to connect
automated warehouse systems such as warehouse control units to SAP EWM. For more information, see Scenarios for Connecting
10/3/2019
Non-SAP Systems and Description of the IDocs.
Integration
The interface allows communication between the connected systems on the basis of the transactional Remote Function Call
(tRFC). In contrast to synchronous RFC, the system saves the data in an intermediate storage area, before sending it to the
connected system. This leads to the decoupling of application and communication.
Scenarios for Connecting Non-SAP Systems

Use
You can use the interface between SAP Extended Warehouse Management (SAP EWM) and non-SAP systems (EWM-WCU
interface) to connect different non-SAP systems to SAP EWM. The following scenarios give you an overview of typical ways in
which this interface can be used.
Non-SAP systems include warehouse systems dependent on SAP EWM, such as warehouse control units.
Features
The EWM-WCU interface supports the following communication transactions between the systems:
Transfer warehouse tasks from SAP EWM to non-SAP system
Transfer release of multiple processing from SAP EWM to non-SAP system
Transfer cancellation requests from SAP EWM to non-SAP system
Create transfer orders in SAP EWM for warehouse tasks reported by non-SAP system
Con rm transfer orders in SAP EWM for warehouse tasks reported as complete by non-SAP system
Move handling units (see Handling Unit (HU))
Blocking storage units or aisles
Cancel transfer orders in SAP EWM for warehouse tasks not reported as complete by non-SAP system
SAP EWM takes on all tasks related to warehouse management. However, warehouse control and execution of driving commands
are not part of SAP EWM's tasks. For this reason, the non-SAP systems always represent standalone systems for the SAP system,
which can take on control of the product ow, as well as other tasks such as optimizing the stock movements or additional control
mechanisms.
The scenarios focus on the task distribution between SAP EWM and the relevant connected non-SAP system. The exibility of the
EWM-WCU interface enables you to make customer-speci c adjustments and enhancements. For more information, see
Modi cation Concepts: IDoc Inbound Processing and Modi cation Concepts: IDoc Outbound Processing.
Activities
You determine the task distribution, according to your own requirements, between SAP EWM and the non-SAP system.
Connecting a Semi-Automated Warehouse

10/3/2019
Purpose
In a semiautomatic warehouse, you manage the warehouse using Extended Warehouse Management (EWM), whilst a linked non-
SAP system performs the actual stock movements.
EWM performs all tasks relevant to warehouse management, including:
Managing product stocks and storage bins
Triggering warehouse movements (stock removal, putaway, stock transfers and posting changes)
Determining the storage bins for warehouse movements based on xed putaway and stock removal strategies
Carrying out the inventory
To optimize the processes in the warehouse you use EWM and a non-SAP system to:
Connect forklift systems
Control automatic conveyors or conveyor equipment
Allow picking without any documents, using RF devices
Control the product ow
Note
The following describes two variations of the scenario:
EWM does not transfer any data using the EWM-WCU interface to the non-SAP system. You can only use this
interface to tell EWM that stock movements have been performed.
The EWM-WCU interface is used to transfer pending stock movements to the non-SAP system, as well as to
report the execution of stock movements to EWM.
Prerequisites
You have con gured the interface between EWM and the non-SAP system in Customizing for Extended Warehouse Management
under Interfaces Non-SAP Systems Connect Subsystem .
Process
Reporting Using EWM-WCU Interface: Putaway
10/3/2019
1. EWM creates warehouse tasks (WTs) for the goods movements.
2. You print the warehouse tasks to use as a pallet receipt/issue slip.
The destination storage bin for putaway is printed on the pallet slip in the form of a barcode.
3. You transport the pallet to the automatic conveyor.
4. You scan in the barcode with the destination storage bin at the automatic conveyor.
5. The automatic conveyor carries the pallet to the storage bin and puts it away.
6. If the Customizing settings are such that the WT transferred from EWM must be reported to EWM, then the non-SAP
system reports the stock movement for the WT using the message type /SCWM/WMTOCO to EWM.
The non-SAP system constructs the warehouse task data in the form of an IDoc for the forklift guidance system, and sends
this IDoc to EWM.
7. EWM con rms the warehouse task using the data reported using message type /SCWM/WMTOCO .
Reporting Using EWM-WCU Interface: Stock Removal
10/3/2019
1. EWM creates warehouse tasks (WTs) for the stock removal.
2. You print the warehouse tasks to use as a stock removal list.
The source storage bin for stock removal is printed on the stock removal list in the form of a barcode.
3. You scan the barcode with the source storage bins into the automatic conveyor.
4. The automatic conveyor removes the pallet from storage.
If picking takes place directly at the storage bin, the automatic conveyor goes directly to the relevant source storage bin
when you scan in the stock removal slip.
5. If the Customizing settings are such that the WT transferred from EWM must be reported to EWM, then the non-SAP
system reports the stock movement for the WT using the message type /SCWM/WMTOCO to EWM.
this IDoc to EWM.
Transferring warehouse tasks for warehouse movements to the external system
10/3/2019
1. EWM creates warehouse tasks (WTs) for the goods movements.
2. EWM transfers the warehouse tasks using the message type /SCWM/WMTORD to the non-SAP system.
3. The external system executes the goods movements in the warehouse on the basis of the transferred data. The forklift
control system monitors all of the movements.
4. If the Customizing settings are such that the warehouse task transmitted from EWM must be reported to EWM, then the
non-SAP system reports the stock movement for the warehouse task using the message type /SCWM/WMTOCO to EWM.
this IDoc to EWM.
Triggering warehouse movements manually via the external system
1. If you trigger stock movements manually (for example, due to a stock transfer within a warehouse, or because you are
collating remainder quantities to make more room), then you enter the stock movement in the forklift guidance system.
2. The forklift guidance system reports the stock movement to EWM using message type /SCWM/WMTOCO .
this IDoc to EWM.
3. EWM creates a warehouse task using the data reported using message type /SCWM/WMTOCO , and updates the stock
data in the warehouse management system.
10/3/2019
Connecting a Fully Automated Warehouse

Purpose
If you want to use Extended Warehouse Management (EWM) in a fully automatic warehouse, consider the warehouse structure
and the automatic warehouse functions when deciding how to distribute the warehouse management tasks suitably between
EWM and the non-SAP system.
In fully automatic warehouses too, EWM takes on the most important tasks of warehouse management:
Managing the product stocks
Managing storage bins
Triggering warehouse movements (stock removal, putaway, stock transfers and posting changes)
Determining the storage bins for warehouse movements based on xed putaway and stock removal strategies
The external system takes over the entire warehouse controlling:
Controlling the conveyor equipment
Controlling the product ow
Optimizing resources
Note
If you want to use EWM with a fully automatic non-SAP system, you should also take account of the scenario
Connecting a Fully Automatic Warehouse as a Black Box .
Prerequisites
You have con gured the interface between EWM and the non-SAP system in Customizing for Extended Warehouse Management
under Interfaces Non-SAP Systems Connect Subsystem .
You have speci ed how warehouse management tasks will be distributed between EWM and the non-SAP system. Here, the level
of automation in the warehouse plays an important role:
In simple automatic warehouses, EWM takes on all warehouse management tasks. The non-SAP system only takes on
warehouse control, where the warehouse control can be used to optimize the stock movements triggered by EWM. For
more information, see Connecting a Semiautomatic Warehouse .
For warehouses with more complex warehouse automation, you should take account of the warehouse technology at
warehouse task creation. The external system then takes on some of the warehouse management tasks. For this reason,
you move products in this kind of storage type using identi cation points (ID points) and pick points.
Process
Putaway via ID points
10/3/2019
1. You receive an inbound delivery in the goods receipt interim storage area. You post the goods receipt for the inbound
delivery, and enter the pallet (handling unit) in EWM.
2. EWM determines the destination storage type for the delivered handling unit (HU).
3. If putaway is performed using an ID point, then EWM creates a warehouse task (WT) from the goods receipt interface to
the ID point.
4. EWM transmits the WT with the required data (including the pallet number) for putaway using the message type
/SCWM/WMTORD to the non-SAP system.
5. You print the WTs to use as a pallet receipt/issue slip.
The destination storage bin for putaway is printed on the pallet slip in the form of a barcode.
6. You transport the HU to the ID point.
7. The non-SAP system identi es the HU at the ID point using the bar code on the pallet slip.
8. To optimize capacity utilization of the conveyor vehicles during putaway, the non-SAP system assigns the destination
storage bin for the HU.
9. The non-SAP system moves the HU to the destination storage bin and puts the HU away.
10. The non-SAP system reports execution of the stock movement for the handling unit to EWM, using message type
/SCWM/WMSUMO .
The non-SAP system constructs the warehouse task data in the form of an IDoc for the non-SAP system, and sends this
IDoc to EWM.
10/3/2019
11. EWM creates the warehouse task for putaway using the data reported using message type /SCWM/WMSUMO , to post the
stock movement triggered by the non-SAP system.
Stock removal via a pick point
1. You trigger a stock removal or picking in EWM by, for example, collating the picking of several outbound deliveries into one
collective action.
2. EWM creates warehouse tasks (WTs) for the outbound deliveries.
3. EWM transfers the WTs using the message type /SCWM/WMTORD to the non-SAP system.
If you want to execute picking on the basis of outbound deliveries, the system treats each warehouse task that is
transferred as an independent pick order.
If you want to control picking based on other criteria (for example, based on a route), you must ensure that the non-SAP
system only picks the transmitted warehouse tasks after EWM has transmitted all the relevant WTs to the non-SAP system.
Caution
The non-SAP system can only collate the WTs into a wave after EWM has transmitted the wave release using message
type /SCWM/WMRREF .
4. The external system processes the pick order, which can consist of one or more transferred WTs.
5. The non-SAP system optimizes the individual stock movements from the pick order, by specifying the sequence in which
the required handling units should be removed from storage.
10/3/2019
If there is more than one ID point in the system, then the non-SAP system also speci es the assignment of the individual
picking transactions and HUs to the available pick points. Only the external system can ensure optimal pick point
assignment, since the utilization of the warehousing equipment is at the fore.
6. You execute picking at the pick point.
The external system displays the items to be picked on the screen at the pick point.
7. You con rm the pick and enter any differences that occured.
8. The non-SAP system reports execution of picking for the handling units to EWM, using message type /SCWM/WMTOCO .
this IDoc to EWM.
Return Transfer for Handling Units with Remaining Quantity
1. After picking, you take the HUs with remaining quantities to the ID point for return transfer into the warehouse.
2. The external system identi es the HU at the ID point, by way of a contour control.
3. To optimize capacity utilization of the conveyor vehicles during putaway, the non-SAP system assigns the destination
storage bin for the HU.
4. The non-SAP system moves the HU to the destination storage bin and puts the HU away.
5. The non-SAP system reports execution of the stock movement for the HU to EWM, using message type
/SCWM/WMSUMO .
The non-SAP system constructs the warehouse task data in the form of an IDoc for the non-SAP system, and sends this
IDoc to EWM.
6. EWM creates the warehouse task for putaway using the data reported using message type /SCWM/WMSUMO , to post the
stock movement triggered by the non-SAP system.
Blocking Storage Bins
In automatic warehouses, conveyor vehicles often cannot access certain storage bins.
Example
Certain routes for the vehicles are no longer valid, or some bins cannot be reached by the warehouse technology.
Since you are performing warehouse management using EWM, you must block these storage bins as quickly as possible in EWM,
so that EWM cannot schedule any more stock movements for these storage bins.
The non-SAP system transmits the storage bins to block using the message type /SCWM/WMBBIN to EWM.
To tell EWM to unblock blocked storage bins, the non-SAP system transmits the storage bins or aisles affected to EWM using
message type /SCWM/WMBBIN .
Connecting a Fully Automated Warehouse as

a Black Box
10/3/2019
Purpose
In your warehouse complex ( Warehouse Number ) that you manage using Extended Warehouse Management (EWM), you have
set up several different storage types . For one or more of these storage types, an external system executes all of the warehouse
functions and thus takes over the entire warehouse management and warehouse control for this storage type.
The automated storage type is connected as a black box to EWM. In this storage type, EWM hands over the entire warehouse
management and warehouse control to the non-SAP system. It does this because the storage type is highly automated and so
accurate and timely information about the current status of the warehouse technology is required for the stock movements.
Recommendation
If you want to connect this kind of storage type to your warehouse, we recommend that you implement a system that combines
warehouse controlling and warehouse management.
Since the automated storage type is only a part of your warehouse complex, you can manage the entire warehouse complex (the
warehouse number) using EWM . EWM distributes the individual putaway and stock removal transactions to the various sub-
storage-types. In storage types not managed by the non-SAP system, EWM takes on all the standard functions.
In storage types managed by the non-SAP system, EWM takes on the following functions:
Management of summary stocks for each product
Triggering and creating warehouse movements
On the other hand, the external system takes over the entire warehouse management and warehouse control within the storage
type:
Determining the storage bins for the individual warehouse movements
Creating warehouse movements within the storage type
Controlling the conveyor equipment
Controlling the product ow
Optimizing resources
Note
When making your decision concerning the type of interface connection, you should also take account of the scenario
for Connecting a Fully-Automated Warehouse .
Prerequisites
You have de ned the automated section of your warehouse as a separate storage type in EWM.
You can de ne a xed storage binfor each product in this storage type, to manage the stocks of product in this storage type
and to support physical inventory operations.
Alternatively, you de ne several storage bins in the warehouse type, which do not correspond to the physical storage bins.
You allow addition to existing stock for this storage type, so that the system always places a product into this storage type.
The system cumulates the stocks of a product in a storage bin. This means that a new product always occupies a new
storage bin.
10/3/2019
Note
The storage bins that you created in EWM for individual products have no meaning for the non-SAP system.
Process
EWM takes on communication with other SAP application components for the entire warehouse number.
Putaway
1. You post the goods receipt of the goods in Inventory Management.
2. EWM creates warehouse tasks for putaway and speci es in which storage type the goods are put away.
3. If you have selected the storage type managed by the non-SAP system for putaway, EWM transmits the relevant WT items
using the message type /SCWM/WMTORD to the non-SAP system.
4. The non-SAP system identi es the goods to put away using either the WT number and WT items, or using the transmitted
HU number.
5. If EWM reports execution goods movements, then the non-SAP system reports the putaway to EWM using message type
/SCWM/WMTOCO .
Stock Removal
1. EWM creates a warehouse task (WT) for the stock removal.
10/3/2019
2. EWM sends all stock removal WTs relevant for the storage type managed by the non-SAP system to the non-SAP system,
using message type /SCWM/WMTORD .
3. The non-SAP system decides the storage bin from which the required products should be removed.
4. The non-SAP system transfers the transfer orders using the message type /SCWM/WMTORD to EWM.
5. EWM con rms the individual items in the warehouse task, using the reported data and actual quantities from the non-SAP
system.
Handling Differences
If differences occur in the storage type managed by the non-SAP system during physical inventory or during productive
operations, the non-SAP system reports these differences to EWM using the message type /SCWM/WMTOCO .
EWM uses the reported differences to create a warehouse task, to post the reported differences to a difference interface.
Note
The non-SAP system must not send product movements within the storage type managed by the non-SAP system, because
EWM only manages the summary stocks for this storage type.
Data Flow: EWM Transmits Data

Purpose
The data ow via the interface between the non-SAP system and Extended Warehouse Management (EWM-WCU interface) is
explained using an example communication process ow for transmitting warehouse task data from EWM to the non-SAP system.
For more information about the business background, see Scenarios for Connecting Non-SAP Systems .
Prerequisites
You have made the required TCP/IP settings.
In Customizing, you have de ned the ALE interface. In Customizing, you have speci ed the circumstances in which a warehouse
task (WT) is relevant for transmission to the non-SAP system. For more information, see the Implementation Guide (IMG) for
Extended Warehouse Management under Interfaces Non-SAP Systems Connect Subsystem .
For each warehouse number, you can specify that WT items for the following criteria are relevant for transmission to the
non-SAP system:
For a storage type
For a warehouse process type or
For combination of storage type and warehouse process type
You de ne the external system, which receives the WT item.
Process
1. When you create a warehouse task (WT) in EWM, the Customizing settings de ne that the WT or WT item is relevant for
transmission to the non-SAP system.
2. During creation of the WT, the system prepares the data to be transmitted, in the form of an IDoc.
10/3/2019
Note
For more information about IDocs and their construction, see Description of the IDocs .
3. The system saves the created IDoc to the database.
4. Asynchronously to creation of the IDoc, the system uses ALE to trigger transmission of this IDoc to the non-SAP system.
The system can transfer individual IDocs or collect several IDocs and then transfer them to the external system later. The
transmission is based on Remote Function Call.
5. The non-SAP system must be ready to receive the transmitted data with a relevant program.
For more information, see Basis Basis Services/Communication Interface Remote Communications The RFC
API Programming with the RFC API .
6. The non-SAP system saves the received IDoc data, and sends a receipt con rmation to the SAP system.
Recommendation
We recommend that you save the transmitted data in the non-SAP system rst, to ensure that transmission of the IDoc
and processing of the transmitted data occur separately.
7. Status management for the data received should prevent the external system from processing the data twice.
The external system should be able to recognize IDocs that have been transferred by the SAP system before. This is made
possible by the unique transaction identi cation number (transaction ID), which the SAP system assigns for each
communication process. For more information, see Basis Basis Services/Communication Interface Remote
Communications The RFC API Transactional RFC Client Programs .
Note
The external system can also recognize double transfers from the IDoc number external system can also use the IDoc
number to identify duplicate transfers. Note that an IDoc number is only unique within a single client in an SAP system.
If several clients of an SAP system or several SAP systems are involved in the communication with the external system,
the IDoc number is no longer unique. In this case the external system cannot recognize IDocs that have been
transferred twice from this number.
Error Processing
If you receive an IDoc from EWM to a non-SAP system, the following problems can occur:
Troubleshooting
Symptom What You Should Know
Update termination in the SAP system during the application An update termination during creation of a warehouse task does not
affect communication with the external system, because the system
only creates an IDoc once the source SAP system document exists.
The WT and the IDoc are creates in the same LUW, therefore they
are updated synchronously.
Error in the ALE interface: ALE adopts the IDoc and saves it, but cannot transfer the IDoc to
the external system. For more information, see IDoc Error
Transferred data is syntactically incorrect
Processing .
10/3/2019
Error in the ALE interface: For more information, see IDoc Error Processing .
The outbound partner pro le for the receiving system
The IDoc message type
are not de ned
There is no connection between the SAP system and the external The SAP system tries to set up the connection to the external
system system by running a report in the background at a later time. As
soon as the connection between the two systems exists again, the
SAP system automatically transfers all IDocs, which have not yet
been sent. You can also start this report manually. For more
information, see Processing Technical IDoc Errors .
Managing TCP/IP Settings

As a prerequisite for communication, you make the following TCP/IP settings:
In order for the SAP system to nd the target system, you must ful ll the TCP/IP prerequisites, in particular the IP
addresses must be known in the relevant hosts le.
You have entered the name of the gateway and the dispatcher in the services le, for example, sapgw00 and sapdp00.
In the standard system, IDocs are sent from the update transaction. Ensure that the TCP/IP link was also created for the
update machine.
You work in registration mode. This means that the connection between the non-SAP system program and the gateway
remains open. For more information, see Registering Server Programs with the SAP Gateway .
If you do not work in registration mode, then the SAP gateway must have the authorization to start the external program
(RFC server) using Remote Shell.
Managing Transaction Identi ers (TID)

Purpose
To ensure the security of the data to transfer, you must work with a unique identi er for a communication transaction. This ID
allows the receiving system to recognize whether this data has already been received and processed.
Process
The following diagram shows the schematic process ow between the sending and receiving system:
10/3/2019
Example
For example, communication could be terminated suddenly during the transmission of data for mobile entry of goods receipts.
The processor would send the data again to ensure your update in the SAP system. However, if the data had already been received
and processed in the the SAP system after the rst attempt at sending, the system must be able to recognize this. It should not
process the data a second time.
10/3/2019
Data Flow: EWM Receives Data

Purpose
The data ow via the interface between the non-SAP system and Extended Warehouse Management (EWM-WCU interface) is
explained using an example communication process ow for transmitting data for the warehouse task (WT) from the non-SAP
system to EWM.
For more information about the business background, see Scenarios for Connecting Non-SAP Systems .
Prerequisites
You have de ned the necessary TCP/IP settings.
You have con gured the ALE interface in Customizing for Extended Warehouse Management under Interfaces Non-SAP
Systems Connect Subsystem .
Process
1. The non-SAP system saves the data relevant for transmission to the SAP system, and prepares this data for transmission
as an IDoc.
2. The external system transfers the IDoc with an appropriate program.
The transmission is based on Remote Function Call (BC-ABA). For more information, see Programming with the RFC API .
The central function module is in the ALE layer. As soon as the external system calls the function module on the SAP system side,
the external system can transfer several IDocs.
Note
If an IDoc type only supports single transmission, then the IDoc system documentation explicitly states this fact.
1. Status management for the data to be transferred should prevent the external system from not transferring data.
Note
If the non-SAP system cannot successfully transmit IDocs, you must ensure that the non-SAP system transmits these
IDocs again at a later point.
2. The SAP system should be able to recognize IDocs that have been transferred by the external system already. This is made
possible by the unique transaction identi cation number (transaction ID), which the SAP system assigns for each
communication process. For more information, see Transactional RFC Client Programs .
The non-SAP system must always ag the transmitted data with this transaction ID. If the non-SAP system re-transmits an
IDoc due to a previous problem with communication, then the non-SAP system must specify the same transaction ID
again.
Caution
The SAP system does not use the IDoc number to recognize a double transfer of IDocs from the external system.
10/3/2019
3. The SAP system receives the transmitted IDoc using ALE, saves the IDoc in the database, and reports the receipt of the
IDoc to the non-SAP system.
4. Asynchronously to the receipt of the IDoc, ALE transmits the IDoc to EWM, which then takes over processing of the IDoc.
5. EWM uses the transmitted data as the basis for creating warehouse tasks.
6. For each IDoc, EWM reports the processing status to ALE.
ALE uses the processing status to trigger error processing for the IDoc.
Error Processing
If you receive an IDoc from the non-SAP system in EWM, the following problems can occur:
Troubleshooting
There is no connection between the external system and the SAP The non-SAP system should use status management to ensure that
system the non-SAP system re-transmits the IDocs again at a later point.
Error in the ALE interface: Although ALE copies the IDoc and saves it, ALE cannot transmit the
IDoc to EWM for processing. For more information, see IDoc Error
There are syntactical errors in the data that the external system
Processing .
sent to the ALE
Error in the ALE interface: For more information, see IDoc Error Processing .
Inbound partner pro le for the sending system
IDoc message type
are not de ned
Error in the application for EWM If processing of the received IDoc did not proceed correctly, EWM
transmits the relevant processing status. For more information, see
Processing Logical IDoc Errors in EWM .
Data Formatting
The system transfers data to structures EDI_DC40 and EDI_DD40 . Since EDI also uses these structures, this means that some
elds are redundant for the EWM-WCU interface.
For more information, see Inbound Processing: Technical Realization .
EDI_DD40
Field Format Name Relevant for Receipt Comments
TABNAM CHAR 10 Table structure name Not relevant
MANDT CLNT 3 Client Not relevant, but the

system transmits the
eld to the non-SAP
system.
DOCNUM CHAR 16 IDoc number X Unique communication

number
10/3/2019
SEGNUM CHAR 6 SAP segment number Sequential numbering of

IDoc segments is
transferred to the
external system, but is
not required during
receipt.
SEGNAM CHAR 10 SAP segment name X IDoc segment name
PSGNUM CHAR 6 Number of higher-level The system transmits the

SAP segment eld to the non-SAP
system, but is not
required at receipt.
HLEVEL CHAR 2 Hierarchy level of SAP The system transmits the

segment eld to the non-SAP
system, but is not
DTINT2 CHAR 2 Empty eld for EDI_DD Not relevant
SDATA LCHR 1000 Application data X Actual application data in

form of IDoc segment
EDI_DC40
TABNAM CHAR 10 Table structure name
MANDT CLNT 3 Client
DOCNUM CHAR 16 IDoc number X Unique communication

number
DOCREL CHAR 4 IDoc SAP release The system transmits the

eld to the non-SAP
system, but is not
STATUS CHAR 2 IDoc status
DOCTYP CHAR 8 IDoc type Recommended as

IDOCTYP
DIRECT CHAR 1 Direction
RCVPOR CHAR 10 Recipient port Not relevant
RCVPRT CHAR 2 Partner type of recipient X Value: LS
RCVPRN CHAR 10 Partner number of X For example:

recipient WM_SUB_00 1 for SAP to
SUB
RCVSAD CHAR 21 EDI: Total SADR elds
RCVLAD CHAR 70 Logical address of

recipient
STD CHAR 1 EDI standard
STDVRS CHAR 6 Version of EDI standard
10/3/2019
STDMES CHAR 6 EDI message type
MESCOD CHAR 3 Logical message code * You can use both elds to
specify a different
function module than the
standard function
module in the ALE
service level, in the table
for inbound methods,
which is used to process
IDocs.
MESFCT CHAR 3 Logical message function * You can use both elds to
specify a different
function module than the
standard function
module in the ALE
service level, in the table
for inbound methods,
which is used to process
IDocs.
OUTMOD CHAR 1 Output mode
TEST CHAR 1 Test indicator
SNDPOR CHAR 10 Sender port Not relevant
SNDPRT CHAR 2 Partner type of sender X Value: LS
SNDPRN CHAR 10 Partner number of X For example:

sender S11MAND000, if S11 is
the sending SAP system
SNDSAD CHAR 21 EDI: Total SADR elds
SNDLAD CHAR 70 Logical address of sender
REFINT CHAR 14 Reference to transfer

data
REFGRP CHAR 14 Reference to message

group
REFMES CHAR 14 Reference to message

type
ARCKEY CHAR 70 EDI archive key
CREDAT DATS D 8 IDoc creation date
CRETIM TIMS T 6 IDoc creation time
MESTYP CHAR 6 Logical message type X For example WMTORD

for warehouse tasks
IDOCTYP CHAR 8 Name of basis IDoc X For example: WMTOID01

for WTs
CIMTYP CHAR 8 Name of intermediate

structure
10/3/2019
RCVPFC CHAR 2 Partner function of

recipient
SNDPFC CHAR 2 Partner role of sender
SERIAL CHAR 20 EDI/ALE: Serialization

eld
EXPRSS CHAR 1 Override during receipt
Note
You do not have to enter data in all elds of EDI-DC or EDI_DD. Make sure that you initialize any elds in which you will not
enter data.
If you create IDoc in R/3 systems using transaction /nWE30, the system automatically creates three structures for each IDoc,
which the system numbers. For example, for the warehouse task item /SCWM/E1LTORI, /SCWM/E2LTORI, and /SCWM/E3LTORI.
/SCWM/E1LTORI is release-independent, /SCWM/E2LTORI is release-dependent, and the system uses /SCWM/E3LTORI for
documentation.
Recommendation
We recommend choosing the E2 segment names during transfer of the segment name, since this is independent of the SAP
release.
Example
If, for example, you send a warehouse task with three items per IDoc from the non-SAP system to Extended Warehouse
Management (EWM), you transmit one header segment and three item segments for each IDoc. In doing so, you send one EDI-
DC40 record and four EDI_DD40 records per IDoc. The system collates the four IDoc segments together under the unique number
of the IDoc or the intermediate document. The corresponding EDI_DC record is also identi ed from the DOCNUM.
You transfer two internal tables with the following construction:
EDI_DD40
9000000000123456 /SCWM/E2LTORH 00112345678905011E (WT header data)
9000000000123456 /SCWM/E2LTORI 0001FRASCATI (Item)
9000000000123456 /SCWM/E2LTORI 0002BORDEAUX (Item)
9000000000123456 /SCWM/E2LTORI 0003CHIANTI (Item)
9000000000123457 /SCWM/E2LTORH 00112345678912011A (WT header data)
9000000000123457 /SCWM/E2LTORI 0001CHATEAU-NEUF (Item)
9000000000123457 /SCWM/E2LTOR 0002BORDEAUX (Item)
9000000000123457 /SCWM/E2LTORI 0003SOAVE ... (Item)
EDI_DC40
9000000000123456 LS S11MAND002 LS SUBSYSTEM1 /SCWM/WMTORD WMTOID01
9000000000123457 LS S11MAND002 LS SUBSYSTEM1 /SCWM/WMTORD WMTOID01
10/3/2019
Description of the IDocs

The interface between SAP Extended Warehouse Management and non-SAP systems (EWM-WCU interface) uses the following
IDocs:
IDoc Partner Agreement Message Type Name
/SCWM/WMTOID01 Inbound and outbound /SCWM/WMTORD Warehouse task
/SCWM/WMTCID01 Inbound /SCWM/WMTOCO Con rm warehouse tasks
/SCWM/WMCAID01 Inbound and outbound /SCWM/WMCATO Cancellation/cancellation

request WT
/SCWM/WMBIID01 Inbound /SCWM/WMBBIN Block storage bins
/SCWM/WMRRID01 Outbound /SCWM/WMRREF Release waves
/SCWM/WMSUID01 Inbound /SCWM/WMSUMO Move handling unit
/SCWM/WMPHID01 Inbound and outbound /SCWM/WMPIHU Create and send pick-HUs
IDoc for Sending WTs to a Non-SAP System

Use
In SAP Extended Warehouse Management (SAP EWM), you use IDoc /SCWM/WMTOID01 to send data from warehouse tasks in
SAP EWM to connected non-SAP systems.
SAP EWM creates a warehouse task order for every warehouse movement, regardless of whether the movement is putaway, stock
removal, stock transfer, or a posting change. SAP EWM transfers the warehouse task data to the connected external system in the
form of IDoc /SCWM/WMTOID01.
The external system requires a precise division of warehouse movements according to type. You should differentiate between the
warehouse tasks according to the respective warehouse movement type as follows:
Based on the following data in the warehouse task:
Warehouse process type
Transfer type
Based on the storage types involved in the warehouse movement
Based on the variant of the SAP EWM message, which you de ned in the de nition of the movement for connection to the
interface.
Which IDoc the system lls and sends to the external system depends on several criteria as follows:
Criteria Details
10/3/2019
Criteria Details
Warehouse movement type

Putaway
Stock removal
Stock transfer
Posting change
Warehouse process type De ning the warehouse process type
You de ne, for example, whether the goods receipt date should be
set during putaway.
Cause of the warehouse task

Manual warehouse task
Warehouse task for inbound or outbound delivery
Warehouse task for warehouse process type
Handling-unit (HU)-managed storage types If HU-managed storage types are affected by the warehouse
movement, the system transfers the numbers of the storage units
involved.
For putaway in HU-managed storage types, the system

transfers the HU number in the NLENR eld.
For stock removals from HU-managed storage types, the

system transfers the HU number in the VLENR eld.
For stock transfers between HU-managed storage types,

the system transfers the HU number in both elds.
If you transfer the complete HU, both HU numbers are the

same. If you transfer material from one HU to another, the
system transfers both HU numbers involved.
Recommendation
You determine the content on the IDoc for the individual customers. We recommend creating test warehouse tasks for
transmission to the external system, so that you can check the content of the IDocs, which the system creates.
Structure
Message Type
You de ne the partner agreement outbound for message type /SCWM/WMTORD.
Segments
IDoc /SCWM/WMTOID01 is made up of the following segments:
/SCWM/E1LTORH (warehouse task header)
/SCWM/E1LTORI (warehouse task items)
/SCWM/E1LPHUX (pick-HU)
10/3/2019
/SCWM/E1LCRSE (serial numbers for warehouse tasks)
Segment Definition /SCWM/E1LTORH001 (Warehouse Task Header)
Field Data Type Description Required Entry Comment
LGNUM CHAR 3 Warehouse number X Activate linkage in

warehouse number rst
WHO NUMC 10 Warehouse order
QUEUE NUMC 10 Queue
BNAME CHAR 12 User name
LSD_DATE DATS 8 Latest starting date

(LSD) - date part
LSD_TIME TIMS 6 Latest starting date

(LSD) - time part
PLANDURA QUAN 15 Planned execution time

of warehouse order
UNIT_T UNIT 3 Warehouse order: time

unit
Segment Definition /SCWM/E1LTORI001 (Warehouse Task Items)
Field Data Type Description
TANUM NUMC 12 Warehouse task
PROCTY CHAR 4 Warehouse process type
MATNR CHAR 40 Product
ENTITLED CHAR 10 Party entitled to dispose
ENTITLED_ROLE CHAR 2 Partner role
OWNER CHAR 10 Owner
OWNER_ROLE CHAR 2 Partner role
CHARG CHAR 10 Batch
LETYP CHAR 4 Handling unit type
ANFME QUAN 31 Requested quantity
ALTME UNIT 3 Alternative unit of measure (AUoM)
OPUNIT UNIT 3 Operative unit of measure (UoM)
VSOLA QUAN 31 Target quantity in AUoM
VSOLM QUAN 31 Target quantity in base UoM
MEINS UNIT 3 Base unit of measurement
VLTYP CHAR 4 Source storage type
VLBER CHAR 4 Source storage section
VLPLA CHAR 18 Source storage bin
10/3/2019
NLTYP CHAR 4 Destination storage type
NLBER CHAR 4 Destination storage section
NLPLA CHAR 18 Destination storage bin
VLENR CHAR 20 Source HU
NLENR CHAR 20 Destination HU
TRART CHAR 1 Warehouse process category
PROCS CHAR 4 External warehouse process
PRCES CHAR 4 Warehouse process
WDATU DATS 8 GR date
WDATZ TIMS 6 GR time
VFDAT DATS 8 Expiration date
ZEUGN CHAR 10 Certi cate number
KOMPL CHAR 1 Complete indicator
SQUIT CHAR 1 Con rmation indicator
KZQUI CHAR 1 Con rmation requirement
MAKTX CHAR 40 Product description
DOCCAT CHAR 3 Reference document category
DOCNO CHAR 35 Reference document number
ITEMNO CHAR 10 Reference document item
KZNKO CHAR 1 Zero stock check
CAT CHAR 2 Stock type
STOCK_DOCCAT CHAR 3 Document category
STOCK_DOCNO CHAR 35 Document number
STOCK_ITEMNO CHAR 10 Document item
WAVE NUMC 10 Wave
FLGHUTO CHAR 1 Handling unit warehouse task indicator
PRIORITY INT1 Priority
PICK_COMP_DATE DATS 8 Picking completion date
PICK_COMP_TIME TIMS 6 Picking completion time
IDPLATE CHAR 20 Identi cation number of stock
PICK_ALL CHAR 1 Withdraw all stock from storage bin
DSTGRP CHAR 10 Consolidation group
Segment Definition /SCWM/E1LPHUX001 (Pick-Handling Unit)
10/3/2019
LGNUM CHAR 3 Warehouse number X Switch on linkage in

warehouse number
WHO CHAR 10 Warehouse order
HUIDENT CHAR 20 Pick-handling unit
HUKNG NUMC 3 HU identi cation
PMAT CHAR 40 Packaging material
ANZHU NUMC 3 Number of pick-HUs to

create
KZRTN CHAR 1 Con rmation to

subsystem
LETYP CHAR4 Handling unit type
LGTYP CHAR 4 Storage type
LGPLA CHAR 18 Storage bin
RSRC CHAR 18 Resource (means of

transportation or user)
Segment Definition /SCWM/E1LCRSE000 (Serial

Numbers for Warehouse Tasks)
SERID CHAR 30 Serial number
IDoc for Receiving WTs from a Non-SAP

System
De nition
You use IDoc /SCWM/WMTCID01 to send warehouse-task-relevant data from the non-SAP system to SAP Extended Warehouse
Management (SAP EWM).
Use
The external system triggers warehouse movements in a warehouse type and executes the physical transportation of products.
Only then does the non-SAP system transfer the data on the warehouse movements to SAP EWM.
You construct IDoc /SCWM/WMTOID01 in the non-SAP system to transfer the warehouse movement data to SAP EWM. SAP EWM
receives the IDoc and creates a warehouse task from it to execute the physical warehouse movements and post the storage bins
involved. SAP EWM creates a warehouse task from the IDoc data it received and immediately con rms it.
You can also create warehouse tasks with incomplete entries in the non-SAP system and send these to SAP EWM. In this case,
SAP EWM, as the leading system, adds the missing entries (for example, the coordinates of the destination storage bin) and sends
10/3/2019
the complete warehouse task back to the external system. The non-SAP system con rms the warehouse task, completing the
warehouse movement.
Structure
Message Type
You de ne the partner agreement inbound for message type /SCWM/WMTORD.
Segments
IDoc /SCWM/WMTOID01 is made up of the following segments:
/SCWM/E1LTORH (warehouse task header)
/SCWM/E1LTORI (warehouse task items)
/SCWM/E1LPHUX (pick-handling unit)
/SCWM/E1LCRSE (serial numbers for warehouse tasks)
For more information about segment de nition, see IDoc for Sending WTs to a Non-SAP System.
Recommendation
Only use warehouse process types for this IDoc that allow immediate con rmation. The physical stock movement has already
taken place when you receive information on a warehouse task from the non-SAP system in SAP EWM.
IDoc for Con rming Warehouse Tasks

De nition
You use IDoc /SCWM/WMTCID01 to send con rmations from the non-SAP system to SAP Extended Warehouse Management
(SAP EWM).
Use
You use this IDoc to report executed warehouse tasks to SAP EWM. SAP EWM uses this reported data to con rm this warehouse
task.
Prerequisites
You have speci ed which warehouse tasks are subject to a con rmation requirement in Customizing for Extended Warehouse
Management under Master Data De ne Storage Type or Cross-Process Settings Warehouse Task De ne Warehouse Process
Type .
When sending the warehouse task data, SAP EWM previously transmitted the data for the con rmation requirement in IDoc
/SCWM/WMTOID01 in segment /SCWM/E1LTROI with eld KZQUI to the non-SAP system.
Con rmation of Handling Units
If you work with handling units (HUs) in your warehouse and move the entire HU, then you for this stock movement you con rm a
warehouse task for the entire HU.
10/3/2019
If the HU is a mixed HU and you move individual products, then there are several warehouse tasks for this HU. You con rm the
relevant warehouse task for each stock movement.
During execution of the warehouse tasks, if you notice differences in the HU, then you con rm the entire HU and enter the
difference quantity for those items where you noticed a difference.
Con rmation Without HU Management
For stock removals, you con rm entire warehouse tasks.
For putaway, you can con rm the warehouse tasks item by item, if you are putting away several pallets in your warehouse using
one warehouse task.
During con rmation of entire warehouse tasks, you can enter differences for individual warehouse task items.
Con rmation of Products Managed in Batches
If you con rm batch-managed products during goods movements in a HU-managed bulk storage type, you transmit the batch
number of the removed products with the con rmation data. You use the CHARG eld (report batch for bulk storage) in segment
/SCWM/E1LTCOI001.
Con rmation in a HU-Managed Bulk Storage Area
You report the picked HUs to SAP EWM when you con rm the warehouse task.
If the reporting of individual HUs is completed for a warehouse task item, set the BQUIT eld in segment /SCWM/E1LTCOI.
In this case, you report the warehouse task item by item. There can be several reports for each warehouse task item. Only one
report is allowed for each picked HU.
Note
If the products are managed in batches, then you transfer the batch number of the products moved when you transfer the
con rmation data. You use the CHARG eld (report batch for bulk storage) in segment /SCWM/E1LTCOI001.
Structure
Message Type
You de ne the partner agreement inbound for message type /SCWMWMTOCO.
Segments
The IDoc for transferring con rmation is constructed as follows:
/SCWM/WMTCID01
/SCWM/E1LTCOX: Con rm entire HU
/SCWM/E1LTCOH: Con rm warehouse task header
/SCWM/E1LTCOI: Con rm warehouse task items
/SCWM/E1LCOHU: Con rm HU data for each warehouse task item
/SCWM/E1LEXCP: Exception during warehouse task con rmation
10/3/2019
/SCWM/E1LCNFS: Serial numbers for warehouse task con rmation
Segment Definition /SCWM/E1LTCOX001: Confirm Handling Unit
LGNUM CHAR 4 Warehouse number X
LENUM CHAR 20 Handling unit X
QNAME CHAR 12 User name for the

con rmation
SQUIT CHAR 1 Con rm entire HU X Value: ʻX’
NLPLA CHAR 18 Destination storage The destination

bin storage bin refers to
the different storage
bin for the complete
HU (Customizing)
NLENR CHAR 20 Destination handling

unit
RSRC CHAR 18 Resource (Means of

Transportation or
User)
PROCESSOR CHAR 12 Processor
STARTED_DATE DATS 8 Start Date
STARTED_TIME TIMS 6 Start Time
CONFIRMED_DATE DATS 8 Con rmation Date
CONFIRMED_TIME TIMS 6 Con rmation Time
Segment Definition /SCWM/E1LCOHU000: HU Data for Each Warehouse Task Item
TANUM NUMC 12 WT number
VONHU CHAR 20 Source HU
NACHU CHAR 20 Destination HU
HUENT CHAR 1 Remove entire HU
MENGA QUAN 31 Quantity
ALTME CHAR 3 Alternative unit of measure (AUoM)
DMEGA QUAN 31 Difference quantity
PAPOS NUMC 4 Sequential number of the HU data line

within a WT item
Segment Definition /SCWM/E1LTCOH001: Warehouse Task Header
10/3/2019
WHO CHAR 12 Warehouse order
QNAME CHAR 12 User name for the

con rmation
SQUIT CHAR 1 Indicator: Con rm X If the entire

entire warehouse task warehouse task is to
be con rmed.
(Version 2, 3, and 5)
RSRC CHAR 18 Resource (Means of

Transportation or
User)
PROCESSOR CHAR 12 Processor
STARTED_DATE DATS 8 Start Date
STARTED_TIME TIMS 6 Start Time
CONFIRMED_DATE DATS 8 Con rmation Date
CONFIRMED_TIME TIMS 6 Con rmation Time
Segment Definition /SCWM/E1LTCOI001: Warehouse Task Items
TANUM CHAR 12 Warehouse task
SQUIT CHAR 1 Indicator: Con rm X If the item is to be

without difference con rmed without
any differences
NISTA QUAN 31 Destination actual X If there are

quantity differences in the
destination storage
bin
NDIFA QUAN 31 Destination difference X If there are

quantity differences in the
destination storage
bin
KZNUL CHAR 1 Indicator: Bin empty X If there is a zero stock

on zero stock check check
ALTME CHAR 3 Unit of measure X If quantity is entered
KZDIF CHAR 1 Differences indicator X If you want to post

differences to certain
interim record for
differences
LENUM CHAR 20 Handling unit number X In case of

con rmation in bulk
storage
10/3/2019
VQUIT CHAR 1 Con rmation in bulk X In case of

storage area, pick con rmation in bulk
entire HU storage
NLPLA CHAR 18 Destination storage If the destination

bin storage bin differs
from that suggested
by the system
PAPOS NUMC 4 Sequential number of

the HU data line within
a WT item
PARTI CHAR 1 Con rming a partial Only relevant for

quantity for a WT item handling units (HUs)
CHARG CHAR 10 Report batch number

for bulk storage area
CWQUAN QUAN 31 Valuation Quantity
CWQUAN_DIFF QUAN 31 Valuation Quantity

Difference
CWUNIT UNIT 3 Unit for Valuation

Quantity
Segment Definition /SCWM/E1LEXCP000: (Exception During Warehouse Task Confirmation)
PAPOS NUMC 4 Sequential number of the DB data line

within a WT number
EXCCODE CHAR 4 Exception code
BUSCON CHAR 3 Business context
EXEC_STEP CHAR 2 Execution step in business context
Segment Definition /SCWM/E1LCNFS000: (Serial Numbers for Warehouse Task Confirmation)
PAPOS NUMC 4 Sequential number of the DB data line

within a WT number
DIFF CHAR 1 Checkbox
SERID CHAR 30 Serial number
IDoc for Canceling Warehouse Tasks

10/3/2019
De nition
Using IDoc /SCWM/WMCAID01, you can send a cancellation request to an external system, or con rm execution of a cancellation
movement to SAP Extended Warehouse Management (SAP EWM).
Use
When physical stock movements are executed via the connected non-SAP system, SAP EWM cannot determine whether the
warehouse tasks transferred to the non-SAP system have already been executed. For this reason, SAP EWM can only send a
cancellation request to the non-SAP system.
The non-SAP system then decides whether or not the movement has already been executed. If the stock movement has already
been executed, the external system con rms to SAP EWM that the stock movement has already been completed and that
cancellation is therefore no longer possible. In this case, the user receives a corresponding message in SAP EWM.
You decide for each individual case what should happen with a warehouse task item that cannot be canceled. In this case, you
make the necessary adjustments manually in the system.
Note
You can only cancel warehouse tasks if they have not yet been con rmed.
Sending a Cancellation Request from SAP EWM to the Non-SAP System
To send a cancellation request from SAP EWM, ll the following elds in IDoc /SCWMWMCAID01/:
Segment Field
/SCWM/E1LTCAH000 LGNUM
WHO
CANRQ
/SCWM/E1LTCAI000 TANUM
Sending a Cancellation from the Non-SAP System to SAP EWM
To send a cancellation of a warehouse task to SAP EWM, ll the following elds in IDoc /SCWM/WMCAID01:
Segment Field
/SCWM/E1LTCAH000 LGNUM
WHO
CANCL
/SCWM/E1LTCAI000 TANUM
Note
You can also cancel a warehouse task from the non-SAP system and send the cancellation to SAP EWM, even if SAP EWM has
not sent a cancellation request rst.
Structure
10/3/2019
Message Type
You de ne message type /SCWM/WMCATO for the inbound and outbound partner pro le.
Segments
IDoc /SCWM/WMCAID01 is made up of two segments:
/SCWM/E1LTCAH (header data for the warehouse task)
/SCWM/E1LTCAI (item data for the warehouse task)
Segment Definition /SCWM/E1LTCAH000
WHO CHAR 12 Warehouse order X
CNAME CHAR 12 User name for WT

cancellation
CANRQ CHAR 1 Request cancellation X X for cancellation

warehouse task request
CANCL CHAR 1 Response cancellation X X for cancellation from

warehouse task external system
Segment Definition /SCWM/E1LTCAI000
TANUM CHAR 12 Warehouse task X
VLENR CHAR 20 Source HU X
NLENR CHAR 20 Destination HU X
SFEHL CHAR 1 Error during cancellation
SFTXT CHAR 80 Error text for cancellation This text appears in the
inbox for error messages
IDoc for Releasing Waves

De nition
IDoc /SCWM/WMRRID01 is used to release transfer orders for a wave pick that have already been sent to a non-SAP system. The
system sends the group number to the header data of the warehouse task to be created.
Use
Prerequisites
You have transferred the wave number to the non-SAP system using IDoc /SCWM/WMTOID01 in segment /SCWM/E1LTORHI for
the warehouse tasks that have been grouped together into waves.
10/3/2019
Features
You group together the warehouse tasks into a wave so that you can execute the goods movements for these warehouse tasks in
one step. For example, processing warehouse tasks for a certain shipping point or removing stock in the same interim storage
type. In this case, you are not permitted to execute the goods movement immediately after the non-SAP system receives the
warehouse task data. You use IDoc /SCWM/WMRRID01 to trigger the start of the stock movements for a certain wave by releasing
the wave.
Structure
Message Type
You de ne the partner agreement outbound for message type /SCWM/WMRREF.
Segments
The IDoc is made up of segment /SCWM/E1LRRFX.
Segment Definition /SCWM/E2LRRFX000
LGNUM CHAR 3 Warehouse number
WAVE CHAR 10 Wave
DATUM CHAR 8 Date
UZEIT CHAR 6 Current time
L2KSR CHAR 1 Relevance for two-step picking
LSKSO CHAR 1 Two-step picking: Release approval level
IDoc for Blocking Storage Bins

De nition
Using IDoc /SCWM/WMBIID01, you can send individual storage bin data or comprehensive storage bin data (for example all of
the storage bins in one aisle) for blocking or unblocking from the non-SAP system to SAP Extended Warehouse Management
(SAP EWM).
Use
When, for example, certain storage bins or aisles are inaccessible for the external system due to technical problems, you block
these storage bins in SAP EWM so that they are not considered during storage bin determination.
The non-SAP system initializes the block on the storage bins via IDoc /SCWM/WMBIID01. As soon as the storage bins are
available again, the external system triggers the unblocking of the non-SAP system by SAP EWM via IDoc /SCWM/WMBIID01.
Structure
Message Type
You de ne the partner agreement inbound for message type /SCWM/WMBBIN.
10/3/2019
Segments
IDoc /SCWM/WMBIID01 is made up of the following segments:
/SCWM/E1LBINH (blocking storage bins IDoc header)
You determine whether blocking or unblocking storage bins is involved.
To block storage bins, set the BLOCK indicator.
To unblock storage bins, set the DEBLO indicator.
/SCWM/E1LBINI (blocking storage bins IDoc items)
To block certain storage bins individually, transfer a /SCWM/E1LBINI segment for each storage bin.
Segment Definition /SCWM/E1LBINH000
LGTYP CHAR 4 Storage type X
BLOCK CHAR 1 Blocking storage bins X Either BLOCK or

DEBLO
DEBLO CHAR 1 Unblocking storage bins X Either BLOCK or

DEBLO
Segment Definition /SCWM/E1LBINI000
LGPLA CHAR 18 Storage Bin X Entry also generic, for

example 01
SKZUA CHAR 1 Block indicator: For stock X At least one of the three
removal indicators
SKZUE CHAR 1 Block indicator: For X At least one of the three

putaway indicators
SKZSI CHAR 1 Blocking indicator: X At least one of the three

Current inventory indicators
SPGRU CHAR 1 Blocking reason
Note
Set at least one of the three indicators.
To block a range of storage bins, use *. For example, enter 01* to block all storage bins that begin with 01.
IDoc for Stock Movement with HUs

De nition
10/3/2019
You use IDoc /SCWM/WMSUID01 to report movements of handling units (HUs), for example, stock transfers, from the non-SAP
system to SAP Extended Warehouse Management (SAP EWM).
Prerequisites
You have constructed the HU in SAP EWM that you want to move in the non-SAP system. The data for the HU is known in SAP
EWM.
Features
If you trigger a stock transfer of HUs in the non-SAP system, or if the non-SAP system speci es that this HU should be put away in
a nal storage bin in the high rack storage area, then the non-SAP system reports the stock movement data to SAP EWM.
In certain cases it is necessary to trigger a stock transfer of HUs in the non-SAP system. During the putaway of a pallet, it can also
be useful if the non-SAP system assigned the nal storage bin of the product in the high rack storage area. The non-SAP system
must report the movement performed for the HU to SAP EWM. SAP EWM subsequently posts the reported HU movement in the
system.
Putaway Using an Identi cation Point (ID Point)
If you put the HU away using an ID point, then instead of IDoc /SCWM/WMSUID01, you can call function module
/SCWM/_TO_CREATE_MOVE_SU synchronously in SAP EWM. This means that you can prevent accidental duplicate postings in
SAP EWM.
1. SAP EWM reports the warehouse task for putaway at the ID point to the non-SAP system, and prints the pallet slip.
2. The non-SAP system identi es the pallet and performs a check of the pallet outline.
3. The non-SAP system changes the HU type of the pallet according to the results of the outline check, or speci es the
destination storage bin for the pallet in the high rack storage area.
4. The non-SAP system calls function module /SCWM/TO_CREATE_MOVE_SU synchronously.
a. If SAP EWM has priority, then SAP EWM reports the destination storage bin for the pallet to the non-SAP system.
b. If the non-SAP system has priority and is waiting for a successful posting of the destination storage bin in SAP
EWM, then the non-SAP system transmits the destination storage bin in the high rack storage area to SAP EWM.
If the HU has already been put away from the ID point, the function module reads the relevant destination storage bin and reports
it to SAP EWM.
Structure
Message Type
You de ne the partner agreement inbound for message type /SCWMWMSUMO.
Segments
The IDoc consists of the segment /SCWM/E1LSUMX with the following elds:
Segment Definition /SCWM/E1LSUMX000 (Move Handling Unit IDoc Segment)
Field Data Description Required Comment

Type Entry
10/3/2019
Field Data Description Required Comment

Type Entry
LGNUM CHAR Warehouse X

3 number
LENUM CHAR Handling unit X

20
PROCTY CHAR Warehouse X

4 process type
LETYP CHAR HU type You do not always need to transmit this eld.
4
BNAME CHAR User name

12
KZQUI CHAR Indicator: You do not set this eld, since the transmitted stock movement has already been
1 con rmation performed and is therefore no longer subject to con rmation.
required
NLTYP CHAR Destination

3 storage type
NLBER CHAR Destination

3 storage section
NLPLA CHAR Destination

10 storage bin
NLENR CHAR Destination HU

20
IDoc for Creating and Sending Pick-Handling

Units
De nition
Using IDoc /SCWM/WMPHID01, you can send instructions to create pick-handling units (pick-HUs) from a non-SAP system to
SAP Extended Warehouse Management (SAP EWM). In addition, pick-HUs created in SAP EWM are sent to the non-SAP system.
Use
The non-SAP system initiates the creation of pick-HUs using IDoc /SCWM/WMPHID01. If the pick-HUs are created in SAP EWM,
the information (especially the pick-HU number) is distributed to the non-SAP system using IDoc /SCWM/WMPHID01.
Structure
Message Type
You de ne the partner agreement inbound for message type /SCWM/WMPIHU.
Segments
10/3/2019
IDoc /SCWM/WMPHID01 is made up of the /SCWM/E1LPHUX (Pick-HUs) segment. You determine the packaging material and
the amount of pick-HUs to be created. If you want to report the created pick-HUs back to the non-SAP system, you must choose
the KZRTN checkbox. If you want to create pick-HUs with external numbering, you must ll the external number into the HUIDENT
eld. The details of the /SCWM/E1LPHUX segment are as follows:
Field Data Type Description Required Entry
WHO CHAR 10 Warehouse order X
HUIDENT CHAR 20 Handling unit identi cation
HUKNG NUMC 3 Identi cation of a handling unit in a warehouse order
PMAT CHAR 40 Packaging material
ANZHU NUMC 3 Number of pick-HUs to be created
KZRTN CHAR 1 Send pick-HU creation con rmation to subsystem
LETYP CHAR 4 Handling unit type
LGTYP CHAR 4 Storage type
LGPLA CHAR 18 Storage bin
RSRC CHAR 18 Resource (means of transportation or user)
IDoc Error Processing

TCP/IP Errors
The basis for IDoc transmission between systems is TCP/IP. If an error occurs during the transfer, the connection between the
sending system and the receiving system is interrupted.
Based on return codes in the RFC function used, you can see in the sending system whether an RFC call has worked. If there are
TCP/IP errors, break the connection and send the IDoc again.
Technical Errors
If errors occur in the ALE service layer during sending or receiving of IDocs, then there is a technical error.
If a technical error occurs, Extended Warehouse Management (EWM) sends a work ow work item for each incorrect IDoc in the
form of an error message. The system sends this message to all responsible users. Based on the error message, the user can
analyze the error and post the document subsequently. For more information, see Processing Technical IDoc Errors .
Logical Errors
The system saves a received IDoc in the database before the IDoc has actually been processed. The system breaks off
communication with the external system before the transferred data is then processed.
If an error occurs during processing of an IDoc in the application system (EWM), then there is a logical error. In this case, EWM
creates a work ow work item for each incorrect IDoc.
10/3/2019
For more information, see Processing Logical IDoc Errors in EWM .
Processing Technical IDoc Errors

Use
During communication between the non-SAP system and Extended Warehouse Management (EWM), errors can occur in the ALE
layer. The following errors can occur:
Syntax error in the IDoc
Missing partner pro le
The system did not transmit the IDoc to an asynchronous Remote Function Call at sending
The system did not transmit the IDoc to an application at receipt
Error During Outbound IDoc Processing

IDoc status07: Syntax error in IDoc
On sending and receiving IDocs, the system checks the syntax of the individual IDocs. The IDoc de nition speci es the syntax of
the IDoc. This syntax can include:
The individual segments of an IDoc type
The relationship between the individual segments
How many segments you can send in an IDoc
Incorrect syntax in IDocs often occurs during tests only. IDocs with incorrect syntax cannot be repaired. You correct the IDoc
structure in the SAP system and send the IDoc again.
Recommendation
We recommend only switching on the syntax check during testing of IDocs created yourself. You activate the syntax check via
the partner pro le for one IDoc type and one particular partner. To do this, on the SAPEasy Accessscreen,
chooseTools ALE ALE Administration Runtime Settings Partner Agreement .
IDoc status29: Missing or incorrect partner agreement
When you send IDocs from the SAP system to the non-SAP system, you must have de ned the outbound section of the partner
agreement for the message type and all relevant partners. To do this, on the SAPEasy Accessscreen, chooseTools ALE ALE
Administration Runtime Settings Partner Agreement.
If the system cannot nd the partner (that is, the connected partner system) for sending the IDocs, proceed as follows:
De ne the missing partner pro le.
You retrigger sending of all pending IDocs that you could not send before.
For this error, the system triggers a work ow work item for the standard task Output: Error processing with IDoc and
sends a message to the inbox of the corresponding user.
You trigger subsequent sending of the IDocs that contained errors from the inbox.
10/3/2019
During this subsequent sending, the system ags the incorrect IDoc with the status 31, and copies the IDoc into a new
IDoc, to which the system adds the data from the partner agreement and transmits to the asynchronous RFC.
Note
Errors in partner pro les only occur in the test run.
IDoc status 30: System does not transmit IDoc to asynchronous RFC
Although you have de ned the partner agreement and the system has constructed the IDoc, the system cannot transmit the IDoc
to the asynchronous RFC. The system cannot send the IDoc. and there is no official entry in the RFC valuation (/nSM58) for the
relevant subsystem.
You trigger transmission of the IDoc using report RSEOUT00 .Choose Tools Business Communication IDoc Basis
Test Outbound from IDoc , to manually start the report, or schedule a regular background job for the report.
Check the outbound processing mode for the IDoc in the partner pro le.
Outbound processing mode 2 : The system sends the IDoc immediately
Outbound processing mode 4 : The system collects IDocs that have been created and sends them in packets of a
prede ned size.
IDocs are not intended to be sent directly.
Status 30 in the IDoc can only occur if outbound mode is set to 4.
Error During Inbound IDoc Processing

IDoc status60: Syntax error in IDoc
On sending and receiving IDocs, the system checks the syntax of the individual IDocs. The IDoc de nition speci es the syntax of
the IDoc. This syntax can include:
The individual segments of an IDoc type
The relationship between the individual segments
How many segments you can send in an IDoc
Incorrect syntax in IDocs only occurs during tests. IDocs with incorrect syntax cannot be repaired. You correct the IDoc structure
in the SAP system and send the IDoc again.
Recommendation
You activate the syntax check via the partner pro le for one IDoc type and one particular partner. We recommend that you
activate the syntax check for all IDocs you create yourself.
IDoc status63: Missing or incorrect partner pro le
When you send IDocs in the SAP system from the non-SAP system, you must have de ned the inbound section of the partner
agreement for the message type and all relevant partners. To do this, on the SAPEasy Accessscreen, chooseTools ALE ALE
Administration Runtime Settings Partner Agreement.
If the system cannot nd the partner (that is, the connected partner system) for receiving the IDocs, proceed as follows:
10/3/2019
De ne the missing partner pro le.
You retrigger receiving of all pending IDocs that you could not process before.
For this error, the system triggers a work ow work item for the standard task Input: Error processing with IDoc and sends
a message to the inbox of the corresponding user.
From the inbox, you trigger the subsequent transmission of the IDocs which contained errors.
Errors in partner pro les only occur in the test run.
IDoc status 64: System does not transmit IDoc to the application
Although you have de ned the partner agreement and the system has constructed the IDoc, the system cannot transmit the IDoc
to the application.
You trigger transmission of the IDoc using report RBDAPP01. To do this, plan a regular job in background processing for this
report.
Check the processing mode for the IDoc in the partner pro le:
Processing mode 1 : The system transmits the IDoc immediately after receipt in the application
Output mode 3 : The system collects received IDocs.
IDocs are not intended to be transmitted directly to the application.
Status 64 in the IDoc can only occur in conjunction with processing mode 3 and output mode 2 .
Processing Logical IDoc Errors in EWM

Use
If you receive an IDoc from the non-SAP system in the SAP system, the following errors can occur in Extended Warehouse
Management (EWM):
Missing or incorrect Customizing settings in EWM
Missing or incorrect data in the IDoc
Error Due to Blocked Objects
Note
Logical IDoc errors do not occur in IDoc outbound from the SAP system, because EWM responds to missing or incorrect
Customizing settings beforehand.
The system ags the incorrect IDocs with status 51 .
Missing or Incorrect Customizing Settings

Cause
The SAP system cannot further process the received IDoc in the following circumstances:
You have not de ned certain data for the IDoc in the SAP system.
10/3/2019
Example
Along with the IDoc, you transmit a stock movement with a warehouse process type from the non-SAP system, which is
unknown in the SAP system.
The received IDoc data does not match the Customizing settings in the SAP system.
Example
The stock movement reported by the external system is de ned for immediate con rmation. However, the warehouse
process type in EWM does not permit immediate con rmation for this stock movement.
Procedure
1. You correct the relevant Customizing settings.
2. You subsequently post the incorrect IDoc
Either from the inbox of the assigned user
Or via report RBDMANIN , which you schedule periodically in background processing.
Missing or Incorrect IDoc Data

If the data in the received IDoc is not complete, you decide whether the system should resend the incorrect IDoc, or whether a
correction in the SAP system is useful and possible.
You make the corrections to the IDoc using the IDoc editor.
Caution
Only correct the IDoc using the IDoc editor in exceptional cases.
You can subsequently post IDocs of the type WMIVID01 on reporting physical inventory data and correct the data in the
relevant transaction.
Procedure
You subsequently post the incorrect IDoc
Either from the inbox of the assigned user
Or via report RBDMANIN , which you schedule periodically in background processing.
Error Due to Blocked Objects

If blocking problems occur in the SAP system, IDoc processing leads to an error.
Example
If there are concurrent attempts (by different users) to access the same SAP object, the system terminates processing, with an
error note for the blocked object.
Procedure
You do not need to intervene manually. Schedule report RBDMANIN for periodical background processing.
10/3/2019
You can use the Error Status parameter in the report to specify that the system automatically reposts IDocs with the error
message describing a lock error.
Important Error Notes in Inbox

For the errors listed above, the system creates a work ow work item in the inbox of the person responsible. For more information,
see Rule Resolution in Exception Handling .
Work ow work items are also suitable for important notes
Which the external system sends to the SAP system
Which occur during IDoc processing in EWM.
These work ow work items
Inform the user about a problem or a con ict situation
Send on important messages from the external system to the SAP system.
The external system transmits the messages via message type WMINFO .
Example
If the system can no longer con rm a warehouse task or handling unit because the con rmation has already been
made, the non-SAP system triggers an internal message. Ensure that the system stores this information, since the
con rmation can only be made by the non-SAP system.
You do not process work ow work items for notes from the inbox as you do for errors, but rather complete the work ow work item.
Modi cation Options

Use
The interface between Extended Warehouse Management (EWM) and non-SAP systems (EWM-WCU interface) offers the following
options for con guring processing at the interface according to each customer's requirements:
Modi cation Concepts: IDoc Inbound Processing
Modi cation Concepts: IDoc Outbound Processing
At this point you can also access multiple BAdI Methods for the Interface , so that you can adapt and enhance the interface
processing to meet your requirements.
Modi cation Concepts: IDoc Inbound

Processing
Use
The following modi cation scenarios are available:
You use the standard IDoc but want to de ne the processing yourself.
10/3/2019
You create a user-de ned processing module, which you copy from the standard function module for the respective
message type and adjust accordingly.
You use the standard IDoc but want to adjust the standard IDoc processing. That is to say, you want to modify error
processing or want to interpret the contents of the IDocs to suit your individual needs.
You implement the Business Add-In (BAdI) in the standard function module:
If you want to in uence error processing, you implement the BAdI /SCWM/WMIDOC with the method
Error_Inbound .
If you want to in uence IDoc processing, you implement the BAdI /SCWM/WMIDOC with the following methods:
WMTORD_INBOUND
WMTOCO_INBOUND
WMCATO_INBOUND
WMSUMO_INBOUND
WMBBIN_INBOUND
For more information about the BAdI methods, see BAdI Methods for the Interface .
You use a modi ed IDoc with user-de ned segments and want to execute a particular process for the data from these
segments.
In the standard IDoc, you de ne your own IDoc segments and use the BAdI /SCWM/WMIDOC with the method
Error_Inbound to process the data from your own segments.
You use a modi ed IDoc with customized segments and want to de ne IDoc processing yourself.
You de ne customized IDoc segments in the standard IDoc and create a customized processing function module.
You use a user-de ned IDoc with a new message type and have to implement processing of the IDoc on your own.
You de ne a user-de ned IDoc and create a user-de ned processing function module. When you create the function
module, you can use the standard auxiliary function modules.
Features
Adjusting the Standard Function Module
As soon as the SAP system has received the IDoc and saved it, the system calls a main function module of the application, which
takes over the processing of the IDoc.
At this point, you have the rst opportunity to intervene in the IDoc processing, by creating a user-de ned function module .
You enter this function module from the SAP Easy Access screen under Tools ALE ALE Development IDoc Inbound
Processing Function Module Assign IDoc Type and Message Type .
There, you can also enter an additional partner pro le for a certain message variant or message function from the external system
to differentiate processing in the SAP system.
Main function modules for inbound IDoc processing
Message type Function module Use
/SCWM/WMBBIN /SCWM/IDOC_INPUT_WMBBIN Block storage bins
/SCWM/WMCATO /SCWM/IDOC_INPUT_WMCATO Cancel TW
10/3/2019
Message type Function module Use
/SCWM/WMSUMO /SCWM/IDOC_INPUT_WMSUMO Move Handling Unit
/SCWM/WMTOCO /SCWM/IDOC_INPUT_WMTOCO Con rm TW
/SCWM/WMTORD /SCWM/IDOC_INPUT_WMTORD_MULTIPLE Warehouse tasks (WT)
The main function module lters out the data for each IDoc and calls the actual processing function module of the application in a
loop.
Implementation of BAdIs
A BAdI method is implemented both before and after each call of the function module:
You can use the BAdI method after the function module call to update your own error status or to change the error status
already set.
You can use the BAdI method before the function module call, for example, to perform your own updates or to evaluate
your own segments (that you have added in the IDoc de nition).
Note
You can nd the name of the BAdI method in the source code for the main function module.
If you create your own function module or BAdIs, make sure that you do not set any COMMIT WORK statements, as these can
cause errors during IDoc processing and inconsistencies during error processing. The system returns to the ALE layer following
processing, where the system updates any application errors that have occured, sets the IDoc status, and may even execute
database rollbacks.
Note
Note that additional I/Os in the BAdIs can reduce performance.
De ning User-De ned IDoc Segments
You de ne your own IDoc segments from the SAP Easy Access screen, by choosing Tools ALE ALE Development IDoc IDoc
Type Development IDoc Types . For more information, see Segment Editor .
Creating User-De ned Processing Function Modules
The SAP system offers function modules for general use for the following tasks for using user-de ned main function modules:
Auxiliary function modules for inbound IDoc processing
Function module Task
/SCWM/IDOC_CREATED_OBJECTS_SAVE Continuously save the documents created from an IDoc
/SCWM/IDOC_ERROR_SAVE Continuously save IDocs with errors
/SCWM/IDOC_INPUT_REFRESH Initialization for IDoc processing (table refresh)
/SCWM/IDOC_OK_SAVE Continuously save processed IDocs
/SCWM/IDOC_RETURN_CREATE Determine and construct status record for the IDoc
/SCWM/IDOC_ROLLBACK_SAVE Update IDoc tables after necessary rollback
10/3/2019
Function module Task
/SCWM/IDOC_STATUS_CREATE Determine and construct status record for the IDoc
/SCWM/IDOC_TIDOC_FETCH Fetch internal table for the purpose of status update
De ning User-De ned IDocs
If you de ne your own IDocs (intermediate structure), you assign this IDoc to a new message type.To do this, on the SAPEasy
Accessscreen, chooseTools ALE ALE Development IDoc IDoc Type Development IDoc Types.For more information,
seeDe ning New IDoc Types.
You create a partner pro le for this message type.
You de ne the tables for inbound processing for this IDoc under Tools ALE ALE Development IDoc Inbound Processing.
Standard task TS00008099 is available for error processing.
Modi cation Concepts: IDoc Outbound

Processing
Use
The following modi cation scenarios are available:
You use the standard IDoc but want to in uence the construction of the IDoc.
You create a user-de ned processing module, which you copy from the standard function module for the respective
message type and adjust accordingly.
You activate the user-exit in the standard function module to in uence the standard IDoc construction.
You use the standard IDoc, but want to specify when and to whom the system should send a warehouse task item. In this
case, you do not use the standard ow of the interface.
You realize your own connection for the interface between Extended Warehouse Management (EWM) and the non-SAP
system.
You use a modi ed IDoc with user-de ned segments and you want to trigger user-de ned processing to construct the data
in the segments.
In the standard IDoc, you de ne your own IDoc segments and use the BAdI method to enter data into your own segments.
You use a modi ed IDoc with user-de ned segments and want to implement IDoc construction yourself.
You de ne your own IDoc segments in the standard IDoc and create your own processing function module, which you copy
from the standard function module of the relevant message type and adjust accordingly.
You use a modi ed IDoc with user-de ned segments and do not want to use the standard ow of the interface.
In the standard IDoc, you de ne your own IDoc segments and realize your own connection for the interface between EWM
and the non-SAP system.
You use an individually de ned IDoc with a new message type and have to implement IDoc construction yourself.
You de ne an individual IDoc and create an individually de ned function module. Standard auxiliary function modules are
available for this purpose.
10/3/2019
You use a modi ed IDoc with a new message type and do not want to use the standard ow of the interface.
You de ne your own IDoc, and realize your own connection for the interface between EWM and the non-SAP system.
Features
Adjusting the Standard Function Module
EWM prepares sending the IDoc to the non-SAP system. The system constructs the IDoc in the relevant application function
module, determines the partner (the connected system), and steers towards the ALE layer for further processing.
At this point, you have the rst opportunity to intervene in the IDoc processing, by creating a user-de ned function module .
You enter this function module in Customizing for Extended Warehouse Management under Interfaces Non-SAP
Systems Connect Subsystem .
EWM uses the following function modules to construct and send IDocs:
Function modules for outbound IDoc processing
Function module Name
/SCWM/IDOC_CREATE_WMTOID01 Warehouse tasks
/SCWM/IDOC_CREATE_WMRRID01 Group release
/SCWM/IDOC_CREATE_WMCAID01 Cancellation request WT
Note
In the function modules, you can use BAdI methods to add your own IDoc segments, or to in uence the structure of the
standard IDoc.
Realizing an individually de ned interface connection
You realize your own interface connection to decide for yourself when communication should take place to the non-SAP system,
and to which non-SAP system you want to send the data.
Caution
In this case, the interface must not be active in EWM.
You use the BAdI method BAdI. WT Con rmation , to realize your own connection between the systems.
De ning User-De ned IDoc Segments
You de ne your own IDoc segments from the SAP Easy Access screen, by choosing Tools ALE ALE Development IDoc IDoc
Type Development IDoc Types . For more information, see Segment Editor .
De ning User-De ned IDocs
If you de ne your own IDocs (intermediate structure), you assign this IDoc to a new message type.To do this, on the SAPEasy
Accessscreen, chooseTools ALE ALE Development IDoc IDoc Type Development IDoc Types.For more information,
seeDe ning New IDoc Types.
You create a partner pro le for this message type.
10/3/2019
BAdI Methods for the Interface

Extended Warehouse Management (EWM) contains the following available BAdI methods:
Enhancements to the EWM-WCU interface using BAdI/SCWM/WMIDOC
Method Name
ERROR_INBOUND Error processing in Idoc inbound for IDocs: /SCWM/WMTOCO,

/SCWM/WMCATO, /SCWM/WMBBIN, and /SCWM/WMSUMO
jointly
WMTOCO_INBOUND Message /SCWM/WMTOCO (con rm warehouse task) inbound
WMCATO_INBOUND Message /SCWM/WMCATO (cancel warehouse task) inbound
WMBBIN_INBOUND Message /SCWM/WMBBIN (block storage bin) inbound
WMSUMO_INBOUND Message /SCWM/WMSUMO (move handling unit) inbound
WMTORD_OUTBOUND IDoc /SCWM/WMTOID01 (warehouse task) outbound
WMCATO_OUTBOUND IDoc /SCWM/WMCAID01 (cancellation request for warehouse task)

outbound
WMREF_OUTBOUND IDoc /SCWM/WMRRID1 (release wave) outbound
WMTORD_INBOUND Message /SCWM/WMTORD (create warehouse task) inbound

Sap Help For Idoc WT in Ewm

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Sap Help For Idoc WT in Ewm

Загружено:

Авторское право:

Доступные форматы

10/3/2019

SAP Extended Warehouse Management

SAP Extended Warehouse Management (SAP EWM) | 9.5.0.2

For more information, please visit the SAP Help Portal.

Warehouse Order Creation

Number Ranges for Warehouse Orders

For each activity area

For each queue

For each consolidation group

For each activity area

For each queue

For each delivery

Parameters for packing

De ne Sort Rules for Warehouse Tasks

De ne Filters for Warehouse Order Creation Rules

De ne Limit Values for the size of a Warehouse Order

Choose warehouse number 0001, the monitor SAP and Execute.

Open Documents Warehouse Tasks .

Enter a warehouse order creation rule.

Filters for Warehouse Order Creation Rules

Limit Values for Warehouse Order Creation

Printing Warehouse Orders and Warehouse

In Customizing, you have de ned the condition maintenance group.

Action De nition Description SAP Smart Forms Form

WO_MULTIPLE Print list for warehouse order with serial /SCWM/WO_MULTIPLE

WO_SINGLE Print single document for warehouse order /SCWM/WO_SINGLE

WO_HUSHIP Print shipping label /SCWM/WO_HUSHIP

WO_LOAD Print loading instruction with warehouse /SCWM/WO_LOAD

WO_UNLOAD Print unloading instruction with warehouse /SCWM/WO_UNLOAD

EWM calls the PPF and transmits the application data.

PPF reads the current application data.

Manual Assembly of Warehouse Orders

A traﬃc light shows the status of the warehouse task.

EWM updates the screen content.

Using a Post Processing Framework action

Pick, Pack, and Pass During Picking

For more information about RF picking, see RF Picking Flow.

Picking Destination Storage Bin

RF picking Destination storage bin, such as goods issue area

You can use this function in either a system-controlled or user-controlled way.

System-controlled pick, pack, and pass function

User-controlled pick, pack, and pass function

Interface Between EWM and Non-SAP

Scenarios for Connecting Non-SAP Systems

Transfer warehouse tasks from SAP EWM to non-SAP system

Transfer release of multiple processing from SAP EWM to non-SAP system

Transfer cancellation requests from SAP EWM to non-SAP system

Move handling units (see Handling Unit (HU))

Blocking storage units or aisles

Connecting a Semi-Automated Warehouse

EWM performs all tasks relevant to warehouse management, including:

Managing product stocks and storage bins

Carrying out the inventory

Connect forklift systems

Control automatic conveyors or conveyor equipment

Allow picking without any documents, using RF devices

Control the product ow

1. EWM creates warehouse tasks (WTs) for the goods movements.

2. You print the warehouse tasks to use as a pallet receipt/issue slip.

3. You transport the pallet to the automatic conveyor.

Reporting Using EWM-WCU Interface: Stock Removal

1. EWM creates warehouse tasks (WTs) for the stock removal.

2. You print the warehouse tasks to use as a stock removal list.