What happens when you delete a profile in SAP

Deleting a profile in SAP removes a user's access to the system and their associated permissions. When you delete a profile, that user can no longer log in, and any roles or authorizations tied to that profile become inactive for them. The profile itself — the collection of settings, access rights, and system parameters — is marked as deleted in SAP's records.

The actual data the user created (documents, transactions, records) stays in the system. Deletion only removes the person's ability to access SAP going forward. This is different from deleting user data, which is a separate process that requires additional steps and permissions.

Most organizations delete profiles when someone leaves a job, changes roles, or no longer needs system access. SAP keeps a record that the profile existed and when it was deleted, which is useful for auditing and compliance purposes.

Key Takeaways

  • Deleting a profile removes a user's login access and all their assigned roles, but does not erase the data they created in SAP.
  • You need administrator rights in SAP to delete a profile — standard users cannot perform this action.
  • The deletion process takes place in the User Maintenance transaction (SU01) or through the Identity Management system if your organization uses one.
  • SAP records the deletion date and the person who performed it, so the action is traceable for security and compliance audits.

Where to find the delete option in SAP

Open the User Maintenance transaction by typing SU01 into the command field at the top left of your SAP screen and pressing Enter. This is the standard place where user profiles are created, edited, and deleted across most SAP systems.

In the User Maintenance screen, enter the username you want to delete in the User field and click the Display button (or press Enter). The system will load that user's profile information. Once the profile is displayed, look for a Delete button in the toolbar at the top of the screen — it usually appears as a trash can icon or is labeled "Delete" in the menu.

If your organization uses SAP Identity Management (a separate module that handles user provisioning), the delete function may be located there instead. Ask your system administrator which tool your company uses, because the steps differ between the two systems.

The steps to delete a profile

First, navigate to transaction SU01 and search for the user profile you want to remove. Type the username exactly as it appears in the system — usernames are case-sensitive in SAP. Click Display to open the profile.

Once the profile is open, click the Delete button from the toolbar menu. SAP will ask you to confirm the deletion. Read the confirmation message carefully — it will tell you whether the user has any active sessions or pending transactions that might be affected. If the user is currently logged in, SAP may ask you to log them out first or warn you that the deletion will terminate their session.

After you confirm, SAP marks the profile as deleted and removes it from the active user list. The system records the deletion timestamp and your administrator ID. The user will not be able to log in after this point, and any attempt to do so will result in an authentication failure.

What you need before you delete

You must have administrator rights in SAP to delete any profile. If you do not have these rights, the Delete button will not appear or will be grayed out. Contact your system administrator if you need to delete a profile but cannot access the function.

Have the exact username ready. If you are unsure of the username, ask the person's manager or check your company's employee directory. Deleting the wrong profile can lock out someone who still needs access, so verify the username before you proceed.

If the user is currently logged into SAP, you have two options: ask them to log out first, or proceed with the deletion knowing that their session will be terminated. Some organizations prefer to notify the user before deleting their profile so they can save any work in progress.

What happens after deletion

The deleted user will be unable to log in when ready. If they try to access SAP, they will see an authentication error or a message stating that their user does not exist. This happens even if they remember their password correctly.

The user's data — any documents they created, transactions they processed, or records they modified — remains in the system. Other users can still see and access this data if they have the appropriate permissions. The deletion only removes the person's ability to log in and make new changes.

If you need to restore access later, you can create a new profile with the same username or a different one. However, the original profile cannot be reactivated once deleted — you must create a fresh profile and reassign all the necessary roles and permissions.

Undoing a deletion or reactivating a user

SAP does not have an "undo" button for profile deletions. Once a profile is deleted, it cannot be restored to its original state. If you delete a profile by mistake, you will need to create a new profile for that user and reassign all their roles and authorizations from scratch.

If a user needs access again after their profile was deleted, create a new profile in SU01 with their username (or a new username if the original one is reserved). Assign the same roles they had before, or the roles they need for their new position. This process takes a few minutes but requires you to remember or look up what permissions they originally had.

To avoid accidental deletions, some organizations require two administrators to approve a deletion, or they disable the delete function and use a deactivation option instead. Ask your system administrator whether your company has a policy on this.

Deactivation as an alternative to deletion

Some organizations prefer to deactivate a profile instead of deleting it. Deactivation prevents a user from logging in but keeps the profile in the system and preserves a record of all their settings and permissions. If the person returns to the role later, you can reactivate their profile without rebuilding it from scratch.

To deactivate instead of delete, open the profile in SU01, look for a Status or Active field, and change it from Active to Inactive. Save the changes. The user will no longer be able to log in, but the profile remains in the system's records.

Ask your system administrator whether your organization uses deactivation or deletion, because the two approaches have different compliance and security implications. Some industries require permanent deletion for regulatory reasons, while others prefer deactivation for operational flexibility.

Frequently Asked Questions

Can I delete my own profile?

No. SAP prevents administrators from deleting their own profile while logged in, because this would lock them out of the system. If you need to remove your own profile, another administrator must do it, or you must log in as a different administrator account first.

What if the user is currently logged into SAP?

You can still delete the profile. SAP will terminate the user's session, and they will be logged out when ready. Any unsaved work they had open will be lost, so it is best to notify the user before deleting their profile if possible.

Does deleting a profile remove the user's data from SAP?

No. Deleting a profile only removes the user's login access. All documents, transactions, and records they created remain in the system. If you need to remove their data as well, that requires a separate data deletion process handled by your system administrator.

Can I search for deleted profiles in SAP?

Yes. In transaction SU01, you can filter the user list to show deleted profiles. This is useful for auditing purposes or if you need to verify when a profile was deleted and by whom. The deletion date and administrator ID are recorded in the system logs.

What if I need to restore a deleted profile?

You cannot restore a deleted profile. You must create a new profile with the same or a different username and reassign all the roles and permissions. Keep a record of what roles each user had before deletion so you can rebuild their access quickly if needed.