SAP RKE_CREATE_BATCH_INPUT Function Module for









RKE_CREATE_BATCH_INPUT is a standard rke create batch input 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 create batch input FM, simply by entering the name RKE_CREATE_BATCH_INPUT into the relevant SAP transaction such as SE37 or SE38.

Function Group: KEA5
Program Name: SAPLKEA5
Main Program: SAPLKEA5
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RKE_CREATE_BATCH_INPUT 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_CREATE_BATCH_INPUT'"
EXPORTING
ERKRS = "Operating concern
GROUP = "Session name
USER = "Batch-input user

TABLES
EP_TAB = "CO-PA line item table
FIELDTAB = "ABAP/4 Dictionary information

EXCEPTIONS
NO_EP_FOUND = 1
.



IMPORTING Parameters details for RKE_CREATE_BATCH_INPUT

ERKRS - Operating concern

Data type: TKEB-ERKRS
Optional: No
Call by Reference: No ( called with pass by value option)

GROUP - Session name

Data type: APQI-GROUPID
Optional: No
Call by Reference: No ( called with pass by value option)

USER - Batch-input user

Data type: APQI-USERID
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for RKE_CREATE_BATCH_INPUT

EP_TAB - CO-PA line item table

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

FIELDTAB - ABAP/4 Dictionary information

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_EP_FOUND - No line items found

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for RKE_CREATE_BATCH_INPUT 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, "   
lt_ep_tab  TYPE STANDARD TABLE OF TKEB, "   
lv_no_ep_found  TYPE TKEB, "   
lv_group  TYPE APQI-GROUPID, "   
lt_fieldtab  TYPE STANDARD TABLE OF APQI, "   
lv_user  TYPE APQI-USERID. "   

  CALL FUNCTION 'RKE_CREATE_BATCH_INPUT'  "
    EXPORTING
         ERKRS = lv_erkrs
         GROUP = lv_group
         USER = lv_user
    TABLES
         EP_TAB = lt_ep_tab
         FIELDTAB = lt_fieldtab
    EXCEPTIONS
        NO_EP_FOUND = 1
. " RKE_CREATE_BATCH_INPUT




ABAP code using 7.40 inline data declarations to call FM RKE_CREATE_BATCH_INPUT

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 GROUPID FROM APQI INTO @DATA(ld_group).
 
 
"SELECT single USERID FROM APQI INTO @DATA(ld_user).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!