Checklists win projects. This is your executable reclassification checklist—a week-by-week roadmap from discovery to audit readiness. Use it. Copy it. Share it with stakeholders. It's your proof that reclassification is methodical, not ad hoc.
Timeline Breakdown
Weeks 1–2: Discovery & Baseline
Tasks to Complete
- Schedule kickoff meeting with SAP CoE, Finance, and Compliance
- Pull current SAP license inventory (all users, current classification)
- Extract Order Form and SOW documents defining license scope
- Request internal org chart and job title hierarchy
- Request HR data on user adds/removes in the last 12 months
- Export full user master from SAP (SUIM: System User Information & Maintenance)
- Create master baseline spreadsheet: User ID, Current License, Job Title, Department, Hire Date
- Lock down Order Form scope interpretation with SAP contract manager (documented in email)
Weeks 3–4: USMM Analysis
Tasks to Complete
- Request 12-month USMM export (monthly snapshots) from SAP BASIS or SI
- Request Effective License Position (ELP) report from STAR
- Request transaction detail logs showing modules/transactions by user
- Analyze each user: module access count, transaction diversity, core modules (80% activity)
- Create USMM analysis summary: Routine vs. occasional vs. anomalous transactions
- Identify candidate users for downgrade (clear single/two-module scope)
- Flag high-risk candidates for later phases (hybrid scope, edge cases)
- Update master spreadsheet with USMM findings
Need Help With USMM Analysis?
Our team can extract, analyze, and model your USMM data within 2 weeks, identifying all reclassification opportunities.
Weeks 5–6: Case Building & Documentation
Tasks to Complete
- Create one-page case file for each candidate user (Current License, Proposed License, USMM Evidence, Scope Definition, Manager Sign-Off)
- Prioritize by risk: High-Confidence (Low Risk) → Medium-Confidence → Low-Confidence (High Risk)
- Write scope definitions for each license type (using Order Form language)
- Get manager approval for each user's proposed scope (email sign-off required)
- Create reclassification evidence pack: USMM reports, role assignments, job descriptions, manager sign-offs
- Build financial impact summary: Cost per user, total Wave 1 savings
- Draft communication for reclassified users (explain scope, guarantee escalation path)
Weeks 7–8: Stakeholder Approvals
Tasks to Complete
- Meet with SAP CoE/IT: Confirm scope definitions won't break system access; discuss test plan
- Meet with Finance: Present cost savings (Year 1, Year 2, Year 3); get budget sign-off
- Meet with each manager: Present user scope; confirm appropriateness; collect written approval
- Engage Compliance/Legal if needed: Confirm reclassifications align with audit expectations
- Create reclassification project charter: Timeline, scope, success criteria, approval list
- Schedule testing window in SAP sandbox or test instance
- Build monitoring alerts: Transaction logs for reclassified users; blocked transaction notifications
Week 9: Implementation
Tasks to Complete
- Execute pre-reclassification testing in sandbox (test proposed scopes; confirm nothing blocks)
- Notify users one week in advance: Explain reclassification; confirm their access won't change; provide escalation contact
- Update SAP user master: Change license classification for all Wave 1 users
- Update security roles in SAP: Align role assignments to new scopes
- Record implementation date and reason in master audit log
- Send follow-up notification to users: Reclassification complete; here's your new scope; contact [X] for issues
- Enable monitoring alerts: Flag blocked transactions daily
- Schedule Week 10 kick-off meeting: Confirm zero escalations so far; plan monitoring cadence
Weeks 10–12: Monitoring & Stabilization
Tasks to Complete
- Weekly monitoring: Check for blocked transactions; escalate immediately if found
- Handle exceptions: If user hits blocked transaction, adjust scope within 24 hours
- Document all exceptions: User, Transaction, Date, Business Reason, Resolution
- Gather stakeholder feedback: Any concerns or escalations from managers or finance?
- Confirm no alerts triggered for 30 consecutive days before proceeding to Wave 2
- Create reclassification success report: Wave 1 results, zero exceptions, cost savings realized
- Plan Wave 2 kick-off: Apply lessons learned; adjust scope definitions if needed
- Schedule contract amendment discussion with SAP: Timing for credit negotiation
Post-Project: Annual Governance
Establish a recurring annual reclassification program:
Annual Reclassification Cycle
- January: Pull fresh USMM report (last 12 months); compare to prior year
- February: Analyze new reclassification opportunities; model cost savings
- March: Build case files for new candidates; get manager approvals
- April: Implement new reclassifications (small batch, low risk)
- May–June: Monitor and stabilize
- July: Collect all reclassification evidence; prepare for potential audit
- August: Manager certification cycle (each manager certifies user scopes)
- September: Contract amendment negotiation (if credits warranted)
- October–December: Carry forward; maintain governance
Audit Readiness Checklist
Before SAP auditors arrive, ensure you have all of this:
Audit Evidence Pack
- 12+ months of USMM data (monthly snapshots) for all reclassified users
- One-page case file per reclassified user (USMM evidence, scope definition, manager sign-off)
- Order Form and SOW documents (proof of scope definitions)
- Security role master data (proof of access control alignment)
- Job description or org chart (proof of job function)
- Manager certification (written proof of scope appropriateness)
- Exception log (proof of active monitoring and remediation)
- Implementation dates and reasons (proof of intentionality, not accidental)
- Cost savings calculation (proof of financial benefit)
Conclusion
Reclassification succeeds when you move methodically and document relentlessly. This checklist takes you from kickoff to audit readiness. Follow it. Update it as you learn. Make it your project backbone. When SAP auditors ask, "Why did you reclassify these users?", hand them this checklist and your evidence pack. You'll have answered the question before they finished asking.