Employee Replication filtering from ECC HR Master to C4C

[Siraj_Saibudeen]

Dear Experts,

I would like to know how to stop all the employees created in ECC HR Master Data from replicating to C4C.

If there are 400 employees for a specific country roll-out and only 100 employees really need C4C application access, then I would like to replicate only 100 employees to C4C. This is really important and critical with the user licenses limit and it has direct impact on cost of these licenses.

I know in 1811 integration content they are introducing an inactive flag for the employees replicated to C4C. But even with this new feature, the employees are still replicated to C4C.

Is there a way to really stop all employees from ECC replicating to C4C. I did check the Idoc filtering but with the HR Master infotypes it works differently. If anyone has implemented this please do share your inputs.

Thanks,

Siraj

[Siraj_Saibudeen]

Dear C4C Experts & SAP Colleagues,

Anyone with any kind of help or any work arounds to solve this issue please!!

Would like to get the feedback from SAP colleagues here - any help is highly appreicated.

Thanks,

Siraj

[Siraj_Saibudeen]

Hi Everyone,

We did not quite fix the complete problem, but we managed to stop the unwanted changes in HR Master Data replicating to C4C all the time.

The IDoc Distribution Model (BD64) for the message type HRMD_A_CFS works a little different compared to other business objects. Adding the infotype in the idoc filtering not only restricts sending that specific infotype to C4C, but also sending only the changes made to that specifc infotype.

We added the infortypes (0000,0002 & 0105) in BD64 - The impact of this is that the changes made only to this infotype are registered in the change pointer tables. These changes are then subsequently replicated to C4C based on the scheduled change pointer jobs.With this idoc filtering settings, we were able to manage most of our issues. The changes to other infotypes were never sent to C4C- and it did not unlock the locked users in C4C.

Regards,

Siraj