SAP IBIP_BATCH_INPUT_RFC Function Module for NOTRANSL: BATCH_INPUT REMOTE FUNCTION CALL INTERFACE
IBIP_BATCH_INPUT_RFC is a standard ibip batch input rfc 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: BATCH_INPUT REMOTE FUNCTION CALL INTERFACE 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 ibip batch input rfc FM, simply by entering the name IBIP_BATCH_INPUT_RFC into the relevant SAP transaction such as SE37 or SE38.
Function Group: IBIP
Program Name: SAPLIBIP
Main Program: SAPLIBIP
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function IBIP_BATCH_INPUT_RFC 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 'IBIP_BATCH_INPUT_RFC'"NOTRANSL: BATCH_INPUT REMOTE FUNCTION CALL INTERFACE.
EXPORTING
IBIPPARMS_IMP = "See field string IBIPPARMS
IMPORTING
IBIPMESS_EXP = "Should messages be exported
TABLES
* BDCDATA_EXP = "Should the BDCDATA be exported
* INT_TAB_IMP = "Batch input data to process
* MESSAGE_TAB = "
EXCEPTIONS
CUSTOMIZING_TABLE_ERROR = 1 DATA_ACCESS_ERROR = 2 EXACTLY_ONE_MODE_NOT_DEFINED = 3 EXACTLY_ONE_SOURCE_NOT_DEFINED = 4 INT_TAB_MORE_THAN_ONE_TRANS = 5 INVALID_DATA_STRUCTURE = 6 NO_SOURCE_DATA = 7 SAPINDX_NOT_FOUND = 8 TRANSACTION_NOT_SUPPORTED = 9
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLIBIP_001 User Exit: Data Transfer Module (IBIP Batch Input)
IMPORTING Parameters details for IBIP_BATCH_INPUT_RFC
IBIPPARMS_IMP - See field string IBIPPARMS
Data type: IBIPPARMSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for IBIP_BATCH_INPUT_RFC
IBIPMESS_EXP - Should messages be exported
Data type: IBIPMESSOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for IBIP_BATCH_INPUT_RFC
BDCDATA_EXP - Should the BDCDATA be exported
Data type: BDCDATAOptional: Yes
Call by Reference: No ( called with pass by value option)
INT_TAB_IMP - Batch input data to process
Data type: IBIPRECOptional: Yes
Call by Reference: No ( called with pass by value option)
MESSAGE_TAB -
Data type: IBIPMESSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CUSTOMIZING_TABLE_ERROR - CUSTOMIZING_TABLE_ERROR
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DATA_ACCESS_ERROR - DATA_ACCESS_ERROR
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXACTLY_ONE_MODE_NOT_DEFINED - EXACTLY_ONE_MODE_NOT_DEFINED
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXACTLY_ONE_SOURCE_NOT_DEFINED - EXACTLY_ONE_SOURCE_NOT_DEFINED
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INT_TAB_MORE_THAN_ONE_TRANS - INT_TAB_MORE_THAN_ONE_TRANSACTION with BDC_EXP
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_DATA_STRUCTURE - INVALID_DATA_STRUCTURE ,
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_SOURCE_DATA - NO_SOURCE_DATA
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SAPINDX_NOT_FOUND - SAPINDX_NOT_FOUND
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TRANSACTION_NOT_SUPPORTED - TRANSACTION_NOT_SUPPORTED
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for IBIP_BATCH_INPUT_RFC 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: | ||||
| lt_bdcdata_exp | TYPE STANDARD TABLE OF BDCDATA, " | |||
| lv_ibipmess_exp | TYPE IBIPMESS, " | |||
| lv_ibipparms_imp | TYPE IBIPPARMS, " | |||
| lv_customizing_table_error | TYPE IBIPPARMS, " | |||
| lt_int_tab_imp | TYPE STANDARD TABLE OF IBIPREC, " | |||
| lv_data_access_error | TYPE IBIPREC, " | |||
| lt_message_tab | TYPE STANDARD TABLE OF IBIPMESS, " | |||
| lv_exactly_one_mode_not_defined | TYPE IBIPMESS, " | |||
| lv_exactly_one_source_not_defined | TYPE IBIPMESS, " | |||
| lv_int_tab_more_than_one_trans | TYPE IBIPMESS, " | |||
| lv_invalid_data_structure | TYPE IBIPMESS, " | |||
| lv_no_source_data | TYPE IBIPMESS, " | |||
| lv_sapindx_not_found | TYPE IBIPMESS, " | |||
| lv_transaction_not_supported | TYPE IBIPMESS. " |
|   CALL FUNCTION 'IBIP_BATCH_INPUT_RFC' "NOTRANSL: BATCH_INPUT REMOTE FUNCTION CALL INTERFACE |
| EXPORTING | ||
| IBIPPARMS_IMP | = lv_ibipparms_imp | |
| IMPORTING | ||
| IBIPMESS_EXP | = lv_ibipmess_exp | |
| TABLES | ||
| BDCDATA_EXP | = lt_bdcdata_exp | |
| INT_TAB_IMP | = lt_int_tab_imp | |
| MESSAGE_TAB | = lt_message_tab | |
| EXCEPTIONS | ||
| CUSTOMIZING_TABLE_ERROR = 1 | ||
| DATA_ACCESS_ERROR = 2 | ||
| EXACTLY_ONE_MODE_NOT_DEFINED = 3 | ||
| EXACTLY_ONE_SOURCE_NOT_DEFINED = 4 | ||
| INT_TAB_MORE_THAN_ONE_TRANS = 5 | ||
| INVALID_DATA_STRUCTURE = 6 | ||
| NO_SOURCE_DATA = 7 | ||
| SAPINDX_NOT_FOUND = 8 | ||
| TRANSACTION_NOT_SUPPORTED = 9 | ||
| . " IBIP_BATCH_INPUT_RFC | ||
ABAP code using 7.40 inline data declarations to call FM IBIP_BATCH_INPUT_RFC
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.Search for further information about these or an SAP related objects