Solution blueprint
Oracle E-Business Suite to Fusion Cloud, finance first
There is no upgrade path from EBS to Fusion. It is a re-implementation, which means you get to redesign the chart of accounts, and you have to rebuild every integration.
The situation
A company runs Oracle E-Business Suite 12.2 for finance and procurement, with years of customizations and a long list of reports. There is no support deadline forcing a move: Oracle’s Lifetime Support Policy places EBS 12.2 Premier Support through at least 2036. The driver is operational: they want quarterly feature updates without upgrade projects, less infrastructure to maintain, and one platform as they grow.
Because Fusion is a different product, nothing converts. The decision to make early is sequence: which pillar first, and how long the two systems coexist.
Constraints that shape the plan
- No hard deadline, so the business case must stand on its own merits.
- Customizations in EBS that have real business value and no standard equivalent.
- A chart of accounts that nobody likes but that every report depends on.
- Quarterly Fusion updates, which affect test plans and templates between rehearsals.
- Auditors who will ask how opening balances were established.
- A finance team that has to keep closing the books through the project.
What is designed, rebuilt and retired
Designed fresh in Fusion
- Chart of accounts and segment structure
- Legal entity and ledger setup
- Approval workflows
- Role and segregation-of-duties design
A re-implementation is the one chance to fix a structure everyone has lived with.
Rebuilt
- Integrations with banks, payroll and operational systems
- Reports in OTBI and BI Publisher
- Data extracts for the warehouse via BICC
- Extensions, as supported configurations rather than code changes
Count these early. Teams underestimate the report and integration inventory more than anything else.
Migrated
- Suppliers, customers, items and employees
- Open payables, receivables and purchase orders
- General ledger opening balances
- Fixed assets with cost and depreciation
- A limited amount of history
Loaded with FBDI templates and REST APIs, in dependency order, and reconciled.
Retired
- EBS customizations with no business value
- Reports nobody has opened in a year
- Interfaces to systems that no longer exist
Project value often comes as much from what you stop carrying as from the new platform.
The load sequence at cutover
- Setup Configuration and reference data
- Master data Suppliers, customers, items
- Open items Payables, receivables, purchase orders
- Balances General ledger and assets
- Reconcile Counts, totals, samples
- Approve Finance sign-off
- Open Users in Fusion
The approach, phase by phase
Phase 1: Assess and design
Six to ten weeks.
-
1
Inventory customizations, reports and integrations
With an owner and a decision for each: standard, rebuild, retire.
-
2
Chart of accounts design
Workshops with finance, a mapping from the old structure and agreement on how history is reported.
-
3
Enterprise structure design
Legal entities, ledgers, business units and inventory organizations.
-
4
Data strategy
What migrates, what is archived, how much history, and the load method per object.
-
5
Sequence decision
Which pillars in which phase, and the coexistence rules while both systems run.
Phase 2: Configure and build
Ten to sixteen weeks.
-
6
Configure Fusion
In a test environment, with design workshops confirming the standard process before extending anything.
-
7
Build integrations
Bank, payroll and operational interfaces, using Oracle Integration or REST, with error handling.
-
8
Build reports
OTBI and BI Publisher, prioritized by the list finance actually uses.
-
9
Build the data loads
FBDI templates and mappings, with validation and a rejection report per object.
-
10
Design security
Roles, data access and segregation of duties, reviewed with internal audit.
Phase 3: Test and rehearse
Eight to twelve weeks.
-
11
Load rehearsals
At least three, each with counts, rejects and timings recorded.
-
12
Process testing
Unit, then end-to-end: procure to pay, order to cash, record to report.
-
13
Parallel close
Run a close in both systems and compare, where the risk justifies it.
-
14
Integration testing
Each interface, including bank formats and failure handling.
-
15
User acceptance
Finance and procurement users, with defects triaged daily.
Phase 4: Cut over and stabilize
Cutover plus four to six weeks.
-
16
Cutover runbook
Load order, timings from rehearsal, reconciliation checkpoints and the rollback decision.
-
17
Final loads and reconciliation
Balances tied out, exceptions owned, finance sign-off recorded.
-
18
Go-live and hypercare
Daily triage, a defect log and a named transition date to support.
-
19
Quarterly update readiness
A regression test pack so each Fusion update is a routine event.
-
20
Next phase
Supply chain or HCM, using the integration and reporting foundations already built.
Phase names and order change with the engagement. This is a typical shape, not a fixed method you would be held to.
The kind of team this needs
Roles can be ours, yours or shared. Where you only need people rather than a project owner, the same roles are available through staffing.
Typical deliverables
- Customization, report and integration inventory with decisions
- Chart of accounts and enterprise structure design, signed by finance
- Data migration strategy and field-level mappings
- Integration specifications and build
- Report inventory with rebuild priority
- Security and segregation-of-duties design
- Rehearsal records with counts, rejects and timings
- Reconciliation pack and finance sign-off
- Cutover runbook, rollback plan and hypercare plan
- Quarterly update regression pack
What usually goes wrong, and what we do about it
-
Trying to recreate every EBS customization
Each one gets a decision in phase one. Rebuilding all of them in a cloud product with quarterly updates is the most expensive mistake available.
-
Reports and integrations left late
They are counted in week one and built in phase two, because they are usually the largest single body of work.
-
Dirty data loaded then fixed
Cleansing happens before loading, with business owners approving the rules.
-
Quarterly updates breaking tests
A regression pack is built during the project, not after, and release notes are reviewed each quarter.
-
Chart of accounts designed by IT
Finance owns it. We facilitate and document; the structure is theirs.
-
Audit questions about opening balances
The reconciliation pack and the sign-off are prepared as audit evidence from the start.
Questions people ask
Should we move at all, given support runs to 2036?
That is a genuine question and the honest answer is sometimes no. We will tell you if staying on EBS and investing there is the better call for your situation.
Can we do finance and HCM at once?
You can, but it doubles the design, testing and change load at the same time. Phasing is usually lower risk unless there is a reason to do both.
Do you provide the whole team?
We can, or we can supply the specialists you are missing while your team leads. Both arrangements are normal.
How much history should we bring?
Enough for operations and for what your auditors and regulators require. Everything else belongs in an archive you can query, not in the new system.
Related
-
Oracle
Oracle Fusion Cloud ERP, SCM and HCM implementations, EBS to Fusion migration, Oracle Integration, reporting and analytics, OCI and database work.
-
Oracle data migration
Extract, map, validate, load and reconcile legacy and EBS data into Fusion using FBDI and HDL, with balance-level proof at every cycle.
-
ERP implementation
SAP, Oracle, Dynamics 365 and Workday implementations covering design, configuration, data migration, integration, testing and hypercare.
-
SAP ECC to S/4HANA conversion
A brownfield conversion for a manufacturer with heavy custom code and a short downtime window.
Have a technology challenge? Let’s work out the approach.
Discuss a project
Tell us the current system, the target and the timeline. A technical lead replies to talk about scope.
Start the project briefRequest technical talent
Need consultants inside your team rather than a project owner? Send the requirement.
Request talentBecome a partner
Delivery firm, staffing supplier or consulting partner? Register your company.
Register as a partner