How To Fix 6P035 - Requirements type cannot be changed

6P035 - Overview

• Message type: E = Error

• Message class: 6P - Messages for planned independent requirements (Appl.area 60)

• Message number: 035

• Message text: Requirements type cannot be changed

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 6P035 - Requirements type cannot be changed ?

  The SAP error message 6P035 ("Requirements type cannot be changed") typically occurs in the context of material requirements planning (MRP) or when dealing with production planning and control. This error indicates that the system is unable to change the requirements type for a particular material or planning scenario due to certain constraints or settings.
  Causes:
  
  Locked Requirements Type: The requirements type may be locked for the material or the specific planning scenario, preventing any changes.
  Inconsistent Data: There may be inconsistencies in the master data or configuration settings that prevent the change.
  Dependencies: The requirements type might be linked to other settings or configurations that do not allow for changes.
  User Authorizations: The user may not have the necessary authorizations to make changes to the requirements type.
  Material Status: The material might be in a status that does not allow changes (e.g., blocked, inactive).
  
  Solutions:
  
  Check Material Master Data: Review the material master data to ensure that the