Entering content frameBackground documentation Data Formatting Locate the document in its SAP Library structure

The system transfers data to structures EDI_DC40 and EDI_DD40. Since these structures are also used for EDI, some of the fields are redundant for the WMS-WCU interface.

For more information see Basis ® Basis Services/Communication Interface ® The IDoc Interface ® IDoc Interface/Electronic Data Interchange ® Processing IDocs ® Inbound Processing ® Structure linkInbound Processing: Technical Background.

EDI_DD40

Field

Format

Description

Relevant for Receipt

Note

TABNAM

CHAR 10

Table structure name

  

Not relevant

MANDT

CLNT 3

Client

  

Not relevant, but transferred to external 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

PSGNUM

CHAR 6

Number of higher-level SAP segment

 

Transferred to external system, but not imperative during receipt

HLEVEL

CHAR 2

Hierarchy level of SAP segment

  

Transferred to external system, but not imperative during receipt

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

Feld

Format

Description

Relevant for Receipt

Note

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

  

Transferred to external system, nut not required for receipt

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_001" 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

*

Both fields can be used to define a function module other than the standard for processing the IDoc in the ALE service layer in the table of input methods

MESFCT

CHAR 3

Logical message function

*

Both fields can be used to define a function module other than the standard for processing the IDoc in the ALE service layer in the table of input methods

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: "S11MAN000" 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 transfer orders

IDOCTYP

CHAR 8

Name of basis IDoc

X

For example WMTOID01 for TOs

CIMTYP

CHAR 8

Name of intermediate structure

    

RCVPFC

CHAR 2

Partner function of recipient

    

SNDPFC

CHAR 2

Partner role of sender

    

SERIAL

CHAR 20

EDI/ALE: Serialization field

    

EXPRSS

CHAR 1

Override during receipt

    

 

Note

You must not fill all of the EDI_DC and EDI_DD fields. Make sure that you initialize the fields that should not be filled first.

On creation of the IDoc in the SAP R/3 system with transaction /nWE30, the system automatically creates three structures for each IDoc segment, which are also numbered sequentially, for example for the transfer order item E1LTORI, E2LTORI, and E3LTORI. E1LTORI is release-independent, E2LTORI release-dependent, and E3LTORI is used 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 transfer order with three items for each IDoc from the external system to the Warehouse Management System (WMS), you transfer one header segment and three item segments per IDoc. In doing so, you send one EDI-DC40 record and four EDI_DD40 records per IDoc. The four segments of an IDoc are pinned together with the unique number of the IDoc. The corresponding EDI_DC record is also identified from the DOCNUM.

You transfer two internal tables with the following construction:

EDI_DD40

9000000000123456

E2LTORH

00112345678905011E

... (TO header data)

9000000000123456

E2LTORI

0001FRASCATI

... (Item)

9000000000123456

E2LTORI

0002BORDEAUX

... (Item)

9000000000123456

E2LTORI

0003CHIANTI

... (Item)

9000000000123457

E2LTORH

00112345678912011A

... (TO header data)

9000000000123457

E2LTORI

0001CHATEAU-NEUF

... (Item)

9000000000123457

E2LTOR

0002BORDEAUX

... (Item)

9000000000123457

E2LTORI

0003SOAVE

... (Item)

 

EDI_DC40

9000000000123456

DS

S11MAND002

DS

SUBSYSTEM1

WMTORD

WMTOID01

9000000000123457

DS

S11MAND002

DS

SUBSYSTEM1

WMTORD

WMTOID01

 

 

Leaving content frame