Skip to end of metadata
Go to start of metadata

Purpose

This Wiki is to assist in guiding and providing answers related to issues that may arise when dealing with Employee Central integration with Onboarding and/or Recruiting.

The idea is that this wiki will give you additional insight into the integration and help you find guides, kbases or known issues that you may need more info on.

Please do keep in mind that this wiki is always expanding and may have info/links or references missing that are available directly by going to the help.sap.com portal or directly to the knowledge base system.

Some data in this Wiki is indeed duplicate or referenced multiple times. This is because the doc/info or article may apply to multiple scenarios (Or some may apply to both recruiting and onboarding for example) 

Index

Quick Jump links to get to the particular Integration section you need:

Please select the Integration you need help on:

Main Recruiting Section

       - RCM Mapping 

Main Onboarding Section

       - ONB Mapping

       - ONB. Pre-Day 1

Known error search

 

Recruiting

Here you will find various topic areas related to recruiting integration with EC. First part will have general info, documentation or kbases that will assist with this integration, second part will have info split on what specific kind of candidate you are hiring within the Manage Pending Hires" tool (new hire, rehire or internal hire) and last part has info specifically related to mapping between recruiting and EC.

General help links:

 

Please check section based on what kind of hiring you doing:

New Hire

This section talks about New hires coming from Recruiting.

The main difference in regards of the various kind of hiring that is available is in regards of field overwrite.

Here is the order of value/data that can be within a field when doing New Hire:

  1. Value coming from onboarding
  2. Value overwritten by oninit rule
  3. Value overwritten by propagation XML
  4. value overwritten by onChange rule
Kbases:


ReHire

This section talks about Rehires coming from Recruiting.

The main difference in regards of the various kind of hiring that is available is in regards of field overwrite.

Here is the order of value/data that can be within a field when doing ReHire:

  1. Value the field previously had coming from database
  2. Value coming from onboarding
  3. Value overwritten by oninit rule
  4. Value overwritten by propagation XML
  5. value overwritten by onChange rule

Note that the value below the field is always the value coming from recruiting.

Example image below:


Kbases:

Internal Hire

This section talks about Internal hires coming from Recruiting.

The main difference in regards of the various kind of hiring that is available is in regards of field overwrite.

Here is the order of value/data that can be within a field when doing Internal Hire:

  1. Value the field previously had coming from database
  2. Value coming from onboarding
  3. Value overwritten by oninit rule
  4. Value overwritten by propagation XML
  5. value overwritten by onChange rule

Note that the first value below the field when PP3 is enabled is always the value is always the previously stored database value and the second field below is coming from recruiting 

If you still are using the old UI (not PP3); You will see the Previous database value always behind the field and the recruiting value always below field.

Example image below:

Kbases:

Mapping RCM

This section has various info, documentation links or Knowledge base articles related to mapping between recruiting and EC.

 

 

Onboarding

Here you will find various topic areas related to Onboarding integration with EC. First part will have general info, documentation or kbases that will assist with this integration, second part will have info split on what specific kind of candidate you are hiring within the Manage Pending Hires" tool (new hire, rehire or internal hire), Third part has info specifically related to mapping between Onboarding and EC and last part will have info related to the Pre-day 1 functionality that is available with Onboarding.

General help links:

Please check section based on what kind of hiring you doing:

New Hire

This section talks about New hires coming from Recruiting.

The main difference in regards of the various kind of hiring that is available is in regards of field overwrite.

Here is the order of value/data that can be within a field when doing New Hire:

  1. Value coming from onboarding
  2. Value overwritten by oninit rule
  3. Value overwritten by propagation XML
  4. value overwritten by onChange rule
Kbases:

Field values not updated when trying to hire onboarding candidate in "manage pending hires" when pre-day 1 feature is enabled.

ReHire

This section talks about Rehires coming from Recruiting.

The main difference in regards of the various kind of hiring that is available is in regards of field overwrite.

Here is the order of value/data that can be within a field when doing ReHire:

  1. Value the field previously had coming from database
  2. Value coming from onboarding
  3. Value overwritten by oninit rule
  4. Value overwritten by propagation XML
  5. value overwritten by onChange rule

Note that the value below the field is always the value coming from onboarding.

Example image below:

 

Kbases:

Internal Hire

This section talks about Internal hires coming from Recruiting.

The main difference in regards of the various kind of hiring that is available is in regards of field overwrite.

Here is the order of value/data that can be within a field when doing Internal Hire:

  1. Value the field previously had coming from database
  2. Value coming from onboarding
  3. Value overwritten by oninit rule
  4. Value overwritten by propagation XML
  5. value overwritten by onChange rule

Note that the first value below the field when PP3 is enabled is always the value is always the previously stored database value and the second field below is coming from onboarding.

If you still are using the old UI (not PP3); You will see the Previous database value always behind the field and the onboarding value always below field

Example image below:


Kbases:

Pre-day 1 Functionality

Pre-day 1 functionality is an onboarding specific funtionality that was introduced not so long ago. This feature will allow you to create a temporary ID for your candidate, so that they can get into the successfactors suite to do certain pre-onboarding task/fill in forms etc. The reason why this feature/topic is mentioned in this integration wiki is that it will affect userid/person-id.external generation when hiring candidates from manage pending hires.

Here is a direct link to pre-day 1 section in the Onboarding implementation guide

Below are knowledge base articles related specifically to Pre-day 1 functionality or issues:

 

  • No labels

1 Comment

  1. Former Member

    Dear Duncan,

    Very detailed document and informative. Thank you for sharing the same.

    Regards,

    Hardik