SAP RKD_BTCTYPE_2_INITIALIZE_BATCH Function Module for
RKD_BTCTYPE_2_INITIALIZE_BATCH is a standard rkd btctype 2 initialize batch 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 rkd btctype 2 initialize batch FM, simply by entering the name RKD_BTCTYPE_2_INITIALIZE_BATCH into the relevant SAP transaction such as SE37 or SE38.
Function Group: KYP4
Program Name: SAPLKYP4
Main Program: SAPLKYP4
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RKD_BTCTYPE_2_INITIALIZE_BATCH 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 'RKD_BTCTYPE_2_INITIALIZE_BATCH'".
EXPORTING
I_APPLCLASS = "
I_TABNAME = "
I_REPID = "
I_SUBCLASS = "
* I_FIKRS = ' ' "
* I_KOKRS = ' ' "
IMPORTING
E_S_RKB1D = "
E_T_COTRL = "
E_T_SF = "
E_HIER_OBL = "
E_WAERSG = "
IMPORTING Parameters details for RKD_BTCTYPE_2_INITIALIZE_BATCH
I_APPLCLASS -
Data type: RKB1D-APPLCLASSOptional: No
Call by Reference: No ( called with pass by value option)
I_TABNAME -
Data type: RKB1D-TABNAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_REPID -
Data type: RKB1D-REPIDOptional: No
Call by Reference: No ( called with pass by value option)
I_SUBCLASS -
Data type: RKB1D-SUBCLASSOptional: No
Call by Reference: No ( called with pass by value option)
I_FIKRS -
Data type: RKB1X-FIKRSDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_KOKRS -
Data type: RKB1X-KOKRSDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RKD_BTCTYPE_2_INITIALIZE_BATCH
E_S_RKB1D -
Data type: RKB1DOptional: No
Call by Reference: No ( called with pass by value option)
E_T_COTRL -
Data type: RKD3_T_COTRLOptional: No
Call by Reference: No ( called with pass by value option)
E_T_SF -
Data type: RKD_T_SFOptional: No
Call by Reference: No ( called with pass by value option)
E_HIER_OBL -
Data type: RKD_FLAGOptional: No
Call by Reference: No ( called with pass by value option)
E_WAERSG -
Data type: RKB1X-WAERSGOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RKD_BTCTYPE_2_INITIALIZE_BATCH 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_e_s_rkb1d | TYPE RKB1D, " | |||
| lv_i_applclass | TYPE RKB1D-APPLCLASS, " | |||
| lv_e_t_cotrl | TYPE RKD3_T_COTRL, " | |||
| lv_i_tabname | TYPE RKB1D-TABNAME, " | |||
| lv_e_t_sf | TYPE RKD_T_SF, " | |||
| lv_i_repid | TYPE RKB1D-REPID, " | |||
| lv_e_hier_obl | TYPE RKD_FLAG, " | |||
| lv_i_subclass | TYPE RKB1D-SUBCLASS, " | |||
| lv_i_fikrs | TYPE RKB1X-FIKRS, " SPACE | |||
| lv_e_waersg | TYPE RKB1X-WAERSG, " | |||
| lv_i_kokrs | TYPE RKB1X-KOKRS. " SPACE |
|   CALL FUNCTION 'RKD_BTCTYPE_2_INITIALIZE_BATCH' " |
| EXPORTING | ||
| I_APPLCLASS | = lv_i_applclass | |
| I_TABNAME | = lv_i_tabname | |
| I_REPID | = lv_i_repid | |
| I_SUBCLASS | = lv_i_subclass | |
| I_FIKRS | = lv_i_fikrs | |
| I_KOKRS | = lv_i_kokrs | |
| IMPORTING | ||
| E_S_RKB1D | = lv_e_s_rkb1d | |
| E_T_COTRL | = lv_e_t_cotrl | |
| E_T_SF | = lv_e_t_sf | |
| E_HIER_OBL | = lv_e_hier_obl | |
| E_WAERSG | = lv_e_waersg | |
| . " RKD_BTCTYPE_2_INITIALIZE_BATCH | ||
ABAP code using 7.40 inline data declarations to call FM RKD_BTCTYPE_2_INITIALIZE_BATCH
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 APPLCLASS FROM RKB1D INTO @DATA(ld_i_applclass). | ||||
| "SELECT single TABNAME FROM RKB1D INTO @DATA(ld_i_tabname). | ||||
| "SELECT single REPID FROM RKB1D INTO @DATA(ld_i_repid). | ||||
| "SELECT single SUBCLASS FROM RKB1D INTO @DATA(ld_i_subclass). | ||||
| "SELECT single FIKRS FROM RKB1X INTO @DATA(ld_i_fikrs). | ||||
| DATA(ld_i_fikrs) | = ' '. | |||
| "SELECT single WAERSG FROM RKB1X INTO @DATA(ld_e_waersg). | ||||
| "SELECT single KOKRS FROM RKB1X INTO @DATA(ld_i_kokrs). | ||||
| DATA(ld_i_kokrs) | = ' '. | |||
Search for further information about these or an SAP related objects