SAP RKE_FILL_FIELD_TABLE Function Module for
RKE_FILL_FIELD_TABLE is a standard rke fill field table SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 rke fill field table FM, simply by entering the name RKE_FILL_FIELD_TABLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: KEFT
Program Name: SAPLKEFT
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function RKE_FILL_FIELD_TABLE 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 'RKE_FILL_FIELD_TABLE'".
EXPORTING
* ERKRS = "Operating concern
* NEU_KZ = ' ' "Indicators: rebuild FIELDTAB
* PROTOKOLL_KZ = ' ' "Indicator: write log
* TABNAME = "CO-PA structure name
* PA_TYPE = '1' "Switch for Fieldtab type
* I_SORTED = RKEA1_OFF "
IMPORTING
SUBRC = "Greatest error code
TABLES
* FIELDTAB = "Field table
* ET_DEPENDENCIES = "
EXCEPTIONS
LEDGER_NOT_DEF = 1 LEDGER_NOT_FOUND = 2 TABLE_NOT_FOUND = 3
IMPORTING Parameters details for RKE_FILL_FIELD_TABLE
ERKRS - Operating concern
Data type: TKEB-ERKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
NEU_KZ - Indicators: rebuild FIELDTAB
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
PROTOKOLL_KZ - Indicator: write log
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABNAME - CO-PA structure name
Data type: TABNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
PA_TYPE - Switch for Fieldtab type
Data type:Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SORTED -
Data type: RKEA1_FLAGDefault: RKEA1_OFF
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RKE_FILL_FIELD_TABLE
SUBRC - Greatest error code
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RKE_FILL_FIELD_TABLE
FIELDTAB - Field table
Data type: RKEA1_FIELDTABOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_DEPENDENCIES -
Data type: RKEA1_T_DEPENDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
LEDGER_NOT_DEF - No ledger defined for operating concern
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LEDGER_NOT_FOUND - Ledger not in TKEL
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLE_NOT_FOUND - Structure not in the Dictionary
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RKE_FILL_FIELD_TABLE 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_erkrs | TYPE TKEB-ERKRS, " | |||
lv_subrc | TYPE SY-SUBRC, " | |||
lt_fieldtab | TYPE STANDARD TABLE OF RKEA1_FIELDTAB, " | |||
lv_ledger_not_def | TYPE RKEA1_FIELDTAB, " | |||
lv_neu_kz | TYPE RKEA1_FIELDTAB, " SPACE | |||
lt_et_dependencies | TYPE STANDARD TABLE OF RKEA1_T_DEPEND, " | |||
lv_ledger_not_found | TYPE RKEA1_T_DEPEND, " | |||
lv_protokoll_kz | TYPE RKEA1_T_DEPEND, " SPACE | |||
lv_table_not_found | TYPE RKEA1_T_DEPEND, " | |||
lv_tabname | TYPE TABNAME, " | |||
lv_pa_type | TYPE TABNAME, " '1' | |||
lv_i_sorted | TYPE RKEA1_FLAG. " RKEA1_OFF |
  CALL FUNCTION 'RKE_FILL_FIELD_TABLE' " |
EXPORTING | ||
ERKRS | = lv_erkrs | |
NEU_KZ | = lv_neu_kz | |
PROTOKOLL_KZ | = lv_protokoll_kz | |
TABNAME | = lv_tabname | |
PA_TYPE | = lv_pa_type | |
I_SORTED | = lv_i_sorted | |
IMPORTING | ||
SUBRC | = lv_subrc | |
TABLES | ||
FIELDTAB | = lt_fieldtab | |
ET_DEPENDENCIES | = lt_et_dependencies | |
EXCEPTIONS | ||
LEDGER_NOT_DEF = 1 | ||
LEDGER_NOT_FOUND = 2 | ||
TABLE_NOT_FOUND = 3 | ||
. " RKE_FILL_FIELD_TABLE |
ABAP code using 7.40 inline data declarations to call FM RKE_FILL_FIELD_TABLE
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 ERKRS FROM TKEB INTO @DATA(ld_erkrs). | ||||
"SELECT single SUBRC FROM SY INTO @DATA(ld_subrc). | ||||
DATA(ld_neu_kz) | = ' '. | |||
DATA(ld_protokoll_kz) | = ' '. | |||
DATA(ld_pa_type) | = '1'. | |||
DATA(ld_i_sorted) | = RKEA1_OFF. | |||
Search for further information about these or an SAP related objects