What is eprentise software?
eprentise hd_suite is a family of functional modules used to manipulate the data in Oracle E- Business Suite (EBS) while maintaining consistent and correct data. For many solutions, it runs one time, propagating all changes throughout your existing EBS data and then is removed from the EBS instance. It gives you the ability to make changes to your EBS that used to be available only through a reimplementation.
What can I do with eprentise software?
With eprentise software you can reorganize, split, divide, or consolidate OEBS instances, and clean up the data within an instance or across multiple instances.
- Reorganize the business structure within an instance. You can:
- Move transactions from one set of books, operating unit, or legal entity to another.
- Move, legal entities between SOBs.
- Change accounting calendars.
- Change currency
- Divide an Oracle application instance into two or more consistent and correct instances.
- Consolidate two or more application instances to take advantage of a single shared source of business data.
- Consolidate inventories within an instance. You can also change the valuation of inventories.
- Propagate data quality standards throughout one or more instances, including elimination of duplicate master data records.
- Change key flexfield (KFF) segments and values, such as Sales Territories or Asset Categories, and reflect the change in the existing transactional data.
In what kind of situations would I use eprentise?
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.
How much does an eprentise project cost? How long do the projects take?
We suggest that our customers plan from one to six months for most projects, depending on the complexity. Consolidations are usually complex and will typically take between six months and a year. We welcome the chance to talk with you about the type of project you are contemplating. After a few discussions we will create a project profile which will include the estimates of the schedule, costs and required resources. It usually takes a few weeks of discussions and discovery for us to create and present a proposal.
What does FlexField software do?
FlexField runs one time, changes your data, and then is removed from the E-Business Suite instance. FlexField transforms an existing accounting flexfield’s segment structure, values, code combinations, and CCIDs according to your mappings, and applies the new code combinations and CCIDs. It propagates the change throughout your existing E-Business Suite data, everywhere the accounting flexfield is used. It removes the old code combinations and CCIDs, and aligns the new Chart of Accounts (COA) so that all balances belonging to a single CCID are summarized into a single line.
What happens after I run FlexField and change my COA?
Your E-Business Suite looks like the new COA has been in use since you first implemented Oracle. The database is functionally and technically consistent and correct.
Other FAQs:
