E2TPTRM- Location Identification

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 twice or up 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	Adj.	Format	SAP Domains	Oblig. Field	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 ID
TSPNT		CHAR 01			Load transfer point ID
ADRNR		CHAR 10	ADRNR		Address number

Special Fields and Domain Values in Segment E2TPTRM

Please take into account certain particular functions and/or permitted value areas in the following fields from segment E2TPTRM.

Field E2TPTRM-TLCCAT: Location Status

This ID specifies the status of the current segment for planning specifications.

Value	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

IDs ‘1’ and ‘2’ occur if a transportation planning system is not used for all the planning of a delivery but, for example, only for the preliminary and subsequent leg planning. For instance 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.

Field E2TPTRM-TRMTYP: Location Category

Category of current location. Different fields within the segment are filled with data according to category.

Value	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 point	NODEID, NODTYP, BORDER, TSPNT, ADRNR
SP	Shipping point	SHPPNT, LODPNT, LDPTXT, ADRNR
CA	Service agent	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.

Value	Significance
C	Distribution center
A	Airport
R	Railway station
E	Express railway station
H	Harbor
S	Road

Example: E2TPTRM-NODTYP = ‘CRS’ means a distribution center with railway and road connections.

Field E2TPTRM-BORDER: Border Location Identification

This ID specifies whether the transportation connection point is a border location.

Value	Significance
0	Non-border location
1	Border location

Field E2TPTRM-TSPNT: Load Transfer Point Identification

This ID specifies whether the transportation connection point is a load transfer point.

Value	Significance
0	Non-load transfer point
1	Load transfer point

This graphic is explained in the accompanying text.

Note the following when processing inward shipment (IDoc TPSSHT01):

Fields NODEID, SHPPNT, LODPNT, SHPPTY, ULDPNT, SUPPLR, SLDPNT, PLANT and STRLOC are included in the location definition of the departure or destination location of a leg in the shipment document.

This takes place according to the following rule:

IDoc	SAP System Shipping 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

The fields are completed as follows:

IDoc	SAP System Shipping 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

This graphic is explained in the accompanying text.

Only one field can be completed in fields NODEID , SHPPNT, SHPPTY, SUPPLR and PLANT.

Field LODPNT is optional and should only be completed if field SHPPNT has been completed.

Field STRLOC is optional and should only be completed if field PLANT has been completed.

Field ULDPNT is optional and should only be completed if field SHPPTY has been completed.

Field SLDPNT is optional and should only be completed if field SUPPLR has been completed.

All other fields in this segment are ignored.

An error occurs if the location definition does not adhere to the rules described above.