and where and how you can detect a change to the required information.
If you want it change by change and all the data is available in tables in your oracle DB then one way would be to get the Oracle DBA to set up a table and punch a pseudo transaction in there (within a trigger say)
Like Part X price changed from Oldvalue To Newvalue at time X.
Don't forget new parts, parts being deleted, you might also want to make the design extensible so you can do 'on order' and expected by etc.
Then you write an other process to suck data out of this table, process it into Mysql, and on success either mark it as done for oracle to delete, or delete it yourself.
Obviously you'll need to harden this up, for comms failures, missing changes on either side etc.
The advantage is the abstraction and the minimal dependency. Change from Oracle to DB2, or MySQL to postgreSQL should have very little impact on the comms process between the two systems. Equally a pseudo transaction will mean you can describe each communication with meta information. If you get the recipient to log and bin ones it doesn't understand you can develop the two systems separately(given an agreed spec !)
For instance you could pass the content of the message as an xml snippet.
A little extra work and you've got a web service!
If you can get away with say once an hour, or over night then you could do it on a report/export basis.
Oracle produces all changes since X and saves it some how, you pick it up and process it.
The other option is not to keep that data in the web system at all, but to pull it from the IBM when you need it. Speed and robustness will need to be good for that though or your web application will die a horrible death. I'd be real wary before I put something like that into place.
How much buy in have you got from the IBM side, have you a budget/commitment for them to help you meet the need?
If there's no timestamped transactional data, you are going to have to do a compare and find differences, that's generally inefficient and flaky.
Also do you have (or may want to) to send data back (orders , allocations) etc.
It's not rocket science, but to get the best system you need your guys and the IBM/Oracle chaps to sit down and design something that will last, both in terms of robustness and future business changes.
HTHs