SAP MEMGMT_DEVICE_USER_ASSIGNMENT Function Module for Checks for consistency of Hierarchy groups of users on single device
MEMGMT_DEVICE_USER_ASSIGNMENT is a standard memgmt device user assignment SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Checks for consistency of Hierarchy groups of users on single device 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 memgmt device user assignment FM, simply by entering the name MEMGMT_DEVICE_USER_ASSIGNMENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: MEMGMT_DEVICE
Program Name: SAPLMEMGMT_DEVICE
Main Program: SAPLMEMGMT_DEVICE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function MEMGMT_DEVICE_USER_ASSIGNMENT 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 'MEMGMT_DEVICE_USER_ASSIGNMENT'"Checks for consistency of Hierarchy groups of users on single device.
EXPORTING
I_USER_NEW = "ME: Hierarchy value
I_USER_ON_DEVICE = "ME: Hierarchy value
I_MODE = "Char 20
I_NODE_ID_HG = "Unique hierarchy node ID
IMPORTING
E_STATUS = "Char 20
E_NODE_TO_BE_ASSIGNED_TO = "Unique hierarchy node ID
E_NODE_NAME = "ME: Hierarchy node description
E_DEVICE_LIST = "ME: User devices list
E_USER_LIST = "ME: User details
IMPORTING Parameters details for MEMGMT_DEVICE_USER_ASSIGNMENT
I_USER_NEW - ME: Hierarchy value
Data type: MEMGMT_HIER_VALUEOptional: No
Call by Reference: No ( called with pass by value option)
I_USER_ON_DEVICE - ME: Hierarchy value
Data type: MEMGMT_HIER_VALUEOptional: No
Call by Reference: No ( called with pass by value option)
I_MODE - Char 20
Data type: CHAR20Optional: No
Call by Reference: No ( called with pass by value option)
I_NODE_ID_HG - Unique hierarchy node ID
Data type: MEMGMT_NODE-NODE_IDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MEMGMT_DEVICE_USER_ASSIGNMENT
E_STATUS - Char 20
Data type: CHAR20Optional: No
Call by Reference: No ( called with pass by value option)
E_NODE_TO_BE_ASSIGNED_TO - Unique hierarchy node ID
Data type: MEMGMT_NODE-NODE_IDOptional: No
Call by Reference: No ( called with pass by value option)
E_NODE_NAME - ME: Hierarchy node description
Data type: MEMGMT_NODE_T-TEXTOptional: No
Call by Reference: No ( called with pass by value option)
E_DEVICE_LIST - ME: User devices list
Data type: MEMGMT_USER_DEVICES_TTOptional: No
Call by Reference: No ( called with pass by value option)
E_USER_LIST - ME: User details
Data type: USGRPS_USR_TTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MEMGMT_DEVICE_USER_ASSIGNMENT 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_status | TYPE CHAR20, " | |||
| lv_i_user_new | TYPE MEMGMT_HIER_VALUE, " | |||
| lv_i_user_on_device | TYPE MEMGMT_HIER_VALUE, " | |||
| lv_e_node_to_be_assigned_to | TYPE MEMGMT_NODE-NODE_ID, " | |||
| lv_i_mode | TYPE CHAR20, " | |||
| lv_e_node_name | TYPE MEMGMT_NODE_T-TEXT, " | |||
| lv_i_node_id_hg | TYPE MEMGMT_NODE-NODE_ID, " | |||
| lv_e_device_list | TYPE MEMGMT_USER_DEVICES_TT, " | |||
| lv_e_user_list | TYPE USGRPS_USR_TT. " |
|   CALL FUNCTION 'MEMGMT_DEVICE_USER_ASSIGNMENT' "Checks for consistency of Hierarchy groups of users on single device |
| EXPORTING | ||
| I_USER_NEW | = lv_i_user_new | |
| I_USER_ON_DEVICE | = lv_i_user_on_device | |
| I_MODE | = lv_i_mode | |
| I_NODE_ID_HG | = lv_i_node_id_hg | |
| IMPORTING | ||
| E_STATUS | = lv_e_status | |
| E_NODE_TO_BE_ASSIGNED_TO | = lv_e_node_to_be_assigned_to | |
| E_NODE_NAME | = lv_e_node_name | |
| E_DEVICE_LIST | = lv_e_device_list | |
| E_USER_LIST | = lv_e_user_list | |
| . " MEMGMT_DEVICE_USER_ASSIGNMENT | ||
ABAP code using 7.40 inline data declarations to call FM MEMGMT_DEVICE_USER_ASSIGNMENT
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 NODE_ID FROM MEMGMT_NODE INTO @DATA(ld_e_node_to_be_assigned_to). | ||||
| "SELECT single TEXT FROM MEMGMT_NODE_T INTO @DATA(ld_e_node_name). | ||||
| "SELECT single NODE_ID FROM MEMGMT_NODE INTO @DATA(ld_i_node_id_hg). | ||||
Search for further information about these or an SAP related objects