2716723 - Instance Refresh error "TENANTREFRESH_VALIDATION_FAILED_FOR_USER_SYNC_DATA_JOB"

• Instance Refresh has "Validation Failed" status.
• How to configure the Employee Export Job for Bizx LMS sync.  
• TENANTREFRESH_VALIDATION_FAILED_FOR_USER_SYNC_DATA_JOB Refresh error when using the Instance Refresh Tool.
• Instance refresh error message is displayed: "Employees Export job is not configured in the xxxxxxxx target instance. Ensure that you’ve created a recurring or one-time future dated Employees Export job in the target instance. Please contact your implementation partner or Product Support to create a new job in Provisioning."

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

SAP SuccessFactors HCM Suite

This error code indicates that the ‘Enable Instance Refresh Tool for SAP SuccessFactors Learning’ is enabled in Provisioning for either or both source and target, without meeting the following requirements:

• The Employee Export Job does not exist or was not submitted in the source or target instance
• The 'Required for SuccessFactors Learning Sync' parameter is not enabled for the Employee Export Job
• The job owner set for the Employee Export Job does not exist in the target instance

To resolve this issue, check the following:

1. Check whether both "Enable SuccessFactors Learning integration" & "Enable Instance Refresh Tool for SAP SuccessFactors Learning" feature checkbox are checked in both source and target provisioning. If any of these features are unchecked, User Sync Job Validation step would be skipped.
2. If above features are checked, validate the LMS integration through SuccessFactors Learning Integration URL & SuccessFactors Learning Integration API URL. Ideally. if the BIZX tenant is properly sealed with LMS tenant, then these two URLs should not be empty. If any of the URLs are empty, User Sync Validation Error is thrown.
3. If the above integration is correct, check User Sync job exists in Target Provisioning. Below are the conditions to be met for the User Sync job, otherwise User Sync Validation Error will be thrown:

• The Job should be one time Future Dated (End date should be greater than Refresh Schedule date) / Recurring (No End date) scheduled in Target Instance. 
• Make sure to configure User Sync Job / Employee Export job properly with all the Required job parameters for BIZX-LMS User Sync. The Job Parameter "Required for SuccessFactors Learning  sync and SAP Jam manual sync" needs to be checked
• Job should be in SUBMITTED Status.

When you configure it from SAP SuccessFactors provisioning for User Connector - SF, you should have settings similar to the screenshot below:

 Note : 

• Provisioning access is not allowed for customers. Please contact your implementation partner to create a new job in Provisioning. 
• As a customer, you can create, manage, and monitor employee export/import jobs directly within Admin Center. Please see KBA 2087542 for the steps on creation the Employee Export job.
• Avoid empty spaces when naming the File and the folders for the File Path, otherwise the job will fail.

FREQUENTLY ASKED QUESTIONS (FAQ):

1. Q: Will the User ID field in the LMS be changed to this new value (PERSON_GUID) or will it remain as it is (USER ID) and this Person_Guid will be a new/different field?
   A: Userid (stud_id in the LMS) will remain as is. There is a new PERSON_GUID field created in the LMS as well that will map to the PERSON_GUID field in BizX Platform. PERSON_GUID is already available for all customers since b1805 release. [Reference: KBA 2390723 - User ID, External ID and PERSON_GUID definition]
2. Q: If it is a new/different field is there a reason to make it visible in the UI (i.e. will support require this ID to troubleshoot, etc.) 
   A: No, there isn’t. It’s an internal field, same way it is for Platform. From the LMS side, you may view the values by generating a report. To do this, please open a support case to LOD-SF-LMS component.
3. Q: If SAP does the initial load of users to this value, what does that mean for ongoing support?
   A: After initial load, the Person_Guid and Person_Id_External will be synced to LMS through Employee Export going forward.
4. Q: As part of the initial load, "all existing users with this data" will be verified and updated?
   A: Person_guid is updated in the LMS based on matching users_sys_id and stud_id. So for example, if the BizX id is SFADMIN and there is a matching student id SFADMIN in the LMS, the connector will update the person_guid accordingly so that both BizX and the LMS will reflect the same value.
5. Q: Is this for Active Users only or will the entire population be updated (active and inactive)?
   A: This is for entire population.
6. Q: Who is doing the user mapping between BizX and LMS – SF ?
   A: The user is synced from BizX to LMS through the Employee Export job / the SF Connector.
7. Q: Is there any impact with using PERSON_GUID to connectors?
   A: None. We are simply enabling the switch to sync the values for this field from BizX to LMS.

• KBA 2375919 - Scheduled jobs in provisioning SF User Connector is dependant on to sync BizX data
• KBA 2318341 - LMS Connectors Knowledge Support and Tips
• KBA 2087542 - Scheduling Employee Imports / Export Job
• KBA 2390723 - User ID, External ID and PERSON_GUID definition

User Sync from BizX to LMS, User Connector, Employee Export, Delta Export, sf, lms, plt, learning, IRT, instance refresh tool, validation failed, SuccessFactors, Platform, TENANTREFRESH_VALIDATION_FAILED_FOR_USER_SYNC_DATA_JOB , KBA , LOD-SF-PLT-IRT , Instance Refresh Tool , LOD-SF-PLT-JOBS , Scheduled Jobs , How To