Governed Capital Equipment Order Booking
A real SAP fit-gap pattern: semiconductor capital equipment is sold configure-to-order, and a sales order sometimes has to be booked against a fab's confirmed capacity slot before the final tool configuration is known. Watch a deterministic policy decide whether booking, finalizing, or rejecting that order executes alone, escalates to a named approver, or gets blocked outright — with an ERP-layer check that catches what the policy alone can't. Illustrative composite scenario, not a real client engagement.
Model spend
$0
of $50 cap
Ledger entries
0
every decision, not just successes
Pending approvals
0
escalated, awaiting a human
Order pipeline
The seed orders each canned scenario targets — watch this update as scenarios execute.
| Order | Customer | Status | Material | Price | Procurement |
|---|---|---|---|---|---|
| SO-9001 | Fab Customer A | tbd material | TBD-ETCH-A | $2,400,000 | none yet |
| SO-9002 | Fab Customer B | tbd material | TBD-DEP-B | $3,100,000 | committed |
| SO-9003 | Fab Customer C | tbd material | TBD-ETCH-C | $1,950,000 | none yet |
| SO-9004 | Fab Customer D | tbd material | TBD-DEP-D | $2,750,000 | committed |
| SO-9005 | Fab Customer E | tbd material | TBD-ETCH-E | $2,200,000 | committed |
Propose an action
Click a scenario, or finalize any order yourself with your own price.
Or finalize a TBD order yourself — pick one and set the final price:
Audit ledger
Blocked and escalated actions are logged with the same fidelity as executed ones.
No actions proposed yet — try a scenario above.
Policy: booking a TBD-material order auto-executes once the customer's capacity slot is confirmed; finalizing to a real material auto-executes if the price stays within 8% of the TBD estimate, and escalates to a named approver above that; rejecting an order auto-executes if no procurement has been triggered yet, and escalates if it has. A raw cancellation is never an authorized action, regardless of state — only the formal reject path exists. The ERP re-validates every finalize independently of the policy layer, catching a configuration that contradicts already-committed procurement even when policy approved the request. Everything on this page runs in your browser; nothing is sent to a server. Illustrative composite scenario grounded in a real SAP fit-gap pattern — not a real client engagement.
Want the full picture for your environment?
A discovery call gets you a scoped assessment from the person who builds these migrations — not a form, a conversation.
Book a discovery call