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?