SAP IB_IBIB_TRANSFER_BTE_DATA Function Module for









IB_IBIB_TRANSFER_BTE_DATA is a standard ib ibib transfer bte data 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 ib ibib transfer bte data FM, simply by entering the name IB_IBIB_TRANSFER_BTE_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function IB_IBIB_TRANSFER_BTE_DATA 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 'IB_IBIB_TRANSFER_BTE_DATA'"
EXPORTING
I_IBIB_HANDLE = "
I_IBIB_TAB = "
I_IBIBT_TAB = "

EXCEPTIONS
IB_HANDLE_NOT_DEFINED = 1
.



IMPORTING Parameters details for IB_IBIB_TRANSFER_BTE_DATA

I_IBIB_HANDLE -

Data type: IBXX_REF-HANDLE
Optional: No
Call by Reference: Yes

I_IBIB_TAB -

Data type: IBCOXEXP_IBIB_TAB
Optional: No
Call by Reference: Yes

I_IBIBT_TAB -

Data type: IBCOXEXP_IBIBT_TAB
Optional: No
Call by Reference: Yes

EXCEPTIONS details

IB_HANDLE_NOT_DEFINED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for IB_IBIB_TRANSFER_BTE_DATA 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_ibib_handle  TYPE IBXX_REF-HANDLE, "   
lv_ib_handle_not_defined  TYPE IBXX_REF, "   
lv_i_ibib_tab  TYPE IBCOXEXP_IBIB_TAB, "   
lv_i_ibibt_tab  TYPE IBCOXEXP_IBIBT_TAB. "   

  CALL FUNCTION 'IB_IBIB_TRANSFER_BTE_DATA'  "
    EXPORTING
         I_IBIB_HANDLE = lv_i_ibib_handle
         I_IBIB_TAB = lv_i_ibib_tab
         I_IBIBT_TAB = lv_i_ibibt_tab
    EXCEPTIONS
        IB_HANDLE_NOT_DEFINED = 1
. " IB_IBIB_TRANSFER_BTE_DATA




ABAP code using 7.40 inline data declarations to call FM IB_IBIB_TRANSFER_BTE_DATA

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 HANDLE FROM IBXX_REF INTO @DATA(ld_i_ibib_handle).
 
 
 
 


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!