EAML_S_LFE_DATA_ALV_KEYS SAP (Linear Feature Extension -ALV with KEY1, KEY2) Structure details
Description: Linear Feature Extension -ALV with KEY1, KEY2
Related tables to EAML_S_LFE_DATA_ALV_KEYS
Access table EAML_S_LFE_DATA_ALV_KEYS
Structure field list including key, data, relationships and ABAP select examples
EAML_S_LFE_DATA_ALV_KEYS 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 "Linear Feature Extension -ALV with KEY1, KEY2" 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_EAML_S_LFE_DATA_ALV_KEYS TYPE EAML_S_LFE_DATA_ALV_KEYS.
The EAML_S_LFE_DATA_ALV_KEYS table consists of various fields, each holding specific information or linking keys about Linear Feature Extension -ALV with KEY1, KEY2 data available in SAP. These include MANDT (Client), OBART (Object Type for Linear Data), KEY1 (First Key Field of Linear Data), KEY2 (Second Key Field of Linear Data (if there is one)).. 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: Can be enhanced (character-type or numeric)
SAP EAML_S_LFE_DATA_ALV_KEYS 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 |
MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
OBART | Object Type for Linear Data | EAML_OBART | CHAR | 2 | EAML_OBART | ||||
KEY1 | First Key Field of Linear Data | EAML_KEY1 | CHAR | 30 | CHAR30 | ||||
KEY2 | Second Key Field of Linear Data (if there is one) | EAML_KEY2 | CHAR | 30 | CHAR30 | ||||
START_POINT | Start Point | EAML_START_POINT_ALV | CHAR | 18 | EAMLC | EAML_POINT_ALV | |||
END_POINT | End Point | EAML_END_POINT_ALV | CHAR | 18 | EAMLC | EAML_POINT_ALV | |||
LINEAR_LENGTH | Length | EAML_LINEAR_LENGTH_ALV | CHAR | 18 | EAMLC | EAML_POINT_ALV | |||
LINEAR_UNIT | Unit of Measurement for Linear Data | EAML_LINEAR_UNIT | UNIT | 3 | T006 | CUNIT | MEINS | EAML_H_T006 | |
LRPID | Linear Reference Pattern | EAML_LRPID | CHAR | 10 | Assigned to domain | EAML_LRPID | LRP | ||
MARKER_START | Marker for Start Point | EAML_MARKER_START_POINT | CHAR | 18 | EAML_MARKER | ||||
MARKER_DIST_STA | Distance between Marker and Start Point | EAML_MARKER_DISTANCE_START | CHAR | 18 | EAML_POINT | ||||
MARKER_END | Marker for End Point | EAML_MARKER_END_POINT | CHAR | 18 | EAML_MARKER | ||||
MARKER_DIST_END | Length Spec for Distance between Marker and End Point | EAML_MARKER_DISTANCE_END | CHAR | 18 | EAML_POINT | ||||
MARKER_DIST_UNIT | Unit for the Distance from Marker | EAML_MARKER_DISTANCE_UNIT | UNIT | 3 | Assigned to domain | CUNIT | MEINS | EAML_H_T006 | |
OFFSET1_TYPE | Type of First Offset | EAML_OFFSET1_TYPE_CODE | CHAR | 2 | EAML_D_OFFSET_TC | EAML_OFFSET_TYPE_CODE | |||
OFFSET1_VALUE | Value of Offset 1 | EAML_OFFSET1_VALUE_ALV | CHAR | 18 | EAMLC | EAML_POINT_ALV | |||
OFFSET1_UNIT | Unit of Measurement for Offset 1 | EAML_OFFSET1_UNIT | UNIT | 3 | T006 | CUNIT | MEINS | EAML_H_T006_OFFSET | |
OFFSET2_TYPE | Type of Second Offset | EAML_OFFSET2_TYPE_CODE | CHAR | 2 | EAML_D_OFFSET_TC | EAML_OFFSET_TYPE_CODE | |||
OFFSET2_VALUE | Value of Offset 2 | EAML_OFFSET2_VALUE_ALV | CHAR | 18 | EAMLC | EAML_POINT_ALV | |||
OFFSET2_UNIT | Unit of Measurement for Offset 2 | EAML_OFFSET2_UNIT | UNIT | 3 | T006 | CUNIT | MEINS | EAML_H_T006_OFFSET |
Key field | Non-key field |
How do I retrieve data from SAP structure EAML_S_LFE_DATA_ALV_KEYS using ABAP code?
As EAML_S_LFE_DATA_ALV_KEYS 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 EAML_S_LFE_DATA_ALV_KEYS as there is no data to select.How to access SAP table EAML_S_LFE_DATA_ALV_KEYS
Within an ECC or HANA version of SAP you can also view further information about EAML_S_LFE_DATA_ALV_KEYS 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