How To Fix MMPUR_REQ_COMMON058 - User not allowed as a requestor

SAP Error Message - Details

• Message type: E = Error

• Message class: MMPUR_REQ_COMMON - Requisition common messages

• Message number: 058

• Message text: User not allowed as a requestor

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 MMPUR_REQ_COMMON058 - User not allowed as a requestor ?

  The SAP error message MMPUR_REQ_COMMON058 indicates that the user is not authorized to act as a requestor in the system. This typically occurs in the context of the SAP Materials Management (MM) module, particularly when creating or processing purchase requisitions.
  
  Cause:
  The error is usually caused by one of the following reasons:
  
  User Authorization: The user does not have the necessary authorizations assigned to their user profile to create or manage purchase requisitions.
  Role Assignment: The user may not be assigned to the appropriate role that includes the necessary permissions for requestor activities.
  Organizational Assignment: The user may not be linked to the relevant organizational units (e.g., company code, purchasing organization) that allow them to act as a requestor.
  
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to check the authorization check that failed. This will provide insight into which specific authorization is missing.
  Review