Hire Oracle Fusion and EBS Consultants

Very little Oracle work is a fresh implementation. It is far more often an estate configured eight or twelve years ago, carrying decisions nobody now present made, with reports and interfaces built on top of tables that were never intended to be a public interface.

Archaeology comes before configuration

That makes archaeology the first skill rather than configuration. Before anything is changed, someone has to establish what the system actually does — which is not the same as what the documentation says, and often not the same as what the business believes. The evidence is in the data: which flexfield segments are populated, which customisation still runs, which report is actually opened. Asking the business whether something is still needed reliably produces the answer yes.

What E-Business Suite tolerated and Fusion does not

The second thing that separates people is what they do about a gap. E-Business Suite tolerated almost any customisation, and estates took full advantage. Fusion does not, and the quarterly update cycle punishes anything built outside the supported extension points. A consultant who still reaches for the EBS habits will build something that works in February and breaks in May. The right instinct is to spend longer looking for the supported way to do it.

Supported, in Fusion, has a specific meaning: sandboxes and page personalisation for the user interface, fast formulas where the module provides them, VBCS for a genuine extension, and published REST or FBDI for anything moving data. Direct manipulation of the underlying tables is not a shortcut, it is an undertaking to re-do the work after an update the customer does not control.

Why reporting decides whether the ERP is trusted

The third is reporting, which is where trust in an ERP is actually won or lost. A report that disagrees with the ledger by a small amount is worse than one that is obviously broken, because it will be believed for a quarter. Agreeing where a figure is defined, and computing it once, is duller than building another dashboard and considerably more valuable.

BI Publisher and OTBI answer different questions and are frequently used for the wrong one. OTBI reads the subject areas Oracle maintains and moves with the product; BI Publisher against a hand-written data model gives complete freedom and inherits none of that maintenance. The freedom is occasionally necessary and is always a liability that somebody has to carry.

What a quarterly update actually costs you

The honest answer is that it costs whatever the estate has accumulated, and it is charged four times a year rather than once a decade. That changes the economics of every extension decision made in between.

A proportionate response is a regression pack sized to risk rather than to coverage: the transactions that move money, the interfaces that feed another system, the reports finance actually closes on, and the personalisations that have broken before. Testing everything each quarter is not sustainable and is usually a sign that nobody has decided what matters.

What we interview for

• How the candidate would establish whether a customisation is still in use, using data rather than opinion
• An extension they built inside the supported points, and one they had to argue somebody out of
• What they check before and after a quarterly update, and how that list was chosen
• A report that disagreed with the ledger, and how the difference was traced

When an Oracle consultant is not the right hire

If the change sits entirely inside a module your own team configured and still understands, an external consultant spends the first fortnight learning what your team already knows. That is worth paying for on a large programme and rarely worth it on a single setup change.

If the real problem is that two departments disagree about a process, this is a functional analysis engagement wearing an Oracle badge, and it will not be settled by configuration.

And if the objective is analytics across Oracle and several other systems, the centre of gravity is a data platform rather than the ERP. Building it inside the ERP because that is where the data starts produces reporting that competes with the transactional load and stops at the system boundary.