SAP ME_AUTH_GETDETAIL Function Module for
ME_AUTH_GETDETAIL is a standard me auth getdetail 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 me auth getdetail FM, simply by entering the name ME_AUTH_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: ME_AUTH
Program Name: SAPLME_AUTH
Main Program: SAPLME_AUTH
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function ME_AUTH_GETDETAIL 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 'ME_AUTH_GETDETAIL'".
EXPORTING
MEUSER = "User Name
DEVICEID = "Authorizations per Client User
IMPORTING
EXMEUSER = "
TABLES
DETAILVALUES = "
RETURN = "Return Parameters
IMPORTING Parameters details for ME_AUTH_GETDETAIL
MEUSER - User Name
Data type: MEUSERS-MEUSEROptional: No
Call by Reference: No ( called with pass by value option)
DEVICEID - Authorizations per Client User
Data type: MEUSERS-DEPLIDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ME_AUTH_GETDETAIL
EXMEUSER -
Data type: MEUSERSOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ME_AUTH_GETDETAIL
DETAILVALUES -
Data type: MEUSVALUESOptional: No
Call by Reference: Yes
RETURN - Return Parameters
Data type: BAPIRET2Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ME_AUTH_GETDETAIL 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_meuser | TYPE MEUSERS-MEUSER, " | |||
| lv_exmeuser | TYPE MEUSERS, " | |||
| lt_detailvalues | TYPE STANDARD TABLE OF MEUSVALUES, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_deviceid | TYPE MEUSERS-DEPLID. " |
|   CALL FUNCTION 'ME_AUTH_GETDETAIL' " |
| EXPORTING | ||
| MEUSER | = lv_meuser | |
| DEVICEID | = lv_deviceid | |
| IMPORTING | ||
| EXMEUSER | = lv_exmeuser | |
| TABLES | ||
| DETAILVALUES | = lt_detailtalues | |
| RETURN | = lt_return | |
| . " ME_AUTH_GETDETAIL | ||
ABAP code using 7.40 inline data declarations to call FM ME_AUTH_GETDETAIL
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 MEUSER FROM MEUSERS INTO @DATA(ld_meuser). | ||||
| "SELECT single DEPLID FROM MEUSERS INTO @DATA(ld_deviceid). | ||||
Search for further information about these or an SAP related objects