Symptom
- The requirement is to use BOOMI API to create an external HRIS external candidate record, which can obtain both Recruitment and Onboarding data of an external new hire
- If we have the recruitment applicant ID (which is a unique identifier) how can that be mapped to onboarding field/portlet to be used as a connector between Recruiting and Onboarding since it is not available int he Recruit-To-Hire functionality or how can we use the Onboarding ID to connect back to Recruitment application information so we can pull the offer information that is being stored on the recruitment application template
- The challenge is to find a unique identifier to connect an applicant's recruitment information and the same candidate's onboarding record. Currently, only the first name and last name are being used, which may not always be unique
- And the goal is for ONE BOOMI API to capture the offer information on the recruitment applicant area and the onboarding information of that same candidate that is stored on multiple Onboarding MDF tables and EC portlets - but yet there does not seem to be a unique identifier that can connect both areas together; other then first name and last name, but that is not always a unique identifying combination
Read more...
Environment
SAP SuccessFactors Onboarding
Product
SAP SuccessFactors Onboarding all versions
Keywords
obx, connector, onboarding, boomi, rcm, unique identifier, api, integration, external hris, candidate , KBA , LOD-SF-OBX-ATS , ATS Integration , LOD-SF-INT-BPI , Dell & Boomi Infrastructure , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.