In simple terms, we create a Purchasre Order Change Order (POCO) when we need to make a change to a particular Purchase Order that we are working with. The standard behaviour, even in apps 10 is that when a POCO exists, the user is always asked to make changes via change orders. If you try to make a change on the PO, then the system will give an error, notifying you that no changes are allowed when a POCO is connected, which is a valid error. 

A customer who is in apps 8, is concerened about this error and they are of the view that this error should not pop-up and the user should be allowed to change the Delivery address under the misc info tab in the supplier window, even if a POCO exists. This is not possible with the standard functionality. 

However, I found the bug 120640 which addresses this error which comes up when we try to change the delivery address on the PO when a POCO exists. But, it doesn’t seem to make any sense of resolving the issue. It says, this error occurs only when the two supplier addresses have two different delivery terms which is not the real behaviour, according to my testing. Even if the two addresses have the same delivery terms, it still gives the error. The solution suggested by the bug is to change the supplier address via the change order. This is anyway the standard way of doing it. If the user wants to change the supplier delivery address, he can simply create another change order (Provided that a POCO already exists), alter the address and then update PO. This is quite straightforward. 

My question is, if someone has noticed and applied this patch (120640), what was the correction done? Did it allow to change the delivery address or make any other change directly on the PO, when a POCO ecxists.? Please exlain.