How To Fix CCSEQ070 - User %1 has been locked, no workflow

SAP Error Message - Details

• Message type: E = Error

• Message class: CCSEQ - Change sequence graph

• Message number: 070

• Message text: User %1 has been locked, no workflow

What causes this issue?

User &V1& has caused a cycle and must be notified per workflow.

System Response

The system could not generate a workflow because the user is locked.

How to fix this error?

Check if the lock is authorized, and unlock the user, if required.
If the user is to remain locked, then any other user with sufficient
authorization can remove the cycle.
You can display the cycle using transaction CCSEQ_CYCLE. To do so, enter
&1 in the "User" field, and activate the "Only as Person Responsible"
option.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CCSEQ070 - User %1 has been locked, no workflow ?

  The SAP error message CCSEQ070 indicates that a user has been locked and that there is no workflow associated with the action that the user is trying to perform. This typically occurs in the context of SAP's workflow management system, where certain actions require user authorization and the user in question has been locked due to various reasons.
  Cause:
  
  User Locking: The user may have been locked due to multiple failed login attempts, administrative actions, or security policies.
  Authorization Issues: The user may not have the necessary authorizations to perform the action, and the system is unable to initiate a workflow to handle the situation.
  Workflow Configuration: There may be a misconfiguration in the workflow settings that prevents the system from processing the request.
  
  Solution:
  
  
  Unlock the User:
  
  An administrator can unlock the user account. This can typically be done in transaction code SU01 (User Maintenance).
  Navigate to the user profile, check the "Lock" status, and unlock the user.
  
  
  
  Check User Authorizations:
  
  Ensure that the user has the necessary authorizations to perform the action they are attempting. This can be done by reviewing the user's roles and profiles in transaction PFCG (Role Maintenance).
  
  
  
  Review Workflow Configuration:
  
  If the action requires a workflow, check the workflow configuration to ensure that it is set up correctly. This may involve reviewing the workflow definitions and ensuring that the appropriate agents are assigned.
  
  
  
  Consult Logs:
  
  Check the system logs (transaction SLG1) for any additional error messages or information that may provide insight into why the user is locked or why the workflow is not being triggered.
  
  
  
  Contact SAP Support:
  
  If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance, especially if it involves complex workflow configurations.
  
  
  
  Related Information:
  
  User Locking Policies: Understand the organization's policies regarding user locking and how many failed attempts are allowed before a user is locked.
  Workflow Management: Familiarize yourself with SAP's workflow management tools and how they can be configured to handle user actions and notifications.
  Transaction Codes:
  
  SU01: User Maintenance
  PFCG: Role Maintenance
  SLG1: Application Log
  SWI1: Work Item Selection
  
  
  
  By following these steps, you should be able to resolve the CCSEQ070 error and restore the user's access to the necessary functionalities within SAP.