SAP VAKEY_TO_2LINES Function Module for NOTRANSL: VAKEY ist für eine Struktur in zwei Zeilen aufbereitet
VAKEY_TO_2LINES is a standard vakey to 2lines SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: VAKEY ist für eine Struktur in zwei Zeilen aufbereitet processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for vakey to 2lines FM, simply by entering the name VAKEY_TO_2LINES into the relevant SAP transaction such as SE37 or SE38.
Function Group: V12D
Program Name: SAPLV12D
Main Program: SAPLV12D
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function VAKEY_TO_2LINES pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'VAKEY_TO_2LINES'"NOTRANSL: VAKEY ist für eine Struktur in zwei Zeilen aufbereitet.
EXPORTING
* SEPARATE_WITH_LINE = ' ' "
TABLE_NUMBER = "
USAGE = "
VARIABLE_KEY = "Variable keys for a structure
* MAX_STRLEN = 80 "
IMPORTING
FIELDS_STRING = "VARIABLE_KEY fields are written here
TEXT_STRING = "List header texts of CONDITION_STRUCTURE
EXCEPTIONS
STRING_OVERFLOW = 1 TABLE_NOT_READABLE = 2
IMPORTING Parameters details for VAKEY_TO_2LINES
SEPARATE_WITH_LINE -
Data type:Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLE_NUMBER -
Data type: T681-KOTABNROptional: No
Call by Reference: No ( called with pass by value option)
USAGE -
Data type: T681-KVEWEOptional: No
Call by Reference: No ( called with pass by value option)
VARIABLE_KEY - Variable keys for a structure
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MAX_STRLEN -
Data type:Default: 80
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for VAKEY_TO_2LINES
FIELDS_STRING - VARIABLE_KEY fields are written here
Data type: RV13A-VAKEY2Optional: No
Call by Reference: No ( called with pass by value option)
TEXT_STRING - List header texts of CONDITION_STRUCTURE
Data type: RV13A-VAKEY1Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
STRING_OVERFLOW - Information does not fit into TEXT/FIELDS_STRIRING
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLE_NOT_READABLE - Table CONDITION_STRUCTURE cannot be read
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for VAKEY_TO_2LINES Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_fields_string | TYPE RV13A-VAKEY2, " | |||
| lv_string_overflow | TYPE RV13A, " | |||
| lv_separate_with_line | TYPE RV13A, " ' ' | |||
| lv_text_string | TYPE RV13A-VAKEY1, " | |||
| lv_table_number | TYPE T681-KOTABNR, " | |||
| lv_table_not_readable | TYPE T681, " | |||
| lv_usage | TYPE T681-KVEWE, " | |||
| lv_variable_key | TYPE T681, " | |||
| lv_max_strlen | TYPE T681. " 80 |
|   CALL FUNCTION 'VAKEY_TO_2LINES' "NOTRANSL: VAKEY ist für eine Struktur in zwei Zeilen aufbereitet |
| EXPORTING | ||
| SEPARATE_WITH_LINE | = lv_separate_with_line | |
| TABLE_NUMBER | = lv_table_number | |
| USAGE | = lv_usage | |
| VARIABLE_KEY | = lv_variable_key | |
| MAX_STRLEN | = lv_max_strlen | |
| IMPORTING | ||
| FIELDS_STRING | = lv_fields_string | |
| TEXT_STRING | = lv_text_string | |
| EXCEPTIONS | ||
| STRING_OVERFLOW = 1 | ||
| TABLE_NOT_READABLE = 2 | ||
| . " VAKEY_TO_2LINES | ||
ABAP code using 7.40 inline data declarations to call FM VAKEY_TO_2LINES
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single VAKEY2 FROM RV13A INTO @DATA(ld_fields_string). | ||||
| DATA(ld_separate_with_line) | = ' '. | |||
| "SELECT single VAKEY1 FROM RV13A INTO @DATA(ld_text_string). | ||||
| "SELECT single KOTABNR FROM T681 INTO @DATA(ld_table_number). | ||||
| "SELECT single KVEWE FROM T681 INTO @DATA(ld_usage). | ||||
| DATA(ld_max_strlen) | = 80. | |||
Search for further information about these or an SAP related objects