How To Fix 42836 - Responsible person no longer exists in the system

SAP Error Message - Details

• Message type: E = Error

• Message class: 42 - Information Workbench

• Message number: 836

• Message text: Responsible person no longer exists in the system

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message 42836 - Responsible person no longer exists in the system ?

  The SAP error message "42836 Responsible person no longer exists in the system" typically indicates that a user or responsible person assigned to a particular task, document, or object in the SAP system has been deleted or is no longer valid. This can occur in various contexts, such as project management, sales orders, or other modules where user assignments are critical.
  Cause:
  
  User Deletion: The responsible person (user) has been deleted from the SAP system.
  User Locking: The user account may be locked or inactive.
  Data Migration: During data migration or system upgrades, user assignments may not have been properly transferred.
  Organizational Changes: Changes in the organizational structure may lead to the removal of users or their roles.
  
  Solution:
  
  Check User Status: Verify if the responsible person exists in the system by checking the user master data (transaction code SU01).
  Reassign Responsible Person: If the user has been deleted, you may need to assign a new responsible person to the relevant document or task.
  Unlock User: If the user is locked, you can unlock the user account if you have the necessary permissions.
  Update Assignments: If the user has been changed due to organizational restructuring, update the relevant assignments in the system to reflect the current responsible person.
  Consult with IT: If you are unable to resolve the issue, consult with your SAP Basis or IT team to investigate further.
  
  Related Information:
  
  Transaction Codes: Use transaction codes like SU01 (User Maintenance) to check user details and SU10 (Mass User Maintenance) for bulk changes.
  Authorization Issues: Ensure that you have the necessary authorizations to view and modify user assignments.
  Documentation: Refer to SAP documentation or support notes related to user management and error handling for more detailed guidance.
  System Logs: Check system logs (transaction code SM21) for any related errors or warnings that might provide additional context.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.