The Go-Live War Room
At an automotive components manufacturer (names and operational specifics have been altered to protect identities), the go-live war room is in full swing. The CIO walks the CEO through dashboards showing UAT completion at 98%, ATP confirmations at 100%, and no critical defects outstanding. Fiori tiles reflect stability across MM, PP, SD, and FI. The implementation partner confirms that MRP Live runs are clean, production orders are converting correctly, and financial postings reconcile within tolerance. From every formal lens, the system appears ready.
What the System Is Saying
In SAP terms, everything checks out. ATP in VA02 confirms delivery dates based on available stock and planned receipts. MRP (MD01N) generates planned orders without exception messages. Production orders (CO02) are released, components issued via MIGO, and confirmations posted through COR6N. FI postings flow automatically through integration points, with goods movements updating inventory and financial ledgers in sync.
In Lydian speak, this means one thing: the system behaves exactly as it was designed to behave.
What the Business Is Experiencing
Now step onto the shop floor. The same company runs a dress rehearsal using real demand conditions. A sales order for 5,000 brake pad assemblies is entered. ATP confirms 3,000 immediately and promises the rest in four days. On paper, this looks precise.
In reality, the production line stalls after 1,200 units. MRP assumed 85% efficiency because that is what was configured during testing. The plant actually runs at 65% due to machine downtime and operator variability. Steel plates required for production are stuck at port, and the goods receipt is delayed. Even when they arrive, putaway into storage location lags because warehouse operations are not synchronised.
In plain business English, this is not a system issue. This is a factory that cannot produce what it promised to sell.
How SAP Makes It Look Better Than It Is
SAP continues to report “On-Time Confirmation: 95%” and “No MRP Exceptions.” Why? Because SAP records what has been posted, not what is physically happening in real time. If goods receipt is posted late but backdated, ATP still sees availability. If production confirmations are partial, the system still considers the order in progress. If inventory sits in quality inspection or pending putaway, MMBE shows stock, but it is not usable.
In Lydian speak, SAP is not lying. It is telling the truth based on the inputs it receives. The problem is that the inputs are incomplete representations of reality.
Where Finance Starts to Disagree
Now the CFO steps in. Production has posted 1,200 finished units into inventory, triggering FI entries that debit inventory and credit WIP. Sales has already invoiced 3,000 units based on ATP commitments. The financial system reflects revenue, but the physical inventory is not there. GR/IR accounts show mismatches due to valuation differences in incoming materials. Variances begin to accumulate in cost settlement.
Translated into business terms, the company has recognised revenue for products it has not yet fully produced and is carrying inventory values that do not match operational reality.
What the CEO Thinks Is Being Approved
The CEO is being asked to approve go-live based on a system that has passed SIT and UAT, where transactions executed correctly under controlled scenarios. The belief is that operations will continue seamlessly, customers will receive orders on time, and financial reporting will remain stable.
This assumption is reasonable. It is also incomplete.
What the CEO Is Actually Signing Off
The CEO is not signing off on SAP configuration, or even on testing success. The CEO is signing off on whether the enterprise can run its entire business through this system under real-world variability. That includes supplier delays, machine breakdowns, partial confirmations, batch inconsistencies, and timing mismatches between physical and financial events.
In Lydian speak, go-live approval is not a technology decision. It is a business continuity decision.
The Structural Reality
SAP works exactly as designed. It executes logic consistently, integrates modules tightly, and enforces data integrity based on configuration. The illusion arises because testing validates behaviour under controlled conditions, while the business operates under uncontrolled conditions. The gap between the two is where risk lives.
This is why dashboards show readiness while the plant experiences friction. The system has been proven in isolation. The enterprise has not been proven in motion.
The Question Before the Signature
The relevant question is not whether SAP is ready. It is whether the business has demonstrated that it can operate through SAP without breakdown across production, procurement, inventory, and finance under real conditions.
The CEO is not approving a system.
The CEO is approving the business to run on it.
