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

Function GM_AUTH_CHECK_DERIVE_ENTRIES 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 'GM_AUTH_CHECK_DERIVE_ENTRIES'"GM: Authority Check for Derivation Tool.
EXPORTING
I_ACTIVITY = "Activity
I_ENVIRONMENT = "Environment for strategy
EXCEPTIONS
NO_AUTHORIZATION = 1
IMPORTING Parameters details for GM_AUTH_CHECK_DERIVE_ENTRIES
I_ACTIVITY - Activity
Data type: ACTIV_AUTHOptional: No
Call by Reference: Yes
I_ENVIRONMENT - Environment for strategy
Data type: ABADRENVOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_AUTHORIZATION - User has no authorization
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GM_AUTH_CHECK_DERIVE_ENTRIES 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_i_activity | TYPE ACTIV_AUTH, " | |||
| lv_no_authorization | TYPE ACTIV_AUTH, " | |||
| lv_i_environment | TYPE ABADRENV. " |
|   CALL FUNCTION 'GM_AUTH_CHECK_DERIVE_ENTRIES' "GM: Authority Check for Derivation Tool |
| EXPORTING | ||
| I_ACTIVITY | = lv_i_activity | |
| I_ENVIRONMENT | = lv_i_environment | |
| EXCEPTIONS | ||
| NO_AUTHORIZATION = 1 | ||
| . " GM_AUTH_CHECK_DERIVE_ENTRIES | ||
ABAP code using 7.40 inline data declarations to call FM GM_AUTH_CHECK_DERIVE_ENTRIES
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