E2EDT1x - Processes 
Segments E2EDT10, E2EDT13 and E2EDT17 describe processes at different document levels. The structures of the segments are the same. They are only different in the location and the categories of the processes that they represent.
· Segment E2EDT10 represents processes at shipment header level; that is, those that refer to the whole shipment.
· E2EDT13 contains processes at delivery header level; that is, processes that refer to the whole delivery.
· E2EDT17 represents processes in the shipment at stage level; that is, processes that refer to a specific stage or point during the shipment.
The three segment types are all structured as follows:
Field name |
Adjust. |
Format |
SAP |
Oblg. field |
Significance |
QUALF |
8 |
CHAR 03 |
|
X |
Process category |
VSTZW |
8 |
CHAR 04 |
VSTZW |
|
Process |
VSTZW_BEZ |
|
CHAR 20 |
BEZEI20 |
|
Significance of process |
NTANF |
|
DATS 08 |
DATUM |
|
Planned start date |
NTANZ |
|
TIMS 06 |
UZEIT |
|
Planned start time |
NTEND |
|
DATS 08 |
DATUM |
|
Planned end date |
NTENZ |
|
TIMS 06 |
UZEIT |
|
Planned end time |
TZONE_BEG |
8 |
CHAR 06 |
TZNZONE |
|
Time zone of location of process start |
ISDD |
|
DATS 08 |
DATUM |
|
Actual start date |
ISDZ |
|
TIMS 06 |
UZEIT |
|
Actual start time |
IEDD |
|
DATS 08 |
DATUM |
|
Actual end date |
IEDZ |
|
TIMS 06 |
UZEIT |
|
Actual end time |
TZONE_END |
8 |
CHAR 06 |
TZNZONE |
|
Time zone of location of process end |
VORNR |
|
CHAR 04 |
VORNR |
|
Number of process |
VSTGA |
5 |
CHAR 04 |
VSTGA |
|
Code for reason of deviation |
VSTGA_BEZ |
|
CHAR 20 |
BEZEI20 |
|
Description of reason of deviation |
Special Fields and Domain Values in Segments E2EDT1x
In the following fields from segments E2EDT1x, you must take note of special functions and/or allowed value areas.
Field E2EDT1x-QUALF: Process category
The field can adopt the following values in the segments described, which involves entering data in the specified field from the table. Values in brackets are allowed for transfer to the IDoc, but are not evaluated during standard inbound processing:
Value |
Significance |
E2EDT10 |
E2EDT13 |
E2EDT17 |
001 |
Transportation planning time |
NTENx |
NTENx |
|
003 |
Loading time/execution |
NTANx, NTENx |
NTENx |
( NTANx,NTENx) |
005 |
Transportation processing |
NTANx, NTENx |
|
|
006 |
Goods issue time |
|
NTENx |
|
007 |
Delivery time |
|
NTENx |
|
008 |
Arrival time |
|
NTENx |
( NTENx) |
009 |
Departure time |
|
NTENx |
( NTANx) |
010 |
Picking time |
|
NTENx |
|
011 |
Time of stay |
|
|
NTANx, NTENx |
012 |
Unloading time |
|
|
( NTANx,NTENx) |
013 |
Time of customs clearance |
|
|
( NTANx,NTENx) |
014 |
Load transfer point |
|
|
( NTANx,NTENx) |
018 |
Optimum arrival time |
|
|
( NTENx) |
019 |
Optimum departure time |
|
|
( NTANx) |
Important Process Categories:
The following process categories are extremely important and should be taken into consideration.
Segment E2EDT13 (Process at Delivery Header Level) in IDoc TSPDLS01
The time framework for planning the shipment is given in departure time (009) and arrival time (008). These must be used for planning. The final planned data is entered here.
For direct shipment of the delivery (that is, during a shipment from the shipping point to the customer, the departure time corresponds with the loading time and the arrival time corresponds with the unloading time). If, however, only a preliminary leg shipment is planned (that is, from the shipping point to the port of departure) then the delivery time is no longer relevant for actual planning.
Segment E2EDT10 (Process at Shipment Level) in IDoc TPSSHT01
The time framework for carrying out the shipment is given in transportation processing (005) in the planned start and end dates.
Loading (003) is optional and contains planned start and end dates.
Time of transportation planning (001) is optional. It contains planned end dates. If it is not specified, then the posting time is determined automatically in the shipment document as the transportation planning time.
Segment E2EDT17 (Process at Shipment Stage Level) in IDoc TSPSHT01
Field QUALF: Only the date with qualifier ‘011’ (Time of stay) is taken into account. All other dates are ignored.
The planned and actual dates (both start and end) for a location are converted into the planned and actual dates for the legs. This means that the end date for a location becomes the start date for the leg that starts at this location. Similarly, the start date of the next location becomes the end date of the leg that finishes at this location.
This can be summarized as follows:
IDoc |
SAP System Shipment Document |
1st location, E2EDT17-NTEND |
1st leg, VTTS-DPTBG |
1st location, E2EDT17-NTENZ |
1st leg, VTTS-UPTBG |
1st location, E2EDT17-IEDD |
1st leg, VTTS-DATBG |
1st location, E2EDT17-IEDZ |
1st leg, VTTS-UATBG |
2nd location, E2EDT17-NTANF |
1st leg, VTTS-DPTEN |
2nd location, E2EDT17-NTANZ |
1st leg, VTTS-UPTEN |
2nd location, E2EDT17-ISDD |
1st leg, VTTS-DATEN |
2nd location, E2EDT17-ISDZ |
1st leg, VTTS-UATEN |
Entries are similar for further locations.
The start dates of the first location and the end dates of the last location are ignored. All other fields are also ignored.
Field E2EDT1x-TZONE_xxx: Time zone
Time zone code. Value derived from SAP table field TTZZ-TZONE.