SAP TRINT_GTABKEY_INTERFACE Function Module for intern: Zugriffe auf GTABKEY









TRINT_GTABKEY_INTERFACE is a standard trint gtabkey interface SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for intern: Zugriffe auf GTABKEY 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 gtabkey interface FM, simply by entering the name TRINT_GTABKEY_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_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_INTERFACE'"intern: Zugriffe auf GTABKEY
  EXPORTING
   IV_MODE =  "
   IV_USERNAME =  "
*  IV_GROUP =  "
*  IV_MASTER =  "
*  IV_LAYOUTID =  "
*  IV_NEW_SWC_REL =  "
*  IV_NEW_GROUP =  "
*  IV_NEW_OWNER =  "
*  IV_ARCHIVE = 'X' "

TABLES
*  IT_USER =  "
*  IT_SWC_REL =  "
*  IT_TABNAME =  "
*  IT_TRKORR =  "
*  IT_GTABKEY =  "
*  ET_GTABKEY =  "
*  CT_SWC_GRP =  "

EXCEPTIONS
   WRONG_CALL = 1    PERMISSION_DENIED = 2    ENQUEUE_FAILED = 3    GROUP_NOT_FOUND = 4
.



IMPORTING Parameters details for TRINT_GTABKEY_INTERFACE

IV_MODE -

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

IV_USERNAME -

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

IV_GROUP -

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

IV_MASTER -

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

IV_LAYOUTID -

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

IV_NEW_SWC_REL -

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

IV_NEW_GROUP -

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

IV_NEW_OWNER -

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

IV_ARCHIVE -

Data type: CHAR1
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for TRINT_GTABKEY_INTERFACE

IT_USER -

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

IT_SWC_REL -

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

IT_TABNAME -

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

IT_TRKORR -

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

IT_GTABKEY -

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

ET_GTABKEY -

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

CT_SWC_GRP -

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

EXCEPTIONS details

WRONG_CALL -

Data type:
Optional: No
Call by Reference: Yes

PERMISSION_DENIED -

Data type:
Optional: No
Call by Reference: Yes

ENQUEUE_FAILED -

Data type:
Optional: No
Call by Reference: Yes

GROUP_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TRINT_GTABKEY_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_iv_mode  TYPE CHAR4, "   
lv_wrong_call  TYPE CHAR4, "   
lt_it_swc_rel  TYPE STANDARD TABLE OF GTABKEY_SWCRELT, "   
lv_iv_username  TYPE AS4USER, "   
lv_permission_denied  TYPE AS4USER, "   
lv_iv_group  TYPE CGKGROUP, "   
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_master  TYPE CHAR1, "   
lv_group_not_found  TYPE CHAR1, "   
lt_it_gtabkey  TYPE STANDARD TABLE OF TR_GTABKEYS, "   
lv_iv_layoutid  TYPE LAYOUTID, "   
lt_et_gtabkey  TYPE STANDARD TABLE OF TR_GTABKEYS, "   
lv_iv_new_swc_rel  TYPE GTABKEY_SWCREL, "   
lt_ct_swc_grp  TYPE STANDARD TABLE OF GTABKEY_SWC_GRPT, "   
lv_iv_new_group  TYPE CGKGROUP, "   
lv_iv_new_owner  TYPE AS4USER, "   
lv_iv_archive  TYPE CHAR1. "   'X'

  CALL FUNCTION 'TRINT_GTABKEY_INTERFACE'  "intern: Zugriffe auf GTABKEY
    EXPORTING
         IV_MODE = lv_iv_mode
         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
         IV_ARCHIVE = lv_iv_archive
    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
         CT_SWC_GRP = lt_ct_swc_grp
    EXCEPTIONS
        WRONG_CALL = 1
        PERMISSION_DENIED = 2
        ENQUEUE_FAILED = 3
        GROUP_NOT_FOUND = 4
. " TRINT_GTABKEY_INTERFACE




ABAP code using 7.40 inline data declarations to call FM TRINT_GTABKEY_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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
DATA(ld_iv_archive) = 'X'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!