SAP SF Employee Central Integration with Cloud for Customer via HCI
With 1811 release of SAP Hybris Cloud for Customer now there is a new way of replicating Employees from SAP SuccessFactors Employee Central to SAP Hybris Cloud for Customer (C4C). Until the 1805 release point-to-point (P2P) and intermediate staging area-based replication was supported in SAP Hybris Cloud for Customer for replication employees from SAP SuccessFactors Employee Central (EC). But with 1811 release SAP offer direct replication to people work-centre via SAP HANA Cloud Integration (HCI) and SuccessFactors Integration Centre. This blog mainly focus on HCI integration.
In the HCI new package was introduced “SAP Cloud for Customer Integration with SAP SuccessFactors Employee Central”. This package consists of 2 integration flow artifacts.
- Replicate Employee from SAP SuccessFactors Employee Central
- Replicate Employee manually from SAP SuccessFactors Employee Central
Let’s examine the content of the HCI package, SAP Cloud for Customer Integration and SAP SuccessFactors Employee Centre.
Make sure the required scoping and questions in C4C Business Configuration is active. The HCI does the handshake with C4C basis communication arrangement.
NOTE: With b1811 communication arrangement service should be “Replicate Employee from SAP SuccessFactors Employee Central”.
Take a note of the My System ID under My Communication Data, we would need this later when we configure the HCI iFlows.
Prerequisite before configuring the the iFlows:-
Under “Security Material” tile deploy the user credential (having all the access rights) for SAP Hybris and Cloud for Customer and SAP SuccessFactors Employee Central.
Replicate Employee from SAP SuccessFactors Employee Central iFlow requires the following configuration:
NOTE: Copy the package “SAP Cloud for Customer Integration with SAP SuccessFactors Employee Central” from Discover. Then the above package will be copied in Design.
Open the artifacts “Replicate Employee from SAP SuccessFactors Employee Central” under package “SAP Cloud for Customer Integration with SAP SuccessFactors Employee Central”
Step 1 : Configure the timer event . This will decide how often the Integration Flow will run to fetch the data from SAP SuccessFactors Employee Central system.
Step 2 : Configure the Receiver system
- Using the Receiver drop down select the receiver channel for Cloud for Customer (C4C).
- In case of authentication is Basic select the corresponding authentication using the drop down and provide the C4C credential name.
- Using the Receiver drop down Select the receiver channel for Employee Central (EC_CE_API_QUERY)
SAP recommend for large employee load to set the Parameters as maxRows to 500 and Page Size to 800.
Note : Do not change/remove the agent=C4CIntHCI from the Parameters.
Step 3 : Configure the external parameters as explained below
Receiver_ID: C4C Receiver Communication system ID (My System ID as explained earlier).
Sender_ID: C4C Sender Communication system ID.
Enable_Logging: If you set this field to true then in the MPL, you can see the employee records pulled from EC inform of attachment. It is only useful for debugging and in production we advise to set it to false (default value).
Save and deploy your iFlow.
There is a second iFlow “Replicate Employee manually from SAP SuccessFactors Employee Central”, which is optional and only required in case you need to pull employee data for individual employees. The configuration is identical to the integration Flow Replicate Employee from SAP SuccessFactors Employee Central, except in the configuration you need to provide a comma-separated list of employees as shown below. Please note you need to surround each id with single quotes ‘’. Example: ‘77889,’88552′,’5000′ and for a single employee ‘88552’.
NOTE : In case of “Replicate Employee from SAP SuccessFactors Employee Central”, if all the users are not being pulled in SAP Hybris C4C and there is no error then under Operation view delete the GV_LAST_MODIFIED_DATE entry. This will automatically make the iFlow run in initial load mode in the next pulling cycle i.e. all employees will be pulled from EC again and replicated to C4C.
In the next blog will update on ECSC employee replication – mapping custom field in HCI from EC to C4C.
Curious to know common use cases for this feature.
Hi Joseph Smith,
Greetings for the day!!
1) Replicating Employees from SAP SuccessFactors Employee Central to SAP Hybris Cloud for customer integration is required.
2) To use Ask HR feature employee needs to be replicated in SAP Hybris C4C. Otherwise, there will be an error “Your user profile is not been configured, please contact with your system administrator”.
3) An employee can create tickets and also SAP JAM can be integrated to use knowledge base for the commonly asked question.
I hope this answers your question. If anything specific is needed please post valuable comments.
Sushil H Maurya
For us the contact phone number is not replicating but email is replicating. Any clue what could be wrong. Its coming as in message monitoring:
Hi Amrit Bansal,
Hello. Would you know of the limitations of this interface? It seems that Organizational related data of the employee (such as Department) are not replicated. Any supporting documentation from SAP on this?
What we have been told is this does not replicate. there was an idea posted by Christel Roujolle
Hi Elia & Petrou,
Issue: Job related data doesn't replicate
Cause: In SAP SuccessFactors Employee Central Job related data is effective dated and in C4C its non-effective dated.
If EC new FO or mdf data is created then same needs to be created in C4C otherwise data will not flow.
I hope this helps.
Thank you. What is "EC", "FO" and "mdf data"?
All the terminologies used was from SAP SuccessFactors i.e Location, Department, Division etc is called FO (Foundation Objects) and Sub-Department, Sub-Division etc is called MDF (Meta data framework).
As we know all this are linked to Employees Job Information. So whenever your SAP SuccessFactors FO or MDF data gets updated then we need to update the C4C custom fields otherwise data will not flow.
In my coming blog will give steps like how to create custom fields in C4C then mapping in CPI with SF Job Info fields also there is a brain teaser as we know in C4C custom field is non-effective dated and in EC job information its effective dated so how to manage this scenario.
Thank you so much! Looking forward to your next blog.
It's really a wonderful blog. Shall I know when are you publishing next blog as you mentioned "In the next blog will update on ECSC employee replication – mapping custom field in HCI from EC to C4C"
For custom field relication pls check https://blogs.sap.com/2017/10/12/employee-central-integration-with-cloud-for-customer-via-hci-part-iii/
Thanks for sharing the link but the issue with that blog is mapping in done on eclipse tool and C4C custom field is non-effective dated and in EC job information is effective dated so how to manage this scenario is missing in that blog.
Blog is coming soon!!
Due to pandemic was not available, now I have started again to release the edition of my blogs.
Will soon publish it.
Please feel free to comment.
Keep Learning keep sharing!!
Thanks for the steps here. As an mandatory step do we need to upload any code list mapping into C4C before we actually run iFlow ? we are seeing some errors and not sure how to upload code list mapping in C4C as we do not have any sample template for this scenario to download. we are able to fetch the employee records from SF using the iFlow but during unable to post it to C4C.
Can you pls guide us here ?