Скачать или смотреть Using OIC for Data Migration

Should you use OIC to migrate data? Probably not...but could you?

In general terms there are a few ground rules for data migration.

Firstly, assume that the Client will be using Excel or CSV files. Rarely does data migration use real-time or near real-time processes to obtain data from sources.

Secondly, the data migration loaders need to be re-useable, and the load mechanism needs to be repeatable. Whether you are using FBDI loaders or Web Services to load data, then approach should be systematic.

The third ground rule is to ensure good data validation and subsequent reporting. There is little point in having good feedback channels if the content of that feedback into your data is unusable. Likewise, having good data validation feedback without an easily digestible reporting channel is also pretty pointless.

For this scenario our Client had an issue with migrating existing Contracts into Oracle ERP Cloud using the normal file based loader. It just so happened that Fujitsu had already developed for them a custom OIC REST service integration which takes a payload from Oracle's Configure, Price, Quote (CPQ) application to Oracle ERP Cloud. That inbound payload contains data relating to a Customer Accounts bill-to and ship-to site, details about a new Project plus information relating to an associated new Contract to be created along with related Bill Plan, Revenue Plan and Contract Line details. By taking those reuseable components from that existing set of OIC integrations, we are able to clone them to create new integrations, and tune them for the purposes of file based data migration, rather than real-time end-to-end Web services.

Using OIC for data migration is not something that we would ever recommend, but it can be done.

In this video I cover an approach you could use.