2438792 - Top 5 Errors why the Employee Central History Processor job fails - Variable Pay

SAP Knowledge Base Article - Public

2438792 - Top 5 Errors why the Employee Central History Processor job fails - Variable Pay

Symptom

Top 5 Errors that causes Employee Central History Processor job to fail.

Environment

Sucessfactors Variable Pay integrated with Employee Central

Resolution

1.   “Could not access code; in class: com.successfactors.hris.service.impl.Propertyresolver$PicklistOption.”

If instead of custom-string7 we decide to use the label or the code for this field (custom-string7.code or custom-strin7.label) we will not be able to import the History.

3.png

This happens as we have defined a picklist for custom-string7. That is a limitation to legacy picklists. By defining jobInfo.custom-string7 the system will return the option externalCode, and if the option externalCode doesn’t exist then it will return the option ID.

4.png

2.    "Proration is 0 due to decimal places of proration is too short”.

This error happens when there are assignments of days or maybe a single day and the decimal precision for proration is too small. For example, if there is an assignment of 1 day:

7.png

If our proration is using 2 decimals we are defining a proration for this assignment of 0, so when used in calculations:

8.png

Making the import fail.

9.png

10.png

11.png

The solution is to increase the number of decimals used by the proration field, for example #,##0.0000.

3.    "Cannot cast class java.lang.String to class java.lang.Number”

Happens when mapping custom-string fields to fields that require a numeric value. When that happens the system shows an error as we are trying to convert text fields into number type fields and the ECT History Import fails to complete.

16.png

17.png

It is necessary to define the target fields as numeric fields instead of string type.

4.    "Wrapped Exception: Fail to add background: SQLException executing:”

This happens when there is a field within the VarPay's Background Section in the data model that is mapped to a float number but the value stored in EC is not a valid float number.

Sample Error: This scheduled job failed to complete. For details, please contact SuccessFactors customer support.
com.successfactors.jobscheduler.ScheduledJobExecutionException: com.successfactors.sca.service.ServiceLegacyRollbackException: Wrapped Exception: Fail to add background: SQLException executing: insert into stg17sfv4_STOCKPM170081.SM_BACKGROUND (SM_BG_ID,USERS_SYS_ID,SM_BG_TYPE,SM_BG_NAME,SM_BG_DESC,SM_BG_VFLD1,SM_BG_VFLD2,SM_BG_VFLD3,SM_BG_VFLD4,SM_BG_VFLD5,SM_BG_VFLD6,SM_BG_VFLD7,SM_BG_VFLD8,SM_BG_VFLD9,SM_BG_VFLD10,SM_BG_VFLD11,SM_BG_STARTDATE,SM_BG_ENDDATE,SM_BG_DFLD1,SM_BG_DFLD2,SM_BG_DFLD3,SM_BG_DFLD4,SM_BG_IFLD1,SM_BG_IFLD2,SM_BG_IFLD3,SM_BG_IFLD4,SM_BG_FFLD1,SM_BG_FFLD2,SM_BG_FFLD3,SM_BG_FFLD4,SM_BG_LASTMODIFIED,SM_BG_ORDERPOS,ATTACHMENT_ID,SM_BG_VFLD12,SM_BG_VFLD13,SM_BG_VFLD14,SM_BG_VFLD15,SM_BG_IFLD5,SM_BG_IFLD6,SM_BG_IFLD7,SM_BG_IFLD8,SM_BG_FFLD5,SM_BG_FFLD6,SM_BG_FFLD7,SM_BG_FFLD8,SM_BG_VFLD16,SM_BG_VFLD17,SM_BG_VFLD18,SM_BG_VFLD19,SM_BG_VFLD20) values (stg17sfv4_STOCKPM170081.smbg_id_sq.nextval,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)Using arguments: : 113106, varPayEmpHistDataECSourceGermany, , , , 4813, 4813, , 367, , , , , , , 2017-01-01 00:00:00.0, 2017-12-31 00:00:00.0, , , , , , , , , 28314.101653913916, 20.0, 161522,04, , 2018-03-01 20:02:53.182, -1, , , , , 1, , , , , , , , , , , , , ,

The solution is to correct the field value according to its type.

5.    "java.lang.IndexOutOfBoundsException”

See article 2555961 - EC History processor job fails with java.lang.IndexOutOfBoundsException error

Keywords

ECT Processor, History, Employee History , KBA , LOD-SF-VRP-EC , Employee Central data, config & settings within VP , Problem

Product

SAP SuccessFactors HCM Suite all versions