SAP SuccessFactors Compensation Information FAQs

SAP SuccessFactors Compensation Information FAQs
Contact Us For AMS Support

This blog compiles frequently asked questions from SAP SuccessFactors Knowledge Base Articles (KBAs), focusing on Employee Central Compensation Information, recurring payments, non-recurring payments, pay components, pay ranges, and related business rules. Each answer is written in a simple, action-oriented format for SAP SuccessFactors users and administrators. 

How to fix an unresponsive Spot Bonus page in SAP SuccessFactors?

Answer: 

  1. Open the employee’s People Profile.
  2. Go to the Compensation section.
  3. Open the Spot Bonus card.
  4. Confirm whether the page becomes unresponsive when using the pencil icon.
  5. Go to Configure Latest People Profile.
  6. Enable the latest edit andhistoryUI. 
  7. Retest the Spot Bonus edit action.
  8. Submitan enhancement request if the business does not want to switch to the latest history and edit UI. 

Note: 

The KBA identifies this as a known limitation when handling many records in PPX without the latest edit and history UI enabled.

How to import end-dated payments in SAP SuccessFactors Employee Central?

Answer: 

  1. Build a Person and Employment Exportreportfor Compensation Information. 
  2. Export the latest Compensation Information records.
  3. Filter records with effective end date 12/31/9999.
  4. Copy the records into a Compensation Information import template.
  5. Remove the end date andsequencenumber values. 
  6. Create one Compensation Information file for the paycomponentstart date. 
  7. Create another Compensation Information file for the paycomponentend date. 
  8. Build a Person and Employment Export report for Pay Component Recurring.
  9. Copy the latest Pay Component Recurring rows into an import template.
  10. Use one file to add the paycomponentand another file to remove it using the DELIMIT operator. 
  11. Import the files in order, waiting for each import to complete before starting the next one.

Note: 

End-dated payments are a UI-only feature and do not trigger directly on imports. The same result requires a structured series of Compensation Information and Pay Component Recurring imports.

How to remove the pie chart from Alternative Cost Distribution in People Profile?

Answer: 

  1. Go to Configure Object Definitions.
  2. Open the Alternative Cost Distribution Item object definition.
  3. SelectTake Action> Make Correction. 
  4. Locatethe Percentage field. 
  5. Click Details.
  6. Set Mask Value on UI to Yes.
  7. Save the changes.
  8. Verify that the pie chart no longer appears in the Alternative Cost Distribution portlet.

Note: 

The pie chart appears because the Percentage field is not masked.

How to handle unsupported cross-entity rules from Employment Details to Compensation Information?

Answer: 

  1. Review business rules that use Employment Information as the source element.
  2. Check whether the target element is Compensation Information, Recurring Pay Components, Non-Recurring Pay Components, or Job Relationships.
  3. Treat thoseruleresults as unsupported. 
  4. Rebuild the rule using a supported rule scenario.
  5. UseJobInformation Model as the base object where applicable. 
  6. Create the new rule from Configure Business Rules > Create New Rule > Employee Central Core > Trigger Cross-Entity Rules.
  7. Test the rule after rebuilding it.

Note: 

Cross-entity rules from Employment Information to the listed target elements are no longer supported and may be ignored. 

What should administrators know about Pay Scale Group API deprecation?

Answer: 

  1. Identifyany integrations or processes using Pay Scale Group API. 
  2. Review whether the API is still being used in the environment.
  3. Treat the API as deprecated because support reached End of Maintenance on November 17, 2023.
  4. Plan replacement or migration activities before the deletion date.
  5. Use Pay Scale MDF objects as the go-forward reference area.

Note: 

The KBA states that Pay Scale Group API is scheduled for deletion on November 13, 2027. 

Which Employee Central portlets support cross-portlet business rules?

Answer: 

  1. Use cross-portletrules only for supported HRIS entities.
  2. Supported entities include Job Information, Compensation Information, Pay Component Recurring, Pay ComponentNon Recurring, Job Relationships, Employment Details, Termination Details, and Dependents Information in Latest People Profile.
  3. Use the source element as the base object of the rule.
  4. UseonSaverules for supported UI, API, or import transactions. 
  5. UseonChangecross-portlet rules only for the limited supported scenarios. 
  6. Do not use cross-portletrules for Employee Profile standard or background elements.

Note: 

Cross-portlet rules have source and target limitations. Pay Component Recurring and Pay Component Non Recurring do not have a direct relationship that allows one to directly control the other through a business rule. 

How to stop deductions from appearing in the Recurring Pay Component portlet?

Answer: 

  1. Go to Manage Organization, Pay and Job Structures.
  2. Open the deduction paycomponent.
  3. Set Display on SelfService toNo. 
  4. Confirm that Is Earningis setto No. 
  5. Confirm that Recurring is set to Yes.
  6. Confirm that Target is set to No.
  7. Save the paycomponent.
  8. Retest the Compensationportlet.

Note: 

The pay component may still appear from Compensation Information > History > Insert New Record. The KBA identifies that as expected behavior for the Display on Self Service flag.

How to trace Compensation Information business rules in SAP SuccessFactors?

Answer: 

  1. Go to Admin Center > Business Rule Execution Log.
  2. Select Create New > Rule Trace.
  3. Enter a code and name for the trace.
  4. Set the start date and end date using the system server date.
  5. Select the login user who executes the transaction.
  6. Leave Rules to be Logged empty to capture all associatedrules, orselect a specific rule. 
  7. Choose Complete or Short trace mode.
  8. Perform the transaction that should trigger the rule.
  9. Download the CSV file and review the rule steps.

Note: 

If the downloaded CSV is empty, the rule did not trigger for the transaction. 

Can HRIS Sync map country-specific Compensation Information fields?

Answer: 

  1. Review whether the field iscountry-specific.
  2. Confirm whether the field belongs to an HRIS element such as Compensation Information.
  3. Treat country-specific HRIS Sync mapping as unsupported.
  4. If a workaround is needed, create a custom field on the corresponding non-country-specific element.
  5. Configure the HRIS Sync mapping for that custom field.

Note: 

The KBA states that HRIS Sync does not support country-specific fields for any HRIS element. 

Can the Compensation Information pie chart color be customized in Latest People Profile?

Answer: 

  1. Review the Compensation Information pie chart in Latest People Profile.
  2. Confirm whether the requirement is to change the chart color.
  3. Treat chart color customization as unsupported.
  4. Submitan enhancement request if the business requires configurable pie chart colors. 

Note: 

The KBA states that changing the pie chart color in Latest People Profile is not supported.

How to fix an onSave rule that does not update an existing pay component record?

Answer: 

  1. Review theruleconfigured under Compensation Information. 
  2. Confirm whether it calculates one paycomponentamount from another pay component. 
  3. Check whether it works for new records but not edited existing records.
  4. Reconfigure the rule using the Trigger Cross-Entity Rules scenario.
  5. Assign and test the rule again. 

Note: 

The KBA resolution is to configure the business rule under the Trigger Cross-Entity Rules scenario. 

How to change decimal separators in SAP SuccessFactors?

Answer: 

  1. Go to Manage Languages.
  2. Download the default labels for the system language to be changed.
  3. Add `COMMON_DecimalPoint` as a key.
  4. Set the value to`,`or `.` based on the requirement. 
  5. Add `COMMON_NumericGroupingSeperator` as a key.
  6. Set it to the separator not used for the decimal point.
  7. Upload the edited language file through Manage Languages > Actions.
  8. Test the affected areas.

Note: 

Some areas, including Compensation Information and Pay Components for certain languages, may not reflect these changes because decimal and separator behavior can be controlled by backend system design.

How to make Use for Leave Loading Only available in Pay Component Type?

Answer: 

  1. Go to Company System and Logo Settings.
  2. Enable the Leave Loading feature.
  3. Go to Provisioning > Company Settings.
  4. Enable Employee Central Payroll.
  5. Confirm that Unit of Measure exists in the corporate data model under the paycomponentobject. 
  6. Set Unit of Measure visibility to both.
  7. Reopen the paycomponent.
  8. Confirm that Use for Leave Loading Only is available in the Pay Component Type dropdown.

Note: 

The option does not appear when required leave loading, payroll, or Unit of Measure configuration is missing.

How to fix the Name of Pay Change already exists error in Manage Pay Increase?

Answer: 

  1. Go to Configure Object Definitions.
  2. Search forPayScalePayIncreaseDefinition.
  3. Confirm that the Secured field is set to Yes.
  4. Go to Manage Permission Roles.
  5. Open the required role.
  6. Grant permission for thePayScalePayIncreaseDefinitionobject. 
  7. Save the role.
  8. Create the pay increase again.

Note: 

The KBA points to missing object permission as the correction before creating the pay increase. 

How to automatically populate Amount from the Pay Component definition?

Answer: 

  1. Go to Configure Business Rules.
  2. Create a newonChangerule. 
  3. Use the scenario TriggeronChangeRules for HRIS Elements. 
  4. SelectCompensationModel as the base object. 
  5. Add the required if-else conditions.
  6. Use the Set operation to set Amount from the Pay Component Value in the paycomponentdefinition. 
  7. Assign the rule as anonChangerule on the pay-component field under payComponentRecurring. 
  8. Test by selecting the pay component in Compensation Information. 

Note: 

The Pay Component Value defined in Manage Organization, Pay and Job Structures does not automatically populate the Amount field by standard design. 

What is the rule execution order for Compensation Information derivation rules?

Answer: 

  1. Review theonSaverules configured in Manage Business Configuration. 
  2. Expect mostonSaverules to run from top to bottom. 
  3. For Manager Self-Service changes involving Job Information and Compensation Information, expect Job Information rules to run first.
  4. Then expect Compensation Information rules.
  5. Then expect Event Reason Derivation rules for Job Information.
  6. Then expect Workflow Derivation rules for Job Information.
  7. Then expect Event Reason Derivation rules for Compensation Information.
  8. Then expect Workflow Derivation rules for Compensation Information.

Note: 

Rules configured for event reason derivation and workflow derivation from rule scenarios run after the other onSave rules.

How to export Pay Range foundation objects for value checks?

Answer: 

  1. Go toReportCenter. 
  2. Create a new Table report.
  3. Select the Foundation Objects domain.
  4. Name the report clearly for future reuse.
  5. Go to Columns > Select Columns.
  6. Select Pay Range.
  7. Select all relevant Pay Range fields.
  8. Remove unnecessary audit fields if they are not needed.
  9. Save the report.
  10. Preview or generate the report.
  11. Open the exported file in a spreadsheet editor.
  12. Filter theassociationvalues to validate whether the needed Pay Range combination exists. 

Note: 

This approach helps identify missing or duplicate Pay Range combinations used in compensation calculations such as Compa-Ratio or Range Penetration.

How does forward propagation work for Compensation Information?

Answer: 

  1. Review the current and future-dated records.
  2. Compare the changed field value with the same field in the next future record.
  3. Expect the new value to propagate when the next future record has the same previous value.
  4. Do not expect propagation when the next future record already has a different value.
  5. For imports, go to Manage Permission Roles.
  6. Open the permission role for the import user.
  7. Go to Administrator Permission > Employee Central Import Entities.
  8. Enable Forward Propagation for the required entity.

Note: 

Forward propagation is available for Job Information and Compensation Information. Deleting the original record does not remove values already saved in subsequent records.

How to refresh Compensation Information after a Job Information change?

Answer: 

  1. Confirm that Refresh Compensation Required is set to Yes.
  2. Avoid making the Job Information change through History > Insert New Record when compensation should refresh.
  3. Go to the employee’s profile.
  4. SelectTake Actionor All Actions. 
  5. Select Change Job and Compensation Info > Job Information.
  6. Update the field value.
  7. Save the change.
  8. Check whether a Compensation Information record is created.

Note: 

The KBA states that Job Information changes made through History do not refresh Compensation Information by design. 

How to create an Event Reason for Compensation Information changes?

Answer: 

  1. Go to Admin Center > Manage Organization, Pay and Job Structures.
  2. Select Event Reason from the Create New dropdown.
  3. Enter the effective date.
  4. Enter a unique Event Reason ID.
  5. Enter the Event Reason Name.
  6. Set the statustoActive or Inactive. 
  7. Select the event that maps to theeventreason. 
  8. Select the employee status associated with theeventreason. 
  9. Save the event reason.
  10. Go to Manage Permission Roles.
  11. Grant permission to the event reason under Employee Data > Event Reason.
  12. Log out and log back in before testing.

Note: 

Event reasons are customer-defined foundation objects used to explain why a job or compensation event occurred. 

Conclusion

Compensation Information issues in SAP SuccessFactors often involve pay component configuration, business rule scenarios, rule execution order, imports, HRIS Sync limitations, forward propagation, or UI behavior in People Profile. Reviewing the configuration path and expected behavior first can help administrators resolve common issues faster. 

For specialized SAP SuccessFactors AMS support, contact 3Core Systems. 

Like It? Share It

Shyam Reganti

SAP SuccessFactors Practice Lead