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, i.e., those that refer to the whole shipment. E2EDT13 contains processes at delivery header level, i.e. processes that refer to the whole delivery. E2EDT17 represents processes in the shipment at stage level, i.e. processes that refer to a specific stage or point during the shipment.

The three segment types are all structured as follows:

In the following fields from segments E2EDT1x, you must take note of special functions and/or allowed value areas.

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:

The following process categories are extremely important and should be taken into consideration.

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.

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 R/3 shipment document as the transportation planning time.

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:

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

Time zone code. Value area according to R/3 table field TTZZ-TZONE.