Diagnosis
If the roles cannot be updated successfully, this does not indicate thatthe entire migration has failed. The migration data is still availablein profiles for all users, and is also already assigned to the users.
However, it is possible that the roles are not adjusted; this can befixed by triggering the migration again once the cause of the problem isresolved.

System Response
The system displays warnings; these warnings do not cause the migrationto terminate.

Procedure
Once the cause of the problem is resolved, a new migration can amend thesituation.
If only the generation of roles or the user comparison fails, this canbe the result of missing execution authorizations, for example; you canresolve this manually in role maintenance.
Caution: If this is not the cause of the problem, generating theroles can delete the migration data. This means that the correspondingprofiles are reverted to the old status from before the migration.
A user comparison can also be triggered manually.
If authorizations were missing, they must be assigned to the executinguser.
Note that from a technical viewpoint, the relevant information foranalysis authorizations is stored in the profiles. This means that themigration was successful from an execution point of view and that usersalready have the migrated authorizations for the current authorizationconcept. The authorizations are only visible in the roles.