Symptom
The integration between the PeopleDoc HR Service Delivery platform within SAP SuccessFactors is enabled by BTP Applicaiton - EDF Connector.
The integration tool EDF Connector needs to do a match between a field from onboarding - dcXrefID and the kmsUserId, and the response is empty meaning that there is no dcXrefID equals to kmsUserId.
There are attachments for those candidates on Onboarding Document center/Contact center, but they're not getting synchronized to PeopleDoc.
Environment
SAP SuccessFactors Onboarding 1.0
Reproducing the Issue
HR attach documents on Onboarding Document center to a candidate. Once employee is Hired, those attachments should be loaded automatically into employee PeopleDoc folder via integration tool EDF Connector.
Process on the EDF Connector is the following:
- First, an API call is made to get the candidate kmsUserId, which can be validated in Manage data > OnboardingCandidateInfo. Canidate profile should be linked with new hired employee profile in SuccessFactors.
- Then, the system proceed to do the authentication using the onboarding credentials with response "status: ok", which means connection is working well.
- But then, the EDF Connector needs to do a match between a field from onboarding dcXrefID and the kmsUserId, yet the response is empty, which means there is no dcXrefID equals to candidate's kmsUserId.
Cause
Known defect.
Resolution
- This issue will be corrected in the 2H 2025 (b2511) Release
- Release dates can be found on SAP SuccessFactors Product Release & Road Map Information
[Workaround]
- Go to Super Admin (ONB 1.0 backend) > Account Options
- Search "DocCenter.UseOptimizedDownload"
- Update the value to "false"
Keywords
SAP, SuccessFactors, Onboarding 1.0, defect, integration, attachment, PeopleDoc HR Service Delivery platform, BTP Application, EDF Connector, synchronization, kmsUserId, UseOptimizedDownload, ONB-35596 , KBA , LOD-SF-OBD-INT , Integrations with Onboarding , Problem