No doubt there'll be a bit of Oracle kicking but maybe one ought to look at the client.
According to the article the changes are "necessary and largely a result of additional requirements and internal requirements changes,"
As a now retired Oracle implementation consultant I still remember trying to establish what the client actually needed as opposed to what the requirements asked for. All too often those doing the job aren't involved in defining the requirements.
The result was often me trying to convince the client that, because they didn't understand what they needed, they would have to stump up more cash. Obviously the client might think I'm just trying to increase our revenue.
Sometimes they would agree and raise the necessary change requests, other times it was "Implement per requirements!" only for that to cause more problems later on.
Of course Oracle ERP isn't the right option for every organisation (although I implemented Oracle ERP at one public sector client back in 1998 and they are still using it). Sometimes it's the client that causes problems. And sometimes it's the implementor, especially when trying to keep costs low.
Bugger I miss work sometimes