I’ve been looking at our current ERP setup. We’re still on Microsoft Great Plains, but I’m starting to plan how Oracle EBS could improve our manufacturing workflows. Before committing to any configuration, I focus on three areas:
Process Mapping
I sketch out every step in our existing GP-based order-to-cash and procure-to-pay cycles, noting where delays or manual workarounds occur. My aim is to ensure that when we set up analogous processes in EBS, the transition feels natural rather than forcing teams to learn entirely new steps overnight.
Master Data Cleanup
In my experience, over-hasty data loads cause the most headaches post-go-live. I’m working with the materials and finance leads to standardise item codes, supplier names and cost centres in our GP system. That way, when we build out EBS’s item hierarchies and costing structures, the foundational data is already consistent. A clear naming convention means fewer mismatches in reports later on.
Pilot Definition
Rather than switching the whole site at once, I plan to define a small pilot, perhaps one production line or one warehouse. We’ll configure a simple inventory organisation and run a parallel cycle: receive material in EBS, compare on-hand balances with GP, and review costing to ensure both systems align. If that smoke test succeeds, we expand to the next area.
By mapping processes, cleansing master data and keeping the first pilot small, I’m confident we can avoid the common pitfalls of rushing an ERP rollout. It keeps disruption to a minimum and gives the team confidence in each step before scaling up.
I’ve covered the next stages separately: migrating the data, customising workflows, and getting the reporting right.