Data Conversion in Oracle

1. Slide 1
APAC Project Management
AIM CRP Overview
Customer Presentation
Data Conversion
Customer Presentation

2. Slide 2
APAC Project Management
AIM CRP Overview
CONVERSIONS
Data Conversion - REQUIREMENTs
Conversion Requirements are contained in the CV010 and include the following:
-Systems to be Converted. - Applications on Old System.
-Order to be Converted – required sequence of conversion
-Business Entities - Conversion List
-Disposition – Manual or Programmatic
-Legacy Source - Source System and Number of Records
(amount of historic data)
-Timing - One Time -(at Transition to Go-Live)- or Periodic.
-Target Application - in the New System

3. Slide 3
APAC Project Management
AIM CRP Overview
CONVERSIONS
CONVERSION TERMINOLOGY
The Conversion Strategy (CV020) addresses the following Conversion activities:
Download Programs - Creation of the Download Programs from Legacy
ASCII Flat File - A Comma or space delimited, variable or fixed format data file
from the existing system should be generated.
Upload Program - To upload direct to Oracle relational Database Interface Tables
on Target System
Interface Tables - A temporary table which mimics the target production table, this
provides a location to manipulate and translate the data as needed before validating the
data and loading the application production tables.
Translation Programs - Scripts to translate data from the existing system format
into useful data for the Oracle target application. -Alternative is Manual Entry
Interface Programs - The interface program scripts are used to populate the
production database with the result from the Translation Programs.. May be through
direct database load or through API .
Application Production Table - Final production data table where the
converted data resides.

4. Slide 4
APAC Project Management
AIM CRP Overview
CONVERSIONS
Data Conversion - CONCEPTS
DATA
CONVERSION
OLD System NEW System
There are four main Challenges in Data Conversion:
 Mapping - Mapping the data available in the Old System to the data
required by the New System.
Conversion - Collection of the Old Data and Converting into a format
suitable for the New System.
Quality – Ensuring that the New Systems Data is clean and unique.
Performance –Ensuring that any data conversion processes required for
Transition or ongoing Maintenance can operate in the time
windows available.

5. Slide 5
APAC Project Management
AIM CRP Overview
CONVERSIONS
Data Conversion - MAPPING
The output of the mapping is Data Mapping Spreadsheets that show what is
needed for the Oracle target application processing to meet business
operational requirements and where these data elements will come from.
 Problem 1- Data required by the New System does not exist on the Old
System
 Problem 2- Single Field Information on the Old System contains data
required in multi field layout in New System.
 Problem 3. -Data Field formats not matched between Old and New
Systems.
 Problem 4.- Historic Data - To Convert or to Archive – that is the
question
 Problem 5- Data required on the New System that requires complex
calculations using multiple fields in Source System

6. Slide 6
APAC Project Management
AIM CRP Overview
CONVERSIONS
Data Conversion - MAPPING
Example (a) - PROBLEM 1. - Data required on the New System that
does not exist on the Old System
Consider for example a Telco Billing System.
The Old System may have had only 2 Fields for Customer Address –
Namely:- “Mail Address” & “Service Address”
The New System for example may have 4 Fields for Customer Address
– Namely:- “ Mail Address , Service Address , eMail Address &
Billing Address”
In this case the Conversion Consultants will have to agree with the
Customer as to the strategy for population of the additional Fields. The
decision may be to embark on a program to create data and enter for
those Fields, to enter it manually before go live or to leave the the Fields
vacant and populate them manually & progressively as Customers call
in to the live system.

7. Slide 7
APAC Project Management
AIM CRP Overview
• Flexibility of General Ledger’s COA – The structure of flexifield
(COA) may be tailored to suit your business needs
• Improves Management reporting and Analysis
• Flexible account classification for reporting to different authorities
• Validation Rules may be defined to prevent the entry of
combinations that should never exist.
Example: Chart of Accounts Conversion
CONVERSIONS
Example (b) Mapping of Chart of Accounts (COA) to Oracle Accounting Key Flexfields
1010065001120000 Mapping
Oracle Key Flexifield Segments
GL Accounts Code
(Single Field on Old System)
Seg 1
Company
Seg 2
Cost
Center
Seg 4
Seg 3
Natural
Account Product
10.100.650011.20000
Company Cost
Center
Natural
Account
Product