2907294 - BIB:Changing termination date to the future creates redundant splits in IT0001 for a while

• You are running ECPAO_EE_ORG_REPL_QUERY (Create and Execute Employee Master Data and Org. Assignment Query)
• An employee is terminated in EC e.g. 15.03.2020
• Employee replication is done, afterwards Org. Asisgnmnents are replicated too
• Then, termination date is moved to the future in EC e.g. from 15.03.2020 to 31.03.2020
• Employee replication is done, afterwards Org. Asisgnmnents are replicated too
• If you check now IT0001, there is an extra split in IT0001: 2 adjacent I0001 records contain the same information:
• <Date1> - 14.03.2020 99999999
• 15.03.2020 - 31.03.2020 99999999

• SAP SuccessFactors Employee Central Integration to SAP Business Suite
• Replicate Organizational Assignments from EC to ERP Org. Mgmt

• Infotype 0001 is filled from two sources, ie from employee replication and org replication. So we are not able to avoid some extra splits at some point of employee replication. For example, first employee replication runs and update IT0001 fields, later org replication updates org specific fields in infotype 0001. At this point you will see some extra splits in infotype 0001 and but data will be same. 

• Next time when employee replication runs, it merges some of this splits in IT0001 as the data is same. Thus we are avoiding some extra artificial splits. This wont have any retro issues as the data is same and we are avoiding some unnecessary splits. This whole process has been done for better overall performance. So as per the process first employee replication triggers and then org replication runs to update org specific IT001 fields. So the second time employee replication trigger will take care of the extra splits in IT0001.
• <Date1> - 31.03.2020 99999999

SFIOM_VIEW_REQUESTS , KBA , LOD-EC-INT-ORG , Org Integration EC to ERP On Premise , LOD-EC-INT-EE , Employee Integration EC to ERP On Premise , How To