LOCATION SAP (City, described by different objects in the SAP System) Structure details
Description: City, described by different objects in the SAP System
Structure field list including key, data, relationships and ABAP select examples
LOCATION 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, described by different objects in the SAP System" 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 TYPE LOCATION.
The LOCATION table consists of various fields, each holding specific information or linking keys about City, described by different objects in the SAP System 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 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 | ||||
| ADRNR | Location: Address | L_ADRNR | CHAR | 10 | Assigned to domain | ALPHA | ADRNR | ||
| ADRHND | Location: Handle of an address | L_ADRHND | CHAR | 10 | TEXT10 | ||||
| ADRKNZ | Location: Origin indicator of address | L_ADRKNZ | CHAR | 1 | ADRKNZ | ||||
| UPDKZ | Location: Update indicator of address | L_UPDKZ | CHAR | 1 | UPDKZ | ||||
| ADRNRD | Location: Address, dynamically determined fr.ship.pnt, etc. | L_ADRNRD | CHAR | 10 | Assigned to domain | ALPHA | ADRNR |
| Key field | Non-key field |
How do I retrieve data from SAP structure LOCATION using ABAP code?
As LOCATION 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 as there is no data to select.How to access SAP table LOCATION
Within an ECC or HANA version of SAP you can also view further information about LOCATION 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