SAP Knowledge Base Article - Public

2555906 - Position Number Mapping Between Onboarding 1.0 and EC

Symptom

How can you map the Position number (Position Code) from Onboarding 1.0 to Employee Central?

 Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental

Environment

  • SAP SuccessFactors Onboarding - 1.0
  • SAP SuccessFactors Employee Central

Cause

  • The Mapping configuration for the PositionCode it's incorrect as the following example:

PositionIncoreectformat.JPG

  • The Position number will not map successfully unless it is maintained correctly in the Field Mapping Tool for Onboarding > Employee Central Integrations

Resolution

  1. Correct Mapping example:
    PositionCorrectFormat.JPG
  2. Position Number and Organizational Units should be mapped always as mentioned in screenshot. Only one-level mappings are allowed.
  3. Please also note it is not possible to add the variant 'code' to the mapping via the Field Mapping Tool in the UI, this is a limitation. This change must be made via XML, in Provisioning with the Onboarding Transformation Template.
  4. The XML code should be as follows: <target refid="jobInfo.[code].position" variant="" country-code=""/>

Please Note:

There are three ways to map over the position value, two of which use variants:

  • jobInfo.position
  • jobInfo.[code].position
  • jobInfo.[name].position

The jobInfo.[code].position mapping, is the recommended mapping, as code is a business key for positions.

All the mapping types use exact matches. This means the value being passed over from ONB must be an exact match for the value in EC of the corresponding variant.

For example, in case a position in EC has the Name: POS_1234 and the Code: POS_1234, the following would occur if an exact match is not being sent over:

  1. If ONB to EC mapping key is like jobInfo.position, the system will use the ONB passed value '1234' to do an exact search of position code and name fields. So, POS_1234 could not be matched.
  2. If ONB to EC mapping key is like jobInfo.[code].position, the system will use the ONB passed value '1234' to do exact search of position code field. So, POS_1234 could not be matched.
  3. If ONB to EC mapping key is like jobInfo.[name].position, the system will use the ONB passed value '1234' to do exact search of position name field. So, POS_1234 could not be matched.

Keywords

Position, Position Number, Position Code, Mapping, Variant, Field Mapping, jobinfo.positioncode, PositionCode, Onboarding Transformation Template, code, [code], Onboarding, obd, EC, Employee Central, Job Information, jobInfo , KBA , LOD-SF-OBD-INT , Integrations with Onboarding , LOD-SF-EC-INT , Manage Pending Hires (Integration RCM/ ONB/ OBX + UI) , How To

Product

SAP SuccessFactors Employee Central all versions ; SAP SuccessFactors Onboarding all versions