SAP Knowledge Base Article - Public

2812823 - Instance Refresh Tool - Status Information - Completed with warning - Full List

Symptom

Instance refresh completes successfully using the Instance Refresh tool however refresh status information shows "completed with warnings".

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

Environment

SAP SuccessFactors HCM Suite

Reproducing the Issue

  1. Go to Admin Center
  2. Go to Instance Refresh
  3. Status shows as "Completed with warning"

warnings.png

Cause

These warnings are Displayed when any of below warnings occur. The warnings do not effect the successful status completion of the refresh and can be resolved by following the steps outlined in 1-9 depending on which message you have encountered.

Resolution

List of Warnings:

  1. There are traces of audit logs in the target instance from the source instance after refresh is complete.

These logs might appear in your audit reports and the target instance will function as expected. Download the error log file and contact SAP Cloud Support with the log file under component LOD-SF-PLT-IRT 

  1. The User Sync process from HXM Suite to Learning failed. This might cause user data inconsistencies between HXM Suite and Learning. 
  • Please check Employee Export job for error code within provisioning. A common reason for this job to fail post refresh is that the job owner will get restored in the target instance post refresh which means if the job owner no longer exists in the Newly refreshed instance the job will fail with "Invalid job owner this is outlined on the KBA 2791468 - Instance Refresh Tool & FAQ Symptom
  • Another reason is that User Connector-SF in target LMS tenant was not enabled prior to Instance Refresh.  You can ignore the warning message and run User Connector-SF manually after the refresh. Next time if you want the users to be in sync right after the refresh, please have the User Connector - SF enabled prior to the refresh.
  1. The user export job cannot be found.
    1. The job is not existing in the target pre-refresh
    2. The job was not submitted
    3. The job owner set for the export job is not existing in the target instance
    4. The job exists on the target but the checkbox "Required for SuccessFactors Learning sync and SAP Jam manual sync" is not enabled. 
  • The resolution is to create a new Employee Export Job, and to this please engage partner or contact SAP Cloud Support under component LOD-SF-PLT-JOBS with the information described on KBA 2716723 
  • If you are not using Employee Export to sync your users from bizX to LMS, we expect that you create one also on the source system -> a valid BizX/LMS integration should always have an Export job configured in provisioning ✅ 
  1. Data anonymization is incomplete.

Some of the fields with personally identifiable information might exist in the target instance without being masked after the refresh completed. There is no action required here this is an informational message only. 

  1. Rebuilding of indexes which is required for efficient searches.  

This can slow down your search. Download the error log file and contact SAP Cloud Support with the log file under component LOD-SF-PLT-IRT

  1. E-mail masking failed.

Masking the internal users with provided input parameter are successful, while creating the refresh request fails. This failure can result in sending emails to real users with reference to test job executions. Download the error log file and contact SAP Cloud Support with the log file under component LOD-SF-PLT-IRT

  1. Data Replication Configuration” data was modified.  The value in “Replication Target System” field was replaced with a dummy value

You don’t have to report this information to SAP Cloud Support. To solve the issue, go to "Manage Data"-> "Data replication Configuration" and set the relevant value in “Replication Target System” field. For more information, see Knowledge Based Article KBA 2813109 in SAP for Me. If you have any further questions kindly contact SAP Support under component LOD-SF-INT-PAY.

  1. Payroll System Configuration data is modified.

Empty values were maintained in “Payroll System URL”, “Payroll System Client ID” and “SAP System Configuration” fields. You don’t have to report this information to SAP Cloud Support. To solve the issue, please go to "Manage Data"-> "Payroll System Configuration" and set the status field to “Active”. Afterwards, maintain the relevant value in “Payroll System URL”, “Payroll System Client ID” and “SAP System Configuration” fields. For more information, see Knowledge Based Article KBA 2813109 in SAP for Me. If you have any further questions kindly contact SAP Support under component LOD-SF-INT-PAY.

  1. Payroll System Assignment” data is modified. The value in “SAP System Configuration” field was replaced with a dummy value.

You don’t have to report this information to SAP Cloud Support. To solve the issue, go to "Manage Data"-> "Payroll System Assignment" and set the relevant value in “SAP System Configuration” field. For more information, see Knowledge Based Article KBA 2813109 in SAP for Me. If you have any further questions kindly contact SAP Support under component LOD-SF-INT-PAY.

   10. USER_MANAGEMENT_SCHEDULE_FIND_USER_SYNC_JOB_ERROR

  • Instance Refresh was completed with warning. Refresh logs shows Error Code :- USER_MANAGEMENT_SCHEDULE_FIND_USER_SYNC_JOB_ERROR , Error Message :- The user export job cannot be found. Please contact your implementation partner or SAP Cloud Support to create a new job in Provisioning.
  • The issue is that the User Sync job is missing or was not correclty configured in the target instance. To resolve this, the customer should engage an Implementation Partner or contact Product Support, who will create/edit the Employees Export job required for the user sync from BizX to LMS. See more information about it in the KBA 2716723.

   11. Latest homepage refresh has the following status: Failed.

You can still log into the refreshed target instance and proceed with your planned activities. Meanwhile, please contact Product Support to get this issue fixed. Download the error log file and contact SAP Cloud Support with the log file under component LOD-SF-PLT-IRT.

   12. The reset of avatar data on target instance have the following status: {0}. This activity is to avoid inconsistencies in the avatar data

This warning means that the Dynamic Teams avatar data might be broken on the target instance. But it does not constitute a failure of the refresh and can be safely ignored. The workaround is to reupload the avatar images for the dynamic teams on the target instance.

   13. Regenerating data for Enhanced To-Do Integration has the following status: Failed. If this activity fails, the integration to SAP Task Center doesn’t work until the error is resolved. Please contact Product Support.
          Regenerating data for Enhanced To-Do Integration has the following status: {0}. If this activity fails, the integration to SAP Task Center doesn’t work until the error is resolved. Please contact Product Support.

This warning can be solved by SOLR Indexing Rebuilld, if customer notice any issues after the rebuild. This action is performed in Provisioning, so customer should contact their Implementation Partner or Product Support. Next recommended action would be refreshing using IRT again.

  1. As Part of User Sync Job, Number of record with exception are : {#}, Total Number of Records Processed: {#} ,You can either ignore these failures or run a subsequent user synch process to try again.

This warning is stating how many records were processed and exceptions from the User Connector - SF. You can ignore this or have the connector process the file again either by an Employee Export job or Integration Center job. Any exception messages can be found in Learning Administration > System Administration > Connectors > User Connector - SF > View Results > View Details. The report that is created will have the details of the exceptions. Any changes to the system to correct the exceptions that are due to improper configurations should be worked with a certified Partner.

   15. System shows a warning message with 'DP_REFRESH_NOT_INVOKED' after IRT instance refresh

This is an issue with DP platform where IRT-DP hook was not invoked due to having warnings from User Sync.

For a complete list of status types in instance refresh see SAP Help Link Here

Keywords

Completed with Warnings, completed with warning, Instance refresh tool, instance refresh, indexes fail, masking, fails, audit logs, warning, warnings   , KBA , LOD-SF-PLT-IRT , Instance Refresh Tool , Problem

Product

SAP SuccessFactors HCM suite all versions