SAP VAKEY_TABLE_CREATE Function Module for NOTRANSL: erzeugt eine VAKEY-Tabelle
VAKEY_TABLE_CREATE is a standard vakey table create 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: erzeugt eine VAKEY-Tabelle 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 table create FM, simply by entering the name VAKEY_TABLE_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: V12D
Program Name: SAPLV12D
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function VAKEY_TABLE_CREATE 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_TABLE_CREATE'"NOTRANSL: erzeugt eine VAKEY-Tabelle.
EXPORTING
USAGE = "Usage of the Condition Table
TABLE_NUMBER = "Condition Table
* WITH_TEXTFIELD = "DE-EN-LANG-SWITCH-NO-TRANSLATION
* ALLOCATE_NEW = "DE-EN-LANG-SWITCH-NO-TRANSLATION
* WIDTH = "DE-EN-LANG-SWITCH-NO-TRANSLATION
IMPORTING
ET_FIELDCAT = "Field Catalog for SAP List Viewer Control
E_STRUC = "DE-EN-LANG-SWITCH-NO-TRANSLATION
E_TABLE = "DE-EN-LANG-SWITCH-NO-TRANSLATION
EXCEPTIONS
TABLE_DOES_NOT_EXIST = 1 FIELDCAT_COULD_NOT_READ = 2 RTTS_ERROR = 3 CREATE_DATA_ERROR = 4
IMPORTING Parameters details for VAKEY_TABLE_CREATE
USAGE - Usage of the Condition Table
Data type: T681-KVEWEOptional: No
Call by Reference: Yes
TABLE_NUMBER - Condition Table
Data type: T681-KOTABNROptional: No
Call by Reference: Yes
WITH_TEXTFIELD - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: XFELDOptional: Yes
Call by Reference: Yes
ALLOCATE_NEW - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: XFELDOptional: Yes
Call by Reference: Yes
WIDTH - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: IOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for VAKEY_TABLE_CREATE
ET_FIELDCAT - Field Catalog for SAP List Viewer Control
Data type: LVC_T_FCATOptional: No
Call by Reference: Yes
E_STRUC - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: DATAOptional: No
Call by Reference: Yes
E_TABLE - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: DATAOptional: No
Call by Reference: Yes
EXCEPTIONS details
TABLE_DOES_NOT_EXIST - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
FIELDCAT_COULD_NOT_READ - Error when reading the field catalog
Data type:Optional: No
Call by Reference: Yes
RTTS_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
CREATE_DATA_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for VAKEY_TABLE_CREATE 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_usage | TYPE T681-KVEWE, " | |||
| lv_et_fieldcat | TYPE LVC_T_FCAT, " | |||
| lv_table_does_not_exist | TYPE LVC_T_FCAT, " | |||
| lv_e_struc | TYPE DATA, " | |||
| lv_table_number | TYPE T681-KOTABNR, " | |||
| lv_fieldcat_could_not_read | TYPE T681, " | |||
| lv_e_table | TYPE DATA, " | |||
| lv_rtts_error | TYPE DATA, " | |||
| lv_with_textfield | TYPE XFELD, " | |||
| lv_allocate_new | TYPE XFELD, " | |||
| lv_create_data_error | TYPE XFELD, " | |||
| lv_width | TYPE I. " |
|   CALL FUNCTION 'VAKEY_TABLE_CREATE' "NOTRANSL: erzeugt eine VAKEY-Tabelle |
| EXPORTING | ||
| USAGE | = lv_usage | |
| TABLE_NUMBER | = lv_table_number | |
| WITH_TEXTFIELD | = lv_with_textfield | |
| ALLOCATE_NEW | = lv_allocate_new | |
| WIDTH | = lv_width | |
| IMPORTING | ||
| ET_FIELDCAT | = lv_et_fieldcat | |
| E_STRUC | = lv_e_struc | |
| E_TABLE | = lv_e_table | |
| EXCEPTIONS | ||
| TABLE_DOES_NOT_EXIST = 1 | ||
| FIELDCAT_COULD_NOT_READ = 2 | ||
| RTTS_ERROR = 3 | ||
| CREATE_DATA_ERROR = 4 | ||
| . " VAKEY_TABLE_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM VAKEY_TABLE_CREATE
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 KVEWE FROM T681 INTO @DATA(ld_usage). | ||||
| "SELECT single KOTABNR FROM T681 INTO @DATA(ld_table_number). | ||||
Search for further information about these or an SAP related objects