SAP TREX_EXT_EXECUTE_PYTHON Function Module for execute python commands
TREX_EXT_EXECUTE_PYTHON is a standard trex ext execute python SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for execute python commands 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 execute python FM, simply by entering the name TREX_EXT_EXECUTE_PYTHON 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_EXECUTE_PYTHON 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_EXECUTE_PYTHON'"execute python commands.
EXPORTING
I_RFC_DESTINATION = "RFC destination to TREX engine
* I_COMMAND = "
* I_COMMAND_STRING = "
* I_NO_AUTHORITY_CHECK = '' "
* I_INDEXSERVER_LOCATION = "IndexServer or QueueServer Location
IMPORTING
E_RETURN_CODE = "Return Code
E_RETURN_TEXT = "Return Text
E_LINES = "Long lines
EXCEPTIONS
CONVERSION_ERROR = 1 ERROR = 2 NO_AUTHORIZATION = 3
IMPORTING Parameters details for TREX_EXT_EXECUTE_PYTHON
I_RFC_DESTINATION - RFC destination to TREX engine
Data type: TREX_RFC-RFC_DESTINATIONOptional: No
Call by Reference: Yes
I_COMMAND -
Data type: TREX_RFC-PATHOptional: Yes
Call by Reference: Yes
I_COMMAND_STRING -
Data type: STRINGOptional: Yes
Call by Reference: Yes
I_NO_AUTHORITY_CHECK -
Data type: TREX_RFC-FLAGDefault: ''
Optional: Yes
Call by Reference: Yes
I_INDEXSERVER_LOCATION - IndexServer or QueueServer Location
Data type: TREX_RFC-LOCATIONOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for TREX_EXT_EXECUTE_PYTHON
E_RETURN_CODE - Return Code
Data type: TREX_RFC-RETURN_CODEOptional: No
Call by Reference: Yes
E_RETURN_TEXT - Return Text
Data type: TREX_RFC-RETURN_TEXTOptional: No
Call by Reference: Yes
E_LINES - Long lines
Data type: TREXT_LINESOptional: 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
NO_AUTHORIZATION -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for TREX_EXT_EXECUTE_PYTHON 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_return_code | TYPE TREX_RFC-RETURN_CODE, " | |||
| lv_conversion_error | TYPE TREX_RFC, " | |||
| lv_i_rfc_destination | TYPE TREX_RFC-RFC_DESTINATION, " | |||
| lv_error | TYPE TREX_RFC, " | |||
| lv_i_command | TYPE TREX_RFC-PATH, " | |||
| lv_e_return_text | TYPE TREX_RFC-RETURN_TEXT, " | |||
| lv_e_lines | TYPE TREXT_LINES, " | |||
| lv_i_command_string | TYPE STRING, " | |||
| lv_no_authorization | TYPE STRING, " | |||
| lv_i_no_authority_check | TYPE TREX_RFC-FLAG, " '' | |||
| lv_i_indexserver_location | TYPE TREX_RFC-LOCATION. " |
|   CALL FUNCTION 'TREX_EXT_EXECUTE_PYTHON' "execute python commands |
| EXPORTING | ||
| I_RFC_DESTINATION | = lv_i_rfc_destination | |
| I_COMMAND | = lv_i_command | |
| I_COMMAND_STRING | = lv_i_command_string | |
| I_NO_AUTHORITY_CHECK | = lv_i_no_authority_check | |
| I_INDEXSERVER_LOCATION | = lv_i_indexserver_location | |
| IMPORTING | ||
| E_RETURN_CODE | = lv_e_return_code | |
| E_RETURN_TEXT | = lv_e_return_text | |
| E_LINES | = lv_e_lines | |
| EXCEPTIONS | ||
| CONVERSION_ERROR = 1 | ||
| ERROR = 2 | ||
| NO_AUTHORIZATION = 3 | ||
| . " TREX_EXT_EXECUTE_PYTHON | ||
ABAP code using 7.40 inline data declarations to call FM TREX_EXT_EXECUTE_PYTHON
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 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 PATH FROM TREX_RFC INTO @DATA(ld_i_command). | ||||
| "SELECT single RETURN_TEXT FROM TREX_RFC INTO @DATA(ld_e_return_text). | ||||
| "SELECT single FLAG FROM TREX_RFC INTO @DATA(ld_i_no_authority_check). | ||||
| DATA(ld_i_no_authority_check) | = ''. | |||
| "SELECT single LOCATION FROM TREX_RFC INTO @DATA(ld_i_indexserver_location). | ||||
Search for further information about these or an SAP related objects