Jungheinrich WCS

Host interface WCS to SAP

Version: 2.6

Date: 10.04.2020
COPYRIGHT
This document and its contents (text, photos and drawings) are protected by copyright.
The copyright owner is Jungheinrich AG, headquartered in Hamburg, Germany. Re-
production in any form (photocopying, scanning, etc.), editing, distribution, translation
or any other type of commercial exploitation is prohibited.

Jungheinrich Aktiengesellschaft
Friedrich-Ebert-Damm 129
22047 Hamburg
Germany

Phone: +49 (0) 40 6948 – 0

Fax: +49 (0) 40 6948-1777
www.jungheinrich.com

Host interface WCS to SAP 10.04.2020

Version 2.6 Page 2 of 14

Table of contents
1 Introduction .............................................................................................. 4

2 Technical data exchange ........................................................................ 5

2.1 RFC ........................................................................................................... 5
2.1.1 tRFC .......................................................................................................... 5
2.1.1.1 Parameters for tRFC.................................................................................. 6
2.1.1.2 Process description ................................................................................... 6
2.2 SAP PI ....................................................................................................... 6

3 WCS .......................................................................................................... 8

3.1 Goods movement ...................................................................................... 9

3.1.1 Transport order (SAP  WCS: WMTOID)............................................... 10
3.1.2 Transport order confirmation (WCS  SAP: WMTCID) .......................... 11
3.1.3 Transport order cancellation request (SAP  WCS: WMCAID) .............. 12
3.1.4 Transport order cancellation response (WCS  SAP: WMCAID) ........... 13

Host interface WCS to SAP 10.04.2020

Version 2.6 Page 3 of 14

1 Introduction
This document describes the standard interface between WCS and SAP.

The described interface is only a template. You need to adapt it for each customer.
This has to be done in a separate interface specification which has to be created to-
gether with the customer.

Host interface WCS to SAP 10.04.2020

Version 2.6 Page 4 of 14

2 Technical data exchange
It is possible to exchange IDOCs (Intermediate Documents) between WMS/WCS and
SAP in two different ways:
 transactional Remote Function Call (tRFC)
 SAP Process Integration (SAP PI)

2.1 RFC
IDOCs which are transmitted via tRFC serve to implement the interface to SAP.

The exchange of data between the WMS/WCS and SAP is done by transmitting IDOCs
(Intermediate Documents). The IDOCs are transmitted via the transactional Remote
Function Call (tRFC) interface by SAP. SAP developed the Remote Function Call
Application Programming Interface (RFC-API) to enable external systems to access
SAP functionalities, which are usually only accessible in the local SAP system.

The RFC-API can be used by a number of applications and is provided as a library of

C-functions. RFC-API is responsible for managing the connections, the communication
and the emulation of the ABAP/4 calling conventions.

2.1.1 tRFC
Errors can occuring during the conventional data transmission via RFC. This means
that the data transmission is not secure. That is why the data exchange between the
WMS/WCS and SAP is carried out via tRFC.
The aim of tRFC is to ensure a secure data transmission so that each transaction can
only be processed once. tRFC stands for transactional Remote Function Call. This
means that every transaction is provided with a unique prefix for identification. The
prefix is responsible for a clear data transmission and prevents data redundancy during
transmission.

The following mechanism can ensure clear data definition. When a remote function
is called up, the SAP host system assigns a globally recognised prefix to a transaction.
This prefix is also transmitted to the client (principal). If an error occurs during data
transmission, the transmission can be repeated with the same prefix. The SAP server
checks whether the dataset with this prefix has yet been processed. If not, the data is
processed. After that, the prefix is marked as processed. This prevents the data from
being processed twice if it is resent during a later transmission. Finally, the client (prin-
cipal) is informed that the transaction with a specific prefix has been processed. Server
and client (principal) can remove the prefix. The transaction is finished.

Host interface WCS to SAP 10.04.2020

Version 2.6 Page 5 of 14

2.1.1.1 Parameters for tRFC
To be clarified in a later project phase.

2.1.1.2 Process description

For the communication with SAP there are two processes on the WMS/WCS side:
 Receipt process: SAP  WMS/WCS
 Transmit process: WMS/WCS  SAP
Both processes were implemented (SAP NetWeaver RFC SDK) according to certifica-
tion specifications (Certified for integration with SAP ECC 6.0 via the SAP integration
scenario LE-IDW 4.6).

The receipt process registers as server at a SAP gateway and waits for the transmis-
sion triggered by SAP.
The transmit process registers as client at a SAP application server and transmits
IDOCs to SAP. The WMS/WCS is responsible for creating the IDOCs.

For the communication both processes register with a SAP user at the SAP system.
The customer must provide the user.

2.2 SAP PI
Data exchange between WMS/WCS and SAP is realised by means of XML files. The
XML files are processed by the WMS/WCS via Windows file operations.

There is one directory, which is used for the exchange. Both systems (WMS/WCS,
SAP) put the XML files which should be transmitted into this directory.
Initially, the sender provides data in a temporary file. Only after the write or copy pro-
cess has been completed, the file is renamed to the actually agreed extension
(xxxxxxx.TMP  xxxxxxx.XML). Thanks to this procedure, simultaneous access to the
same file can be prevented. The data of the respective reception system is received
and processed at cyclic intervals. After the files have been received, the reception sys-
tem deletes and stores them, if necessary.

The WMS/WCS stores the sent and received files in a backup directory. The same
transmission procedure is simultaneously applied for a test system (two additional di-
rectories).

Structure of the XML file:

Name scheme:
 WMS/WCS  SAP: WMS/WCS_nnnn.xml
 SAP  WMS/WCS: SAP_nnnn.xml

Host interface WCS to SAP 10.04.2020

Version 2.6 Page 6 of 14

Normally, the IDOC number and the actual timestamp are used for the file name. This
ensures that every file has a unique name.

Each file contains one IDOC. For performance reasons SAP can be configured in a
way that the file only contains segments and fields which are needed for the project.
In the course of the project, the customer provides the needed IDOC specification
which can be generated in SAP.

Host interface WCS to SAP 10.04.2020

Version 2.6 Page 7 of 14

3 WCS
The following list provides an overview of all aspects of the WCS standard interface
with the according IDOCs in parenthesis:
 Goods movement:
 SAP  WCS: transport order (WMTOID)
 WCS  SAP: transport order confirmation (WMTCID)
 SAP  WCS: transport order cancellation request (WMCAID)
 WCS  SAP: transport order cancellation response (WMCAID)

In the following chapters, only the fields that relevant for the WCS are described. The
specific, exchanged IDOCs include the full set of data (all segments containing all data
fields) according to the definition of the used SAP system.

Host interface WCS to SAP 10.04.2020

Version 2.6 Page 8 of 14

3.1 Goods movement
This interface renders it possible to move LCs in the warehouse via the WCS. In this case SAP behaves like a WMS and is responsible
for the following processes:
 Stock administration
 Stocktaking
 Customer order management
 Scheduling of warehouse movements

The WCS is responsible for the following activities:

 Controlling the material flow
 Navigating forklift trucks
 Optimising resources

The WCS only moves full-LCs!

Example: Putaway and retrieval via conveyor system:

A truck delivers new goods which are registered by means of SAP. This means that stocks and LCs are captured and that a transport
order (TRART = E) is sent to the WCS. Next, the LC is put on the conveyor system and moved towards the I-point. The WCS receives
a signal from the I-point and determines the transport destination. The destination is possibly determined by means of an existing
contour control which is used for identifying the LC type. As the WCS is responsible for coordinating the forklift trucks, it determines
the destination in order to ideally use the truck capacity. Next, the LC is put away. After the arrival at the destination, the transport
order is acknowledged and reported to SAP.

Host interface WCS to SAP 10.04.2020

Version 2.6 Page 9 of 14

If you want to retrieve this LC again (e.g. for a customer order), SAP sends a new transport order (TRART = A) and predetermines a
destination (e.g. picking area, loading gate). The WCS carries out the movement. When the LC arrives at its destination, am acknowl-
edgement is reported to SAP.

3.1.1 Transport order (SAP  WCS: WMTOID)

Field Type M/ Field in WCS Comment WCS internal*
(Length) O

E1LTORH (TO header – 1:1)

LGNUM (Warehouse num- CHAR (3) M SAP Warehouse- Hostkopf.P1

ber) number

TANUM (Transport order CHAR (10) M Order number Needed to identify order in WCS Hostkopf.Auftr
number)
Hostin.Auftr

TRART (Transport type) CHAR (1) M Order type E: Putaway Hostkopf.Atyp

A: Stock Removal Hostin.Atyp

E2LTORI (TO item – 1:1)

TAPOS (Transport order CHAR (3) M Entry within order Entry within order Hostin.Pos
item)

NLENR (Destination stor- CHAR (20) (M) LC-number Has to be set if TRART = E Hostin.LhmNr
age unit number)
Hostin.P1

Host interface WCS to SAP 10.04.2020

Version 2.6 Page 10 of 14

 NLBER (Destination stor- CHAR (3) (M) Destination Area Has to be set if TRART = 'A' Hostin.PlatzNr
age area)
Destination area

VLENR (Source storage CHAR (20) (M) LC-number Has to be set if TRART = 'A' Hostin.LhmNr
unit number)
Hostin.P1

MATNR (Material) CHAR (18) O Product code Hostin.Anr

CHARG (Batch) CHAR (10) O Batch number only if MATNR is set Hostin.Charge

*WCS internal field, not relevant for customer

3.1.2 Transport order confirmation (WCS  SAP: WMTCID)

Field Type M/ Field in WCS Comment WCS internal*
(Length) O

E1LTCOH (Confirm TO header – 1:1)

LGNUM (Warehouse num- CHAR (3) M SAP Warehouse- Hostkopf.P1

ber) number

TANUM (Transport order CHAR (10) M Order number Needed to identify order in WCS Hostkopf.Auftr
number)
Hostin.Auftr

Host interface WCS to SAP 10.04.2020

Version 2.6 Page 11 of 14

 E1LTCOI (Confirm TO item – 1:1)

TAPOS (Transport order CHAR (3) M Entry within order Entry within order Hostin.Pos
item)

SQUIT (Confirm entire CHAR (1) M Fix. X

storage unit)

*WCS internal field, not relevant for customer

3.1.3 Transport order cancellation request (SAP  WCS: WMCAID)

Field Type M/ Field in WCS Comment WCS internal*
(Length) O

E1LTCAH (TO header data – 1:1)

LGNUM (Warehouse num- CHAR (3) M SAP Warehouse- Hostkopf.P1

ber) number

TANUM (Transport order CHAR (10) M Order number Needed to identify order in WCS Hostkopf.Auftr
number)
Hostin.Auftr

CANRQ (Request cancel- CHAR (1) M X for cancellation request

lation transport order)

Host interface WCS to SAP 10.04.2020

Version 2.6 Page 12 of 14

 E1LTCAI (TO item data – 1:1)

TAPOS (Transport order CHAR (3) M Entry within order Entry within order Hostin.Pos
item)

*WCS internal field, not relevant for customer

3.1.4 Transport order cancellation response (WCS  SAP: WMCAID)

Field Type M/ Field in WCS Comment WCS internal*
(Length) O

E1LTCAH (TO header data – 1:1)

LGNUM (Warehouse num- CHAR (3) M SAP Warehouse- Hostkopf.P1

ber) number

TANUM (Transport order CHAR (10) M Order number Needed to identify order in WCS Hostkopf.Auftr
number)
Hostin.Auftr

CANCL (Response cancel- CHAR (1) M X for cancellation response

lation transport order)

E1LTCAI (TO item data – 1:1)

TAPOS (Transport order CHAR (4) M Entry within order Entry within order Hostin.Pos
item)

Host interface WCS to SAP 10.04.2020

Version 2.6 Page 13 of 14

 SFEHL (Error during can- CHAR (1) O X if an error occurred
cellation)

SFTXT (Error text for can- CHAR (80) O Error text if an error occurred
cellation)

*WCS internal field, not relevant for customer

Host interface WCS to SAP 10.04.2020

Version 2.6 Page 14 of 14