Safely decommissioning SAP users: dependency checks

Documented problems

• Critical
  RFC destinations log on with the user

  DECOM_ACTIVE_RFC_DEPENDENCY

• Critical
  Background job steps run under the target user (TBTCP)

  DECOM_JOB_STEP_USER_DEPENDENCY

• Critical
  Locked user still receives logon attempts

  DECOM_LOCKED_USER_CALL_FLOOD

• Critical
  Scheduled integrations depend on the target

  DECOM_SCHEDULED_INTEGRATION_DEPENDENCY

• Critical
  Background jobs run under the user

  DECOM_SCHEDULED_JOB_DEPENDENCY

• Critical
  RFC destination to decommission absent from RFCDES

  DECOM_TARGET_NOT_FOUND

• Critical
  Candidate user absent from USR02

  DECOM_USER_NOT_FOUND

• Major
  Target user is the recorded technical owner of objects

  DECOM_OWNERSHIP_TRANSFER_REQUIRED

• Major
  User active within the grace period

  DECOM_RECENT_ACTIVITY_DETECTED

• Major
  Open workflow items assigned to the user

  DECOM_WORKFLOW_AGENT_DEPENDENCY

• Minor
  Role assignments of the target still valid (AGR_USERS)

  DECOM_ROLE_ASSIGNMENTS_ACTIVE

• Minor
  No technical owner recorded for the technical target

  DECOM_TARGET_OWNER_MISSING

Informational findings

These findings confirm a good state or document a change. They are listed for completeness and are not problems.

• Info
  No dependencies found in the supplied extracts

  DECOM_SAFE_FOR_ARCHIVING

Terms used in this area

• Work item
• System refresh

Background articles

• Why SAP Business Workflow items get stuck and how to find the causeThe typical reasons a workflow does not continue — no agent found, failed background steps, missing events, configuration gaps — and the standard tools to diagnose them.
• SAP system refresh checklist: BDLS logical system conversion and RFC outbound isolationWhy a quality assurance system refresh from production risks sending live IDocs, emails or RFC calls to production partners, and how to verify post-copy delta settings deterministically.