SAP K_BP_BATCHINPUT Function Module for Create business process (batch input)









K_BP_BATCHINPUT is a standard k bp batchinput SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create business process (batch input) 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 k bp batchinput FM, simply by entering the name K_BP_BATCHINPUT into the relevant SAP transaction such as SE37 or SE38.

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



Function K_BP_BATCHINPUT 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 'K_BP_BATCHINPUT'"Create business process (batch input)
  EXPORTING
*  CLIENT = SY-MANDT "Client
*  HOLDDATE = ' ' "Date Format Folder Locked Until:
*  KEEP = ' ' "Save or delete folder?
*  MAPN_E = 'ERRORMAP' "Default 'errormap'
*  MAP_NR = 'BATCHMAP' "Folder Name
*  ONLINE = ' ' "Online indicator: X
*  USER = SY-UNAME "BENUTZER KENNZEICHEN DEFAULT SY-UNAME

TABLES
   I_LIST =  "CBPRZ STRUKTUR

EXCEPTIONS
   ERROR_IN_CALL_TRANSACTION = 1    NO_ENTRIES_IN_TABLE = 2    WRONG_KOKRS = 3    WRONG_ONLINE_PARAMETER = 4
.



IMPORTING Parameters details for K_BP_BATCHINPUT

CLIENT - Client

Data type: APQI-MANDANT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

HOLDDATE - Date Format Folder Locked Until:

Data type: APQI-STARTDATE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

KEEP - Save or delete folder?

Data type: APQI-QERASE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

MAPN_E - Default 'errormap'

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

MAP_NR - Folder Name

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

ONLINE - Online indicator: X

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

USER - BENUTZER KENNZEICHEN DEFAULT SY-UNAME

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

TABLES Parameters details for K_BP_BATCHINPUT

I_LIST - CBPRZ STRUKTUR

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

EXCEPTIONS details

ERROR_IN_CALL_TRANSACTION - ??

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

NO_ENTRIES_IN_TABLE - Empty Transfer Table

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

WRONG_KOKRS - Incorrect controlling area?

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

WRONG_ONLINE_PARAMETER -

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

Copy and paste ABAP code example for K_BP_BATCHINPUT 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_client  TYPE APQI-MANDANT, "   SY-MANDT
lt_i_list  TYPE STANDARD TABLE OF CBPRZ, "   
lv_error_in_call_transaction  TYPE CBPRZ, "   
lv_holddate  TYPE APQI-STARTDATE, "   SPACE
lv_no_entries_in_table  TYPE APQI, "   
lv_keep  TYPE APQI-QERASE, "   SPACE
lv_wrong_kokrs  TYPE APQI, "   
lv_mapn_e  TYPE APQI-GROUPID, "   'ERRORMAP'
lv_wrong_online_parameter  TYPE APQI, "   
lv_map_nr  TYPE APQI-GROUPID, "   'BATCHMAP'
lv_online  TYPE APQI, "   ' '
lv_user  TYPE APQI-USERID. "   SY-UNAME

  CALL FUNCTION 'K_BP_BATCHINPUT'  "Create business process (batch input)
    EXPORTING
         CLIENT = lv_client
         HOLDDATE = lv_holddate
         KEEP = lv_keep
         MAPN_E = lv_mapn_e
         MAP_NR = lv_map_nr
         ONLINE = lv_online
         USER = lv_user
    TABLES
         I_LIST = lt_i_list
    EXCEPTIONS
        ERROR_IN_CALL_TRANSACTION = 1
        NO_ENTRIES_IN_TABLE = 2
        WRONG_KOKRS = 3
        WRONG_ONLINE_PARAMETER = 4
. " K_BP_BATCHINPUT




ABAP code using 7.40 inline data declarations to call FM K_BP_BATCHINPUT

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 MANDANT FROM APQI INTO @DATA(ld_client).
DATA(ld_client) = SY-MANDT.
 
 
 
"SELECT single STARTDATE FROM APQI INTO @DATA(ld_holddate).
DATA(ld_holddate) = ' '.
 
 
"SELECT single QERASE FROM APQI INTO @DATA(ld_keep).
DATA(ld_keep) = ' '.
 
 
"SELECT single GROUPID FROM APQI INTO @DATA(ld_mapn_e).
DATA(ld_mapn_e) = 'ERRORMAP'.
 
 
"SELECT single GROUPID FROM APQI INTO @DATA(ld_map_nr).
DATA(ld_map_nr) = 'BATCHMAP'.
 
DATA(ld_online) = ' '.
 
"SELECT single USERID FROM APQI INTO @DATA(ld_user).
DATA(ld_user) = SY-UNAME.
 


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!