⚓ The world's modern militaries have run their supply chains on enterprise software for more than a decade. The US Army finished rolling out its system in 2018. Germany's Bundeswehr took its version into Afghanistan back in 2011. Japan's Maritime Self-Defense Force? Its equivalent went live in May 2026 — and it is the first time a Japanese central-government ministry has run on an SAP ERP system. This is the story of a conspicuously late arrival, the tangle of legacy systems it finally replaces, and why the company building it cannot afford a "sorry, it broke" moment.

In late May 2026, Fujitsu announced it had delivered a new core business system for the Maritime Self-Defense Force (JMSDF), used by roughly 45,000 personnel. The system pulls together, in real time, the entire inventory the navy touches: parts for ships and aircraft, ammunition, medicine, fuel, food. Stock levels, procurement status and maintenance records from every vessel, base and supply depot in the country now live in one place. It is built on SAP's S/4HANA platform plus a "Defense & Security" solution used by militaries in dozens of countries. And, Fujitsu notes, it is the first SAP ERP ever adopted by a central-government ministry in Japan.

That "first" is the whole story. It sounds like a milestone. It is also an admission of how far behind Japan has been.

Everyone else got here years ago

Strip away the uniform and a military's logistics backbone today is just enterprise resource planning — the same category of software a manufacturer uses to run procurement, inventory and finance. The big armed forces standardized on it long ago, and they overwhelmingly chose one of two vendors: SAP or Oracle.

The clearest example is the United States. The Army's GCSS-Army is an SAP-based ERP that swallowed more than 40,000 aging, stovepiped logistics databases and folded them into a single web-based system — the largest ERP deployment in US Army history. It reached full deployment in early fiscal 2018 and now serves over 100,000 users. The Navy runs its own SAP system for tens of thousands of users; the Air Force and Marine Corps went with Oracle instead. (Even Washington learned this is hard the expensive way: the Air Force scrapped its Oracle-based logistics program in 2012 after sinking roughly a billion dollars into it.)

Germany tells a similar story. Under a massive modernization contract, the Bundeswehr built SASPF — SAP tailored for defense. For the 1st Armored Division alone it replaced five separate, incompatible systems. By 2012 more than 45,000 personnel were using it, and it had already been deployed on operations in Kosovo and Afghanistan in 2011. At the alliance level, NATO members plug national ERP systems into shared logistics planning tools. SAP has described itself as the software of choice for more than a dozen NATO governments, with adopters ranging from Denmark to New Zealand.

So when Japan's navy "modernizes" to an integrated ERP in 2026, it is not pioneering anything. It is arriving at a destination its allies reached eight to seventeen years earlier.

So what was Japan actually running?

To understand the lateness, look at what the new system replaces — and the picture is a museum of Japanese government IT.

The Defense Ministry's own digitization records list a string of separate "legacy system modernization" projects: a Maritime Staff supply system (the so-called "supply three-system"), a separate ship-repair-and-maintenance supply system, a standalone payroll system, a standalone unit-accounting system. Pay, accounting, procurement and maintenance each ran on their own island, built in different eras, sharing little.

The deeper problem was that the three services barely talked to each other. A logistics study in the National Diet Library's collection bluntly flagged the gap: demand planning, inventory management, transport visibility and any cross-service linkage between the Ground, Maritime and Air Self-Defense Forces remained underdeveloped, with supply still run service-by-service. Item numbering had been partly standardized and requisitions had largely been computerized — but the connective tissue, the part that lets a commander see where everything is at once, simply wasn't there.

Why it took this long

Why does a wealthy, technologically capable country lag its allies by more than a decade on something this basic?

Part of the answer is structural. For most of the postwar era, Japan's defense spending was capped around 1% of GDP, and within a tight budget the glamorous end — ships, jets, missiles — competes with the unglamorous "tail" of logistics and back-office IT. Sustainment loses that fight almost everywhere, and it lost it for a long time in Japan. Rigid government procurement and a sprawl of custom-built systems did the rest.

What changed is the security environment. Japan's 2022 revision of its three core security documents put "sustainment and resilience" — the ability to keep fighting in a prolonged contingency — near the center of defense policy, and debate over further revision is ongoing. Fujitsu frames the JMSDF system squarely in that language: real-time visibility of all materiel, faster command decisions, fewer people doing manual work, demand forecasting from data — all in service of keisen nōryoku, the capacity to sustain operations in a crisis. After decades of treating logistics as an afterthought, Japan seems to have decided it can no longer afford to.

Japan and SAP have an uneasy relationship

Here is where the optimism meets a wall of recent memory.

Japan has a conspicuous track record of SAP migrations going badly. The case that lodged in the public mind is confectioner Ezaki Glico. On 3 April 2024, Glico cut over to a new S/4HANA-based core system — and chilled products, including its beloved Pucchin Purin pudding and Café au Lait drinks, vanished from shelves for months as the shipping system seized up. Partial shipments resumed only in mid-June. Press reporting said the project had already slipped more than a year and ballooned to roughly 1.6 times its budget; Glico itself estimated the disruption would knock around ¥20 billion (about $125 million) off annual sales and some ¥6 billion (about $38 million) off operating profit. Around the same time, Unicharm hit shipment delays on diapers traced to a breakdown between its SAP system and its logistics software.

These weren't Fujitsu projects, and the failures share a structural cause rather than a single villain: the temptation to bolt heavy custom add-ons onto SAP instead of adapting the organization to the software's standard processes. There's also timing. SAP's older ERP loses mainstream support in 2027, pushing a wave of Japanese companies to migrate all at once — straining a limited pool of skilled people and all but guaranteeing more stumbles. To a Japanese reader watching pudding disappear from convenience stores, "we put it on SAP" is not automatically reassuring.

Can Fujitsu deliver?

Which brings us to the company in the hot seat, and a question with unusual stakes: is Fujitsu up to this?

There's a genuine case for confidence. Fujitsu didn't just sell SAP to others; it put itself through the same fire. Its "OneERP+" program migrated the company's own group — about 130,000 employees and ¥4 trillion in revenue — onto S/4HANA, billed as the largest SAP deployment by a Japanese company and led by an executive recruited from the top job at SAP Japan. By late 2024 it was being presented at Japan's main SAP user-group event as a success story. The Defense Ministry announcement leans explicitly on this: Fujitsu is applying the hard-won lessons of its own enterprise overhaul to the navy job.

The shadow over that résumé sits in the United Kingdom. Fujitsu built and maintained the Post Office's Horizon accounting system, whose faults helped send more than 900 British sub-postmasters to wrongful prosecution between 1999 and 2015 — one of the worst miscarriages of justice in modern British history. After a 2024 television drama reignited public fury, its global CEO apologized, a senior executive called the Post Office's conduct shameful, the company acknowledged a moral obligation to help compensate victims, and it paused bidding for new UK public-sector work. Horizon was a different system from a different era, not SAP — but it is exactly why "can we trust this vendor with a mission-critical public system" is a fair question, not a cheap shot.

And the stakes here are not pudding. Glico lost a quarter's profit and some goodwill; painful, recoverable. The JMSDF system governs ammunition, medicine, fuel and food for 45,000 people. A wobble during a peacetime go-live can be patched. A failure during an actual contingency — the precise keisen nōryoku scenario the system exists for — cannot be walked back with an apology and a press release.

That is the real test, and it hasn't started yet. The Glico saga taught Japan one lesson above all: going live is not the same as succeeding. The honest verdict on the JMSDF system can only be written over years of stable operation — and over whether Fujitsu's stated ambition to extend the platform to other Defense Ministry agencies and ministries earns the trust to do so. For now, Japan has caught up to where its allies stood a decade ago. Staying caught up, without a "whoops," is the harder part.

Japan ran its military on a patchwork of disconnected systems for decades, and is only now consolidating. How does your country's military handle the unglamorous machinery of supply — and would you trust a private contractor to run it?

References