WFA - Permission artifacts sync job failing

[amfonseca64]

Hello.

Workforce Analytics permission artifacts sync job is failing, which is preventing us to use some structural dimensions in workforce analytics. Error log is the following:

Full exception:com.successfactors.jobscheduler.ScheduledJobExecutionException: com.successfactors.jobscheduler.ScheduledJobExecutionException: com.successfactors.jobscheduler.ScheduledJobExecutionException: com.successfactors.jobscheduler.ScheduledJobExecutionException: com.successfactors.rbp.app.api.RBPFacadeException: Error update dimension [82].
at com.successfactors.inform.scheduledjob.SyncWfaAndBizxInstanceJob.executeJob(SyncWfaAndBizxInstanceJob.java:149)
at com.successfactors.jobscheduler.jobimpl.SimpleJob.execute(SimpleJob.java:471)
at jdk.internal.reflect.GeneratedMethodAccessor599.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)

Can you please help?

@YSE-1 

SAP SuccessFactors Workforce Analytics 

[YSE-1]

Hi @amfonseca64 - based on what appear in the log, the issue is with location structure:

Error: System.ArgumentException: Item has already been added. Key in dictionary: '[location].[location].[level1_fra_zznostateprovince_avermes]' Key being added: '[location].[location].[level1_fra_zznostateprovince_avermes]'

If you check using Dimension Editor, you will see two Avermes nodes but with different letter case (i.e. all uppercase or camel case):

This cause the error when processing the structure in artifact sync.  Also, the WFA site is not case sensitive so it also caused application error when I select location structure as hierarchy option.  The log only provides one example but there could be more than one who has the same issue.  You will need to handle this in your query for the structure.  Also, there is another location structure created in Requisition fact table which has the same issue.  You need to fix both of them.

This issue did not occur during initial load or incremental load processing because the back-end processing support case sensitive value and treat them as two different values.  It is just the artifact sync and WFA site are not case sensitive.

[amfonseca64]

Hello. Thank you for the feedback. I corrected the data and now we don't have 2 Avermes cities. After triggering full load of the cube, load is successful but permission artifacts sync job is still failing. I could not find other cases with duplicate locations. Can you please check the error log and let me know where the job is failing now? Thanks in advance for your help @YSE-1 

[YSE-1]

Hi @amfonseca64 - there still duplicate nodes in location structure: Error: System.ArgumentException: Item has already been added. Key in dictionary: '[location].[location].[level1_tza_zznostateprovince_dar es salaam]' Key being added: '[location].[location].[level1_tza_zznostateprovince_dar es salaam]'. The log only provided the first duplicate nodes but it does not mean this is the only one. So you need to check yourselves on other duplicate nodes. Thank you.

[amfonseca64]

Hello. Unfortunately this issue is happening again. Can you access error logs for the permission artifacts sync job and see where it is failing? Company ID is assaabloya in DC2.

[YSE-1]

Hi @amfonseca64 ,

This is the node causing issue: 

Error: System.ArgumentException: Item has already been added. Key in dictionary: '[location].[location].[level1_chn_9692_shenzhen]' Key being added: '[location].[location].[level1_chn_9692_shenzhen]'

Error: System.ArgumentException: Item has already been added. Key in dictionary: '[fact_table_5_s_3].[fact_table_5_s_3].[level1_chn_9692_shenzhen]' Key being added: '[fact_table_5_s_3].[fact_table_5_s_3].[level1_chn_9692_shenzhen]'

On Location hierarchy in Workforce fact and also in Recruiting.

[YSE-1]

Hi @amfonseca64,

Can you please narrow down on which structural dimension the artifact sync failed?  If this happened on Location structure, usually this is caused by duplicate nodes in the structure.  That is nodes with different letter case but actually refer to the same thing.  You can use Dimension Editor menu to have a look at the Location structure.  If it was failed on other structural dimensions, please check for duplicate as well.  

[amfonseca64]

Hello @YSE-1 .

The sync indeed seems to be failing in Location dimension. However, I can't find any duplicate nodes, and I thought that, if there are any duplicate nodes, OLAP cube full load would fail and provide information on the load status log of which node is duplicate - but cube load is not failing. Can it be any other reason for the permission artifacts sync job to fail? Can you access error logs for this job and see where it is failing? Company ID is assaabloya in DC2.

Thanks