Symptom
In case forward propagation is triggered, when a position record is inserted or corrected, the start date of all the change events that are generated (i.e., the event for the change done by the user and the events for the records changed by the forward propagation) will contain the effective start date of the most current position record,which is changed by forward propagation.
Environment
SAP SuccessFactors HXM Suite
Resolution
Event Generation with Position Management and forward propagation
Position Management enables you to generate events whenever you create, or update a given position. These events can be subscribed by integrated applications.
The event contains the following fields as part of the business key:
- Start date
- External code
Limitation: In case forward propagation is triggered, when a position record is inserted or corrected, the start date of all the change events that are generated (i.e., the event for the change done by the user and the events for the records changed by the forward propagation) will contain the effective start date of the most current position record,which is changed by forward propagation.
Example:
Existing records on Position A
01/01/2020 – 31/12/2021
· Position Title: Developer
· Location: New York
01/01/2022 – 31/12/9999
· Position Title: Developer (no change)
· Location: Walldorf
Now the user inserts a record on the position, changing the position title as of 01/01/2021:
01/01/2021
· Position Title: Development Expert
The record is inserted on 01/01/2021 and the changed position title is forward propagated into the existing future record on the position (with effective date 01/01/2022).
Resulting records on the position:
01/01/2020 – 31/12/2020
· Position Title: Developer
· Location: New York
01/01/2021 – 31/12/2021
· Position Title: Development Expert
· Location New York
01/01/2022 – 31/12/9999
· Position Title: Development Expert (changed due to forward propagation)
· Location: Walldorf
This means, that one record was inserted (as of 01/01/2021) and one record (as of 01/01/2022) was changed due to forward propagation. As a result, two events are raised. Both events will have 01/01/2022 as the effective start date.
This is a known limitation of the system only in cases in which forward propagation is triggered.
Please note this limitation applies only if you are using the start date from the event to update effective dated objects in target integrations.We recommend to not use the start date from the event. For non-effective dated objects this limitation does not have an impact.
If you would like to change or improve this system behavior, please submit an enhancement request to the product management team.
See Also
Keywords
Start date, Effective Start Date, External code, Position Management, Event Generation , KBA , LOD-SF-PLT-ISC , Intelligent Services , LOD-SF-EC-POS , Position Management , How To