data migration in e-business suite

Data Migration in E-Business Suite

Draft

Revision: 06/22/2011

of 17 05/05/11

Table of Contents TABLE OF CONTENTS ...................................................................................................1

1 OVERVIEW............................................................................................................3

1.1 Challenges ...................................................................................................................... 3

1.2 Setup and Data Migration Options .............................................................................. 3

1.3 Types of data .................................................................................................................. 3

2 MIGRATION – USING OPEN INTERFACE / API ..............................................4

3 MIGRATION – USING PROVIDED BY ORACLE UTILITIES ...........................5

4 MIGRATION – USING THIRD PARTY TOOLS ..................................................7

5 USING ISETUP FOR SETUP DATA MIGRATION ..............................................8

5.1 What can be Migrated Between Instances ................................................................ 8

5.2 Usage Scenarios............................................................................................................. 9

6 REVISION HISTORY .........................................................................................11

7 GLOSSARY OF TERMS .......................................................................................12

8 REFERENCES ......................................................................................................13

9 APPENDIX A - ISETUP ......................................................................................14

9.1 iSetup Templates in R12 ............................................................................................. 14

9.2 iSetup Financial Setup Selection Set Parameters in R12 ....................................... 14

of 17 05/05/11

of 17 05/05/11

1 Overview

1.1 Challenges Different project scenarious in E-Business Suite Implementation, instances consolidation, migration to new platform or just Re-Implementation when moving to R12 have many challenges in providing smooth and reliable data and setup migration process:

Tight deadlines Multiple environments Squized time for migration activities Multiple legacy systems to integrate with or to consolidate into one instance

100% data quality requirement Complexity of the overall setup model

1.2 Setup and Data Migration Options Using open interface / API Utilities provided by Oracle Third Party Tools

1.3 Types of data

At very high level there are at least three types of data need to be migrated:

Setup Data (Application Object Library (AOL) data) o Profiles o Flexfield definitions

Master Data o Items o Customers o Suppliers

Transaction Data o Purchase Orders o Invoices

of 17 05/05/11

2 Migration – using open interface / API This is the most used and simple method for conversion purposes. It is a multi-step process:

• Extract: Get the date from the legacy system database and save into flat files or temporary database. • Cleansing/enrichment: Remove not needed data and enrich with new data elements • 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

Good approach is to run the conversion programs in the E-Business Suite as concurrent programs for security / accessability / traceability. The process includes set upof a document with the file structure definition describing the data requirements to be met by the legacy data. Data cleansing and enrichment should be done prior to extract of legacy data orin a temporarymetadata layer before the load step. Load program is just a generic shell script taking name of SQL*Loader control file as parameter. There Validate and Transfer programs need to be created per each interface.

Staging tables Core tables

of 17 05/05/11

3 Migration – using provided by Oracle utilities Here are some of the utilities provided by Oracle that can be used in setup and data migration/conversion process:

Utility Name

Usage FNDLOAD iSetup ADI ACMP

Setup Yes Yes No Yes

Master No Yes No Yes

Transactional No No Yes No

Extract Yes Yes Yes Yes

Import Yes Yes Yes Yes

OA Instans to OA Instance Yes Yes Yes Yes

Anything to OA Instance No No Yes No

Custom Patch Management No No No Yes

FNDLOAD

• 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.

FNDLOAD is a developer tool that migrates data between Oracle Application instances. It is executed at the

UNIX command line or via unix scripts created by the developer. Oracle provides configuration files for AOL setup data, HR setups and AME. These configuration files define the parent and child entities to be downloaded and uploaded. This “out of the box” standard functionality ensures a reliable, repeatable

process to migrate setup data between instances.

iSetup • Load original configuration multiple times • Load modified configuration • Load extract • Load subset of extract

ADI • ADI is a well known 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).

The Import Text File feature allows you to import data from legacy systems, third party payables applications,

barcode scanners, or any other flat data file sources, to your worksheet. Using the Import Text File feature, you can map fields in your source file to fields in your worksheet. Once you have created the map using the Import Text File feature, you can save it and apply it to future conversions. ACMP

Application Change Management Pack(ACMP) has three noteworthy new capabilities:

of 17 05/05/11

• Customization Manager: Takes all files associated with a custom application, report or

extension and bundles them into an Oracle patch. Standard AD utilities can then be used to

apply the patch to different Apps instances.

• Patch Manager: Auomates many of the manual tasks associated with applying EBS patches,

as well automates installing patches in multiple EBS instances.

• Setup Manager: Automates the migration of configuration/setup data across instances.

Provides over 300 functional APIs (AOL, Financials, Manufacturing, Distribution) for setup data

management.

of 17 05/05/11

4 Migration – using Third Party Tools In the table below some of the available Third Party Tools are listed along with their general usage features:

Company/Tool

Usage DataLoad Classic /

Professional

Mercury

WinRunner

Mercury Object

Migrator

Various Adapter/

Connectors - Insevo,

Librados,

iWay Software

Setup Yes Yes Yes Yes

Master Yes Yes No Yes

Transactional Yes Yes No Yes

Extract No No Yes Yes

Import Yes Yes Yes Yes

OA Instans to OA

Instance Yes Yes Yes Yes

Anything to OA Instance Yes No No Yes

DataLoad Software is offered in two versions – Classic and Professional.

• 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.

Mercury WinRunner

• 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.

Mercury Object Migrator

• 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. Various Adapters/Connectors

• Usually they provide Bi-directional connectivity • Any application, any platform, any data structure, any message type • Reduced risk

of 17 05/05/11

5 Using iSetup for Setup Data migration iSetup is a module provided within the E-Business Suite that allows you to easily migrate setups using a user-friendly interface. You’ll work through E-Business Suite screens rather than at the Unix level, so you do not have to be a programmer or DBA to feel comfortable using this tool. iSetup includes templates that make it easy to move commonly migrated objects, and, unlike our other two options, iSetup documents the

configuration changes to allow you to compare changes across instances and timelines.

iSetup is the nearest Oracle provided alternative to FNDLOAD that meets some of the needs for change

management. iSetup is ideal during implementations and is a front end functional tool. iSetup additionally has the advantage of being able to migrate application data where FNDLOAD is only for setup data.

However, several significant limitations are a factor in the change management process:

• iSetup does not consider the owner or timestamp in order to preserve the seeded data or most recent

version of data. iSetup migrates data only in the primary language. • There are no multi-language capabilities. • More significantly for change management, iSetup has limited ability to migrate specific objects. In

some cases, filters are available to migrate individual setups such as a single concurrent program, but in many cases, it’s all or nothing.

• The source and target instance must be at the same patch level for iSetup.

• iSetup is not an option during the upgrade process even for a point release upgrade. • Finally, iSetup will not migrate Approvals Management entities and needs FNDLOAD and ADI to provide

better coverage of the migration scope.

In R12 iSetup is completely rewritten and no additional license required. It allows you to migrate setups and data between OraApps Instances and Operating Units. It allows also to create a snapshot of setups then run

difference reports to see “What has changed all of the sudden…”.

5.1 What can be Migrated Between Instances The following list demonstrates items that can be migrated in iSETUP in addition to FNDLOAD:

• Discrete Mfg and Distribution Setups • Payroll Elements • Employees • Product Foundation • Financials Operating Units • Profitability Manager Setups • Financials Setups Suppliers • GL Daily Rates • Transfer Pricing Setups • Organization Structure • XML Publisher

Full list of R12 iSetup extraction templates can be found in Appendix A to this document A full list of the Financial Setup Selection Set Parameters can be found in Appendix A to this document.

of 17 05/05/11

5.2 Usage Scenarios There are many scenarios where Oracle iSetup can be used. Following are some of these:

Migrate Data The CRP instance is configured and ready for test by the quality team. Now, you need to:

1. Migrate select configuration to the test instance.

2. After testing, modify the configuration in the CRP instance.

3. Migrate the configuration to the production instance.

Migrate Data

Transform Data The test instance is configured. Using Oracle iSetup you have extracted the data. You

want to transform select data and load to the target instance. Oracle iSetup helps you to

transform the data and load it to the target instance.

Save Configuration Extract data from an instance using Oracle iSetup. The extracted data is stored in the

Oracle iSetup repository. You can download this data and save it in an external

repository.

Report on Current Configuration Generate a report on the extracted data available in the Oracle iSetup repository. This

report can be viewed online or downloaded in different formats. The report can also, be

sent to a functional analyst. The Reporter module enables this functionality.

of 17 05/05/11

Comparison Reporting Compare the differences in data between the production instance and the test instance.

Configuration notes:

o The Source and Target instances must be on the same patchset before migrating setup

data. Also, the ATG Family Pack level has to be the same. o A user must have an account on both the source and target instances. o The DBC file name is case-sensitive, so be careful when filling out the Instance Mapping

screen. o The file $TNS_ADMIN/sqlnet.ora on both the source and target instances must have the

corresponding instance invited. o MetaLink Note: 560719.1, “How to troubleshoot iSetup issues” references some patches for

performance issues and java.lang.OutOfMemory Errors.

of 17 05/05/11

6 Revision History

Date Draft Author Changes

06/21/2011 0.1 M.Mihaylov Document creation

06/22/2011 1.0 M.Mihaylov Document updated

of 17 05/05/11

7 Glossary of Terms

of 17 05/05/11

8 References Metalink Note: 256.1 - Upgrade Advisor: Oracle E-Business Suite Financials and Projects Upgrade from 11.5.10.2 to 12.1.3 and 12.1.2 Metalink Note : 453137.1 - Oracle Workflow Best Practices Release 12 and Release 11i MetaLink Note: 560719.1 - How to troubleshoot iSetup issues Metalink Note: 1097333.1 - Installation And Configuration Management Troubleshooting

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=256.1

https://support.oracle.com/CSP/ui/flash.html#tab=KBHome(page=KBHome&id=()),(page=KBNavigator&id=(from=BOOKMARK&bmDocID=453137.1&bmDocType=REFERENCE&bmDocTitle=Oracle%20Workflow%20Best%20Practices%20Release%2012%20and%20Release%2011i&viewingMode=1143&bmDocD

https://support.oracle.com/CSP/ui/flash.html#tab=KBHome(page=KBHome&id=()),(page=KBNavigator&id=(from=BOOKMARK&bmDocDsrc=KB&bmDocType=TROUBLESHOOTING&bmDocID=560719.1&bmDocTitle=How%20to%20Troubleshoot%20iSetup%20issues&viewingMode=1143))

https://support.oracle.com/CSP/ui/flash.html#tab=KBHome(page=KBHome&id=()),(page=KBNavigator&id=(from=BOOKMARK&bmDocDsrc=KB&bmDocType=TROUBLESHOOTING&bmDocID=1097333.1&bmDocTitle=Installation%20And%20Configuration%20Management%20Troubleshooting%20Notes&vie

of 17 05/05/11

9 Appendix A - iSetup

9.1 iSetup Templates in R12 Template Name Description

General Foundation This Selection Set is used to migrate AOL Foundation set ups.

Product Foundation This Selection Set is used to migrate Foundation set up needed before migrating any other setup data for other products.

Organization Structure This Selection Set is used to migrate the Organization Structure set up.

All Profile Options This Selection Set is used to migrate all exportable profile options.

Employees This Selection Set is used to migrate Employees data.

Financials Setup This Selection Set is used to migrate Financials setup.

General Ledger Daily Rates This Selection Set is used to migrate General Ledger Daily Rates setup.

Suppliers This Selection Set is used to migrate Suppliers setup.

Discrete Mfg. and Distribution This Selection Set is used to migrate the Discrete Manufacturing and Distribution setups.

Financials Operating Unit Level Setup

This Selection Set is used to migrate operating unit level setups in Oracle Payables, Oracle Receivable and Cash Management modules.

Payroll Element This Selection Set is used to migrate HRMS Payroll Elements.

Australian Leave Liability This Selection Set is used to migrate Australian leave liability setup.

Profitability Manager Setups This Selection Set is used to migrate Profitability Manager setups.

Transfer Pricing Setups This Selection Set is used to migrate Transfer Pricing Setups.

Projects Setup This Selection Set is used to migrate Projects setup.

Personalizations This Selection Set is used to migrate Personalizations

XML Publisher This Selection Set is used to migrate XML Publisher Metadata, Templates, Translations, XML Sample and Schema

Payroll Element This Selection Set is used to migrate HRMS Payroll Elements.

Australian Leave Liability This Selection Set is used to migrate Australian leave liability setup.

Profitability Manager Setups This Selection Set is used to migrate Profitability Manager setups.

9.2 iSetup Financial Setup Selection Set Parameters in R12

Name

Supports Update

Financials Setup

General Ledger

Currencies

Chart Of Accounts

Accounting Calendars

Budgets

Code Combinations

Conversion Rate Types

Statistical Units of Measure

of 17 05/05/11

Encumbrance Types

Accounting Setups

Ledger Sets

Data Access Sets

Journal Reversal Criteria

Accounts Payable

Financials Options

Payables Options

Payables Payment Terms

Special Calendars

Aging Periods

Distribution Sets

Invoice Tolerances

Invoice Approvals

Withholding Tax

Reporting Entities

Payment Process Profile

Expense Templates

Accounts Receivable

Receivables System Options

Receivables Payment Terms

Receivables Transaction Types

Transaction Sources

Memo Lines

Auto Accounting

Approval User Limits

Receivables Territories

Receivables Activities

Invoice Grouping Rules

Invoicing Rules

Line Ordering Rules

Auto Cash Rule Sets

Receipt Sources

Receipt Classes and Methods

Collectors

Customer Profile Classes

Statement Cycles

Aging Buckets

Fixed Assets

Asset System Controls

Asset Quick Codes

Asset Locations

Asset Keywords

Asset Depreciation Calendars

Fiscal Years

Asset Prorate Conventions

Asset Book Controls

of 17 05/05/11

Asset Categories

Cash Management

System Parameters

Bank Account Uses

Bank Accounts

Transaction Codes

Payment Documents

Credit Management

Credit Management Setup Options

Credit Management Scoring Model

Credit Management Check Lists

Credit Management Automation Rules

Public Sector Financials

Budget Organizations

Summary Templates

Budgetary Control Groups

Transaction Codes

10