SAP Inactive User Cleanup: Checklist and Action Plan

Key Takeaways

Prerequisites matter: Complete data gathering and baseline measurement before you identify a single inactive user.
Four phases, 12 weeks: From identification through governance automation, follow this timeline to execute cleanly.
Stakeholder engagement is non-negotiable: Manager notification and 10-business-day response windows eliminate post-deletion disputes.
Technical execution is straightforward: Lock, verify, wait, delete. The process is mechanical once stakeholder approvals are confirmed.
Governance prevents recurrence: Quarterly reviews and integrated offboarding ensure you never accumulate 20% inactive users again.

Before You Start: Prerequisites and Data Gathering

Do not identify a single inactive user until your baseline is complete. The largest failure mode in cleanup projects is starting with an incomplete picture and then discovering critical data gaps mid-project. Spend Weeks 0–2 gathering and verifying data. This prevents chaos later.

Prerequisite Checklist

Extract full user list from SU10 with last logon date (USR02 table). Include TRDAT (last transaction date) and LDATE (last logon date).

Identify user types for all users: Professional, Limited Professional, Developer, Employee, ESS, or Functional.

Cross-reference against current HR employee list. Identify all users who are no longer employed.

Identify users with posted documents (SD, MM, FI). Cannot delete without archiving through SAPNote archiving program.

List users with open workflows, approval chains, or delegation. Cannot safely delete until workflows are resolved.

Confirm SAP system measurement schedule. Cleanup must complete 60+ days before audit or renewal measurement.

Assign a licence manager / cleanup project owner. Single point of accountability.

Document current named user count by type (baseline measurement). This is your starting point for ROI calculation.

Data validation is critical: Before proceeding to Phase 1, confirm that your user list, HR database, and SAP system counts are internally consistent. Any major gaps should be investigated. You cannot reliably identify inactive users if your source data is incomplete.

Phase 1 (Weeks 1–2): Identification and Classification

Now identify inactive users using SAP's standard reporting tools. The goal is to create a segmented list: Priority 1 (delete candidates), Priority 2 (review), and Exclude (service accounts, seasonal users).

Phase 1 Checklist

Run SUIM report: Users → By Logon Date to identify users with zero logon in past 90/180/365 days.

Query USR02 table directly for TRDAT (last transaction) and LDATE (last logon) — provides more granularity than SUIM.

Flag users with zero logon in the past 12 months as Priority 1 (immediate cleanup candidates).

Flag users with no logon in 6–12 months as Priority 2 (review and confirm with business).

Identify seasonal users (tax, year-end, month-end close). Exclude from deletion, mark for periodic review.

Identify service/technical users (background jobs, interfaces, BAPI users). Never delete. Mark as excluded.

Create inactive user register: username, user type, last logon date, business area, manager name, deletion candidate (Y/N).

At the end of Phase 1, you should have a segmented list of approximately:

Priority 1: Users with zero logon in 12+ months (immediate candidates)
Priority 2: Users with zero logon in 6–12 months (requires manager verification)
Exclude: Service accounts, seasonal users, users with open documents/workflows

The register is your project backbone. Keep it updated throughout the cleanup.

Phase 2 (Weeks 3–4): Stakeholder Engagement and Approval

This phase prevents post-deletion disputes and ensures executive alignment. Notify each user's manager and set a clear approval window.

Phase 2 Checklist

Send notification to each user's manager: "This user has been inactive for X days. Confirm if still required or approve for cleanup."

Set 10-business-day response deadline. Manager non-response = implicit approval for deletion.

Create formal exception process. Manager can request retention with business justification (e.g., "User on extended leave, returning Q4").

Get written sign-off from IT and HR before any deletions. Email trail is acceptable; formal approval is required.

Check employment status for all Priority 1 users. Confirm with HR: active employee, contractor, or terminated?

Legal review (if required): Confirm archiving and retention requirements for users with posted transactions before deletion.

Sample notification email:

Subject: SAP User Verification — [USERNAME]

Hi [Manager],

During a user population audit, we identified that [USERNAME] has not logged into SAP since [DATE]. This user is classified as a [USER TYPE] licence holder.

Please confirm by [DUE DATE] whether this user should be retained or can be removed from the SAP system. If you do not respond by the deadline, we will assume this user is no longer required.

Reply with "RETAIN" or "REMOVE" or provide comments.

Best regards,
IT Systems / SAP Administration

The 10-business-day window is critical. It demonstrates due diligence and creates an audit trail. If challenged later, you can show that you actively notified stakeholders and gave them an opportunity to object.

Phase 3 (Weeks 5–6): Technical Execution

Once approvals are confirmed, execute cleanly and document everything.

Phase 3 Checklist

Lock all confirmed inactive users in SU01 (set Valid To date to a past date or toggle lock checkbox).

Run USMM (Usage and Usership Measurement) to verify that locked users are excluded from licence count in your environment.

Wait 2 weeks — monitor for any system alerts, failed jobs, or workflow triggers caused by locked users.

Delete users with no pending items (or archive using SAP's archiving program if they have posted documents).

Document each deletion: username, user type, last logon date, deletion date, reason, approver name.

Run USMM/LAW after cleanup. Compare before/after user counts to confirm the reduction was recorded.

Why lock before delete? Locking validates that no active processes or approvals depend on the user. If background jobs fail after locking, you can immediately restore without losing data. Deletion is irreversible; locking gives you a safety window.

Documentation is non-negotiable: In an audit, SAP will ask to see evidence of your deletion decisions. A spreadsheet with username, type, last logon, deletion date, and manager approval is your defence. "We deleted inactive users" is not credible. "Here is the list of 247 users, their last logon dates, and the managers who approved their removal" is.

Phase 4 (Ongoing): Governance and Automation

Once you've cleaned the data, prevent accumulation from happening again.

Phase 4 Checklist

Schedule quarterly inactive user reviews (every 90 days). Add to SAP governance calendar.

Integrate user provisioning with HR offboarding. When HR terminates an employee, that should trigger a review of SAP user records.

Set up automated alert: any user inactive for 90+ days triggers a workflow notification to the licence manager.

Assign a named licence manager to own the user cleanup process as an ongoing responsibility (not a one-time project).

Track cumulative savings in a dashboard: before/after maintenance costs, user counts, cleanup frequency.

Include inactive user count and cleanup status in monthly SAM (Software Asset Management) reporting to finance/procurement.

Execute Your Cleanup with Expert Guidance

Our SAP licence compliance team can manage the full cleanup process: data extraction, stakeholder engagement, technical execution, and governance setup. We handle the complexity so you don't have to.

Explore SAP Licence Compliance Services

90-Day Timeline Summary

Here is a complete week-by-week breakdown:

Week 0–1

Baseline measurement. Extract user list, HR cross-reference, document current count by type.

Week 2–3

Phase 1: Run SUIM/USR02 reports. Create inactive user register with Priority 1/2 segmentation.

Week 4–5

Phase 2: Send manager notifications. 10-business-day response window opens.

Week 6–7

Phase 2 concluded: Collect approvals. Reconcile exceptions. Get IT/HR sign-off.

Week 8–9

Phase 3: Lock confirmed inactive users. Run USMM to verify exclusion.

Week 10–11

Phase 3: 2-week monitoring period. Watch for alerts, failed jobs. Then delete confirmed users.

Week 12

Phase 3–4: Final USMM measurement. Document deletions. Brief governance process to CFO/IT.

This timeline is aggressive but realistic for a mid-size enterprise (3,000–5,000 users). Larger populations may require 16–20 weeks. The critical path is stakeholder engagement (Phase 2) — do not try to accelerate this or you will face disputes and exceptions downstream.

Ready to Start Your Cleanup?

Book a free consultation with our SAP licensing experts. We'll help you scope the project, estimate savings, and plan the timeline.

Book a Free Consultation

Frequently Asked Questions

Can we speed up the timeline?

Not safely. The 10-business-day stakeholder engagement window is critical for creating an audit trail and preventing post-deletion disputes. The 2-week monitoring period after locking users prevents undetected dependencies. Cutting these phases risks failed jobs, escalations, and audit findings. 90 days is the minimum for a clean, documented execution.

What if a manager doesn't respond to the notification?

Non-response = implicit approval. This is why the notification email must be explicit: "If you do not respond by [DATE], we will assume this user is no longer required." Your email trail is the evidence. If a manager later complains, you can show they were notified and did not object within the defined window.

How do we handle users with open documents or workflows?

These cannot be deleted until the documents are archived and workflows are resolved. Archiving is handled through SAP's document archiving programs (ArchiveLink, near-line storage). Workflows should be reassigned to active users. In Phase 1, these users should be marked as "Cannot delete — has pending items" and managed separately.

Should we notify SAP of the user count reduction?

Yes, formally notify SAP when the cleanup is complete. Inform them of the user count reduction and provide a summary. This is especially important if you have an upcoming audit or renewal. SAP will measure your current user population; if your stated count differs from their measured count, that becomes an audit finding. Proactive communication demonstrates governance and reduces dispute risk.

What documentation should we keep after the project?

Keep the inactive user register with: username, user type, last logon date, deletion date, reason, and manager approval. Keep email records of all manager notifications and approvals. Keep USMM before/after reports showing the user count reduction. Keep a summary of any exceptions (users retained despite inactivity, with business justification). This documentation is your audit defence if SAP questions the cleanup.

Can we automate the identification process?

Partially. SUIM reports and USR02 queries are automated. But manager notification, approval, and exception handling require human judgment. You can automate the data extraction and segmentation, but stakeholder engagement must remain manual and documented. Some enterprises use workflow tools (SAP Workflow or third-party BPM tools) to automate the notification and approval process, which is efficient for large populations.

SAP Licensing Experts Advisory Team

Independent SAP licensing advisors with 100+ years combined experience in enterprise licence management, audit defence, and cost optimisation. We are not affiliated with SAP SE.

Independence Statement: SAP Licensing Experts is an independent advisory firm and is not affiliated with SAP SE, SAP SuccessFactors, or any SAP subsidiary. We do not receive compensation from SAP for any recommendations or analysis. Our role is to represent the interests of SAP customers in licensing matters, user governance, and audit defence. All content is produced independently based on our experience and is not endorsed by or representative of SAP's official position.