How To Fix MMPUR_CQTN_CRT_POHUB018 - You are not authorized to create PO for purch.org. &1 in system &2.

SAP Error Message - Details

• Message type: E = Error

• Message class: MMPUR_CQTN_CRT_POHUB - Messages from Create PO from MPRC app

• Message number: 018

• Message text: You are not authorized to create PO for purch.org. &1 in system &2.

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_CQTN_CRT_POHUB018 - You are not authorized to create PO for purch.org. &1 in system &2. ?

  The SAP error message MMPUR_CQTN_CRT_POHUB018 indicates that a user is not authorized to create a Purchase Order (PO) for a specific purchasing organization in the SAP system. This error typically arises due to authorization issues related to user roles and permissions.
  Cause:
  
  Authorization Issues: The user does not have the necessary authorizations assigned to their user profile for the specified purchasing organization.
  Role Assignment: The user may not be assigned to the correct roles that include the permissions to create POs for the purchasing organization in question.
  Organizational Structure: The purchasing organization may not be included in the user's assigned organizational units.
  
  Solution:
  
  
  Check User Roles:
  
  Go to transaction code SU01 (User Maintenance) and enter the user ID.
  Check the roles assigned to the user and ensure that the roles include the necessary authorizations for creating POs in the specified purchasing organization.
  
  
  
  Review Authorization Objects:
  
  The relevant authorization objects for purchasing include M_BEST_BSA (Purchasing Document: Authorization for Purchase Order) and M_BEST_EKO (Purchasing Document: Authorization for Purchase Order - Purchasing Organization).
  Ensure that the user has the necessary authorizations for these objects, particularly for the purchasing organization in question.
  
  
  
  Modify User Roles:
  
  If the user lacks the necessary roles, work with your SAP security team to assign the appropriate roles that include the required authorizations for the purchasing organization.
  
  
  
  Organizational Assignment:
  
  Ensure that the user is assigned to the correct organizational units that correspond to the purchasing organization.
  
  
  
  Testing:
  
  After making changes, have the user log out and log back in to test if they can now create a PO for the specified purchasing organization.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SU01: User Maintenance
  PFCG: Role Maintenance (to create or modify roles)
  SU53: Display Authorization Check (to analyze authorization failures)
  
  
  
  Documentation: Refer to SAP documentation on authorization management and role assignment for detailed guidance on managing user permissions.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to authorization for purchasing organizations.
  
  
  If the issue persists after following these steps, it may be necessary to consult with your SAP Basis or Security team for further investigation.