What problem does it solve? SAP IBP has no transaction-log undo: a key-figure overwrite, a version promoted into the baseline, or a plan released to ERP can silently destroy the plan of record or create real execution documents. This Skill gives an AI agent the operator judgment to classify every IBP action as read, reversible write, committing write, or destructive, and to gate the dangerous ones behind snapshots and human approval. ## Core Features & Use Cases - Risk classification of IBP operations: Distinguishes Simulate vs Save Data, sandbox vs baseline targets, and sharing vs publishing a version, so the same operator is gated correctly by blast radius. - Snapshot-first recovery discipline: Enforces taking a snapshot or backup version before any baseline-writing operator, since an unbacked baseline overwrite is unrecoverable. - Edge-state and gotcha coverage: Documents 19 real failure modes including disaggregation on empty basis, version-independent key figures, concurrent last-write-wins saves, and scheduled application jobs repeating a bad overwrite. - Use Case: Before running an S&OP supply operator or promoting a scenario into the baseline, the agent checks the target version, confirms a snapshot exists, re-reads the current plan, and requires a named human approver before releasing supply to S/4HANA. ## Quick Start Ask the agent to run the S&OP supply heuristic into the baseline planning version and have it classify the risk, take a snapshot first, and pause for approval before executing.
