SAP TR_REQ_CHECK_GLOBAL_KEYS Function Module for Kollisionscheck gegen GTABKEY

Search SAP Function Modules

TR_REQ_CHECK_GLOBAL_KEYS is a standard tr req check global keys SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Kollisionscheck gegen 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 tr req check global keys FM, simply by entering the name TR_REQ_CHECK_GLOBAL_KEYS 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): Normal Function Module
Update:

Function TR_REQ_CHECK_GLOBAL_KEYS 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 'TR_REQ_CHECK_GLOBAL_KEYS'"Kollisionscheck gegen GTABKEY
  EXPORTING
   IS_OBJECTS =  "
*  IV_WITH_TADIR =  "
*  IS_E071E =  "
   IS_KEYS =  "
   IS_HEADER =  "
*  IV_CDLVUNIT =  "
*  IV_CRELEASE =  "
*  IV_SIMULATION =  "
*  IV_EXCEPTION =  "
*  IV_EXC_STATUS =  "
*  IV_ONLY_COUNT =  "

 IMPORTING
   E_RETURN_CODE =  "
   E_GTABKEY_RES =  "

EXCEPTIONS
   WRONG_CALL = 1    GROUP_NOT_FOUND = 2    ENQUEUE_FAILED = 3    GLOBAL_KEY_ERROR = 4    NO_SW_COMP_FOUND = 5 

.

IMPORTING Parameters details for TR_REQ_CHECK_GLOBAL_KEYS

IS_OBJECTS -

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

IV_WITH_TADIR -

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

IS_E071E -

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

IS_KEYS -

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

IS_HEADER -

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

IV_CDLVUNIT -

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

IV_CRELEASE -

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

IV_SIMULATION -

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

IV_EXCEPTION -

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

IV_EXC_STATUS -

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

IV_ONLY_COUNT -

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

EXPORTING Parameters details for TR_REQ_CHECK_GLOBAL_KEYS

E_RETURN_CODE -

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

E_GTABKEY_RES -

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

EXCEPTIONS details

WRONG_CALL -

Data type:
Optional: No
Call by Reference: Yes

GROUP_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

ENQUEUE_FAILED -

Data type:
Optional: No
Call by Reference: Yes

GLOBAL_KEY_ERROR -

Data type:
Optional: No
Call by Reference: Yes

NO_SW_COMP_FOUND -

Data type:
Optional: No
Call by Reference: Yes

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

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