3417815 - When running PayComponentWhereUsed in Check Tool, RecurringDeductionItem record type shows as no permission - Employee Central

• When running PayComponentWhereUsed in Check Tool, result shows no permission for record type RecurringDeductionItem.
•  Check Tool - PayComponentWhereUsed - Records without permission

"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

1.Go to Check Tool

2.Go to Validation and run check for Pay components are used (PayComponentWhereUsed) under Employee Central Core.

3.Choose specific Pay Component and Run.

4.Result shows that: 

• An exception occurred during the check execution.
• records without permission for record type RecurringDeductionItem or PayComponentWhereUsed

5. We have checked that all the related permission has been granted and no user has related pay component records in instance.

One Time Deduction Items are automatically generated by the system when a One Time Deduction is added. In some cases, the One Time Deduction Item remains on Database when the One Time Deduction was deleted. 

Hence system detects the data inconsistency and pops up this permission issue.

Customer Action:

• Please raise an incident to dev side and they would run a script to extract One Time Deduction Items on Database for that specific pay component and then remove those remaining dummy data.
• Customer must provide a written approval for an correction Script and Run the script to delete the remaining dummy data 

Employee Central Support Engineer Team Action:

• Please refer to Internal Meno 
• Replicate issue
• Collect error Id
• check Splunk log using : Error ID + Company Id
• After Script Result
• example: Refer to an incident INC7018047

• 2472648 - Using the Check Tool to Check a SuccessFactors Configuration

• Check tool issue: GUIDE: Using the Check Tool  //URL: https://help.sap.com/viewer/15279cffa8074ac8b686fb8212498c11/latest/en-US

View The table summarizes the allowed behaviour in  Guide- Implementing Employee Compensation Data Chapter- Preventing Changes to a Pay Component Already in Use

• The system doesn't allow changes to assigned pay components to prevent the data inconsistencies
• Once used, none of the pay components can be deleted or set to inactive. If a pay component is no longer used after a specific date, it is possible to create a new time slice in which the pay component is inactive after that date.

Pay components are used, run check, Records Without Permission, pay component check result,  One Time Deduction,  One Time Deduction Item, exception=Cannot assign field "previousCompositeField" because "head" is null , checkId=PayComponentWhereUsed, description=An exception occurred during the check execution, Cannot assign field "previousCompositeField" because "head" is null , , KBA , LOD-SF-EC-CMP , Compensation Information & One-Time Bonus , Problem