How To Fix PK136 - Not possible to maintain person responsible

PK136 - Overview

• Message type: E = Error

• Message class: PK - Production - KANBAN

• Message number: 136

• Message text: Not possible to maintain person responsible

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 PK136 - Not possible to maintain person responsible ?

  The SAP error message PK136 ("Not possible to maintain person responsible") typically occurs in the context of maintaining master data or transaction data in SAP, particularly when dealing with organizational structures, such as cost centers, internal orders, or projects. This error indicates that the system is unable to assign or change the person responsible for a particular object.
  Causes of Error PK136
  
  
  Authorization Issues: The user may not have the necessary authorizations to change the person responsible for the object in question.
  
  
  Object Status: The object (e.g., cost center, internal order) may be in a status that does not allow changes to be made. For example, if the object is locked or has been archived, modifications may not be possible.
  
  
  Data Inconsistencies: There may be inconsistencies in the data that prevent the assignment of a person responsible. This could be due to missing or incorrect entries in related tables.
  
  
  Configuration Settings: The configuration settings in