Hi,
I am using AX 2012 R2 CU8.
I have a question with regards to the use of the "approval limits" which are configured within the "Signing limit policies" (Organisation Administration - Setup - Signing Limits - Signing Limit Policies - Default signing limit). I am using such "approval limits" for purchase requisitions in order to ensure that a worker with the appropriate "approval limit" approves the purchase requisition line.
My problem is that when, for example, there is a purchase requisition line with a net amount of $1000 - this purchase requisition line is sent to John who has an approval limit of $2000 and thus has the proper approval limits to approve the purchase requisition line however, John decides to "delegate" the purchase requisition line to Sam for approval. Sam has an approval limit of only $200 (which is less than the purchase requisition net amount of $1000) and therefore should not be allowed to approve the purchase requisition. However AX is still allowing Sam to approve the purchase requisition line and ignores the approval limit set for Sam of $200.
Has anyone come across this issue before please?
Thanks,
Alexia
*This post is locked for comments
Hi Alexia, we are facing the same un-desired effect with a signing limit being delegated to user with lower authorised signing limit. We are using AX2012 R3. Did you find a fix for this issue. Kind regards,
Danny
Hi Alexia,
I have the same situation to tackle. Did you get some answers regarding this issue? or if solved how do you solve it? An insight will be helpful.
Thanks,
Faisal
Hi Alexia,
We have built the workflows using conditional value based decisions and workflow user groups rather than signing limits in the HR module.
I would imagine the signing limits will never be enforced unless the workflow instructs them to be. So you would have to set up each individual workflow to decision based on the signing limit of the user.
Thanks for your reply Bruce - the problem is however that these "approval limits" are not being enforced at all unless they are added in a condition within the purchase requisition workflow. I gave the example of delegation however it seems that the same problem occurs when the purchase requisition is routed to any user - the "approval limits" are not stopping users from approving purchase requisitions unless there is a condition in the purchase requisition workflow which states to skip users which do not have the appropriate "approval limits". The same goes for the "spending limits" where by any user can issue a purchase requisition of any amount irrespective or their "spending limit".
I may be wrong here but I am under the impression that when you 'delegate' an action to a user in AX, provided that they have correct permissions within the system, they assume the rights of the user who has delegated the work item. So the signing limits are essentially overwritten because you are delegating your authority to someone else.
To get round this we have an internal policy where approvals can only be delegated vertically.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 290,900 Super User 2024 Season 2
Martin Dráb 229,297 Most Valuable Professional
nmaenpaa 101,156