Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Data migration

6,340 views

Published on

  • Be the first to comment

Data migration

  1. 1. Data Migration in Oracle E-Business Suite OAUG Paris, June 18, 2004 Trond Steensnaes trond.steensnaes@accenture.comCopyright 2003 Accenture. All rights reserved. Accenture, its logo, and Accenture Innovation Delivered are trademarks of Accenture.
  2. 2. Project ScenarioChallenges:• Tight deadlines• 5-15 Environments• Squeezed time for migration activities• Numerous legacy systems to integrate with• 100% quality requirement
  3. 3. 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
  4. 4. Introduction: Migration scenariosData 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
  5. 5. Introduction: Types of Data• Setup Data (Application Object Library (AOL) data) – Profiles – Flexfield definitions• Master Data – Items – Customers• Transaction Data – Purchase Orders – Invoices
  6. 6. 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
  7. 7. Migration to OracleSupported:- Entering data via the UI- Using Open Interfaces / API’s- Using Oracle data migration utilitiesNot supported:- Direct manipulation of the data in the database.
  8. 8. 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
  9. 9. Migration to Oracle – using open interface / APISample 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 tableRun the conversion programs in the E-Business Suite for security / accessability / traceability.
  10. 10. Migration to Oracle – using open interface / APILoad program: generic shell script taking name of SQL*Loader control file as parameter.Validate program: 1 per interface.Transfer program: 1 per interface. SQL*Loader API’s Staging tables Core tables
  11. 11. 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
  12. 12. Migration to Oracle – Oracle UtilitiesFNDLOADUsage: OA Instance OA InstanceSetup Master TransactionalExtract 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.
  13. 13. Migration to Oracle – Oracle UtilitiesFNDLOADAn example of downloading is:FNDLOAD apps/apps@devdb 0 Y DOWNLOAD testcfg.lct out.ldtFND_APPLICATION_TL APPSNAME=FNDAn example of uploading is:FNDLOAD apps/apps@custdb 0 Y UPLOAD fndapp.lct fnd1234.ldt –Oracle Applications System Administrator’s Guide, Appendix C
  14. 14. Migration to Oracle – Oracle UtilitiesiSetupUsage: OA Instance OA InstanceSetup Master TransactionalExtract Import iSetup.oracle.com Central instance Target instance iSetup Configurator iSetup Migrator iSetup Reporter• Load original configuration multiple times• Load modified configuration• Load extract• Load subset of extract
  15. 15. Migration to Oracle – Oracle UtilitiesiSetupTypical scenario:1. Configurator -> CRP2. Migrator -> Systemtest3. Migrator -> Production- Complete or partial collection of data- Copy data within the same instance (e.g. from one OU to another)http://isetup.oracle.com, Oracle iSetup User Guide
  16. 16. Migration to Oracle – Oracle UtilitiesADIUsage: Anything OA InstanceSetup Master TransactionalExtract 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
  17. 17. 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
  18. 18. Migration to Oracle – Third party toolsDataLoad ClassicUsage: Anything OA InstanceSetup Master TransactionalExtract 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.http://www.dataload.net/
  19. 19. Migration to Oracle – Third party toolsDataLoad ProfessionalUsage: Anything OA InstanceSetup Master TransactionalExtract 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.http://www.dataload.net/
  20. 20. Migration to Oracle – Third party toolsMercury WinRunnerUsage: Anything OA InstanceSetup Master TransactionalExtract 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.http://www.mercury.com/us/products/quality-center/functional-testing/winrunner/
  21. 21. Migration to Oracle – Third party toolsMercury Object MigratorUsage: OA Instance OA InstanceSetup Master TransactionalExtract 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.http://www.mercury.com/us/products/it-governance-center/change- management/extensions/object-migrator.html
  22. 22. Migration to Oracle – Third party toolsVarious adapters / connectorsUsage: Anything AnythingSetup Master TransactionalExtract ImportInsevo (formerly Taviz)LibradosiWay Software• Bi-directional connectivity• Any application, any platform, any data structure, any message type• Reduced riskhttp://wwws.sun.com/software/connectors/
  23. 23. 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
  24. 24. Migration from OracleMake your own customized outbound interfaces usingMaterialized 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
  25. 25. Migration from OracleBusiness Event System- Most significant events are predefined- Define your own events- Elegant way to trigger workflow activities / custom logic- Non-invasive
  26. 26. Questions?Trond SteensnaesConsultant, Accenturetrond.steensnaes@accenture.comPhone: 0047 93011983

×