3809899 - RBP role and assignment IDs change after transport across environments

• After transporting a role from source environment to a target environment, role assignment IDs change.
• The new IDs are applied to both newly added and previously existing assignments within the role.
• The RBP User Role Change Report shows that users associated with the previous ID were deleted and re-added under a new ID.
• Role IDs are not consistent across environments after transport.

SAP SuccessFactors HCM Core

1. In the source environment, add a new assignment to an existing RBP permission role.
2. Transport the role configuration to the target environment.
3. In the target environment, review the role’s assignment IDs and run the RBP User Role Change Report.
4. Observe that assignment IDs differ from the source environment and that the report shows delete/re-add entries tied to the ID change.

Permission role and role assignment IDs are system-generated per environment based on object creation time and are not preserved during transport. The target system regenerates IDs for incoming role configurations, which makes IDs differ across environments and leads reports to reflect ID-level delete/re-add events.

• This is expected behavior.
• If a change to this behavior is desired, please submit an enhancement idea.
• Refer to: 2090228 - How to submit enhancement ideas for SAP SuccessFactors Product - SAP for Me

KBA 2090228 - How to submit enhancement ideas for SAP SuccessFactors Product

RBP, role-based permissions, role id, assignment id, id regeneration, transport, cross-environment, inconsistent ids, user role change report, delete re-add, by design, instance differences, permission role, SuccessFactors platform, audit report , KBA , LOD-SF-PLT-RBP , Role Based Permissions , LOD-SF-PLT-CHA , Change Audit , LOD-SF-PLT-CGC , Configuration Center , How To