How To Fix MM_PUR_SRCGPROJ036 - Purchaser responsible &1 doesnÆt exist.

MM_PUR_SRCGPROJ036 - Overview

• Message type: E = Error

• Message class: MM_PUR_SRCGPROJ - Message class of MM PUR Sourcing Project

• Message number: 036

• Message text: Purchaser responsible &1 doesnÆt exist.

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 MM_PUR_SRCGPROJ036 - Purchaser responsible &1 doesnÆt exist. ?

  The SAP error message MM_PUR_SRCGPROJ036 indicates that the purchaser responsible for a specific purchasing document or project does not exist in the system. This error typically arises in the context of procurement processes, particularly when trying to assign or reference a purchaser who is not defined in the system.
  
  Cause:
  
  Missing User Master Record: The user responsible for purchasing may not have been created in the SAP system or may not have the necessary roles assigned.
  Incorrect Configuration: The configuration settings for purchasing may not be set up correctly, leading to the system not recognizing the purchaser.
  Data Inconsistency: There may be inconsistencies in the master data, such as the purchaser being deleted or not properly assigned to the relevant purchasing organization.
  Authorization Issues: The user may not have the required authorizations to access the purchaser data.
  
  
  Solution:
  
  
  Check User Master Record:
  
  Go to transaction code SU01 to check if the purchaser exists in the system.
  If the user