- OracleApps Epicenter - http://www.oracleappshub.com -
Data Conversion,Migration and interface ..Why important
Posted By Sanjit Anand On June 9, 2007 @ 2:14 am In Conversion | 68 Comments
Do you know how many ways; we can enter the data into oracle application. Most of us can guess three different ways as:
But those who works in some complex business environment may figure out some of more like:
And there are many more, but most of these are used for master data, and few cases for transaction data via Open interface if available.
Importance of data conversion/migration and interfaces within any ERP implementation project can't be ignored. Since ERP mostly deals with data which finally leads into Information , thus it is equally important to understand the aspect how "data" is important in any ERP system specailly in implementation phase, no matter how simple and unified operation is. Since I been involved in some big transformation oracle apps project thus It is a absolute a good cause to share some information about integration touch point, conversion/migration and interface development to someone who is very new to ERP world as well as Oracle application.
Let's start with some common situation, we have three cases,
The answer of the 1 is data migration and 2 is more pronounced as data conversion where as thirds is popularly known as Interface. The ways these are working haven't much difference but it is more important to understand definition and need. I never found any big difference between migration/conversion unless there is huge transformation of data, the only things figure out is conversion might required some less steps to perform, as assumption is that set up related stuff been already been taken care before execution of activity.
Let's understand like this: Data Migration as a process of moving required (and most often very large) volumes of data from our clients' existing systems to new systems. Existing systems can be anything from custom-built IT infrastructures to spreadsheets and standalone databases. Data conversion can be defined as a process of converting data from one structural form to another to suit the requirements of the system to which it is migrated.
Lets take a deep drive to understand better:
Why conversion/Migration is more important in ERP?
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. Initial data can be migrated by any other means as discussed above depending upon cetain paramater like Volumn, usage, complexity , business rule etc..
How we Define Data Conversion
What Is An Interface then
Does the conversion/migration/interface have Life Cycle
Yes, they have, because they have a significant efforts required in development and design and implementation
Conversion is assumed as one time activity but never looks like small activity which can be performed with couple of days.
How conversion and interface differ?
There are good numbers of parameter on which they can be categorize. Take few of them:
You have learned how interface is differ from Conversion/Migration. Now lets take few types of interfaces:
Normally in any system , there are two kinds of interface as:
- An inbound interface receives data from one system (legacy) and inserts into Oracle open interface tables.
- A typical inbound interface would follow these steps:
- Extract data from legacy system into a flat file.
- Use SQL*Loader or equivalent tool to upload information into a temporary table.
- Write a PL/SQL program to take data from the temp table and insert into the Open Interface Tables.
- Through the concurrent manager in Oracle Applications, run the standard Oracle Interface program to transform interface tables into Oracle data.
o An outbound interface takes data from Oracle tables and inserts it into an external system (via tables or flat file).
o A typical outbound interface would follow these steps:
- Write a PL/SQL program to extract data from Oracle base tables into a flat file.
- Use a custom program to read that data and post it into the legacy system
Do we have some other standard way to do interface?
What Is An Open Interface Table (OIT)?
Oracle Interface Program
Examples of standard import programs:
- GL: Journal Import
- AP: Payables Open Interface
- AR: Customer Interface
- INV : Item Import
- AR - Autoinvoice
Ok, thats is all about Conversion and Interfaces briefing. I will write some more for Tools used for Conversion/Interface and will discuss some granular details about a conversion/migration project and share some information about how and where AIM's documents fits into conversion and Migration projects. So watch out this space for some more stuff for conversions.. Till than..your comment and requset you to share some information relaeted to these areas.
Article printed from OracleApps Epicenter: http://www.oracleappshub.com
URL to article: http://www.oracleappshub.com/conversion/data-conversionmigration-and-interface-why-important/
URLs in this post:
 : http://www.oracleappshub.com
 : mailto:email@example.com
 : mailto:firstname.lastname@example.org
 : mailto:email@example.com
 : mailto:firstname.lastname@example.org
 : mailto:email@example.com
Disclaimer The opinions expressed here represent solely my own represent personal conjecture based upon experience, practice and observation and does not represent the thoughts, intentions, plans or strategies of my current & previous employers and their clients. Copyright © 2007-2010 OracleApps Epicenter. All rights reserved.