LOCATION_I SAP (City: Identification) Structure details
Description: City: Identification
Structure field list including key, data, relationships and ABAP select examples
LOCATION_I is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "City: Identification" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_LOCATION_I TYPE LOCATION_I.
The LOCATION_I table consists of various fields, each holding specific information or linking keys about City: Identification data available in SAP. These include VSTEL (Location: Shipping point), LSTEL (Location: Loading point at shipping point), KUNNR (Location: Customer), KUNABL (Location: Customer's unloading point).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Not classified
SAP LOCATION_I structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| KNOTE | Location: Points | L_KNOTE | CHAR | 10 | TVKN | KNOTN | |||
| VSTEL | Location: Shipping point | L_VSTEL | CHAR | 4 | TVST | VSTEL | VST | ||
| LSTEL | Location: Loading point at shipping point | L_LSTEL | CHAR | 2 | TVLA | LSTEL | |||
| KUNNR | Location: Customer | L_KUNNR | CHAR | 10 | KNA1 | ALPHA | KUNNR | KUN | |
| KUNABL | Location: Customer's unloading point | L_KUNABL | CHAR | 25 | KNVA | TEXT25 | |||
| LIFNR | Location: Vendor | L_LIFNR | CHAR | 10 | LFA1 | ALPHA | LIFNR | LIF | |
| WERKS | Location: Plant | L_WERK | CHAR | 4 | T001W | WERKS | WRK | ||
| LGORT | Location: Storage location in plant | L_LGORT | CHAR | 4 | T001L | LGORT | LAG | ||
| LGNUM | Location: Warehouse number | L_LGNUM | CHAR | 3 | T300 | LGNUM | LGN | ||
| TOR | Location: Door for warehouse number | L_LGTOR | CHAR | 3 | T30B | LGTOR | |||
| BELAD | Loaction: Additional information (e.g. load./unload.point) | L_BEABLAD | CHAR | 25 | TEXT25 | ||||
| NAME1 | Name 1 | AD_NAME1 | CHAR | 40 | TEXT40 | ||||
| CITY1 | City | AD_CITY1 | CHAR | 40 | TEXT40 | CLCITYNAME | |||
| POST_CODE1 | City postal code | AD_PSTCD1 | CHAR | 10 | CHAR10 | ||||
| POST_CODE2 | PO Box Postal Code | AD_PSTCD2 | CHAR | 10 | CHAR10 | ||||
| POST_CODE3 | Company Postal Code (for Large Customers) | AD_PSTCD3 | CHAR | 10 | CHAR10 | ||||
| STREET | Street | AD_STREET | CHAR | 60 | TEXT60 | CLSTRTNAME | |||
| STREETCODE | Street Number for City/Street File | AD_STRNUM | CHAR | 12 | Assigned to domain | ALPHA | STRT_CODE | ||
| HOUSE_NUM1 | House Number | AD_HSNM1 | CHAR | 10 | TEXT10 | ||||
| PO_BOX | PO Box | AD_POBX | CHAR | 10 | CHAR10 | ||||
| PO_BOX_LOC | PO Box city | AD_POBXLOC | CHAR | 40 | TEXT40 | CITY_NAME | |||
| TRANSPZONE | Transportation zone | AD_TRNSPZN | CHAR | 10 | Assigned to domain | ZONE | |||
| CITY_CODE | City code for city/street file | AD_CITYNUM | CHAR | 12 | Assigned to domain | ALPHA | CITY_CODE | ||
| CITYP_CODE | District code for City and Street file | AD_CITYPNM | CHAR | 8 | Assigned to domain | ALPHA | CITYP_CODE | ||
| COUNTRY | Country Key | LAND1 | CHAR | 3 | Assigned to domain | LAND1 | LND |
| Key field | Non-key field |
How do I retrieve data from SAP structure LOCATION_I using ABAP code?
As LOCATION_I is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on LOCATION_I as there is no data to select.How to access SAP table LOCATION_I
Within an ECC or HANA version of SAP you can also view further information about LOCATION_I and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects