Skip to main content

Cannot explain myself around a behaviour in purchase order authorisation. 

Below is how my auth rule is setup. Note the ‘Use Delta Amounts for Auth’ is set to Yes. 

Now, my PO is initially a placeholder for total of 0.01 value. 
Then a POCO is created to add another line with a value of 120,000.
An authorisation is expected on this POCO, however is not fetched when the Delta Amt for Authorisation is set to yes. 
In my pov, there is a clear delta amt which is within the range of the auth rule. 
When the Delta Amt check is set to no, the auth rule is fetched. 

System - IFS Cloud 23.1.3
 

Hi ​@Vimukthi Mahakumbura , Is the setting ‘Consider PO Max Authorized Amount in Change Order Authorization’ in company level (company → supply chain information → procurement → Authorization Parameters for Change Management section) enabled? And is there a value for ‘PO Max Authorized Amount’ field in PO authorizations tab for this PO?

If this check box is selected, it indicates that a check against maximum authorized amount on the purchase order when purchase authorization rules are retrieved to a purchase order change order is made. This check will only be done when the Use Delta Amount for Change Orders check box is selected on the rule. If the new amount on the purchase order change order exceeds the maximum authorized amount on the purchase order then the system tries to find a rule which authorizes the full amount instead of delta amount for the change order. 

This check is done when the initially fetched change order rule is using delta amounts. If the change order amount is greater than ‘PO Max Authorized Amount’ instead of using the delta amount change order authorization rule, system would try to look for an authorization rule that can be used to authorize full change order amount. So, it would be a rule which has ‘Use Delta Amount for Change Orders’ unchecked and enough amount limit to cover the change order amount. You need to have some Authorization Rule that does NOT have the Use Delta Amount selected.

Else disable the ‘Consider PO Max Authorized Amount in Change Order Authorization’ in company level and check. 

Hope this helps. 

 

Kind regards,

Sayuri.


Hi ​@Sayuri Perera 

Thanks so much for your reply. Apologies I get to check this now.

Yes, the setting you mentioned in company makes a difference. We had it on. Now once off, the behavior has started to make sense.

However, the behavior I experienced with the value set to true is not exactly how you explained. 

If the POCO delta amount is below the PO Max Auth, amount it triggers the rule.
If the POCO delta amount is over the PO Max Auth amt it does not trigger the rule. FYI we have working rules defined to fetch over values.

Some numbers for you. (company setting = yes, delta in rule = yes)
PO value is 0.01 > PO auth rule (1-5000) fetched > Approved > PO Max Auth Amt is 5000
POCO created to increase the value upto 12,000 > released > no rule fetched
POCO created to increase the value upto 4,000 > released > rule fetched 

Thanks again

 


Hi ​@Vimukthi Mahakumbura , What you have explained is the system intended behavior. I have explained the scenario where the POCO delta amount is greater than/ exceeds the PO Max Auth amt in above comment.

If the change order amount is greater than ‘PO Max Authorized Amount’, instead of using the delta amount change order authorization rule, system would try to look for an authorization rule that can be used to authorize full change order amount.

So,

  1. If the change order amount is below the PO max authorized amount, system fetches the rule which has ‘use delta amounts’ enabled. 
  1. If the change order amount is greater than the PO max authorized amount, system fetches a rule which has ‘use delta amounts’ disabled and enough amount limit. (In your case since all rules are enabled with ‘use delta amounts’, system does not fetch a rule.)

Hope it’s clear. 

 

Kind regards,

Sayuri.


Hello ​@Sayuri Perera Thanks again for your reply. I can agree with you this being the system behavior, however not to be an intended behavior. At least in my pov, it doesnt make sense why the system needs to look for an auth rule which doesnt check the delta. 
The example scenario I mentioned above creates a serious gap in auth is my experience. 

There is a high chance I have not fully understood this. If you think you can answer, why the system is looking for an auth tule which doesnt check the delta in a business pov, that would be immensely helpful. 

Thanks for your help anyways, we are happy to turn off the setting in the company. 


Reply