SAP Knowledge Base Article - Public

2511104 - Position to Job Information Synchronization Rule, Field Mapping Order

Symptom

Does it matter in which order I set the "Then" conditions in a Position to Job Information Sync Rule.

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

Environment

Employee Central - Position Management

Cause

If you are using Object association, the field order is essential.

The order in which the fields are mapped, should depend on the structure of your object Associations.

Resolution

For example, if you have the following Structure in place:
1.jpg

Business Unit is the Parent of Department.
Department is the Parent of Division.

Then the fields should be mapped also in that order.

The below example is incorrect as the object association Structure is not respected.
This will lead to you Position to Job Information Sync Rule not working correctly and in some cases not at all:
2.jpg

The correct order based on this object association structure is as follows:
3.jpg

Keywords

Company, Legal Entity, association, child, parent, relationship, position to job info, sync, field order, mapping , KBA , LOD-SF-EC-POS , Position Management , Problem

Product

SAP SuccessFactors Employee Central all versions