Copyright 2003 Accenture. All rights reserved. Accenture, its logo, and Accenture Innovation Delivered are trademarks of Accenture. Data Migration in Oracle E-Business Suite OAUG Paris, June 18, 2004 Trond Steensnaes

Project Scenario Challenges: Tight deadlines 5-15 Environments Squeezed time for migration activities Numerous legacy systems to integrate with 100% quality requirement

Agenda Introduction Migration to Oracle – Migration to Oracle – using open interface / API – Migration to Oracle – Oracle Utilities – Migration to Oracle – Third party tools Migration from Oracle

Introduction: Migration scenarios Data migration: moving data from one database to another. Types of migration: Migrating in an upgrade process Migrating legacy data in a new implementation Migrating between CRP, Test and Prod instances Propagating master reference data

Introduction: Types of Data Setup Data (Application Object Library (AOL) data) – Profiles – Flexfield definitions Master Data – Items – Customers Transaction Data – Purchase Orders – Invoices

Agenda Introduction Migration to Oracle – Migration to Oracle – using open interface / API – Migration to Oracle – Oracle Utilities – Migration to Oracle – Third party tools Migration from Oracle

Migration to Oracle Supported: - Entering data via the UI - Using Open Interfaces / API’s - Using Oracle data migration utilities Not supported: - Direct manipulation of the data in the database.

Agenda Introduction Migration to Oracle – Migration to Oracle – using open interface / API – Migration to Oracle – Oracle Utilities – Migration to Oracle – Third party tools Migration from Oracle

Migration to Oracle – using open interface / API Sample usage of open interfaces for conversion purpose: 3-step process: Load: Get the data from the flat file into the staging table Validate: Assess the quality of the data by calculating and evaluating metrics. Transfer: Insert data into interface table / call APIs with values in staging table Run the conversion programs in the E-Business Suite for security / accessability / traceability.

Migration to Oracle – using open interface / API Load program: generic shell script taking name of SQL*Loader control file as parameter. Validate program: 1 per interface. Transfer program: 1 per interface. Staging tablesCore tables SQL*LoaderAPI’s

Agenda Introduction Migration to Oracle – Migration to Oracle – using open interface / API – Migration to Oracle – Oracle Utilities – Migration to Oracle – Third party tools Migration from Oracle

FNDLOAD Usage: OA Instance OA Instance Setup Master Transactional Extract Import Moves OA data between database and text file representations. Can be modified with any editor Use to synchronize databases during new installations or maintenance. Good for moving data between test and prod instances, e.g. in upgrade projects. Command-line based tool, requires technically skilled personell to execute No cost, well documented. Migration to Oracle – Oracle Utilities

FNDLOAD An example of downloading is: FNDLOAD 0 Y DOWNLOAD testcfg.lct out.ldt FND_APPLICATION_TL APPSNAME=FND An example of uploading is: FNDLOAD 0 Y UPLOAD fndapp.lct fnd1234.ldt – Oracle Applications System Administrator’s Guide, Appendix C

iSetup Usage: OA Instance OA Instance Setup Master Transactional Extract Import Load original configuration multiple times Load modified configuration Load extract Load subset of extract Migration to Oracle – Oracle Utilities iSetup.oracle.comCentral instance Target instance iSetup ConfiguratoriSetup Migrator iSetup Reporter

iSetup Typical scenario: 1. Configurator -> CRP 2. Migrator -> Systemtest 3. Migrator -> Production - Complete or partial collection of data - Copy data within the same instance (e.g. from one OU to another) Oracle iSetup User Guide Migration to Oracle – Oracle Utilities

ADI Usage: Anything OA Instance Setup Master Transactional Extract Import ADI is a spreadsheet-based extension of Oracle Applications. Limited to GL and FA data Import Text File feature to simplify work with Oracle Assets. (Assets and physical inventory). Applications Desktop Integrator User’s Guide Migration to Oracle – Oracle Utilities

Agenda Introduction Migration to Oracle – Migration to Oracle – using open interface / API – Migration to Oracle – Oracle Utilities – Migration to Oracle – Third party tools Migration from Oracle

DataLoad Classic Usage: Anything OA Instance Setup Master Transactional Extract Import Automated loading using copy & paste If there is a form for it, DataLoad can insert data into it Freeware, no support Quick and easy Not suitable for large volume loads, ‘out of sync’ problem. Migration to Oracle – Third party tools

DataLoad Professional Usage: Anything OA Instance Setup Master Transactional Extract Import Automated secure loading Fast because load is processed on the middle tier Inexpensive Requires some technical skills Suitable for medium volumes Rerun load multiple times in test environment until 100% successful. Migration to Oracle – Third party tools

Mercury WinRunner Usage: Anything OA Instance Setup Master Transactional Extract Import A testing tool, but has functionality that makes it suitable for automating data load Work similarly to DataLoad Classic, but more reliable. Records keystrokes and creates playback script for you. Expensive If you have it for testing, might as well use it for migration too. Migration to Oracle – Third party tools

Mercury Object Migrator Usage: OA Instance OA Instance Setup Master Transactional Extract Import Utilizes FNDLOAD Runs as a concurrent program within OA Version control, reporting capabilities, rollback functionality Useful if you have to synchronize lots of instances or require elaborate version control. management/extensions/object-migrator.html Migration to Oracle – Third party tools

Various adapters / connectors Usage: Anything Anything Setup Master Transactional Extract Import Insevo (formerly Taviz) Librados iWay Software Bi-directional connectivity Any application, any platform, any data structure, any message type Reduced risk Migration to Oracle – Third party tools

Agenda Introduction Migration to Oracle – Migration to Oracle – using open interface / API – Migration to Oracle – Oracle Utilities – Migration to Oracle – Third party tools Migration from Oracle

Make your own customized outbound interfaces using Materialized views - Customizations must be non-invasive - Complete control - Several pitfalls: - A change in any column in any table, even if it not selected in the MV definition, will lead to refresh of the MV - Cannot distinguish between inserts and updates of the MV - Triggers work differently on MV’s than regular tables

Migration from Oracle Business Event System - Most significant events are predefined - Define your own events - Elegant way to trigger workflow activities / custom logic - Non-invasive

Questions? Trond Steensnaes Consultant, Accenture Phone: