Description of the IDoc Segments, Fields and Domain Values 
The following section describes the individual segments of IDocs TPSLOC01, TPSDLS01, TPSSHT01 and SYSTAT01. The fields contained in the segments are all listed with name, data category with length, corresponding R/3 domains, obligatory field indicators and their meaning. In the connection to the field list, segment fields that have special properties, fixed value areas or non-R/3 functionality are described in greater detail.
Adjustment and Setting of Domain Values
During communication between the R/3 system and the transportation planning system, adjustment and setting of many fixed values is necessary in order to guarantee correct and efficient planning and processing. To this end, the following adjustment procedures are used to determine how and in which system adjustments need to be made.
Adjust. |
Significance |
1 |
SAP sets the standard that must be implemented in the planning system |
2 |
Manual master data adjustment between the systems, R/3 is master system |
3 |
Different value areas are used in both the R/3 system and in the planning system. Duplicated or common values can be adjusted |
4 |
SAP adopts the value area of the planning system for it’s development partner into the R/3 system |
5 |
The R/3 system is adjusted in Customizing to the planning system value area |
6 |
Translation / adjustment of technical expressions between the two systems |
7 |
Value area is fixed and was determined by agreement between SAP and development partners |
8 |
SAP defines a basic value are which must be included in the planning system. It can be enhanced and must then also be enhanced in R/3 Customizing, if necessary |
9 |
The value area is specified with international standards (e.g. ANSI, ISO,...) |
A |
Electronic master data adjustment per data transfer, R/3 is the master system |
B |
Master data value that can be set as customer-specific and can only be adjusted in special circumstances |
The various adjustment procedures are listed in the table with the segment descriptions in the Adjustment column. If no specification is made here, then you only need to take the specifications on data formats into account.
E2EDT1x - Processes E2KNVAM - Opening Times Profiles E2STATS - EDI Status Record E2TPACC - Action Code E2TPALC - Permitted Service Agent E2TPCOC - Goods Code E2TPDIH - Delivery Dimensions at Header Level E2TPDII - Delivery Dimensions at Item Level E2TPDIS - Shipping Unit Dimensions E2TPDLC - Shipment Costs at Delivery Level E2TPDLH - Delivery Header E2TPDLI - Delivery Item E2TPEQT - Means of Transport E2TPFRC - Shipment Costs at Shipment Header Level E2TPLCT - Location Code E2TPLOC - Location Master Record Address E2TPNOT - Delivery Texts E2TPSHA - Transport Activity E2TPSHH - Shipment Header E2TPSHI - Delivery in Shipment E2TPSHR - Rail Data E2TPSHT - Leg Data in Shipment E2TPSHU - Shipping Unit E2TPSLS - Shipment Points E2TPSUC - Shipping Unit Contents E2TPTIW - Time Frame E2TPTRP - Existing Shipment E2TPTRM- Location Identification