on ‎2022 Sep 01 8:27 AM
Hello everyone,
I would like to know if it is possible to synchronize the key allocation field from object Position with the Job Information portlet of the incumbent?
I tried to go through Position Management Settings > Synchronization > SFCC_PosMgmt_SyncPosToJobInfo. It is not possible to add the key allocation field in the configuration of the rule.
Thanks in advance,
Antonio Roppa.
Request clarification before answering.
karenperez,
We just use this just to maintain proper data (in Job Info portlet of the employee) when updating Position (attached to the concerned employee) when needed during the "lifecycle" of the employee.
No particular scenario.
If for example, we need to edit Position title and key allocation, only Position title change is synchronized with Job Info portlet; key allocation still remains the same despite being edited in the Position.
Thanks,
Antonio Roppa.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi antonioroppa,
With the rule example that I shared before, which is assigned on the Position Management Settings > Synchronization > Rule for Synchronizing Position to Job Information, but also onSave in the Job Information portlet (Manage Business Configuration > jobinfo), it does work for me when I update the FTE in the position, it propagates to the employee.
What do you have in the 'Position to Job Information Synchronization' setting under Position Management Settings > Synchronization? In my case I have always, so the sync always run.
Another thing that could be the issue is the effective date. Are you updating the position in a effective date which the employee is already assigned?
Thank you.
Best Regards,
Karen Perez
karenperez,
Unfortunately, it doesn't work at all :
- 1st rule with Basic scneario: key allocation fields are findable but during synchronization with incumbent, they don't synchronize.
- 2nd rule with Synchronize Position Changes to Incumbents scenario: key allocation fields are not findable at all
Cordially,
Antonio Roppa.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi antonioroppa,
I understand that you now can add the field to the business rule, but maybe your use case is missing something. When are you trying to propagate this info, during a hire/rehire? If so, you need to have this same rule onSave in the job information portlet.
Thank you.
Best Regards,
Karen Perez
Hello karenperez,
SFCC_PosMgmt_SyncPosToJobInfo is used in Position Management Settings > Synchronization > Rule for Synchronizing Position to Job Information.
This rule was created in December 2020 and has a Basic scenario. The rule is working fine. I am able to add the "Then" part : Set Job Information.Key Allocation to be equal to Job Information.Position.Key Allocation
But unfortunately, when the rule is triggered, each parameters are well synchronized except for Key Allocation.
I tried to duplicate the rule but with changing scenario from "Basic" to "Synchronize Position Changes to Incumbents". With this particular scenario, I am unable to add the "Set Job Information.Key Allocation to be equal to Job Information.Position.Key Allocation" since the Key Allocation is not findable and selectable.
Thanks in advance,
Antonio Roppa.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, antonioroppa, for clarifying.
Yes, the FTE can be used in the rule as per the example below. Check if you are trying to map to the correct fields. Also check if both, Position and Job Info FTE fields are enable. Finally, check if the business rule Parameters are correct.

Image from demo
Thank you.
Best Regards,
Karen Perez
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 7 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 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.