SAP TREX_EXT_SPLIT_INDEX Function Module for Split index

Search SAP Function Modules

TREX_EXT_SPLIT_INDEX is a standard trex ext split index SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Split index 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 split index FM, simply by entering the name TREX_EXT_SPLIT_INDEX 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_SPLIT_INDEX 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_SPLIT_INDEX'"Split index
  EXPORTING
   I_RFC_DESTINATION =  "RFC destination to TREX engine
   I_INDEX_ID =  "Index Id
   I_NO_OF_LOGICAL_PARTS =  "NoOfLogicalIndex
*  I_PARTITION_ATTRIBUTE =  "Partition Attribute
*  I_PARTITION_SPECIFICATION =  "Partition Specification

 IMPORTING
   E_RETURN_CODE =  "Return Code
   E_RETURN_TEXT =  "Return Text

EXCEPTIONS
   CONVERSION_ERROR = 1    ERROR = 2 

.

IMPORTING Parameters details for TREX_EXT_SPLIT_INDEX

I_RFC_DESTINATION - RFC destination to TREX engine

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

I_INDEX_ID - Index Id

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

I_NO_OF_LOGICAL_PARTS - NoOfLogicalIndex

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

I_PARTITION_ATTRIBUTE - Partition Attribute

Data type: TREX_RFC-ATTRIBUTE
Optional: Yes
Call by Reference: Yes

I_PARTITION_SPECIFICATION - Partition Specification

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

EXPORTING Parameters details for TREX_EXT_SPLIT_INDEX

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 - Fehler beim Konvertieren nach utf8

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ERROR - Fehler, siehe Fehlernachricht

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for TREX_EXT_SPLIT_INDEX 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.

ABAP code using 7.40 inline data declarations to call FM TREX_EXT_SPLIT_INDEX

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