Skip to main content

Within Ad-Hoc Purchasing Basic Data, you can add a Maximum Spend Limit but this is not enforced, i.e., the Engineer can still add a PO for a value over that limit.

Is there a way to prevent this, i.e., to stop the PO being Released and then follow the standard PO Auth Rules?

Alternatively, is there a way to add No Part Lines to Purchase Requisition on MWO?

 

Hi

Max spend limit is not enforced in any of the clients (web, mobile) and the idea is just to inform the user that it has exceeded the purchase limit but never prevent user from processing further. User might not even add purchase details at the trade counter so they might not even find that the limit has exceeded at the time of receiving the parts from the supplier. So this information is helpful mainly to the purchase department to find what purchases has exceeded the limits and then find out why.

If enforcement is needed, please add this as a request with the relevant use case for future considerations.

Thanks

Sampath


Reply