Symptom
- After transporting the PPX configuration to the target environment, users experience issues with category-based access and permissions
- Certain cards or categories may not be displayed correctly, access may be inconsistent, or permission-related errors may occur despite the configuration working as expected in the source environment
Environment
SAP SuccessFactors HCM Suite
Cause
- The issue is caused by a mismatch in Category IDs and permission metadata between environments
- The PPX transport does not include the associated RBP configuration, resulting in incomplete configuration alignment after transport
- The behavior is caused by differences in Category ID and permission metadata between the environments, as the transported PPX configuration does not include the associated RBP (Role-Based Permissions) setup
Resolution
- The Product team is tentatively targeting a fix in the 2H 2026 release (subject to the standard roadmap disclaimer).
- This enhancement is expected to address the current limitations related to transporting card-level and category-level configurations.
Workaround
- Transport the latest People Profile, including the Full Profile, from Production to lower environment, using the Configuration Transport Center.
- By doing so, the Category IDs for each category will remain consistent between the source and target environments. As a result, the corresponding generated permission items will also be aligned, which should help prevent the permission mismatches encountered during RBP synchronization.
See Also
Keywords
2H 2026, RBP configuration, PPX transport, metadata, permission , Category IDs , KBA , LOD-SF-PLT-CGC , Configuration Center , Product Enhancement
Product
SAP SuccessFactors HCM Suite 2605
SAP Knowledge Base Article - Public