Warehouse Order Creation

5/21/2018 Warehouse Order Creation

1/37

Warehouse Order CreationPDF download from SAP Help Portal:

http://help.sap.com/saphelp_scm50/helpdata/en/c0/0ea74046033913e10000000a155106/content.htm

Created on July 15, 2014

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

Note

This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

2014 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose

without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE

and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by

SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not beliable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express

warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other

SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other

countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

PUBLIC 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 37
http://help.sap.com/saphelp_scm50/helpdata/en/c0/0ea74046033913e10000000a155106/content.htmhttp://help.sap.com/


2/37

Table of content1 Warehouse Order Creation

1.1 Warehouse Order

1.2 Filters for Warehouse Order Creation Rules

1.3 Limit Values for Warehouse Order Creation Rules

1.4 Printing Warehouse Orders and Warehouse Tasks

1.5 Interface Between EWM and Non-SAP Systems

1.5.1 Scenarios for Connecting Non-SAP Systems

1.5.1.1 Connecting a Semi-Automated Warehouse

1.5.1.2 Connecting a Fully Automated Warehouse

1.5.1.3 Connecting a Fully Automated Warehouse as a Black Box

1.5.2 Data Flow: EWM Transmits Data

1.5.2.1 Managing TCP/IP Settings

1.5.2.2 Managing Transaction Identifiers (TID)

1.5.3 Data Flow: EWM Receives Data

1.5.4 Data Formatting

1.5.5 Description of the IDocs

1.5.5.1 IDoc for Sending WTs to a Non-SAP System

1.5.5.2 IDoc for Receiving WTs from a Non-SAP System

1.5.5.3 IDoc for Confirming Warehouse Tasks1.5.5.4 IDoc for Canceling Warehouse Tasks

1.5.5.5 IDoc for Releasing Waves

1.5.5.6 IDoc for Blocking Storage Bins

1.5.5.7 IDoc for Stock Movement with HUs

1.5.6 IDoc Error Processing

1.5.6.1 Processing Technical IDoc Errors

1.5.6.2 Processing Logical IDoc Errors in EWM

1.5.7 Modification Options

1.5.7.1 Modification Concepts: IDoc Inbound Processing

1.5.7.2 Modification Concepts: IDoc Outbound Processing

1.5.7.3 BAdI Methods for the Interface

1.6 Material Flow System (MFS)

1.6.1 Setting Up the Material Flow System

1.6.2 Communication Point

1.6.3 Conveyor Segment


Page 2 of 37


3/37

!--a11y-->

1 Warehouse Order Creation

Use

This function groups together warehouse tasks into warehouse orders, according to your settings in Customizing for warehouse orders, and thus creates optimum

work packages for you. For warehouse order creation, you define 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 defined the following in Customizing for Extended Warehouse Management (EWM):

Number Ranges for Warehouse Orders

For more information about defining number ranges for warehouse orders, see the Implementation Guide (IMG) for SAP Supply Chain Management ( SAP

SCM ) under Extended Warehouse Management Cross-Process Settings Warehouse Order Define Number Ranges for Warehouse Order.

Storage Bins

For more information about defining number ranges for warehouse orders, see the (IMG) for SAP SCM under Extended Warehouse Management Master

Data Storage Bins.

Activity Areas

For more information about defining number ranges for warehouse orders, see the Implementation Guide (IMG) for SAP SCM under Extended Warehouse

Management Master Data Activity Areas Define Activity Area.

Start Locations

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

defined. 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 monitorto 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 examp le, in the warehouse management monitor in the dialog structure under the node Documents Warehouse Order using the

More Methods action menu (see Processing Waves).

During this summarization of the warehouse tasks into warehouse orders, EWM uses the search sequence for WO creation, for example, first rule A, then B, then

C. EWM works through the WO creation rules in sequence, as you have defined for each activity area. You can change the sequence subsequently.

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-

defined 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-

defined 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 define 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

You can use the following parameters to define creation of warehouse orders in detail for your warehouse processes:

Sorting rule

For more information about defining sorting rules, see the Implementation Guide (IMG) for SAP Supply Chain Management under Extended Warehouse

Management Cross-Process Settings Warehouse Order Define Sorting Rules for Warehouse Tasks.

Filters

For more information about item filters or subtotal filters, 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 profile, which you

assign to a packaging sp ecification.

For more information about defining pack ing profiles, see the Implementation Guide (IMG) for SAP Supply Chain Management under Extended Warehouse


Page 3 of 37
http://help.sap.com/saphelp_scm50/helpdata/en/1b/62254144e9f423e10000000a155106/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/e1/3da74046033813e10000000a155106/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/13/b34123241465429b406279f39a8516/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/d1/12391796f18547b8f71140a79142ca/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/ae/702c7cd987c5488bc1b046487a288f/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/b0/01fc636433504daa8d22f97dea3a53/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/43/0f66909f115737e10000000a11466f/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/b2/5bfd40ce3df123e10000000a155106/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/75/f58f414141a709e10000000a155106/content.htm


4/37

Management Cross-Process Settings Warehouse Order Define Sorting Rules for Warehouse Tasks.

Packing mode

Consolidation group

During warehouse order creation, the consolidation group influences 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.

You define the maximum number of consolidation groups in a warehouse order as the definition of a limit value.

You can simulate creation of warehouse orders for your warehouse tasks.

Activities

EWM creates a list of warehouse requests.

EWM groups the warehouse requests into a wave (for example, a wave pick) and releases i t.

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.

To make settings for the sorting rules, filters, limi t values, parameters for packing, and the pack ing mode, go to the Implementation Guide (IMG) for SAP

SCM under Extended Warehouse Management Cross-Process Settings Warehouse Order

Define Sort Rules for Warehouse Tasks

Define Filters for Warehouse Order Creation Rules

Define Limit Values for the Size of Warehouse Order

Define Packing Profile for Warehouse Order Creation , and selec t an option for Spl it WT .

Define Packing Profile for Warehouse Order Creation , and select an option for Split TO .

To make settings for the consolidation group, go to the Implementation Guide (IMG) for SAP SCM under Extended Warehouse Management Goods

Receipt Deconsolidation Define Number Ranges for Consolidation Group or Extended Warehouse Management Goods Issue Define

Number Range for 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 .

i. Choose warehouse number 000 1, the monitor SAP and Execute .

ii. Open Documents Warehouse Tasks .

iii. In the dialog box, choose the warehouse task status Open and Execute .

iv. Select one or more open warehouse tasks and choose Other Methods Simulate Warehouse Order . The WO Create Rule dialog box

appears.

v. 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.

!--a11y-->

1.1 Warehouse Order

Definition

Document that represents an executable work package that a warehouse employee should perform at a specific time. The warehouse order consists of warehouse

tasks or phys ical 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 defined in Customizing.

For more information about warehouse order creation rules, see the Implementation Guide (IMG) for SAP Supply Chain Management under

Extended Warehouse Management Cross-Process Settings Warehouse Order Define Creation Rule for Warehouse Orders.

Integration

The warehouse groups together warehouse tasks or physical inventory items.


Page 4 of 37


5/37

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.

!--a11y-->

Filters for Warehouse Order Creation Rules

Definition

The filter 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 filters on all warehouse tasks that you have not yet assigned to a warehouse order, and which WO creation should process.

Use

You can define two types of filters: Item Filtersand Subtotal Filters.

Item Filter

You define item filters, so that EWM checks the individual warehouse task against the filter criteria defined in your Customizing settings.

During processing of a warehouse task, EWM checks whether the given item filter fits. If the filter fits the warehouse task, then EWM continues processing for the

warehouse task. If it does not fit, 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 settings for filter parameters for warehouse tasks, see the Implementation Guide (IMG) for SAP Sup ply Chain

Management ( SAP SCM ) under Extended Warehouse Management Cross-Process Settings Warehouse Order Define Filters for Warehouse Order

Creation Rules.

Subtotal Filter

You define subtotal filters, so that EWM can use the filter criteria defined in your Customizing settings to compare several warehouse tasks against a subtotal,

containing values you have defined. During this, EWM works out the subtotal for each consolidation group. You must have defined sorting rules with the sort field

DSTGRP (consolidation group), for the warehouse tasks to process.

For more information about defining sorting rules, see the Implementation Guide (IMG) for SAP SCM under Extended Warehouse Management Cross-

Process Settings Warehouse Order Define Sorting Rules for Warehouse Tasks.

During processing of several warehouse tasks, EWM checks whether the given item or subtotal filter fits. If the filter fits the transfer orders, then EWM continues

processing for the warehouse tasks. If it does not fit, EWM stops processing the warehouse tasks. In the case of a subtotal filter, this means that EWM does not

process the entire group of warehouse tasks for a consolidation group using the current filter. 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 settings for filter parameters for warehouse tasks, see the Implementation Guide (IMG) for SAP SCM under Extended

Warehouse Management Cross-Process Settings Warehouse Order Define Filters for Warehouse Order Creation Rules.

!--a11y-->

Limit Values for Warehouse Order Creation Rules

Definition

The limit value of a warehouse order creation rule specifies 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, filter criteria), against the limit values defined 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 settings for limit values for warehouse orders, see the Implementation Guide (IMG) for SAP Supp ly Chain Management

( SAP SCM ) under Extended Warehouse Management Cross-Process Settings Warehouse Order Define Limit Values for the Size of a Warehouse

Order.


Page 5 of 37
http://help.sap.com/saphelp_scm50/helpdata/en/ae/df2f193243fb428b2425a16462c422/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/92/4c8aa58cf1f24e8e5a12b39ae5d340/content.htm


6/37

!--a11y-->

Printing Warehouse Orders and Warehouse Tasks

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 specific 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 first printout is damaged, or your require a second printout.

Integration

Printing of warehouse orders and warehouse tasks is b ased on SAPscript texts and SAP Smart Forms as form templates.

EWM uses the Post Process ing Framework (PPF) for message control.

Additionally, EWM uses the condition technique in the schedule condition for PPF to determine the printer, the form type, and the spool parameter.

For more information about the structure and Customizing for the Post Process ing Framework, see the SAP Library under SAP NetWeaver

Components SAP Web App lication Server Basis Services /Communication Interface (BC-SRV ) SAP Communication: Configuration(BC-SRV ) Business Workplace and Services (BC-SRV-OFC Generic Business Tools for App lication Developers (BC-SRV-GBT)

Post Processing Framework (BC-SRV-GBT) .

For more information about the condition technique, see the SAP Library under mySAP Customer Relationship Management CRM Enterprise

Enterprise Sales Sales Management for Commercial and Industrial Customers Basic Functions Condition Technique.

Prerequisites

You have made the settings in Customizing for PPF:

You have defined the PPF action definitions with the relevant processing types.

In Customizing for the PPF action definition, you have defined the following data:

Process ing time

Scheduling

Determination technique

Rule type

Action aggregation

You have spec ified the PPF conditions for the defined PPF action definitions.

In Customizing for the condition technique, you have defined the condition tables.

In Customizing, you have defined your condition tables from the field catalog, which SAP delivers. You have selected fields from the field catalog as key

fields. These fields represent the condition under which the condition technique finds the condition record. If a data record transferred by EWM matches your

key fields, then condition technique finds the matching condition record.

In Customizing, you have defined condition types, and therefore the access sequence to the condition tables to search.

In Customizing, you have ass igned the relevant condition schemas to your condition types.

The condition schema specifies the conditions that you permit for determining data (such as printer, form type) and specifies the sequence (access

sequence) in which condition technique should consider them.

In Customizing, you have assigned the condition schema to the application object (warehouse process type, packaging material type, work center).

In Customizing, you have defined the condition maintenance group.

The condition maintenance group is required for creating condition records. The condition maintenance group specifies the condition tables and therefore the

key fields.

You have defined the logical conditions that you want to use in the condition records. You have defined warehouse-number-spec ific print settings (in particular the spool parameters).

Features

For printing warehouse orders, the following action definitions are supported in PPF in the app lication /SCWM/WME in the action profile /SCWM/HU . These

action definitions 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 definition there is also an SAP Smart Forms form. The system only sup ports printing of SAP Smart Forms . The following table gives you an

overview of the action definitions and their corresponding SAP Smart Forms forms. The assignment between action definition and SAP Smart Forms form is

specified in the created condition records.

Action Definition Description SAP Smart Forms Form

WO_MULTIPLE Print list for warehouse order /SCWM/WO_MULTIPLE

WO_SINGLE Print individual document for warehouse order /SCWM/WO_SINGLE

WO_HUSHIP Print HU transportation label /SCWM/WO_HUSHIP

WO_LOAD Print loading list with warehouse tasks /SCWM/WO_LOAD


Page 6 of 37


7/37

WO_UNLOAD Print unloading list with warehouse tasks /SCWM/WO_UNLOAD

During warehouse order creation, transfer order confirmation, and activation of product warehouse tasks, if you attempt to print during storage control, then you

automatically call up PPF . The decis ion whether to print is dep endent 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 definition matches the current PPF action definition.

The logical condition is entered in the condition record, and is fulfilled.

During printing or repeat printing, you can also execute PPF action definitions for which there are no defined 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 process ing, or you trigger it manually .

EWM calls the PPF and transmits the application data.

PPF determines the PPF action definitions you have defined in Customizing for the PPF applic ation /SCWM/WME and the PPF action profile

/SCWM/WO .

The PPF calls the schedule condition that corresponds to the PPF action definition.

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.

!--a11y-->

Interface Between EWM and Non-SAP Systems

Use

Extended Warehouse Management (EWM) has an interface (EWM-WCU interface) that you can use to connect automated warehouse systems such as

warehouse control units (WCU) to EWM.

Integration

The interface allows communication between the connected systems on the basis of the transactional Remote Function Call(tRFC).

In contrast to synchronous Remote Function Call (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.

Features

Interface Between EWM and Non-SAP Systems (WMS-WCU Interface)

You use the EWM-WCU interface to connect automated warehouse sys tems, such as warehouse control units (WCU) to Extended Warehouse Management

(EWM).

For more information, see Scenarios for Connecting Non-SAP Systemsand Description of the IDocs.

!--a11y-->

1.5.1 Scenarios for Connecting Non-SAP Systems

Use

You can use the interface between Extended Warehouse Management (EWM) and non-SAP systems (EWM-WCU interface) to connect different non-SAP

systems to 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 EWM, such as warehouse control units (WCU).


Page 7 of 37
http://help.sap.com/saphelp_scm50/helpdata/en/f3/216f410eda5658e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/81/f56f4151dc5758e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/35/26aff8afab52b9e10000009b38f974/content.htm


8/37

Features

The EWM-WCU interface supports the following communcation transactions between the systems:

Transfer warehouse tasks from EWM to non-SAP sys tem

Transfer release of multip le process ing from EWM to non-SAP system

Transfer cancellation requests from EWM to non-SAP sys tem

Create transfer orders in EWM for warehouse tasks reported by non-SAP system

Confirm transfer orders in EWM for warehouse tasks reported as complete by non-SAP system

Move handling units

Blocking storage units or aisles Cancel transfer orders in EWM for warehouse tasks not reported as complete by non-SAP system

EWM takes on all tasks related to warehouse management. However, warehouse control and execution of driving commands are not part of 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 flow, as well as other

tasks such as optimizing the stock movenents or additional control mechanisms.

The scenarios focus on the task distribution between EWM and the relevant connected non-SAP system. The flexibility of the EWM-WCU interface enables you to

make customer-specific adjustments and enhancements. For more information, see Modification Concepts: IDoc Receiptand Modification Concepts: IDoc Issue.

Activities

You determine the task distribution, according to your own requirements, between EWM and the non-SAP system.

!--a11y-->

Connecting a Semi-Automated Warehouse

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 fixed 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 flow

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 configured 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


Page 8 of 37
http://help.sap.com/saphelp_scm50/helpdata/en/6b/2c73412c315458e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/32/2c73412c315458e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/2e/d93d41d19bf623e10000000a155106/content.htm


9/37

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 confirms the warehouse task using the data reported using message type/SCWM/WMTOCO .

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.

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.



Transferring warehouse tasks for warehouse movements to the external system


Page 9 of 37


10/37

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 bas is 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.



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 forkli ft guidance system reports the stock movement to EWM using message type/SCWM/WMTOCO .


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.

!--a11y-->

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, EWMtakes 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 fixed putaway and stock removal strategies

The externalsystemtakes over the entire warehouse controlling:

Controlling the conveyor equipment

Controlling the product flow

Optimizing resources

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 configured the interface between EWM and the non-SAP system in Customizing for Extended Warehouse Management under Interfaces Non-SAP

Systems Connect Subsystem .

You have specified 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:


Page 10 of 37
http://help.sap.com/saphelp_scm50/helpdata/en/dd/966f41e8d95558e10000000a1550b0/content.htm


11/37

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 c reation. 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 identification points

(ID points) and pick points.

Process

Putaway via ID points

1. You receive an inbound delivery in the goods receipt interim storage area. You post the goods receip t 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 identifies 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 sys tem 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.

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.


Page 11 of 37
http://help.sap.com/saphelp_scm50/helpdata/en/35/26b59aafab52b9e10000009b38f974/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/2e/d93d41d19bf623e10000000a155106/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/8f/297341738e5358e10000000a1550b0/content.htm


12/37

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.

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 consis t 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.

If there is more than one ID point in the system, then the non-SAP system also specifies the assignment of the individual picking transactions and HUs to the

available p ick points. Only the external sys tem can ensure optimal pick point assignment, s ince the utilization of the warehousing equipment is at the fore.

6. You execute picking at the pick p oint.

The external system disp lays the items to be picked on the screen at the pick point.

7. You confirm 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 .



Return Transfer for Handling Units with Remaining Quantity

1. After pick ing, you take the HUs with remaining quantities to the ID point for return transfer into the warehouse.

2. The external sys tem identifies 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 sys tem 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.

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/WMBBINto 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.

!--a11y-->

Connecting a Fully Automated Warehouse as a Black Box

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 controlfor 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.

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 flow


Page 12 of 37
http://help.sap.com/saphelp_scm50/helpdata/en/97/d94541c47a6e24e10000000a155106/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/5f/d94541c47a6e24e10000000a155106/content.htm


13/37

Optimizing resources

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 defined the automated section of your warehouse as a separate storage type in EWM.

You can define a fixed 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 define several s torage bins in the warehouse type, which do not correspond to the physical storage bins. You allow addition to exis ting 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.

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 specifies in which storage type the goods are put away.

3. If you have selec ted 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 identifies 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 sys tem reports the putaway to EWM using message type/SCWM/WMTOCO .

Stock Removal

1. EWM creates a warehouse task (WT) for the stock removal.

2. EWM sends all stock removal WTs relevant for the storage type managed by the non-SAP sys tem 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 confirms the individual items in the warehouse task, using the reported data and actual quantities from the non-SAP sy stem.

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.

The non-SAP system must not send product movements within the storage type managed by the non-SAP system, because EWM only managesthe summary stocks for this storage type.


Page 13 of 37
http://help.sap.com/saphelp_scm50/helpdata/en/35/26b59aafab52b9e10000009b38f974/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/35/26c132afab52b9e10000009b38f974/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/93/f373412c315458e10000000a1550b0/content.htm


14/37

!--a11y-->

Data Flow: EWM Transmits Data

Purpose

The data flow via the interface between the non-SAP system and Extended Warehouse Management (EWM-WCU interface) is exp lained using an example

communication process flow 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. For more information, see BC SAP Communication: Configuration.

In Customizing, you have defined the ALE interface. In Customizing, you have specified 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 sp ecify 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 define the external sys tem, which receives the WT item.

Process

1. When you create a warehouse task (WT) in EWM, the Customizing settings define 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.

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 sys tem.

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 confirmation to the SAP system.

We recommend that you save the transmitted data in the non-SAP system first, 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 sys tem should be able to recognize IDocs that have been transferred by the SAP system before. This is made p ossible b y the unique

transaction identification 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 .

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:

Transferred data is syntactically i ncorrect

ALE adopts the IDoc and saves it, but cannot transfer the IDoc to the external system.

For more information, see IDoc Error Processing.


The outbound partner profile for the receiving sys tem

The IDoc message type

are not defined


There is no connection between the SAP system and the external system The SAP system tries to set up the connection to the external system by running a report


Page 14 of 37
http://help.sap.com/saphelp_scm50/helpdata/en/15/2b73412c315458e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/15/2b73412c315458e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/22/042899488911d189490000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/f3/216f410eda5658e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/bb/9f11794b9b11d189750000e8322d00/frameset.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/07/4c7341738e5358e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/81/f56f4151dc5758e10000000a1550b0/content.htm


15/37

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.

!--a11y-->

Managing TCP/IP Settings

As a prerequisite for communication, you make the following TCP/IP settings:

In order for the SAP system to find the target system, you must fulfill the TCP/IP prerequis ites, in particular the IP addresses must be known in the relevant

hosts file.

You have entered the name of the gateway and the dispatcher in the services file, 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 regis tration 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.

For details on the TCP/IP settings, see the documentation SAP Communication: Configuration.

!--a11y-->

Managing Transaction Identifiers (TID)

Purpose

To ensure the security of the data to transfer, you must work with a unique identifier 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 flow between the sending and receiving system:


Page 15 of 37
http://help.sap.com/saphelp_scm50/helpdata/en/bb/9f11794b9b11d189750000e8322d00/frameset.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/22/0429aa488911d189490000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/87/2b73412c315458e10000000a1550b0/content.htm


16/37

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 first attempt at

sending, the system must be able to recognize this. It should not process the data a second time.

!--a11y-->

1.5.3 Data Flow: EWM Receives Data

Purpose

The data flow via the interface between the non-SAP system and Extended Warehouse Management (EWM-WCU interface) is exp lained using an example

communication process flow 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 defined the necessary TCP/IP settings. For more information, see SAP Communication: Configuration.

You have configured the ALE interface in Customizing for Extended Warehouse Management under Interfaces Non-SAP Systems Connect

Subsystem .


Page 16 of 37
http://help.sap.com/saphelp_scm50/helpdata/en/bb/9f11794b9b11d189750000e8322d00/frameset.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/81/f56f4151dc5758e10000000a1550b0/content.htm


17/37

Process

1. The non-SAP system saves the data relevant for transmiss ion to the SAP system, and prepares this data for transmiss ion as an IDoc.

2. The external sys tem 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.

If an IDoc type only supp orts single transmission, then the IDoc sys tem documentation explicitly states this fact. 3. Status management for the data to be transferred should prevent the external system from not transferring data.

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.

4. The SAP system should be ab le to recognize IDocs that have been transferred by the external system already. This is made possible by the unique

transaction identification 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 flag 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.

The SAP system does notuse the IDoc numberto recognize a double transfer of IDocs from the external system.

5. 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.

6. Asynchronously to the receip t of the IDoc, ALE transmits the IDoc to EWM, which then takes over process ing of the IDoc.

7. EWM uses the transmitted data as the basis for creating warehouse tasks. 8. For each IDoc, EWM reports the processing status to ALE.

ALE uses the processing s tatus 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

Symptom What You Should Know

There is no connection between the external system and the SAP system The non-SAP system should use status management to ensure that the non-SAP

system re-transmi ts the IDocs again at a later point.


There are syntactical errors in the data that the external system sent to the ALE

Although ALE copies the IDoc and saves it, ALE cannot transmit the IDoc to EWM for

processing. For more information, see IDoc Error Processing.

Error in the ALE interface: Inbound partner profile for the sending system

IDoc message type

are not defined


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.

!--a11y-->

1.5.4 Data Formatting

The system transfers data to structures EDI_DC40and EDI_DD40. Since EDI also uses these structures, this means that some fields 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 field to the non-SAP

system.

DOCNUM CHAR 16 IDoc number X Unique communication number

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


Page 17 of 37
http://help.sap.com/saphelp_scm50/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/c0/2b73412c315458e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/15/2b73412c315458e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/15/2b73412c315458e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/22/042aca488911d189490000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/22/042899488911d189490000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_scm50/helpdata/en/46/9acb3d1d1f7c4a85c0d61901b30b54/content.htm


18/37

PSGNUM CHAR 6 Number of higher-level SAP

segment

The system transmi ts the field to

the non-SAP system, but is not

required at receipt.

HLEVEL CHAR 2 Hierarchy level of SAP segment The system transmits the field to



DTINT2 CHAR 2 Empty field for EDI_DD Not relevant

SDATA LCHR 1000 Application data X Actual application data in form of

IDoc segment

EDI_DC40

Field Format Name Relevant for Receipt Comments

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 field to



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 recipient X For example: WM_SUB_00 1 for

SAP to SUB

RCVSAD CHAR 21 EDI: Total SADR fields

RCVLAD CHAR 70 Logical address of recipient

STD CHAR 1 EDI standard

STDVRS CHAR 6 Version of EDI standard

STDMES CHAR 6 EDI message type

MESCOD CHAR 3 Logical message code * You can use both fields to specify a

different function module than the

standard function module in the

ALE service level, in the table for

inbound methods, wh ich is used

to process IDocs.

MESFCT CHAR 3 Logical message function * You can use both fields to specify a

different function module than the

standard function module in the

ALE service level, in the table for

inbound methods, wh ich 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 sender X For example: S11MAND000, if

S11 is the sending SAP system

SNDSAD CHAR 21 EDI: Total SADR fields

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

RCVPFC CHAR 2 Partner function of recipient


Page 18 of 37


19/37

SNDPFC CHAR 2 Partner role of sender

SERIAL CHAR 20 EDI/ALE: Serialization field

EXPRSS CHAR 1 Override during receipt

You do not have to enter data in all fields of EDI-DC or EDI_DD. Make sure that you initializeany fields 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. Forexample, 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.

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 identified 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

!--a11y-->

1.5.5 Description of the IDocs

The interface between Extended Warehouse Management and non-SAP systems (EWM-WCU interface) uses the following IDocs:

IDocs for EWM-WCU Interface

IDoc Partner Agreement Message type Name

/SCWM/WMTOID01 Inbound and outbound /SCWM/WMTORD Warehouse task

/SCWM/WMTCID01 Inbound /SCWM/WMTOCO Confirm 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

!--a11y-->

IDoc for Sending WTs to a Non-SAP System


Page 19 of 37


20/37

Definition

In Extended Warehouse Management , you use IDoc /SCWM/WMTOID01 to send data from warehouse tasks from EWM to connected non-SAP systems .

Use

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. 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.

Based on the 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 EWM message, which you have defined in the definition of the movement for connection to the interface.

Which IDoc the system fills and sends to the external system depends on several criteria:

Criteria Details

Warehouse movement type Putaway

Stock Removal

Stock Transfer

Posting Change

Warehouse process type Defining the warehouse process typeYou define, for example, whether the goods receipt date should be set during putaway.

Cause of the warehouse task Manual WT

WT for inbound or outbound delivery

WT for warehouse process type

Handling-unit-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 putawayin HU-managed storage types, the system transfers the HU

number in field NLENR.

For stock r emovalsfrom HU-managed storage types, the system

transfers the HU number in field VLENR.

For stock transfersbetween HU-managed storage types, the system

transfers the HU number in both fields.

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.

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 define the partner agreement outbound for message type /SCWM/WMTORD .

Segments

IDoc /SCWM/WMTOID01 is made up of the following segments:

/SCWM/E1LTOIRH (warehouse task header)

/SCWM/E1LTOIRH (warehouse task items)

/SCWM/E1LPHUX (pick-handling unit)

Segment definition /SCWM/ E2LTORH0040 (WT header)

Field Format Name Required Entry Comments

LGNUM CHAR 3 Warehouse Number X Activate linkage in warehouse

number first

WHO NUMC 10 Warehouse order

QUEUE NUMC 10 Queue

BNAME CHAR 12 User name

Fields for segment /SCWM/ E2LTORI00 04 (WT items)

Field Format Name Required Entry Comments


Page 20 of 37


21/37

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

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 Certificate number

KOMPL CHAR 1 Complete indicator

SQUIT CHAR 1 Confirmation indicator

KZQUI CHAR 1 Confirmation 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

Segment definition /SCWM/E2LPHUX000 (pick-handling unit)

Field Data Type Description Required Entry Comments

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 identification

PMAT CHAR 40 Packaging material

ANZHU NUMC 3 Number of pick-HUs to create

KZRTN CHAR 1 Confirmation to subsystem


Page 21 of 37


22/37

!--a11y-->

IDoc for Receiving WTs from a Non-SAP System

Definition

You use IDoc /SCWM/WMTCID01 to send warehouse-task-relevant data from the non-SAP system to Extended Warehouse Management (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 EWM.

You construct IDoc /SCWM/WMTOID02 in the non-SAP system to transfer the warehouse movement data to EWM. EWM receives the IDoc and creates a WT

from it, to execute the physical warehouse movements and post the storage bins involved. EWM creates a warehouse task from the IDoc data it received and

immediately confirms it.

You can also create warehouse tasks with incomplete entries in the non-SAP system and send these to EWM. In this case, EWM, as leading system,

adds the missing entries (for example, the coordinates of the destination storage bin) and sends the complete WT back to the external system. The non-SAP

system confirms the WT, completing the warehouse movement.

Structure

Message type

You define the partner agreement inbound for message type /SCWM/WMTORD .

Segments

IDoc /SCWM/WMTOID01 is made up of the following segments:

/SCWM/E1LTOIRH (warehouse task header)

/SCWM/E1LTOIRH (warehouse task items)

/SCWM/E1LPHUX (pick-handling unit)

For more information in segment definition, see IDoc for Sending WTs to a Non-SAP System.

Only use warehouse process types for this IDoc, which allow immediate confirmation. The physical stock movement has already taken place

when you receive information on a warehouse task from the non-SAP system in EWM.

!--a11y-->

IDoc for Confirming Warehouse Tasks

DefinitionYou use IDoc /SCWM/WMTCID01 to send confirmations from the non-SAP system to Extended Warehouse Management (EWM).

Use

You use this IDoc to report executed warehouse tasks (WTs) to EWM. EWM uses this reported data to confirm this WT.

Prerequisites

In Customizing for Extended Warehouse Management , under Master Data Define Storage Type or Cross-Process Settings Warehouse Task Define

Warehouse Process Type , you have spec ified which warehouse tasks are subject to a confirmation requirement.

When sending the WT data, EWM prev iously transmitted the data for the confirmation requirement in IDoc /SCWM/WMTOID01 in segment /SCWM/E1LTROI

with field KZQUI to the non-SAP system.

Confirmation of Handling Units

If you work with handling units (HUs) in your warehouse and move the entire handling unit, then you for this stock movement you confirm a warehouse task for the

entire HU.


Page 22 of 37
http://help.sap.com/saphelp_scm50/helpdata/en/24/f76f4151dc5758e10000000a1550b0/content.htm


23/37

If the HU is a mixed HU and you move individual products, then there are several warehouse tasks for this handling unit. You confirm the relevant warehouse task

for each stock movement.

During execution of the warehouse tasks, if you notice differences in the handling unit, then you confirm the entire handling unit and enter the difference quantity for

those items where you noticed a difference.

Confirmation without HU Management

For stock removals, you confirm entire warehouse tasks.

For putaway, you can confirm the WTs item by item, if you are putting away several pallets in your warehouse using one warehouse task.

During confirmation of entire WTs, you can enter differences for individual WT items.

Confirmation of Products Managed in Batches

If you confirm batch-managed products during goods movements in a HU-managed bulk storage type, you transmit the batch number of the removed products

with the confirmation data. You use the CHARG field (report batch for bulk storage) in segment /SCWM/E2LTCCOI004 .

Confirmation in a HU-Managed Bulk Storage Area

You report the picked HUs to EWM when you confirm the warehouse task.

If the reporting of individual HUs i s completed for a WT item, set the BQUIT field in the segment /SCWM/E1LTCOI .

In this case, you report the WT item by item. There can be several reports for each WT item. Only one report is allowed for each picked HU.

If the products are managed in batches, then you transfer the batch number of the products moved when you transfer the confirmation data. You use the CHARG

field (report batch for bulk storage) in segment /SCWM/E2LTCCOI004 .

Structure

Message type

You define the partner agreement inbound for message type /SCWMWMTOCO .

Segments

The IDoc for transferring confirmation is constructed as follows:

/SCWM/WMTCID01 (as of SAP APO 3.0A)

/SCWM/E1LTCOX : Confirm entire handling unit

/SCWM/E1LTCOH : Confirm WT header /SCWM/E1LTCOI : Confirm WT items

/SCWM/E1LCOHU : Confirm HU data for each WT item

Segment definition /SCWM/E2LTCOX002 : Confirm handling unit

Field Data Type Name Required Entry Comments

LGNUM CHAR 4 Warehouse Number X

LENUM CHAR 20 Handling unit X

QNAME CHAR 12 User name for the confirmation

SQUIT CHAR 1 Confirm entire HU X Value: X

NLPLA CHAR 18 Destination storage bin The destination storage bin refers

to the different storage bin for the

complete HU (Customizing)

NLENR CHAR 20 Destination handling unit

Segment definition /SCWM/E2CO HU000 : HU data for each WT item


LBNUM 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


Page 23 of 37


24/37

line within a WT item

Segment definition /SCWM/E2LTCOH000: WT header (released as of SAP R/3 4.6A)



WHO CHAR 12 Warehouse order

QNAME CHAR 12 User name for the confirmation

SQUIT CHAR 1 Indicator: Confirm entire

warehouse task

X If the entire warehouse task is to

be confirmed. (Version 2, 3, and

5)

Segment definition /SCWM/E2LTCOI0004 : WT items


LBNUM CHAR 12 Warehouse Task

SQUIT CHAR 1 Indicator: Confirm without

difference

X If the item is to be confirmed

without any differences

NISTA QUAN 31 Destination actual quantity X If there are differences in the

destination storage bin

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

destination storage bin

KZNUL CHAR 1 Indicator: Bin empty on zero stock

check

X If there is a zero stock 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 i nterim record for

differences

LENUM CHAR 20 Handling unit number X In case of confirmation in bulk

storage

VQUIT CHAR 1 Confirmation in bulk storage area,

pick entire HU

X In case of confirmation in bulk

storage

NLPLA CHAR 18 Destination storage bin If the destination storage bin differsfrom that suggested by the system

PAPOS NUMC 4 Sequential number of the HU data

line within a WT item

PARTI CHAR 1 Confirming a partial quantity for a

WT item

Only relevant for handling units

(HUs)

CHARG CHAR 10 Report batch number for bulk

storage area

!--a11y-->

1.5.5.4 IDoc for Canceling Warehouse Tasks

Definition

Using IDoc /SC WM/WMCAID01 , you can send a cancellation request to an external system, or confirm execution of a cancellation movement to Extended

Warehouse Management (EWM) .

Use

When physical stock movements are executed via the connected non-SAP system, EWM cannot determine whether the warehouse tasks (WTs) transferred to the

non-SAP system have already been executed. For this reason, the 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 confirms to 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 EWM.

You decide for each individual case what should happen with a WT item that cannot be cancelled. In this case, you make the necessary adjustments manually in

the system.


Page 24 of 37


25/37

You can only cancel warehouse tasks (WTs) if they have not yet been confirmed.

Sending a Cancellation Request from EWM to the Non-SAP System

To send a cancellation request from EWM, fill the following fields in IDoc /SCWM/ WMCAID01 :

Segment Field

/SCWM/E2LTCAH LGNUM

WHO

CANRQ

/SCWM/E2LTCAI LBNUM

Sending a Cancellation from the Non-SAP System to EWM

To send a cancellation of a WT to EWM, fill the following fields in IDoc /SCWM/WMCAID01 :

Segment Field

/SCWM/E2LTCAH LGNUM

WHO

CANCL

/SCWM/E2LTCAI LBNUM

You can also cancel a warehouse task from the non-SAP system and send the cancellation to EWM, even if EWM has not sent a cancellation

request first.

Structure

Message type

You define message type /SCWM/WMCATO for the inbound and outbound partner profile.

Segments

IDoc /SCWM/WMCAID01 is made up of two segments:

/SCWM/E2LTCAH (header data for the warehouse task)

/SCWM/E2LTCAH (item data for the warehouse task)

Segment definition /SCWM/E2LTCAH000



WHO CHAR 12 Warehouse order X

CNAME CHAR 12 User name for WT cancellation

CANRQ CHAR 1 Request cancellation warehouse

task

X X for cancellation request

CANCL CHAR 1 Response cancellation warehouse

task

X X for cancellation from external

system

Segment definition /SCWM/E2LTCAI000


LBNUM 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

!--a11y-->


Page 25 of 37


26/37

1.5.5.5 IDoc for Releasing Waves

Definition

The 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/E1LTORH for the WTs that have been

grouped together into waves.

Features

You group together the warehouse tasks into a wave so that you can execute the goods movements for these WTs 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 sys tem receives the warehouse task data. You use the IDoc /SCWM/WMRRID01 to trigger the start of the stock

movements for a certain wave by releasing the wave.

Structure

Message type

You define 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 Time (clock-time)

L2KSR CHAR 1 Relevance for two-step picking

LSKSO CHAR 1 Two-step picking: Release

approval level

!--a11y-->

1.5.5.6 IDoc for Blocking Storage Bins

Definition

Using IDoc /SCWM/WMBIID01 , you can send individual storage bin data or comprehens ive storage bin data (for example all of the storage bins in one aisle) for

blocking or unblocking from the non-SAP system to Extended Warehouse Management (EWM).

Use

When, for example, certain storage bins or aisles are inaccessib le for the external system due to technical problems, you block these storage bins in EWM so

that they are not considered during storage bin determination.

The non-SAP system initializes the block on the storage bins v ia IDoc /SCWM/WMBIID01 . As soon as the storage bins are available again, the external system

triggers the unblocking of the non-SAP system by EWM via IDoc /SCWM/WMBIID01.

Structure


Page 26 of 37


27/37

Message type

You define the partner agreement inbound for message type /SCWM/WMBBIN .

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 c ertain storage bins individually, transfer a /SCWM/E1LBINI segment for each s torage bin.

Segment definition /SCWM/E2LBINH000

Field Data Type Description Required Entry Com