Farewell Oracle® EBS - A Smooth Exit

© 2017 eprentise. All rights reserved.| 1
Farewell Oracle® EBS:
A Smooth Exit
Transforming Oracle® E-Business Suite
Helene Abrams
CEO
eprentise

Webinar Mechanics
• Submit text questions.
• Q&A addressed at the end of the
session. Answers will be posted within
two weeks on our new LinkedIn Group,
EBS Answers:
http://www.linkedin.com/groups/EBS-
Answers-4683349/about
• Everyone will receive an email with a link
to view a recorded version of today’s
session.
• Polling questions will be presented
during the session. If you want CPE
credit for this webinar, you must answer
all of the polling questions.

Objectives
Objective 1: Explore reasons why companies may
choose to move away from EBS now or in the
future.
Objective 2: Explore why restructuring an existing
EBS environment beforehand is the best approach
for migrating.
Objective 3: Learn steps to streamline your EBS
environment for a more efficient, cleaner and
faster transition.

Agenda
Introduction
Business Scenarios and Challenges for…
▪ Multiple Instances
▪ Different Charts of Accounts
▪ Divestures
▪ Multiple Calendars
▪ Unused Data
Why eprentise?
▪ Out-of-the-box Software
▪ Proven Methodology and Approach
Benefits
Roles and Responsibilities and Project Post-Steps
Getting Started

Consolidate Multiple EBS Instances
Change Underlying Structures and
Configurations
▪ Chart of Accounts, Other
Flexfields
▪ Merge or Split Ledgers or Sets
of Books, Operating Units,
Legal Entities, Inventory
Organizations
▪ Calendars, Currency, Costing
Methods
▪ Asset Revaluation, Inventory
Valuation
Separate Data for a Divestiture
Reduce Operating Costs and Increase
Efficiencies
eprentise Can… …So Our Customers Can:
Adapt to Change
Avoid a Reimplementation
Reduce Complexity and Control Risk
Improve Business Continuity, Service
Quality and Compliance
Streamline Operations with Visibility
to All Parts of the Business
Establish Data Quality Standards and
a Single Source of Truth
Companies Need to Change Their Oracle®
E-Business Suite Without Reimplementing
Finished But Not Done®

eprentise Transformation Solution
Ultimately Generates the
Single Source of Truth
Transformation Engine
▪ Metadata transformation specific to product (documented &
undocumented)
▪ Rules learned automatically during each implementation
▪ Knowledge acquired from product and process
▪ Converts all historical data including financial with100%
accuracy.
Copy, Change, Filter, and
Merge functionality
identifies and transforms the
required rules into business
functions
Metadata Analysis
▪ Knowledge Repository – intelligent, learning and building
from each successive implementation
▪ Rules Engine
▪ No need for data mapping
▪ User interface

The Business Scenarios
You’ve been acquired
▪ The acquiring company does not use Oracle E-Business
Suite (EBS)
▪ The plan is to move to SAP or Dynamic or Netsuite or
another ERP system within the next two years
You are moving to Oracle Cloud (Fusion)
▪ There is no direct migration path to Oracle Cloud from
EBS
You have been divested from a parent company
who used Oracle EBS, and you need a smaller,
stand-alone footprint that you can manage with
fewer resources

Challenge: Multiple Instances
Data needs to be extracted from multiple systems
▪ Different formats in each system
▪ Different configurations in each system
▪ Ledgers, Operating Units, Inventory Orgs
▪ Charts of Accounts
▪ Calendars
▪ Inconsistent business processes
▪ Duplicate data
▪ Master data
▪ IDs (document sequence numbers, invoice numbers, etc.)
▪ Multiple interfacing systems and customizations
Coordination and synchronization of extracts
▪ Multiple teams – possibly of hundreds of technical consultants for each
team
▪ Different extract scripts, error handling, unit testing of code

The Solution: Consolidate Instances
Automatically find differences among instances
Automatically resolve conflicts
Automatically create the mapping from source(s) to target
instance
Consolidation represents the union of all the data including
history in each of the instances with duplicates, conflicts, and
configuration differences resolved
Only need to create extract scripts for one instance in order to
migrate to new ERP
Added benefits
▪ Significant immediate cost savings until EBS exit is complete
▪ Little modification to CEMLI objects that already exist in the target
▪ Users see the same data, used in the same way as in their original
instance so the transition is smooth.

eprentise Consolidation

eprentise Compare Reports

Automatic Conflict Resolution
Between Source and Target
Three Types of Changes:
ID Changes
ID of Source data
(and all related
data)is changed so
there is no conflict
with target IDs
Synchronization
Source Data is identical to
target data but with different
IDs. In that case, the ID of
the source (and all related
data) is synchronized with
the target ID
Name
Changes -
Source data is
renamed so
there is no
conflict with
target names

Poll Question

Challenge: Different Charts of Accounts
You have many different charts of accounts
▪ Many systems do not accommodate multiple charts
of accounts
▪ You need many external products/modules/features
(HFM, custom reports, GL Consolidation, secondary
ledgers, etc.) to close each month
▪ Each of those charts of accounts will need to be
transformed before migrating into the new system
Your chart of accounts does not match the
acquired company’s chart of accounts

The Solution: Change Charts of Accounts
with FlexField® software
There is no software product like eprentise’s FlexField product
for EBS for any other ERP system
Add additional segments
Eliminate redundant information across segments
Eliminate unused values
Restructure to align with the new ERP and new business
requirements
Allow for growth in existing segments
Simplify for financial management, shortening the close cycle,
reporting, compliance with statutory and regulatory
requirements, and integration with 3rd party applications

FlexField Software to Change your EBS
Chart of Accounts
Map Segments and Values
or Code Combinations
Changes CCID everywhere
• All setups
• All subledgers
• All history
• Looks as though the
new chart of accounts
was part of the original
implementation
• Full audit trail, drill
down, roll up
• Built in exception
reporting

Challenge: Carve-out is Sold to Different
Company
You have been divested from a parent
company who used Oracle EBS, and you need
a smaller, stand-alone footprint that you can
manage with fewer resources
Acquiring company doesn’t want all divisions
Acquiring entity is planning on doing a flip of
selected lines of business
Only a few divisions are going to be integrated
into the new ERP

Solution: eprentise Divestiture Software
Limit the data to be migrated to the new
system
Filter on any criteria, and on multiple criteria
Specify Retain or Delete

Challenge: Different Calendars
There may be a statutory or regulatory requirement to
have a different year-end, change the number of
periods, or to change the period dates to align with an
acquiring company’s systems.
In the case of an acquisition, preparing consolidated
financial reports and revaluing assets must be
completed shortly after the acquisition date.
It is useful to have year-over-year reports and
projections with the same periods to obtain an accurate
financial picture of an acquired company.
Multiple calendars require additional custom extract,
transform, and load scripts and make the migration to a
new system more difficult.

Challenge: Too Much “Unused” Data
Challenge: Streamline and Simplify
Over time, as companies grow by acquisition and sell parts of their
business, EBS accumulates data that the current business does not need
▪ Historical data from an acquired system that does not belong to the current company
▪ Data from divisions that have been divested
▪ Modules that are no-longer in use or have been replaced by another system
▪ Localizations that are not needed for the new company
Ledgers, operating units, inventory orgs are redundant and make EBS
more complex
▪ Data that exists after a “start-over” when a new ledger or legal entity or operating unit was
created and the old, historical data is beyond the required retention period
▪ Migration is more complex when there are duplicate business processes
▪ The “garbage-in”, “garbage-out” means that reporting and operations in the new system
will inherit the same issues that you had within your EBS environment that made your close
cycle longer, reconciliation more complex, and required extensive use of spreadsheets and
third-party systems
▪ Data in the new system will not be complete, consistent, and correct

Solution: eprentise Reorganization
Software
Copy, Change, Filter, and
Merge functionality
identifies and transforms
the required rules into
business functions

Proven Out-of-the-Box Software Products

Poll Question

eprentise Software Methodology – All Automated, Intelligent
Mine and validate rules
▪ Based on relational database patterns (documented and undocumented)
▪ Constraints (unique, primary and foreign-keys)
▪ Column names
▪ Functional purpose
▪ Domains and usage
▪ Sequence of transformation operations
▪ Automated discovery tools find approximately 90% of rules
▪ Analysis/discovery of other 10% of rules
▪ New rules discovered through projects are tested and added to the rules repository
▪ Rules are validated (impact, completeness, applicability for all customers)
Compare sources and targets
▪ Every table, every column
▪ Every database object
▪ Reports generated
Automatically generate mappings
Resolve conflicts
▪ Duplicates
▪ Conflicting IDs, names
▪ Synchronize and rationalize sources and targets
Copy, Filter, Change and Merge from sources to targets
Validate results

Why is the eprentise Transformation Solution Different Than Traditional
Consulting Migration, Integration, or Conversion Projects?
Complex business challenges can not be met with typical conversion approach:
▪ Data between disparate systems doesn’t lend itself to simple mapping
▪ Effect of change on underlying database structure complicates the process
▪ Users and engineers are often unaware of these intricate, complex issues
▪ Changes can impact thousands of tables and columns
What transformation offers over conversion:
▪ Maintaining database integrity
▪ Ultimate delivery of consistent data
▪ Complete, 100% accurate set of historical financial (and other) transactions
▪ Ability to support various situations (mergers and acquisitions, divestiture etc.)
▪ Increased data quality
▪ Repeatable process reduces risk
Consistency and completeness:
▪ Code is dynamically generated to implement required changes which eliminates coding errors
▪ Rules execution engine saves the time and cost of custom coding and error handling, and reduces the risk
of compromising the data integrity
▪ Definition, design and re-use of rules
▪ Permits modeling scenarios as requirements change
Enables fastest and safest time-to-value:
▪ Improves accuracy and predictability Reduces project timelines and costs, allowing IT executives to more
efficiently manage the project

The Benefits
Planning for the Transition with eprentise
Clean data to go into a new ERP
Simplified structures that reflect the current business
environment
Easier and faster migration path to new ERP
Alignment of the business
Easier for users to recognize their data in a new environment
Clean audit trail before the move
Less expensive than trying to transform the data once you are
in the new environment
Ability to purge data that is no longer needed for the new ERP

eprentise Offers a Competitive Solution
No other software products in market for any transformation for any other ERP
Many system integrators have scripts that they run
▪ Equivalent to custom code for each customer
▪ No standard, out-of-the box extract, transform scripts from EBS
▪ Has not gone through extensive testing, code review, or impact assessment
▪ Requires very qualified technical consultants or there is a significant risk of data corruption or violating
the relational integrity
▪ Qualified consultants are not readily available and are only assigned to one project at a time.
Most often for eprentise customers the competitive solution considered was a
reimplementation (setting up a new environment, or a new organization unit from scratch).
The alternatives:
▪ Typically migrate only a year’s data and beginning balances
▪ Data is extracted, transformed and loaded into new environment
▪ Requires maintaining a sunset environment for audits, compliance, and historical data
▪ Often takes more than a year, and can cost millions of dollars
Neither migration scripts or a reimplementation can accommodate changing requirements
either during the duration of the project, or afterwards without a significant amount of
recoding

eprentise Value Proposition
Transformation with 100% Accuracy
Proven track record
▪ eprentise software has been successfully
utilized to support over $120 billion of
merger, acquisition and divestiture deals
within the last two years
▪ Software product company with unique
approach to common business issues
▪ Success stories – Many Fortune 50
companies
▪ 100% Customer satisfaction
Competitive advantages
▪ Much lower cost of implementation
(product vs. services)
▪ Unique knowledge set developed from
years of use
▪ Proprietary, patented, proven technology
Benefits of eprentise approach
▪ Maintains database integrity
▪ Retains all history
▪ All conflicts resolved
▪ Reduces risk
Efficiency gains because of shorter
project duration with fewer
resources translates to lower costs
▪ Repeatable results, reusable as
requirements change
▪ Requires significantly less time and
resources than consulting efforts
Accurate, consistent results
▪ No need to worry about different
coding styles, standards, skill levels,
corrupting database, differences in
different versions
▪ Eliminates need to “qualify”
consultants on technical skills
▪ Generates code automatically
without technical knowledge
No need for external mapping,
data warehouse, or reporting to
reconcile different businessesSoftware, not Consulting
Transformation, not Migration or Integration

Oracle Support
Oracle will support R12.1 until December 2021
Oracle will support R12.2 until September 2023
Not on the below diagram, but Oracle will be releasing version
12.3 sometime in 2019 and it will be supported for 10 years
(until sometime in 2029).

eprentise Project Resources
(eprentise)
▪ Account Manager
▪ Customer Delivery Engineer (CDE)
▪ Technical Team
(customer/partner)
▪ Client Project Manager (PM)
▪ Client Database Administrator (DBA)
▪ Client System and/or Network Administrator
▪ Client Functional Team
▪ Client Technical Team

eprentise Tasks, Roles & Responsibilities
Preparation
▪ Analysis Phase (Divestitures/Complex Projects)
▪ Rules Analysis / Identification of Source and Target/ Fit to Requirements
▪ Run Book
Software Runs
▪ Iterative Process
▪ Rule Revisions
▪ Validation of Results (backend)
▪ Software Execution and Performance
▪ Run Book Modifications
▪ Software Quality Assurance
Product Support
▪ Patches
▪ Issue Resolution
Remote with Many Concurrent Projects

Poll Question

Client/Partner Tasks, Roles &
Responsibilities
Project Manager
▪ Project Plan, Client Resources/Schedule
▪ Status Meetings and Reports
▪ Client Liaison
▪ Tracking Testing/Issues
Database/System/Network Administrator
▪ Access for eprentise Team
▪ Negotiation with Hosting Company
▪ Standard Database/System Administration, Maintenance, Patching
▪ Instance Strategy, Preparation of Test and Reference Instances, and Environment Refresh
▪ System and Database Performance
Functional Team
▪ Testing, Recording of Issues, Requirements Changes, Reporting of Results
▪ Testing Includes Full Close Cycle for Each Module, Running of Standard Reports, Creation of New Transactions,
Update of Open Items
▪ Pre- and Post- Steps
Technical Team
▪ CEMLI Objects
▪ Reconfigure and/or Reload of Data Warehouse

Example Post-Change Steps
(Not Covered by Software)
Hard-Coded (RICE-W Activities)
▪ Interfaces to third-party systems
▪ Data Warehouse
▪ Reports
▪ Workflows
▪ OFA – Oracle Financial Analyzer
▪ ADI Templates
Uses Ranges
▪ Approval Assignments
▪ Budget Assignments
New EBS Features
▪ New Modules/Functionality
▪ Some Configuration – New CoA,
Ledgers
▪ Upgrade to R12
Definition of target
Testing and Cutover Strategy
and Execution
Example COA Rules (Use
Business Logic)
▪ Cross Validation
▪ Consolidation
▪ Account Derivation Rules
▪ Accounting Generator
▪ Roll-up Groups
▪ Security Rules
▪ Summary Templates
▪ Mass Allocations
▪ Costing and Revenue
Recognition Rules
▪ Descriptive Flexfields
▪ “Auto” - anything

Getting Started
Client Download Site
▪ Diagnostic script
▪ FlexField software download
▪ Articles, data sheets, project plans
▪ Project expectations
System Requirements for eprentise
▪ Access
▪ Server, OS, and DB details
▪ Reference instance
License Requirements for FlexField
▪ Name of source COA
▪ Server, DB details

Questions?

Thank You!
Helene Abrams
407.591.4950
habrams@eprentise.com
- One World, One System, A Single Source of Truth -
www.eprentise.com
www.agilitybydesign.com

Farewell Oracle® EBS - A Smooth Exit

More Related Content

What's hot (20)

Similar to Farewell Oracle® EBS - A Smooth Exit (20)

More from eprentise (18)

Recently uploaded (20)

Farewell Oracle® EBS - A Smooth Exit