SAP TREX_EXT_SUGGEST_OPTIMIZE_ROWS Function Module for suggest optimize rows









TREX_EXT_SUGGEST_OPTIMIZE_ROWS is a standard trex ext suggest optimize rows SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for suggest optimize rows 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 trex ext suggest optimize rows FM, simply by entering the name TREX_EXT_SUGGEST_OPTIMIZE_ROWS into the relevant SAP transaction such as SE37 or SE38.

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



Function TREX_EXT_SUGGEST_OPTIMIZE_ROWS 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 'TREX_EXT_SUGGEST_OPTIMIZE_ROWS'"suggest optimize rows
EXPORTING
I_INDEX_ID = "Index Id
I_RFC_DESTINATION = "RFC destination to TREX engine

IMPORTING
E_ROWS = "rows
E_RETURN_CODE = "Return Code
E_RETURN_TEXT = "Return Text

EXCEPTIONS
CONVERSION_ERROR = 1 ERROR = 2
.



IMPORTING Parameters details for TREX_EXT_SUGGEST_OPTIMIZE_ROWS

I_INDEX_ID - Index Id

Data type: TREX_RFC-INDEX_ID
Optional: No
Call by Reference: Yes

I_RFC_DESTINATION - RFC destination to TREX engine

Data type: TREX_RFC-RFC_DESTINATION
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for TREX_EXT_SUGGEST_OPTIMIZE_ROWS

E_ROWS - rows

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

E_RETURN_CODE - Return Code

Data type: TREX_RFC-RETURN_CODE
Optional: No
Call by Reference: Yes

E_RETURN_TEXT - Return Text

Data type: TREX_RFC-RETURN_TEXT
Optional: No
Call by Reference: Yes

EXCEPTIONS details

CONVERSION_ERROR - Error during conversion to UTF-8

Data type:
Optional: No
Call by Reference: Yes

ERROR - Error, see error message

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TREX_EXT_SUGGEST_OPTIMIZE_ROWS 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_rows  TYPE NUM10, "   
lv_i_index_id  TYPE TREX_RFC-INDEX_ID, "   
lv_conversion_error  TYPE TREX_RFC, "   
lv_error  TYPE TREX_RFC, "   
lv_e_return_code  TYPE TREX_RFC-RETURN_CODE, "   
lv_i_rfc_destination  TYPE TREX_RFC-RFC_DESTINATION, "   
lv_e_return_text  TYPE TREX_RFC-RETURN_TEXT. "   

  CALL FUNCTION 'TREX_EXT_SUGGEST_OPTIMIZE_ROWS'  "suggest optimize rows
    EXPORTING
         I_INDEX_ID = lv_i_index_id
         I_RFC_DESTINATION = lv_i_rfc_destination
    IMPORTING
         E_ROWS = lv_e_rows
         E_RETURN_CODE = lv_e_return_code
         E_RETURN_TEXT = lv_e_return_text
    EXCEPTIONS
        CONVERSION_ERROR = 1
        ERROR = 2
. " TREX_EXT_SUGGEST_OPTIMIZE_ROWS




ABAP code using 7.40 inline data declarations to call FM TREX_EXT_SUGGEST_OPTIMIZE_ROWS

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 INDEX_ID FROM TREX_RFC INTO @DATA(ld_i_index_id).
 
 
 
"SELECT single RETURN_CODE FROM TREX_RFC INTO @DATA(ld_e_return_code).
 
"SELECT single RFC_DESTINATION FROM TREX_RFC INTO @DATA(ld_i_rfc_destination).
 
"SELECT single RETURN_TEXT FROM TREX_RFC INTO @DATA(ld_e_return_text).
 


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!