3594029 - Daily or Full HRIS Sync job failure caused by Foundation Object Field Maximum Length

Daily or Full HRIS Sync job failure caused by Foundation Object Field Maximum Length 

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 HXM Suite 
• SAP Successfactors Employee Central

• Run Daily or Full HRIS Sync : 2512570 - Creating an HRIS Sync Job in SAP SuccessFactors Via Scheduled Job Manager or Provisioning
• Go to Test user Employee Profile or UDF file
• Check Foundation such as: Legal Entity, Company, Job Code or Job Classification, Division, Department, cost center
• Result: Old value still appearing or Blank value 

Also

• Run: 2766367 - Important Notes About Change Audit - Employee Profile
• Result: New value appeared in audit but didn't display in EP UI

Synced value exceeds the max length of target field 

1. Go to Manage data
2. Check foundation object or MDF
3. In this Example Select Division
4. Select Division
5. Check title max length : "Public Works Department, SAP , Employee Central Division and EC Terminate & EC Core Time off Department , New York, USA (10000520)"

Note: The sync process fails because of the following division which exceeds the maxlength of the data field at UDF  ,Max. 128) while the calculated string is 140 

• Foundation Object or Foundation MDF object Field name considers both the title and code into the byte count. The text will need to be reduced to 128 bytes or less before any changes can be saved.
• NOTE: Some languages have double byte characters e.g., Traditional Chinese, Simplified Chinese, Japanese, Korean.

Please update or reduce foundation object field : Name + Code to: 128 character View Guide: Job Information (hris-element-id: jobInfo)

In This Example:

The division with a shorter Name to make the Division Name + Division code to a string no longer than 128 then Run the full sync again? 

Step 1:  Export all user impacted by wrong job code

You must run a report and filter all user with impact job code :2317955 - Correct or Remove Job Information record via Import in Full Purge mode

1. Go to Analytic then Adhoc Report
2. Create new Report
3. Select sub domain: Person and Employment Export
4. In the column, select only the column Employee Job Infos
5. Filter Test user
6. Save
7. Back up your report into your Desktop (will be used as a Backup)

Step 2: Correct label Maximum length: Max. Length: 128

1. Go to Manage data
2. Select Foundation such as: legal entity. company, job code or job clarification ,Division, Department , cost center
3. Select code

Or 

1. Correct Via Import and Export Data : 2277155 - MDF - How to Export Data for MDF Objects?

Step 3: Insert new record or Update Job Information

• 2080801 - How to update Foundation Objects, and the respective Employee Data - Employee Central
• 2551350 - How to Update Generic Objects and the Respective Employee Data - Employee Central
• For Hris sync Gap: 2964383 - MDF Field label name Change Doesn't Sync to Employee Profile Header after HRIS Sync (real time or Incremental Sync job)

Step 4: Run full Hris Sync

• 2512570 - Creating an HRIS Sync Job in SAP SuccessFactors Via Scheduled Job Manager or Provisioning
• Full HRIS Sync job: 3044382 - User Based HRIS Sync 2080728 - Employee Central: What is HRIS Sync?
• 3210602 - Hourly Daily Hris Sync causing Importing employee data such us causing Job Information failure

FAQ - Additional Information

Q) Where can I get information on this from the Guide?

A) Guide: For any EC Standard field creation please refer to Guide: 

• Guide: Data Model Field Information for Employee Central - 
• Job Information (hris-element-id: jobInfo)
• For : Job Classification - job-code Max. Length: 128
• Field: employee-class //  Max. Length= 258
• Field: Department - division : Max. Length= 128

Q) Hris sync JOB best practice?

A) We recommend not to schedule delta Sync or Full Sync job on an hourly basis.

• 2512570 - Creating an HRIS Sync Job in SAP SuccessFactors Via Scheduled Job Manager or Provisioning 
• 2080728 - Employee Central: What is HRIS Sync?
•  3210602 - Hourly Daily Hris Sync causing Importing employee data such us causing Job Information failure

To sync data from Employee Central to the user data tables: Notes on Some Common Job Types

The maximum times that the job can run each day in the Admin Center.

• 3 times for a One-Time job
• 3 times for a Recurring job

For more information, each HRIS Sync Jobs.

• 3585819 - Job Information or termination Update failure caused by USERS_SYS_JOBCODE Maximum Length
• 2472648 - Using the Check Tool to Check a SuccessFactors Configuration
• 2172427 - HRIS Sync - Data Synchronization From EC to EP - Hard Coded Sync Mappings
• 2336779 - Invalid HRIS Sync Mapping Configuration " HRIS Sync Job Failure"
• 2964383 - MDF Field label name Change Doesn't Sync to Employee Profile Header after HRIS Sync (real time or Incremental Sync job)
• 2236017 - Mass Deletion of MDF Data via Import
• 2317955 - Correct or Remove Job Information record via Import in Full Purge mode
• 2080801 - How to update Foundation Objects, and the respective Employee Data - Employee Central
• 2551350 - How to Update Generic Objects and the Respective Employee Data - Employee Central
• 2964383 - MDF Field label name Change Doesn't Sync to Employee Profile Header after HRIS Sync (real time or Incremental Sync job)
• 2740031 - Label remains with old value on Employee Export after being changed on Manage Data.- Employee Central
• 2766367 - Important Notes About Change Audit - Employee Profile

Incident, INC12245559 hris sync, Full hris sync, The text will need to be reduced to 128 bytes or less before any changes can be saved, department, division, foundation object,STATUS_MARKED_ROLLBACK, USERS_SYS_, 128 character , manage data, Job Classification  , Job Code, terminate, max length , exerntalCode , Max. Length , Max Length , department , cost center , division , foundation object  , KBA , LOD-SF-EC-HRS , HRIS Sync , Problem