SAP TRINT_GTABKEY_READ_INTERFACE Function Module for
TRINT_GTABKEY_READ_INTERFACE is a standard trint gtabkey read interface SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 gtabkey read interface FM, simply by entering the name TRINT_GTABKEY_READ_INTERFACE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SGTA
Program Name: SAPLSGTA
Main Program: SAPLSGTA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function TRINT_GTABKEY_READ_INTERFACE 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_GTABKEY_READ_INTERFACE'".
EXPORTING
IV_USERNAME = "
* IV_GROUP = "
* IV_MASTER = "
* IV_LAYOUTID = "
* IV_NEW_SWC_REL = "
* IV_NEW_GROUP = "
* IV_NEW_OWNER = "
TABLES
* IT_USER = "
* IT_SWC_REL = "
* IT_TABNAME = "
* IT_TRKORR = "
* IT_GTABKEY = "
* ET_GTABKEY = "
EXCEPTIONS
WRONG_CALL = 1 PERMISSION_DENIED = 2 ENQUEUE_FAILED = 3 GROUP_NOT_FOUND = 4
IMPORTING Parameters details for TRINT_GTABKEY_READ_INTERFACE
IV_USERNAME -
Data type: AS4USEROptional: No
Call by Reference: No ( called with pass by value option)
IV_GROUP -
Data type: CGKGROUPOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_MASTER -
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_LAYOUTID -
Data type: LAYOUTIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_NEW_SWC_REL -
Data type: GTABKEY_SWCRELOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_NEW_GROUP -
Data type: CGKGROUPOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_NEW_OWNER -
Data type: AS4USEROptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for TRINT_GTABKEY_READ_INTERFACE
IT_USER -
Data type: GTABKEY_REQTOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_SWC_REL -
Data type: GTABKEY_SWCRELTOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_TABNAME -
Data type: GTABKEY_TABTOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_TRKORR -
Data type: GTABKEY_TRKORRTOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_GTABKEY -
Data type: TR_GTABKEYSOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_GTABKEY -
Data type: TR_GTABKEYSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_CALL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PERMISSION_DENIED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ENQUEUE_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
GROUP_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TRINT_GTABKEY_READ_INTERFACE 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: | ||||
| lt_it_user | TYPE STANDARD TABLE OF GTABKEY_REQT, " | |||
| lv_wrong_call | TYPE GTABKEY_REQT, " | |||
| lv_iv_username | TYPE AS4USER, " | |||
| lv_iv_group | TYPE CGKGROUP, " | |||
| lt_it_swc_rel | TYPE STANDARD TABLE OF GTABKEY_SWCRELT, " | |||
| lv_permission_denied | TYPE GTABKEY_SWCRELT, " | |||
| lv_iv_master | TYPE CHAR1, " | |||
| lt_it_tabname | TYPE STANDARD TABLE OF GTABKEY_TABT, " | |||
| lv_enqueue_failed | TYPE GTABKEY_TABT, " | |||
| lt_it_trkorr | TYPE STANDARD TABLE OF GTABKEY_TRKORRT, " | |||
| lv_iv_layoutid | TYPE LAYOUTID, " | |||
| lv_group_not_found | TYPE LAYOUTID, " | |||
| lt_it_gtabkey | TYPE STANDARD TABLE OF TR_GTABKEYS, " | |||
| lv_iv_new_swc_rel | TYPE GTABKEY_SWCREL, " | |||
| lt_et_gtabkey | TYPE STANDARD TABLE OF TR_GTABKEYS, " | |||
| lv_iv_new_group | TYPE CGKGROUP, " | |||
| lv_iv_new_owner | TYPE AS4USER. " |
|   CALL FUNCTION 'TRINT_GTABKEY_READ_INTERFACE' " |
| EXPORTING | ||
| IV_USERNAME | = lv_iv_username | |
| IV_GROUP | = lv_iv_group | |
| IV_MASTER | = lv_iv_master | |
| IV_LAYOUTID | = lv_iv_layoutid | |
| IV_NEW_SWC_REL | = lv_iv_new_swc_rel | |
| IV_NEW_GROUP | = lv_iv_new_group | |
| IV_NEW_OWNER | = lv_iv_new_owner | |
| TABLES | ||
| IT_USER | = lt_it_user | |
| IT_SWC_REL | = lt_it_swc_rel | |
| IT_TABNAME | = lt_it_tabname | |
| IT_TRKORR | = lt_it_trkorr | |
| IT_GTABKEY | = lt_it_gtabkey | |
| ET_GTABKEY | = lt_et_gtabkey | |
| EXCEPTIONS | ||
| WRONG_CALL = 1 | ||
| PERMISSION_DENIED = 2 | ||
| ENQUEUE_FAILED = 3 | ||
| GROUP_NOT_FOUND = 4 | ||
| . " TRINT_GTABKEY_READ_INTERFACE | ||
ABAP code using 7.40 inline data declarations to call FM TRINT_GTABKEY_READ_INTERFACE
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