Symptom
As Learning becomes more deeply integrated into the SAP SuccessFactors Suite, it is important to keep in mind the implications of partial refreshes – especially when only a subset of modules is refreshed rather than the full suite (like refreshing only the Learning module, instead of both BizX and Learning modules together).
Environment
SAP SuccessFactors Learning
Resolution
The information below addresses the Key Issues Post Partial Refresh:
1. Feature Enablement Issues
- Partial refreshes can lead to partial feature enablement, where the Target instance inherits the enablement status from the Source, which may differ from the intended configuration.
- The table below is designed to provide information regarding the enablement status of a feature based on the refresh performed.
- Note: Machine Learning recommendations are automatically disabled in the Target post-refresh, regardless of their prior status.
|
Source system feature status |
Target system feature status pre-refresh |
Refresh type |
Target system feature post-refresh |
|
ENABLED |
ENABLED |
Full refresh |
ENABLED |
|
DISABLED |
ENABLED |
Full refresh |
DISABLED |
|
ENABLED |
DISABLED |
Full refresh |
ENABLED |
|
DISABLED |
DISABLED |
Full refresh |
DISABLED |
|
ENABLED |
DISABLED |
Partial refresh (BizX only) |
ENABLED in BizX |
|
DISABLED |
ENABLED |
Partial refresh (BizX only) |
DISABLED in BizX ENABLED in Learning |
|
DISABLED |
DISABLED |
Partial refresh (BizX only) |
DISABLED |
|
ENABLED |
ENABLED |
Partial refresh (BizX only) |
ENABLED |
|
ENABLED |
DISABLED |
Partial refresh (Learning only) |
DISABLED in BizX ENABLED in Learning |
|
DISABLED |
ENABLED |
Partial refresh (Learning only) |
ENABLED in BizX |
|
DISABLED |
DISABLED |
Partial refresh (Learning only) |
DISABLED |
|
ENABLED |
ENABLED |
Partial refresh (Learning only) |
ENABLED |
2. Data Integrity Challenges
Refreshing only BizX or Learning of an integrated pair causes discrepancies between the two systems with the Learning data. SAP cannot fix these issues individually via script and it will be required to perform a full system refresh (BizX + Learning) to address them. Here are some examples of data/features which may be impacted and how to currently try to mitigate them:
- User data mismatches: Learning may retain BizX user data that does not exist in BizX, preventing proper purging via Master Data Purge or Native User Purge. While this is currently an issue, enhancements are underway to address this.
- Person_guid mismatches: These can impact Learning access, Learning activity status in development goals, competency ratings, and OMP recommendations. While mitigated by running an SAP SuccessFactors User Connector run, inconsistencies may still occur.
- BizX Home Page Learning card discrepancies: These are addressed by raising a ticket to the Learning Technical Support team, so they can run a backend card refresh job.
- Regarding the New Learning Homepage, Custom cards and Banners may not reflect correctly.
- SAC access and data issues, which could also impact BDC.
- Skills and attributes data from Talent Intelligence Hub may not align with Learning post-refresh.
IMPORTANT:
When submitting partial instance refreshes, please be aware of the following:
- SAP will not provide troubleshooting or corrective scripts for issues arising from partial refreshes. To resolve them, it is required to perform a full system refresh (BizX + Learning) from the same source.
See Also
Keywords
sf, sfsf, lms, hcm, partial, refresh, learning, talent, story, report, sac, tih, bizx, platform, issue, data, mismatch, card, home, page, instant, module, growth, portfolio, instance, suite, irt, manual , KBA , LOD-SF-LMS-REF , LMS Manual Refresh , LOD-SF-LMS-IRT , Instance Refresh Tool , LOD-SF-LMS , Learning Management System , Problem
SAP Knowledge Base Article - Public