How To Fix FSSC_RDS091 - User &1 exists in ERP system &2

FSSC_RDS091 - Overview

• Message type: E = Error

• Message class: FSSC_RDS - Financial Shared Service Center, RDS

• Message number: 091

• Message text: User &1 exists in ERP system &2

What causes this issue?

You tried to create a user with the same name as an existing user.

System Response

The system does not create a new user. Instead it changes the existing
user. The system creates a business partner for the user. It also
assigns new roles to the user, if these roles are not already assigned
to the user. The system also assigns the user to the Financial Shared
Service Organization structure. The system does not change the
attributes of the existing user. For example, the address is not
changed.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FSSC_RDS091 - User &1 exists in ERP system &2 ?

  The SAP error message FSSC_RDS091 indicates that a user already exists in the specified ERP system. This error typically arises during processes such as user creation or synchronization between systems, particularly in the context of SAP S/4HANA or SAP Fiori applications.
  
  Cause:
  The error occurs when:
  
  You attempt to create a user in the SAP system, but a user with the same ID already exists in the specified ERP system.
  There may be a mismatch in user IDs or an attempt to create a duplicate entry.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Existing Users:
  
  Verify if the user ID already exists in the ERP system. You can do this by using transaction code SU01 (User Maintenance) to search for the user.
  
  
  
  Modify or Delete Existing User:
  
  If the user exists and is not needed, you can delete or modify the existing user to free up the user ID.
  If the user is needed, consider using