Committing Duplicate User Data Changes to the Dependent SAP Systems
- Using the Update User Data button.
- Using the User Maintenance button (transaction SU01).
Recommendations that are gray are read-only and cannot be processed. This could have a number of reasons, such as the dependent SAP system has no logical RFC destination, the dependent SAP system may be unavailable, the user may not have sufficient rights for the system, or the recommendation may be blocked by another user.
To commit duplicate user data changes to the dependent SAP systems:
- Run a Duplicate User Recommendations report (see Creating a Duplicate User Recommendations Report.
-
On the Process Duplicate Users screen, select for which
user, or users (using Ctrl + click), you want to accept
the recommendations. Follow one of the following procedures:
- Click Update User Data to update the user data using FlexNet Manager for SAP Applications features.
- In the Update dialog, select the check boxes for the user primary data fields that you want to update. Usually, these will be the fields that you modified earlier. Click Continue or press Enter.
- Click Yes in the dialog.
- If the update was successful, the cell that contains the updated value is highlighted in green. If the update was not successful, the cell is red. If multiple fields were selected for the update, but only one field returns an error, all selected fields are highlighted in red.
Click User Maintenance to access the user data directly on the dependent SAP system. This will open the transaction SU01 on the dependent SAP system. This requires that the Dialog RFC destination has been set up for the system that you want to access. Perform the usual steps for user maintenance in SAP to change the user data.
Important: Any changes that are made using the User Maintenance button (transaction SU01) will not be reflected in the Duplicate User Recommendations report.
FlexNet Manager Suite (On-Premises)
2020 R2