Data Formatting 
The system transfers data to structures EDI_DC40 and 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 |
PSGNUM |
CHAR 6 |
Number of higher-level SAP segment |
|
The system transmits 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 the non-SAP system, but is not required at 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
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 the non-SAP system, but is not required at 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_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, which 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, which is used to process IDocs. |
OUTMOD |
CHAR 1 |
Output mode |
|
|
TEST |
CHAR 1 |
Test indicator |
|
|
SNDPOR |
CHAR 10 |
Sender port |
|
Not relevant |
SNDPRT |
CHAR 2 |
Partner type of sender |
X |
Value: LS |
SNDPRN |
CHAR 10 |
Partner number of 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 |
|
|
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 initialize any 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. For example, for the warehouse task item /SCWM/E1LTORI, /SCWM/E2LTORI, and /SCWM/E3LTORI. /SCWM/E1LTORI is release-independent, /SCWM/E2LTORI is release-dependent, and the system uses /SCWM/E3LTORI for documentation.
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 |