SAP GMIT_AUTH_CHECK Function Module for Authorization Check for Report Writer
GMIT_AUTH_CHECK is a standard gmit auth check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Authorization Check for Report Writer 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 gmit auth check FM, simply by entering the name GMIT_AUTH_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: GMREPPOOL
Program Name: SAPLGMREPPOOL
Main Program: SAPLGMREPPOOL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GMIT_AUTH_CHECK 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 'GMIT_AUTH_CHECK'"Authorization Check for Report Writer.
EXPORTING
I_TABNAME = "Ledger Table Name
I_RECORD = "RW record structure
IMPORTING
E_SUBRC = "Return Code to Authorization Check
IMPORTING Parameters details for GMIT_AUTH_CHECK
I_TABNAME - Ledger Table Name
Data type: TABNAMEOptional: No
Call by Reference: Yes
I_RECORD - RW record structure
Data type: ANYOptional: No
Call by Reference: Yes
EXPORTING Parameters details for GMIT_AUTH_CHECK
E_SUBRC - Return Code to Authorization Check
Data type: SY-SUBRCOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for GMIT_AUTH_CHECK 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: | ||||
| lv_e_subrc | TYPE SY-SUBRC, " | |||
| lv_i_tabname | TYPE TABNAME, " | |||
| lv_i_record | TYPE ANY. " |
|   CALL FUNCTION 'GMIT_AUTH_CHECK' "Authorization Check for Report Writer |
| EXPORTING | ||
| I_TABNAME | = lv_i_tabname | |
| I_RECORD | = lv_i_record | |
| IMPORTING | ||
| E_SUBRC | = lv_e_subrc | |
| . " GMIT_AUTH_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM GMIT_AUTH_CHECK
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.| "SELECT single SUBRC FROM SY INTO @DATA(ld_e_subrc). | ||||
Search for further information about these or an SAP related objects