SAP IB_COM_GET_ENGINE_INTERFACE Function Module for









IB_COM_GET_ENGINE_INTERFACE is a standard ib com get engine interface 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 com get engine interface FM, simply by entering the name IB_COM_GET_ENGINE_INTERFACE into the relevant SAP transaction such as SE37 or SE38.

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



Function IB_COM_GET_ENGINE_INTERFACE 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_COM_GET_ENGINE_INTERFACE'"
EXPORTING
I_IBCO_HANDLE = "

IMPORTING
E_ADDRESS = "
E_ENGINE = "
E_TEXT = "

EXCEPTIONS
IB_HANDLE_NOT_DEFINED = 1
.



IMPORTING Parameters details for IB_COM_GET_ENGINE_INTERFACE

I_IBCO_HANDLE -

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

EXPORTING Parameters details for IB_COM_GET_ENGINE_INTERFACE

E_ADDRESS -

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

E_ENGINE -

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

E_TEXT -

Data type: CL_IBASE_IBINTX
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_COM_GET_ENGINE_INTERFACE 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_e_address  TYPE IF_IBASE_ENGINE_ADDRESS, "   
lv_i_ibco_handle  TYPE IBXX_REF-HANDLE, "   
lv_ib_handle_not_defined  TYPE IBXX_REF, "   
lv_e_engine  TYPE CL_IBASE_ENGINE, "   
lv_e_text  TYPE CL_IBASE_IBINTX. "   

  CALL FUNCTION 'IB_COM_GET_ENGINE_INTERFACE'  "
    EXPORTING
         I_IBCO_HANDLE = lv_i_ibco_handle
    IMPORTING
         E_ADDRESS = lv_e_address
         E_ENGINE = lv_e_engine
         E_TEXT = lv_e_text
    EXCEPTIONS
        IB_HANDLE_NOT_DEFINED = 1
. " IB_COM_GET_ENGINE_INTERFACE




ABAP code using 7.40 inline data declarations to call FM IB_COM_GET_ENGINE_INTERFACE

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_ibco_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!