SAP TREX_EXT_CHECK_SPARSE Function Module for Check if attribute are sparse (and change)
TREX_EXT_CHECK_SPARSE is a standard trex ext check sparse SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check if attribute are sparse (and change) 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 check sparse FM, simply by entering the name TREX_EXT_CHECK_SPARSE into the relevant SAP transaction such as SE37 or SE38.
Function Group: TREX_EXT_AE
Program Name: SAPLTREX_EXT_AE
Main Program: SAPLTREX_EXT_AE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TREX_EXT_CHECK_SPARSE 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_CHECK_SPARSE'"Check if attribute are sparse (and change).
EXPORTING
I_RFC_DESTINATION = "RFC destination to TREX engine
I_INDEX_ID = "Index Id
I_ATTRIBUTES = "Angeforderte Attribute
IMPORTING
E_RETURN_CODE = "Return Code
E_RETURN_TEXT = "Return Text
EXCEPTIONS
CONVERSION_ERROR = 1 ERROR = 2
IMPORTING Parameters details for TREX_EXT_CHECK_SPARSE
I_RFC_DESTINATION - RFC destination to TREX engine
Data type: TREX_RFC-RFC_DESTINATIONOptional: No
Call by Reference: Yes
I_INDEX_ID - Index Id
Data type: TREX_RFC-INDEX_IDOptional: No
Call by Reference: Yes
I_ATTRIBUTES - Angeforderte Attribute
Data type: TREXT_ATTRIBUTESOptional: No
Call by Reference: Yes
EXPORTING Parameters details for TREX_EXT_CHECK_SPARSE
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
EXCEPTIONS details
CONVERSION_ERROR - Fehler beim Konvertieren nach utf8
Data type:Optional: No
Call by Reference: Yes
ERROR - Fehler, siehe Fehlernachricht
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for TREX_EXT_CHECK_SPARSE 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_index_id | TYPE TREX_RFC-INDEX_ID, " | |||
| lv_e_return_text | TYPE TREX_RFC-RETURN_TEXT, " | |||
| lv_i_attributes | TYPE TREXT_ATTRIBUTES. " |
|   CALL FUNCTION 'TREX_EXT_CHECK_SPARSE' "Check if attribute are sparse (and change) |
| EXPORTING | ||
| I_RFC_DESTINATION | = lv_i_rfc_destination | |
| I_INDEX_ID | = lv_i_index_id | |
| I_ATTRIBUTES | = lv_i_attributes | |
| IMPORTING | ||
| E_RETURN_CODE | = lv_e_return_code | |
| E_RETURN_TEXT | = lv_e_return_text | |
| EXCEPTIONS | ||
| CONVERSION_ERROR = 1 | ||
| ERROR = 2 | ||
| . " TREX_EXT_CHECK_SPARSE | ||
ABAP code using 7.40 inline data declarations to call FM TREX_EXT_CHECK_SPARSE
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 INDEX_ID FROM TREX_RFC INTO @DATA(ld_i_index_id). | ||||
| "SELECT single RETURN_TEXT FROM TREX_RFC INTO @DATA(ld_e_return_text). | ||||
Search for further information about these or an SAP related objects