Anda di halaman 1dari 11



Introduction Methods Data Migration Interfaces Data Conversion Key points Data Conversion at AHUS

Before Go-Live in the production environment the required master data, the open transaction data and the historical transaction data need to be imported from the old legacy applications to Oracle Applications. Since data structure and data design in legacy systems are different from those of Oracle Applications, data need to be messaged/ converted satisfying the business rules to suite the Oracle requirement.

We will discuss various techniques for moving data from one system to another. Such data transfer is divided into mainly three types depending upon the techniques used for this purpose. Data Migration Data Conversion Interface

Data migration is just what migration means (moving something from one place to another): a) moving data (in its associated database) from one hardware platform to another hardware platform (as when the hardware is upgraded ), b) moving the data from one version of a DBMS (i.e. Oracle 2.0) to a new version of the DBMS (Oracle 2.1), as when the DBMS is upgraded, or c) moving the data into a test or quality assurance database for test purposes. Data migration requires very little if any conversion. It is just moving data around, but the physical data model remains the same.

These are programs for connection between Two Systems In Order To Synchronize the Data. Used repeatedly and should therefore be designed and constructed in the most efficient manner possible. These can be triggered by an event (such as running a concurrent program) Or it can be scheduled to run at a certain time. Can be very costly to construct and maintain.

Data conversion is just what conversion means (changing from one form to another): (a) converting customer data from MySQL to Oracle because you changed DBMS provider, or (b) converting data from your transactional database every night into the data warehouse, or (c) converting data in your relational DBMS into XML documents, or (d) converting customer data that's in an Oracle database to a new schema still in an Oracle database, but the application changed and so did the physical schema. Conversion involves changing the format of the data because of any number of reasons.

Key Points..
Data Migration Moving large data One time process Executed before Go-Live Functional setups involved in process Complexity depends upon data mapping activity Data Conversion Moving small data One time process Executed before Go-Live Mostly setups done prior Complexity depends upon data mapping activity Interface Synchronizing data Ongoing process Executed during production Setups done already Complexity in coordination with other system

Can be manual or automated

Extensive testing and preparation Source and target schema are identical

Can be manual or automated

Extensive testing and preparation Source and target schema are different

Can be manual, batch or real-time

Lesser effort for testing Source and target schema can be different


In AHUS solution, data conversion is being performed for moving data from Oracle application to R12.1.3. For this purpose, templates have been prepared by the project team for various modules. These templates include fields according to the R12 database tables.

Created templates for fields in R12 for each module Mapped template fields to 11i database table columns. Prepared SQL scripts to fetch data from 11i database tables. Registered the scripts as concurrent programs generating .csv files containing the required data. Then conversion team will perform data validations, formatting and cleansing to install data into new system R12.