on 06-01-2023 3:08 PM
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
3 | |
3 | |
3 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.