This Article/kbase is to explain and provide more info on when and why to use [code] attribute that can be manually used in the mapping xml between EC and Onboarding or EC and Recruiting(RCM).
Below are some examples of symptoms that may happen when not using the [code] attribute in mapping xml:
- No value is being mapped for specific field for candidate in Manage Pending Hires (MPH)
- incorrect value is being mapped for specific field for candidate in MPH
- Slow performance loading candidates section (like personal info or job info) when hiring candidate.
- SAP Successfactors Employee Central
- Suite Integration
With [code] option in the XML, I mean to describe that it is possible to manually update the mapping xml by adding the [code] in the refid of the fields being mapped.
Below are 2 examples of the mapping difference using the company field in job info:
Default mapping is: <target country-code="" variant="" refid="jobInfo.company"/>
Optional mapping using [code] is: <target country-code="" variant="" refid="jobInfo.[code].company"/>
What are the benefits and potential problems/limitations of using using [code] attribute vs not using it (default):
- Benefit of not using [code] attribute - (Example: refid="jobInfo.company")
- Can be set easily within UI (this only applies to onboarding field mapping tool).
- The ability sending full label(code) value (as example value can be send as SAP(001). In this example "SAP" is name/label and "001" is the code/ID)
- Problems/limitation of not using [code] attribute - (Example: refid="jobInfo.company")
- Due to the mapping logic of sending label/name and ID it is possible that wrong value is populate if similar names values exist in instance (Example: value "Monthly" is similar as "Bi-Monthly")
- It is also possible that nothing is populated as value for the mapped field as the system mapping logic is not finding exact match.
- Without the [code] attribute the search for value would be done on codes/id's and labels, which can be taxing if you have large amounts of data. So performance may be impacted.
- Benefit of using [code] attribute - (Example: refid="jobInfo.[code].company")
- Using this attribute forces system to just look at the ID of object (It does not care or will look at labels/names). ID's are always unique and therefore no chance of getting wrong values and less chance of blank values due to no matches found.
- Performance will be better as the system only has to look at codes/ids of object and not Id's and labels etc. Faster returns due to lookup of smaller subset of data.
- Problems/limitation of using [code] attribute - (Example: refid="jobInfo.[code].company")
- You will have to do changes directly in the mapping xml as this can not be done using the UI tool (This again only affects onboarding Field mapping tool).
- You have to make sure you only send the ID/code of the field/object. So do not send the full name/label of the object. (Using same example for company object "SAP(001)", you would just have to send "001")
onboarding, EC, RCM code, id, blank, wrong value, mapping, xml, code attribute explained, code map,map code, map code explanation, rcm mapping, onboarding mapping, , KBA , LOD-SF-EC-INT , Manage Pending Hires (Integration RCM/ ONB/ OBX + UI) , LOD-SF-RCM , Recruiting Management , LOD-SF-OBD , Onboarding , How To