E2TPTRM- Location Identification
Definition
Segment E2TPTRM contains the identification numbers of a location which can be used as a key to an address database. The segment may occur within IDoc TPSDLS01 from two to four times. With the minimum number of 2, the departure and destination location identification are transferred and in the next two segments, the sold-to party and payer ID can be defined.
Field name |
Adjust. |
Format |
SAP |
Req’d |
Significance |
TLCCAT |
1 |
CHAR 01 |
X |
Location status | |
TRMTYP |
1 |
CHAR 02 |
X |
Location category | |
SHPPNT |
A |
CHAR 04 |
VSTEL |
Shipping point | |
LODPNT |
A |
CHAR 02 |
LSTEL |
Loading point | |
LDPTXT |
CHAR 20 |
BEZEI20 |
Loading point text | ||
PLANT |
A |
CHAR 04 |
WERKS |
Plant | |
STRLOC |
A |
CHAR 04 |
LGORT |
storage location | |
STLTXT |
CHAR 16 |
LGOBE |
Storage location text | ||
SHPPTY |
A |
CHAR 10 |
KUNNR |
Ship-to party, customer number | |
ULDPNT |
A |
CHAR 25 |
ABLAD |
Unloading point | |
SUPPLR |
A |
CHAR 10 |
LIFNR |
Vendor | |
SLDPNT |
A |
CHAR 25 |
BELAD |
Loading point | |
NODEID |
A |
CHAR 10 |
KNOTN |
Transportation connection point | |
NODTYP |
CHAR 10 |
Transportation connection point characteristic | |||
BORDER |
CHAR 01 |
Border location indicator | |||
TSPNT |
CHAR 01 |
Load transfer point indicator | |||
ADRNR |
CHAR 10 |
ADRNR |
Address number |
Special Fields and Domain Values in Segment E2TPTRM
Please take into account these particular functions and/or permitted value areas in the following fields in segment E2TPTRM.
E2TPTRM-TLCCAT field: Location status
This indicator specifies the status of the current segment for planning specifications.
Val. |
Significance |
S |
Departure location that corresponds to the delivery’s shipping location |
D |
Destination that corresponds to the delivery’s destination |
1 |
Departure location that does not correspond to the delivery’s shipping location |
2 |
Destination that does not correspond to the delivery’s destination |
B |
Sold-to party |
P |
Payer |
Indicators 1 and 2 occur if a transportation planning system is used only for preliminary and subsequent leg planning, for example, and not for the entire planning of a delivery. For instance, one segment E2TPTRM with location status S and one with location status 2 would appear for the preliminary leg between the shipping point and the departure harbor.
E2TPTRM-TRMTYP field: Location category
Category of current location. Different fields within the segment are filled with data according to category.
Val. |
Significance |
Completed fields |
PL |
Plant |
PLANT, STRLOC, STLTXT, ADRNR |
CU |
Customer |
SHPPTY, ULDPNT |
SU |
Vendor |
SUPPLR, SLDPNT |
OC |
One-time customer |
SHPPTY, ADRNR |
NO |
Transportation connection point, distribution center |
NODEID, NODTYP, BORDER, TSPNT, ADRNR |
SP |
Shipping point |
SHPPNT, LODPNT, LDPTXT, ADRNR |
CA |
Service agents |
SUPPLR, SLDPNT |
AD |
Address |
ADRNR |
Field E2TPTRM-NODTYP: Transportation connection point characteristic
The field lists the different characteristics of a transportation connection point. Each characteristic is coded with a single letter. Up to 10 characteristics can be shown in field E2TPTRM-NODTYP as a character string.
Val. |
Significance |
C |
Distribution center |
A |
Airport |
R |
Railway station |
E |
Express railway station |
H |
Harbor |
S |
Street |
Example: E2TPTRM-NODTYP = CRS means a distribution center with railway and road connections.
E2TPTRM-BORDER field: Border location indicator
This indicator specifies whether the transportation connection point is a border location.
Val. |
Significance |
0 |
Non-border location |
1 |
Border location |
E2TPTRM-TSPNT field: Load transfer point indicator
This indicator specifies whether the transportation connection point is a load transfer point.
Val. |
Significance |
0 |
Non-load transfer point |
1 |
Load transfer point |
Please note the following when processing an inbound shipment (IDoc TPSSHT01).
The NODEID, SHPPNT, LODPNT, SHPPTY, ULDPNT, SUPPLR, SLDPNT, PLANT and STRLOC fields are included in the location definition of the departure or destination location of a leg in the shipment document.
This occurs according to the following schema:
IDoc |
R/3 System shipment document |
1st location |
1st leg departure location |
2nd location |
1st leg destination + 2nd leg starting point |
3rd location |
2nd leg destination + 3rd leg starting point |
Fields are completed as follows:
IDoc |
R/3 System shipment document | |
Leg: departure location |
Leg: destination | |
E2TPTRM-NODEID |
VTTS-KNOTA |
VTTS-KNOTZ |
E2TPTRM-SHPPNT |
VTTS-VSTEL |
VTTS-VSTEZ |
E2TPTRM-LODPNT |
VTTS-LSTEL |
VTTS-LSTEZ |
E2TPTRM-SHPPTY |
VTTS-KUNNA |
VTTS-KUNNZ |
E2TPTRM-ULDPNT/SLDPNT |
VTTS-BELAD |
VTTS-ABLAD |
E2TPTRM-SUPPLR |
VTTS-LIFNA |
VTTS-LIFNZ |
E2TPTRM-PLANT |
VTTS-WERKA |
VTTS-WERKZ |
E2TPTRM-STRLOC |
VTTS-LGORTA |
VTTS-LGORTZ |
Only one of the following fields can be completed: NODEID, SHPPNT, SHPPTY, SUPPLR and PLANT.
The LODPNT field is optional and should only be completed if the SHPPNT field has been completed.
The STRLOC field is optional and should only be completed if the PLANT field has been completed.
The ULDPNT field is optional and should only be completed if the SHPPTY field has been completed.
The SLDPNT field is optional and should only be completed if the SUPPLR field has been completed.
All other fields in this segment are ignored.
If the location definition does not follow the rules listed above, an error occurs.