Fit-to-Standard and Clean Core Decisions

Keep this: job aid

Gap decision card

• Default answer: adopt the standard. Ask "what problem does this solve?" before anything else.
• Four options: adopt, adapt (configure), extend, change the business.
• Score each gap: required? differentiating? lifecycle cost? risk?
• If extending, go cleanest first: key user, ABAP Cloud, side-by-side, then classic only by exception.
• Ask the architect for the clean core level (A–D); expect strong reasons below B.
• Estimate lifecycle cost: build + project test + regression per release + remediation + support.
• Log every decision: options, decision, rationale, level, owner, approver, date, linked tests.
• Link each non-standard decision to positive and negative test scenarios and the regression set.
• Public Edition: no modifications or classic exits. Private Edition: allowed, but governed.
• Before each upgrade, review the log: retest, and retire anything standard now covers.