HCI Integration - Employee bulk load from SAP SFEC to SAP C4C

[former_member216636]

Hi Everyone,

We are working on SFEC integration with SAP C4C replicating bulk employees using SAP HCI as middleware.Since most of the clients are asking for setting up Ticket Routing rules using “Company” as parameter.

To meet this requirement we added an extension field(Legal Entity) to Biographical data in C4C (Which is under PersonalDetails node in Webservice), as sugested by SAP due to extension limitations in C4C service. We have done the mapping of new C4C Extension Field (EmployeeCompleteMasterDataReplicateRequest/CompleteEmployeeMasterData/PersonalDetails/ns10:LegalEntity(0..1)) with CompoundEmployee/person/employment_information/job_information/company (0..n) value of SuccessFactors response message.

Since C4C extension field “LegalEntity” is of cardinality (0..1) and mapped to “Company” field under job_information which is having 0..n cardinality we are getting issues while performing bulk loading.

I have mapped it as below and changed the context of source (company) to “compound Employee as shown in the figure, however this only works when replicating a single employee. While performing bulk load of employees then the mapping works intermittently (if Employee contains only 1 Record of Person details record it will work).

We expect the first record under job_information --> company of SF response should be added to PersonalDetails --> ns10:LegalEntity(0..1). But when an employee in bulk load having multiple records of personal_information for an employee in SF response this data mapping is getting an issue due to cardinality mismatch. It will be really helpful if any one can throw some pointers or idea's.

Thanks,

Rajesh N

[former_member216636 · Accepted solution]

Hi - We have implemented script and resolved the issue.

Thanks,

Rajesh N

[vikas_agarwal]

Hi Rajesh,

Sometime back i made similar change in my project. Please find the similar type of mapping requirement solution:

Here I am sending cost_center from Job_information to Data in PersonalDetails fields. I have kept the context of cost_center at CompoundEmployee only.

Regards,

Vikas