Enterprise Architecture Decisions for SAP Transformations

Keep this: job aid

SAP architecture decision card

• Significant = costly to reverse, many teams affected, or risk changed.
• Frame: problem, drivers, constraints, three real options, criteria agreed before scoring, owner, date.
• Effort follows reversibility and impact; decide at the last responsible moment.
• Always score quality and test impact over the release horizon, not just build cost.
• Clean core levels A–D double as a scale of upgrade and regression risk.
• ADR: title, status, context, decision, consequences; plus options, criteria, test consequences, assumptions, review date, links.
• Never rewrite an accepted ADR; supersede it.
• Check SAP dates and roadmaps; record what you checked and when. Roadmap items are plans.
• Revisit on new facts or failed assumptions; guard against sunk cost, churn and silent drift.
• A changed decision is a change: plan its migration and regression testing.