Skip to main content

IFS Tracks tested: App9 and App10 [Haven’t really tested in the latest versions] 

 

For me, it dosen’t make sense to use the RMB option on the PO header / lines ‘Confirm with Differences Via Change Order’ since it really doesn't enforce a POCO, rather it does the job without a POCO. What do ya’ll think? I think it needs to be corrected. 

Previous post on the Community tThread closed, so cannot really post there] :

Apps10: Purchase Order Change Order (Enforced) Prom/Plan Delivery Dates | IFS Community

Can I bounce on this please to make sure my understanding is correct? 

If you don’t want to use it or don’t like the way the RMB operates, why not just hide it from use?

 

We enforce change orders for all purchase orders, but have not found the lack of change order on this one instance at the very start to be a problem.

I’ve always viewed it as this:  We can raise a purchase order for anything we want for any requested date we want, but it doesn’t become a real contract with the supplier until they provide a confirmation.  It is really from that point that the PO needs to track the changes, which it does.

For me….it isn’t broken.

Reply


Terms & ConditionsCookie settings