SAP TRINT_SPLIT_TABU Function Module for Break Down an R3TR TABU Object Name into Table Name and Key

Search SAP Function Modules

TRINT_SPLIT_TABU is a standard trint split tabu SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Break Down an R3TR TABU Object Name into Table Name and Key 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 trint split tabu FM, simply by entering the name TRINT_SPLIT_TABU into the relevant SAP transaction such as SE37 or SE38.

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

Function TRINT_SPLIT_TABU 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 'TRINT_SPLIT_TABU'"Break Down an R3TR TABU Object Name into Table Name and Key
  EXPORTING
   IV_OBJ_NAME =  "

 IMPORTING
   EV_TABNAME =  "
   EV_TABKEY =  "
   EV_OBJ_NAME =  "
   EV_NAME_TOO_LONG =  "
   EV_HAS_KEY =  "
   EV_POS_KEY =  "

.

IMPORTING Parameters details for TRINT_SPLIT_TABU

IV_OBJ_NAME -

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

EXPORTING Parameters details for TRINT_SPLIT_TABU

EV_TABNAME -

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

EV_TABKEY -

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

EV_OBJ_NAME -

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

EV_NAME_TOO_LONG -

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

EV_HAS_KEY -

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

EV_POS_KEY -

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

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

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