SAP SLIM_GET_ENGINE_RESULT Function Module for









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

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



Function SLIM_GET_ENGINE_RESULT 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 'SLIM_GET_ENGINE_RESULT'"
EXPORTING
RESULT_TYPE = "

TABLES
ENGINE_RESULTS = "
* CLIENTS = "
.



IMPORTING Parameters details for SLIM_GET_ENGINE_RESULT

RESULT_TYPE -

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

TABLES Parameters details for SLIM_GET_ENGINE_RESULT

ENGINE_RESULTS -

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

CLIENTS -

Data type: SLIM_CLIENT_LIST
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for SLIM_GET_ENGINE_RESULT 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_result_type  TYPE SYM_KEY, "   
lt_engine_results  TYPE STANDARD TABLE OF TUL_ENG_RESULT, "   
lt_clients  TYPE STANDARD TABLE OF SLIM_CLIENT_LIST. "   

  CALL FUNCTION 'SLIM_GET_ENGINE_RESULT'  "
    EXPORTING
         RESULT_TYPE = lv_result_type
    TABLES
         ENGINE_RESULTS = lt_engine_results
         CLIENTS = lt_clients
. " SLIM_GET_ENGINE_RESULT




ABAP code using 7.40 inline data declarations to call FM SLIM_GET_ENGINE_RESULT

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



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!