cancel
Showing results for 
Search instead for 
Did you mean: 

ECT-210699 Cannot Sync Job Info Supervisor Position to Employee Position

SteveMontanye
Explorer

With H1'2023 release ECT-210699 removed the ability to sync the Supervisior's position from Job Information to the Employee's Position > Higher Level Manager Position using a Business Rule.  We had this condition defined on a Business Rule because in our organization we use 1:1 relationships between Position and Employee so the Supervisor (Position) on the Employee's Job Info Profile, should always be the Position assigned to the Higher Level Position on the Employee's Position. 

We did this because using the Move currently assigned Position below new Manager's position would ONLY change the Manager on the Employee's position, and not change any other attributes that might have been updated during the same transaction.  This causes the user to have to execute two transactions: One to update the manager and move the position, and another to update the additional Job Attributes that might have changed.  Using the Business Rule to sync the Job Information Supervisor Position to the Employee Position removed the necessity of having to execute two transactions. 

Do you have a suggestion for how you think that the issue can be addressed?

Bring the ability to sync the Job Information Supervisor Position to the Employee Position back - return the ability to use the Higher Level Position in the THEN Statements of Business Rules.

OR

Develop functionality that will allow all Job Info changes to be updated, even if a Manager Change is included, on the employee's position so the user does not have to execute two transactions. 

Liam_Murphy
Explorer
0 Kudos
We have the same issue. For now we are planning on manually updating Positions at the end of the workflow, but it's not a great solution...
jessicalund-d
Newcomer
0 Kudos
We are also planning to address in the workflow by having the Org Design Experts update the positions - but it will be adding more to their workload. Not very pleased by this change.
SteveMontanye
Explorer
0 Kudos
Vote here on the Improvement Request: Improvement Request Details - Customer Influence (sap.com)
Liam_Murphy
Explorer
0 Kudos
Hi @SteveMontanye - please can you send the link for the improvement request?
SteveMontanye
Explorer
View Entire Topic
siddharthrajora
Product and Topic Expert
Product and Topic Expert
0 Kudos

This is due to Compound Employee API which is used by BOOMI to query, after each successful run ie query is successful, the date and time is updated to reflect that, typically customers run the Master data replication every 5 minutes etc.

if there is a failure ie complete query, time is not updated, Also you can retrigger it by changing the time as well

As you are aware its going to always update or overwrite in HCM what was sent, We see rarely the whole replication fails, only handful of errors which can be manually sent by DRM , you can send upto 200 per request for manual replication via DRM!!

There is no sync job per se, we read DRM and SLG1 or SLGD error logs and make a decision.

Former Member
0 Kudos

thank you Siddharth.

I am wondering that is there a tools available on EC to mass update the date ,so that the error employee will be picked again in the next sync?

thanks