2881897 - Custom Calculated Field in Compensation Information not Updated on Import

A custom calculated field (calculated via a rule onSave on Compensation Information) which uses Pay Component Recurring data in the calculation is not updated on import of Compensation Information and Pay Component Recurring.

The calculation is updated when changes are made from the UI.

• Employee Central - Employee Data Imports
• Employee Central - Compensation Information

1. Create an onSave rule which calculates the value of a Compensation Information field based on data from Recurring Pay Components, such as amount.
2. Test the rule in the UI by changing the pay component amount value.
3. The rule triggers and the calculation is updated.
4. Carry out a compensation information import.
5. Carry out a Recurring Pay Component import with the new amount value.
6. The value is not updated with the new calculation amount.

This is a functional gap caused by the order of the imports.

The order of the imports causes this functional gap, as described below:

• The Rules are triggered on Comp Info. This is the first import file to be imported.
• This means when the rules trigger there is no change to the Pay Component Amount.
• The Pay Component amount is used in the calculation in the rules.
• When you update the pay component amount the rules will not trigger again as they are triggered under comp info not pay component recurring.

Workaround:

• In order for the rules to set the right values comp info would need to be updated again via import.
• This requires 3 imports in the following sequence:
  1. Compensation Information Import
  2. Recurring Pay Component Import
  3. Compensation Information Import

Things to consider in the work round:

• The user carrying out the import has permissions to trigger business rules on Compensation Information Imports.
• You must use the sequence number field in all imports. Without the use of Sequence number the above import sequence would create two compensation records on the one day. By using the sequence number you will only be updating the existing (created by the first import) compensation record with the second import.
  For further information on this please see the following KBA: 2741295 - Sequence Number Field in Compensation Information
• In order to use this record you must make sure that you are not Suppressing Identical Records While Importing Employee Data, as this will block the second compensation information import.
  For further information on this feature, please see the following section of the handbook:
  Employee Central Imports - Suppressing Identical Records While Importing Employee Data

import, calculation, compInfo, payComponentRecurring, imports, , KBA , LOD-SF-EC-EDP-CMP , Compensation Information Imports , LOD-SF-EC-CMP-CAL , Calculated - Pay Comp Groups, Compa/ Range & Charts , Problem