2160734 - Forward Propagation of Job Information or Compensation Information Data

• Note: This Centralized services switch for compensation information is universal now. See blog: Employee Central Centralized Services in Second Half 2023 (2H 2023) Release – Innovation Alert
• When forward propagation in UI for Compensation information is enabled, and a new record is inserted into Compensation information, through either the History page or Take Action (MSS UI), the existing values of fields are automatically updated for records that have Effective Start Dates after the Start Date of the New record. 

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

SAP SuccessFactors Employee Central

Let’s consider the employee Test Propagation for an example. It has two records, one with effective date 03/03/2013 and the other one with effective date 04/04/2014 as shown below.

Please note values of the fields Supervisor, Job Classification, Job Title and FTE for these two records.

Record with effective date 03/03/2013:	Record with effective date 04/04/2014:

 

Please note that the Supervisor field has a different value and all other marked fields have same values. Now let’s add a new record through Job Information > History --> Insert New Record, and set the Effective Start Date to 01/01/2014. In this new record we change the Supervisor, Job Classification, Job Title and FTE values:




When saving the new record the system will perform a check and determine whether values in the records that start after the one we inserted, need updating. This is to ensure there is some consistency with the data correction being inserted, and ensuring the rest of the employees data structure is kept consistent.

In this scenario, as the record we inserted made changes to values where the exact same previous value was present in the next record up the history, the system will also replace the value in the next record up the history, to ensure the data is kept consistent. If we now check the record for our text example, dated 04/04/2014, we’ll see that the values for Job Classification, Job Title and FTE have changed, but the value for Supervisor has not changed.

This happens due to the standard Employee Central feature "Automatic Forward Propagation of Job Information data".

Another way to look at this behavior would be using the following table, which depicts how the Propagation works, and how the system determines what to propagate and what not to propagate:

.

In above table of records:

Case 1: Since, 01.01 record and it's immediate 01.04 record 's field 1 value were same = X, and we inserted new record on 01.03 with field 1 new value = Z.

That is the reason this new value  Z is propagated to 01.04 record as well. But not to another future record 01.09 because this record contains completely different value Y than previous records.

Case 2: Similarly, when field value that we inserted is already same value in immediately next future record, there would be no change. Here, 01.01 field 2 has different value A and 01.04 has value B. In 01.09 record also this won't propagate because the value C is different than previous records.

Inserted record 01.03 field 2 with value B, this doesn't forward propagate to 01.04 because in this record value of field 2 is already B. It appears as if the value forward propagated but the values are same /unchanged between new record and existing future record.

Case 3: Also, now observe field 3 value in 01.01, 01.04, 01.09 all three records had same value in field 3 as O, that's why when we insert a new value Q, all the records's field 3 value gets updated to this new value.

Expected Behavior

In the given example, changes to Job Classification, Job Title and FTE are automatically Forward Propagated to the record dated 04/04/2014 because the values for the fields Job Classification, Job Title and FTE changed because in both the records they had the same values. But, the value for Supervisor did not change as the values for this field in the records 03/03/2013 and 04/04/2014 were different from the beginning.

UI

Forward Propagation for Job Information is enabled by default in the UI (hard-coded) and cannot be disabled.

Imports

To enable Forward Propagation of Job Information via Import, you must grant the corresponding permission to the Permission Role assigned to the user performing the import

1. Go to Admin Center > Manage Permission Roles
2. Select the Permission Role in question > click "Permissions..." button
3. Scroll down to Employee Central Import Settings > and select "Enable Forward Propagation during Incremental Import"

 

NOTE:  Deleting one of the records does not affect the others. When you delete the original record the information is already saved inside the subsequent records and deleting the original record will not change that, as you can see in the image below:

There is no way to delete the propagation. You will need to update each one of the records with the changes.

 

FAQ - Additional Information

Q) Where can I get information on this from the Guide?

 A) Guide:Implementing Employee Central Core

Chapter: Forward Propagation in Job Information

Guide: Implementing Employee Compensation Data

Chapter: Forward Propagation in Employee Central Compensation Information

Guide: Import: Forward Propagation of Data with Imports

Note:

• Forward Propagation is currently available for Job Information AND Compensation Information  (it is not designed to work for other elements such as Personal Info)
• This feature cannot be turned off for the Job Info UI's as it has been hard-coded.
• This feature cannot be enabled for Compensation Information UI via Admin Center > Company System and Logo Settings > Enable Forward Propagation for Compensation Information (Note: Not applicable for Imports) as this is now universal. See blog: Employee Central Centralized Services in Second Half 2023 (2H 2023) Release – Innovation Alert
  
• It works only when we Insert a new Job Information record through either Job History or Take Action (MSS UI).
• Forward Propagation does not occur when updating records through Job History > "Make Correction" nor when a record is Deleted via Job History.
• All records that are updated by the Forward Propagation logic now also have their "Last updated by" timestamp information updated to reflect that a change has been made to the record. Prior to b1608 the "Last modified by" timestamp did not get updated.
• Business rules are not triggered for the forward propagation modified time slices.
• Notes field is not forward propagated as it relates to information specific to current timeslice data like hiring or suspension.

 

• 3057168 - Forward propagation Pay Component Recurring
• 2160734 - Forward Propagation of Job Information Data
• 2160799 - Forward propagation of Job Information fields during incremental import
• 2345839 - Forward Propagation of Compensation Information Data

Onward, Population, Setting, Employee Central, Forward Propagation, Copy, Forward Propagation with Centralized Services, ECT-45709, Forward Propagation without Centralized Services, ECT-36066, Job Information, Compensation Information   , KBA , LOD-SF-EC-JOB-UI , History UI & MSS UI , LOD-SF-EC-CMP-UI , History or MSS UI , LOD-SF-EC-CMP-FOR , Forward Propagation , LOD-SF-EC-JOB-FWP , Forward Propagation , How To

SAP SuccessFactors Employee Central all versions ; SAP SuccessFactors HCM Core all versions