EC – HCM Replication, FTSD, to get better recommendation (to get latest SF Employee central Data)

[Aji_Kottayil]

Hi ,

EC – HCM Replication, FTSD, to get better recommendation

EC to SAP HCM (S4) Data replication employee and ORG objects – FTSD date

• EC live system from Mar 2020
• HCM fresh system, no emp data
• HCM using only for employee/PERNR dependency on other on premise modules (HR mini master) FI/MM/PS etc..

Question – Best practice to replicate employee effective from latest record to avoid any errors due to inactive objects, inactive employees etc… in EC

• No Past date replication
• Go-live on Jan 2022
• NO Payroll in HCM
• No HR transactions to be performed in HCM
• Only dependency is employee date / Position data for other modules WFs

What will be the best FTSD date to set up and its not only FTSD we need to map all EC events to a cutover event

Please share the best expertise, best practices for this approach

thanks

[Aji_Kottayil]

++

This will be help to have a cutover window in EC & HCM

Eg: Cutover event (both EC/HCM) = FTSD= Dec 1st , not HCm query should not go back and pick old event records from EC ..

Please share your thoughts , better approaches .

Note in our case EC is Live instance and HCM is brand new ..!!

[Aji_Kottayil]

Thank you Siddharth,

Appreciate your reply ..

For cutover we are planning like this,

Create EC Event reason "Cutover event reason" map to HCM Action reason "Cutover conversion hire" .

[siddharthrajora]

if the go live is Jan 2022, This should be your FTSD, this would be recommended. otherwise, you can move the FTSD after replicating data from 2020 to 2022 etc