SAP FBIW_DATA_TRANSFER_GL_2 Function Module for
FBIW_DATA_TRANSFER_GL_2 is a standard fbiw data transfer gl 2 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 fbiw data transfer gl 2 FM, simply by entering the name FBIW_DATA_TRANSFER_GL_2 into the relevant SAP transaction such as SE37 or SE38.
Function Group: FBIW
Program Name: SAPLFBIW
Main Program: SAPLFBIW
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FBIW_DATA_TRANSFER_GL_2 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 'FBIW_DATA_TRANSFER_GL_2'".
EXPORTING
* I_ISOURCE = "
I_REQUNR = "
* I_MAXSIZE = "
* I_INITFLAG = "
* I_UPDMODE = "
* I_DATAPAKID = "
TABLES
* E_T_DTFIGL_2 = "
* I_T_FIELDS = "
* I_T_SELECT = "
EXCEPTIONS
NO_MORE_DATA = 1 ERROR_PASSED_TO_MESS_HANDLER = 2 WRONG_REQUEST_NUMBER = 3 INVALID_SELECTION = 4 INVALID_INFO_SOURCE = 5
IMPORTING Parameters details for FBIW_DATA_TRANSFER_GL_2
I_ISOURCE -
Data type: SBIWA_S_INTERFACE-ISOURCEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_REQUNR -
Data type: SBIWA_S_INTERFACE-REQUNROptional: No
Call by Reference: No ( called with pass by value option)
I_MAXSIZE -
Data type: SBIWA_S_INTERFACE-MAXSIZEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_INITFLAG -
Data type: SBIWA_S_INTERFACE-INITFLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_UPDMODE -
Data type: SBIWA_S_INTERFACE-UPDMODEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DATAPAKID -
Data type: SBIWA_S_INTERFACE-DATAPAKIDOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FBIW_DATA_TRANSFER_GL_2
E_T_DTFIGL_2 -
Data type: DTFIGL_2Optional: Yes
Call by Reference: No ( called with pass by value option)
I_T_FIELDS -
Data type: SBIWA_T_FIELDSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_T_SELECT -
Data type: SBIWA_T_SELECTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_MORE_DATA -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_PASSED_TO_MESS_HANDLER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_REQUEST_NUMBER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_SELECTION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_INFO_SOURCE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FBIW_DATA_TRANSFER_GL_2 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_i_isource | TYPE SBIWA_S_INTERFACE-ISOURCE, " | |||
| lt_e_t_dtfigl_2 | TYPE STANDARD TABLE OF DTFIGL_2, " | |||
| lv_no_more_data | TYPE DTFIGL_2, " | |||
| lv_i_requnr | TYPE SBIWA_S_INTERFACE-REQUNR, " | |||
| lt_i_t_fields | TYPE STANDARD TABLE OF SBIWA_T_FIELDS, " | |||
| lv_error_passed_to_mess_handler | TYPE SBIWA_T_FIELDS, " | |||
| lv_i_maxsize | TYPE SBIWA_S_INTERFACE-MAXSIZE, " | |||
| lt_i_t_select | TYPE STANDARD TABLE OF SBIWA_T_SELECT, " | |||
| lv_wrong_request_number | TYPE SBIWA_T_SELECT, " | |||
| lv_i_initflag | TYPE SBIWA_S_INTERFACE-INITFLAG, " | |||
| lv_invalid_selection | TYPE SBIWA_S_INTERFACE, " | |||
| lv_i_updmode | TYPE SBIWA_S_INTERFACE-UPDMODE, " | |||
| lv_invalid_info_source | TYPE SBIWA_S_INTERFACE, " | |||
| lv_i_datapakid | TYPE SBIWA_S_INTERFACE-DATAPAKID. " |
|   CALL FUNCTION 'FBIW_DATA_TRANSFER_GL_2' " |
| EXPORTING | ||
| I_ISOURCE | = lv_i_isource | |
| I_REQUNR | = lv_i_requnr | |
| I_MAXSIZE | = lv_i_maxsize | |
| I_INITFLAG | = lv_i_initflag | |
| I_UPDMODE | = lv_i_updmode | |
| I_DATAPAKID | = lv_i_datapakid | |
| TABLES | ||
| E_T_DTFIGL_2 | = lt_e_t_dtfigl_2 | |
| I_T_FIELDS | = lt_i_t_fields | |
| I_T_SELECT | = lt_i_t_select | |
| EXCEPTIONS | ||
| NO_MORE_DATA = 1 | ||
| ERROR_PASSED_TO_MESS_HANDLER = 2 | ||
| WRONG_REQUEST_NUMBER = 3 | ||
| INVALID_SELECTION = 4 | ||
| INVALID_INFO_SOURCE = 5 | ||
| . " FBIW_DATA_TRANSFER_GL_2 | ||
ABAP code using 7.40 inline data declarations to call FM FBIW_DATA_TRANSFER_GL_2
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 ISOURCE FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_isource). | ||||
| "SELECT single REQUNR FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_requnr). | ||||
| "SELECT single MAXSIZE FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_maxsize). | ||||
| "SELECT single INITFLAG FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_initflag). | ||||
| "SELECT single UPDMODE FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_updmode). | ||||
| "SELECT single DATAPAKID FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_datapakid). | ||||
Search for further information about these or an SAP related objects