Software maker Oracle is four years into a massive project to consolidate its internal ERP systems. The effort grew out of a simple query from CEO Larry Ellison: He wanted to know how many employees Oracle had worldwide.
“Guess what we had to do? We had to go out and pull information from 70 different systems,” says Bret Fuller, senior vice president of information technology for applications at Oracle.
At the time, Oracle was running 70 instances of its financials software – basically one instance per country, Fuller says. Each instance ran on separate hardware with its own database. By the time the staff information was extracted from the systems and pooled together, a few days had passed and no one was sure if the employee headcount was still accurate, Fuller says.
Today Oracle has whittled its systems down to three instances: its soon-to-be-solo master instance, which today serves Oracle offices in the Americas, Eastern Europe and most of Asia Pacific from the company’s Austin, Texas data center; a Western Europe instance serving offices in Western Europe, Africa and the Middle East; and a Japan instance.
By October the Western Europe and Japan instances will be migrated to the master instance, and Oracle will have a single, global database for all of its financial systems, Fuller says.
Oracle decided to consolidate its ERP systems for three primary reasons: to improve the quality and availability of information; to reduce hardware, facility and personnel costs; and to move to standardized processes and shared services.
Since starting the project, the company has made significant progress migrating to common processes, Fuller says. When Oracle first started its consolidation efforts, the company had 12 standard business flows. The company now has close to 50. And whereas different countries once had different application portfolios, today all offices are outfitted with a company-standard 42-module application footprint, Fuller says.
“Everybody worldwide is running the same products and using the same processes,” Fuller says. For example, revenue recognition rules are consistent from country to country, as are expense approval hierarchies. This makes it easier on financial staff, as well as on IT staff, Fuller says. “When there’s an application problem, it’s much easier to diagnose and correct,” he says.
In years past, finance used to be a country-level operation, Fuller says. Converting to standard processes required not only technology changes but also cultural changes. Oracle had to overcome the mindset that every country needs unique systems, Fuller says. “Countries are special in terms of some local legal issues and customs,” he says. “But in general, business processes can be implemented on a global system while still supporting the unique requirements of any given country.”
Having standardized its financial processes, Oracle worked to set up regional service centers to consolidate tasks that previously were handled by individual offices – such as booking of orders, accounting, cash management and expense processing.