Required Authorization
Contact a super or cloud administrator in your company.
Edit User Data
Additionally, authorization Edit Authorizations to perform special tasks within the application, see below.
To access the support applications in SAP for Me, visitors need a S-User ID and in most cases, special permissions. For security reasons, SAP customers administer their users and support-related authorizations themselves:
All these tasks are carried out in the User Management application(opens in new tab), which:
Contact a super or cloud administrator in your company.
Edit User Data
Additionally, authorization Edit Authorizations to perform special tasks within the application, see below.
To start the application, go to Users & Contacts → Overview tab → Manage Users and Authorizations card. The card shows this at-a-glance info:
The application interface features eight sub-sections that can be accessed using tabs. The figures on the tabs indicate the number of items in the respective sub-section.
The Action Required section lists all self-service requests that S-users have submitted for approval: to have their ID extended close to the end of its lifetime, or to get more authorizations assigned.
There are three types of request statuses – Awaiting Approval, Approved, and Rejected.
Upon entering the section, the list is filtered by requests in status Awaiting approval. To show the full history of already approved and rejected requests, simply remove this filter or use the filter bar to specify other selection criteria.
In the table of all requests, the column Type of Request categorizes the requests by topic, and Processed By indicates which administrator in your organization processed the respective request.
By clicking Download, the result list can be downloaded as a CSV file.
Click an authorization request to proceed to the Authorization Request page. A tab strip provides access to page sub-sections that contain contact details (including the reason for request) and authorization details. You can now easily approve or reject the request by clicking the respective buttons in the footer action bar.
If required, you can set the authorization level for the newly granted permission.
Process an expiry date request by selecting it from the list in the Action Required section. This brings you to the Manage Expiry Date page with its two sub-sections about contact details (including the reason for the request) and the option to manage the expiry date. To set a new expiry date, enter it manually or specify it using the date picker icon, then click Approve in the footer action bar. Alternatively, click Reject to dismiss the request.
Important: Once the S-user ID has been requested, this association cannot be changed.
It can take up to 24 hours for it to be generated. The new user will receive an e-mail with an activation link, which is valid for 10 days.
User administrators can track the progress of the request under the Requested Users tab where the Status column initially shows In Process and, once the ID has been created, Successful.
Once the new S-user ID has been generated, it will also be listed under the Users tab.
Administrators with the authorization Edit User Data can change basic properties of their company's (or Customer CoE's) S-user IDs: Telephone numbers, e-mail addresses, job titles, department associations. In addition, this authorization lets them request and delete S-user IDs.
If you have the authorization Edit Authorizations, you can also grant other S-users special permissions for support applications.
On the application's overview screen, click a list item in the sections Users, Requested Users, or Important Contacts to enter the User Details page for that user.
The header shows the user's ID, name, history, and company association.
A tab strip provides access to page sub-sections that contain contact details, a summary of the user's authorization profile as well as important functions, and information about a linked SAP Universal ID:
Note: If the user has activated SMS text notifications about important SAP for Me alerts, by default these are sent to phone 2. Unless the Phone 2 field is empty, in which case notifications are sent to phone 1.
To remove the user from a department, select the first list option, NONE.
Users can be assigned to departments defined by you and other user administrators in your company. You can filter lists of users or run reports based on this criterion.
You can assign one individual user to or remove him from a department by entering the User Details page and changing the basic settings, see above. Alternatively, or to simultaneously change the department assignment for multiple users, proceed as follows:
The department information is updated in the users' information immediately.
You can remove departments from the list of options in the Manage Departments dialog.
Note: All users who are assigned to that department will get unassigned.
To delete a department:
For your own security, regularly delete inactive S-user IDs and S-user IDs of people who have left your company to prevent unauthorized access to company data and keep your user data up-to-date.
S-users with special functions (such as software recipient or technical contact person for an installation) cannot be deleted. This is only possible once SAP has transferred the function to somebody else. To do this, report an incident(opens in new tab) using component XX-SER-SAPSMP-USR and nominate a contact person who is to assume the role of the S-user to be deleted. It is, of course, also possible to request changes to contact person roles without deleting an S-user.
To delete one individual S-user ID:
Alternatively, or to delete multiple S-user IDs:
Deleted S-user IDs are listed in the Deleted Users section of the application for twelve months and cannot be reactivated (see KBA 1811859).
When an S-user ID is deleted, the following are not affected:
Authorization management deals with permissions that are required to fulfill certain tasks using applications in the SAP for Me website, for instance, report incidents, download software, or check software orders. Most authorizations contain not only the user's right to perform a specific task, but also the level at which the user can exercise this right.
Example – A user may be allowed to report incidents for one particular SAP product that your company has licensed (represented by "installation"), but not for others.
An important principle is the following:
Rule of Authorization Inheritance – Administrators can only grant those authorizations that they have been granted themselves.
There are several ways to maintain an S-user's authorization profile:
In the application's Users, Requested Users, or Important Contacts sections click a row in the list to enter the User Details page for that user.
You can copy an existing authorization profile from one user (source user) to one or multiple other users (target users) so that they share the exact same authorizations on the same levels.
Notes:
To copy authorizations from a source user to one or multiple target users:
Authorization packages are bundles of authorizations that you can flexibly define and then grant to one or multiple users in your company. This is helpful if several users need the same authorization profile, for instance because they work on the same tasks.
Note that the Rule of Authorization Inheritance applies: Only those authorizations contained in a package are granted to the user, which the person who applies the package possesses themselves.
Entering the Authorization Packages sub-section requires the authorization Edit Authorizations. A table lists all packages that the logged-on user administrator is entitled to assign to colleagues.
Revert the protection by clicking Unprotect.
Creating a new authorization package is done in two steps: First, a new item is added to the list of all packages. Second, the new package's authorizations are defined.
Adding authorizations to the new package or removing or changing authorizations for an existing package, is done in a similar way to maintaining individual authorizations for a user:
Note: If you (unnecessarily) select installations that belong to a customer number that was already selected in the previous steps, these entries will disappear when you save.
All changes are immediately reflected in the Overview section of the package's details page. It lists authorizations that are contained in the package, the type of levels they have been granted on (Installation, Customer, Customer CoE, i.e. Customer Center of Expertise), as well as the level IDs and names.
There are several ways to assign authorization packages to users. However, only the first one is suitable to remove packages from a user's authorization profile.
Option 1 — Use if you want to assigning multiple packages to one user (or remove packages from the user's authorization profile):
Option 2 — Use if you want to assign multiple packages to multiple users:
Note: The list of packages does not indicate packages that have previously been assigned to the users.
Option 3 — Use if you want to assign multiple packages to multiple users:
To change the authorization profiles of multiple S-users at the same time, there are three options:
With the help of powerful selection criteria, the section Reports and Updates lets you identify all users that share certain authorizations or compare permissions of different users. If required, you can then update their authorizations simultaneously.
Each item in the result list is a data set consisting of the following:
Note that, depending on the number of granted authorizations and granularity of authorization levels, one user can be listed multiple times in the list!
To retrieve a particular set of such items, the following criteria are offered:
Multiple S-user IDs are logically connected by OR, i.e. all items are retrieved that contain at least one of the specified IDs.
The three filters:
refer to authorization levels. If you select a value in any of them, all users will be listed where an authorization has been granted on one of the specified customer numbers, installation numbers, or S-user IDs.
Select Match AT LEAST ONE Filter Criterion if you want to link the filters through a logical OR. The result list will then feature all items that contain any of the values that you selected in one of the filters.
Note: Within one filter the specified values are always logically connected by OR.
Note: The result list will also feature items where the Close Incidents authorization was granted on the higher-level customer numbers (or Customer CoE) that your installations are linked to.
If you run the same reports on a regular basis, you can save filter settings for future re-use as so-called "views".
An asterisk (*) next to the view's name will indicate that the current view has been modified but not saved.
Note: The default view Standard cannot be modified, hence the Save button is grayed out and only Save As is offered to store your filter settings.
Alternatively:
To change the selection criteria of a particular view, proceed as follows:
To change the name or behavior of a view, do the following:
You can hide selection criteria that are not relevant to you. You can then add this setting to an existing view.
You can enhance or restrict the authorization profile of all users in a result list. Proceed as follows:
In long lists, use the search or advanced search to find a particular customer number: Enter the search term and click Go.
Click Delete Authorizations and proceed in a similar way if you want to restrict the users' authorizations. Also see the section Assigning, amending, or removing individual authorizations.
For information on technical communication users (formerly called Support Hub users) please see this page, Technical Communication User.