Breadcrumbs
Home / Case Studies / Data Quality and Standardization / Clean Up Your Data Before Upgrading to R12Clean Up Your Data Before Upgrading to R12
You want to clean up your data before upgrading to R12.
Problem
After years of running E-Business Suite 11.5.9, a global company was planning an upgrade to R12 but realized that it would be difficult to utilize the additional functionality of R12 without cleaning up the data first. While they previously had several sets of books to accommodate different statutory and regulatory requirements as well as different currencies, they wanted to use the subledger accounting features of R12 and use a single primary ledger along with multiple subsidiary ledgers that would handle the local requirements.
Solution
The company used FlexField software to change the accounting flexfields in each set of books to the same chart of accounts and put its accounts in clean logical ranges, standardizing the accounting structure and making consolidated financial reporting easier. They then used eprentise Reorganization software's MS Sets of Books module to consolidate the different sets of books into a single set of books to prepare the instance for subledger accounting with a single primary ledger in R12. Furthermore, the company used eprentise Data Archive software to purge obsolete data and eprentise Data Quality software to eliminate duplicate data.
Frequently Asked Questions
- Doesn’t Oracle E-Business Suite documentation say not to use Oracle database tools to modify Oracle Applications data?
- I’m going to upgrade from 11i to R12 soon. Can I use eprentise or FlexField before the upgrade, and if I do, are there any special considerations?
- What does FlexField software do?
- What happens if something does go wrong and I need to call Oracle Support?
- What is eprentise software?
Solution: Change Sets of Books
Merge or split your EBS sets of books to reflect your current business and to take advantage of EBS features.

Solution: Data Quality
Standardize data (abbreviations, punctuation, etc.) within a single EBS database or across disparate databases.



