Consider eprentise in situations like these: 

• A merger or acquisition where both parties run E-Business Suite.
• The set-up of E-Business Suite is more than 3-5 years old and doesn’t support the business.
• There are inconsistencies in different parts of the organization.
• The business is supporting several different instances of E-Business Suite.
• Business reorganization, shared service center, and IT consolidation scenarios.
• The database is very large and different subsets of data are needed for testing.
• There is a lot of duplicate data (suppliers, customers, products).
• Divestiture or spin off of part of the business.

This M&A scenario is an example. 

• Company A sells its Division M to a competitor, Company B. Both companies, A and B, run E-Business Suite. Company A runs eprentise Divestiture to split off a copy that contains all of Division M’s business (but none of A’s confidential information). Company A continues to run its main instance, which retains Division M history. It gives the new Division M instance to Company B.
• Company B may choose to run Division M in a stand alone manner until the end of their fiscal year. The instance is functionally complete, consistent, and correct. One optional change would be to run our FlexField software to transform the Division M instance to use the Company B Chart Of Accounts (COA). That would make it easier to consolidate the financial reports between Company B’s main instance and Division M.
• Next, Company B would run eprentise Consolidate to combine the Division M instance into its main instance. They would add all of Division M’s history and open business transactions, setups that define how Division M transactions work, plus other data like Division M’s customers, suppliers, and employees into Company B’s E-Business Suite instance.