Hire Oracle and Dynamics 365 Specialists

Most Oracle and Dynamics work is not a new implementation. It is an estate somebody else configured eight or twelve years ago, carrying decisions nobody now present made, with reports and interfaces built on top of tables that were never meant to be a public interface.

So the skill that earns its money is archaeology before change: reading the configuration and the data to work out what the business actually does, separating what is deliberate from what is accident, and then changing the system without breaking the twelve downstream things quietly reading from it.

Archaeology here means evidence rather than interview. Which flexfield segments are actually populated, which custom program has run this year, which report was opened last quarter, which interface still moves rows. Asking the business whether something is needed produces the answer yes about everything, because nobody wants to be the person who agreed to remove the thing that turned out to matter.

The second thing that separates practitioners is what they do with a gap. E-Business Suite tolerated almost any customisation and estates took full advantage; Fusion does not, and a quarterly update cycle punishes anything built outside the supported extension points. Dynamics has the same shape with different names — extension rather than overlayering, and a monthly cadence that turns deferred work into one bad release. Habits formed on the older platform produce something that works in February and breaks in May.

Underneath both sits the data, and usually a considerable amount of PL/SQL that nobody has on an architecture diagram. A meaningful share of an estate’s real business logic lives in packages written over a decade by people who have left, running at two in the morning, on the critical path for the following working day. Changing an ERP without reading that layer is how a modernisation programme acquires a silent regression.

Reporting is where trust in an ERP is actually won or lost, and it is the last thing anybody staffs for. 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.