Symptom
While accessing worksheets or executive review for either Compensation or Variable Pay there is an error.
What is the cause of this and how can is be corrected?
**Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental**
Environment
- SAP SuccessFactors Compensation
- SAP SuccessFactors Variable Pay
Cause
This error message populates due to one of the following reasons:
- Incorrect custom field types
- Syntax error's on custom formulas
- Formula's using "" when the system looks for either 0, N/A etc
- Incorrect formatting of formulas. For example, having the correct number of conditions however missing outputs
- Custom validations missing an output (result)
- Employee data
The biggest cause is having blanks values within custom formulas.
Resolution
The main cause of this is custom formulas, the way they're defined and the data which is coming into them from other columns in the template.
To avoid this type of error message ensure you take the following precautions.
Avoid using blanks
Do not use "" in formulas as this will return as a blank. The system will be looking for a value such as 0, NA, #N/A etc.
Therefore, should you have this requirement for a custom formula we would recommend you adjust this and use NA.
For example, below is a formula which will cause the error message when accessing the worksheet via a planner's inbox:
if(comp_MeritEligibility = "No" , "",
if(payGuide ="", "", if( salaryRateFinal > toNumber(comp_payGuideMAX) && toNumber(comp_payGuideMAX) !=0, salaryRateFinal - toNumber(comp_payGuideMAX) , "")))
The formula which could be used in this scenario and avoids you getting this error would be something as follows:
if(comp_MeritEligibility = "No", "NA",
if( payGuide ="", "NA", if (salaryRateFinal > toNumber(comp_payGuideMAX) && toNumber(comp_payGuideMAX) !=0, salaryRateFinal - toNumber(comp_payGuideMAX),"NA")))
Formula formatting
Ensure your custom formulas are correctly formatted within your templates.
If these are not, then it may cause this error message to populate.
For example, we have the following custom formula within custom column:
if(customField19>0, customField17>= customField18,1,0)
This does not look correct as the formatting should be one condition and two argument. However, this formula has one condition but three arguments.
The formula should be updated to something as follows:
if(customField19>0, if(customField17>= customField18,1,0),0)
This configuration will prevent this error message from being generated.
Another example would be as follows:
if(CustomSAPCol="N/A", CustomSAPrpt, CustomSAPCol)
Updatinting the formula to the below corrects the issue as we are separating the conditions and managing the "" with "#N/A".
if(CustomSAPCol="N/A", if(CustomSAPrpt="", "#N/A", CustomSAPrpt), if(CustomSAPCol="","#N/A",CustomSAPrpt))
More information on custom formulas can be found in 2084135 - Managing Data, Custom Calculations / Formulas and Functions - CMP & VRP
Syntax errors
Before launching worksheets, we recommend to use the check tool for template configuration settings.
One check for custom formulas is the Worksheet check labelled CompCheckWorksheetCustomFields. This check checks the formatting of formulas.
For example, in the above example the formatting of the formula was:
if(customField20>=0, customField16>= customField18,1,0)
While running the check tool it'll come back with a syntax error.
This should be corrected to be as follows as we mentioned above:
if(customField19>0, if(customField17>= customField18,1,0),0)
More information on the check tool can be found in the guide as well as KBA 2643643 - Compensation & Variable Pay check tool
Column types
While using custom formulas there can be multiple columns being used which have different column types.
You may have a custom column which is a PERCENT type where you are pulling in data from custom STRING, MONEY column.
One cause of this error can be the use of STRING columns coming into PERCENT columns.
If you are using a STRING type column in multiple formulas and the data within these columns are numeric, then we recommend using AMOUNT rather than STRING.
This is to ensure there are no potential error's while accessing the forms as the custom STRING columns are being used for numeric calculations.
For example, you have a custom STRING column which has an import key from the UDF which is used in a formula for a PERCENT type column.
This may cause issues so updating the custom import key type to be AMOUNT will avoid this.
Custom Validations
If you do not have custom validations corrected formatted, then this may also cause this error message to occur.
For more information on this please review KBA 2822386 - Compensation - Custom field validations
NOTE: Making changes to any formula(s) will NOT update the existing form and new ones will need to be created.
Keywords
error occurred, refresh and try again, unable to access compensation form, executive review error, variable pay form error, , KBA , LOD-SF-CMP , Compensation Management , LOD-SF-VRP , Variable Pay Programs , LOD-SF-CMP-FRM , Forms & Templates , LOD-SF-VRP-FRM , Forms & Templates , Problem