Field Notes: The 24-Hour Delay That Ended a Cost Variance Problem for Good

As ERP Architect, I stepped into an on-premise Oracle EBS to Oracle Cloud (Fusion) migration at a decades-old manufacturer. Before the migration work could really start, I found a live operational problem underneath it.

The company builds to customer-specific configuration only. Every sales order generates a unique part number, built manually off a spreadsheet. The BOM for that part number is auto-created overnight, then reviewed and edited the next day by a material coordinator. Once finalized, the system emails accounting to roll the standard cost.

The problem: the work order was auto-created and released to the shop floor before the BOM existed. Production could start building against a BOM that hadn’t been finalized yet — and was often still being edited by the material coordinator the next morning. By the time the work order closed and the item shipped, cost accounting was chasing large, unexplained standard-cost-to-work-order variances on every custom job, with no clear source.

Beyond that, inventory control was minimal — one auto-generated work order per sales order pulled inventory, adjustments happened only when stock physically couldn’t be found, and BOMs were manually maintained with no governance around when or how they changed.

The fix wasn’t a system redesign. I put a 24-hour delay on work order release, so the BOM was finalized before production could pull against it. Leadership resisted the delay — it looked like it would slow the shop floor down. It didn’t. It eliminated 100% of the standard-cost-to-work-order variance issue, immediately.