How To Fix MMPUR_REQ_COMMON020 - No Authorisation to create items for Purchasing Org &1


SAP Error Message - Details

  • Message type: E = Error

  • Message class: MMPUR_REQ_COMMON - Requisition common messages

  • Message number: 020

  • Message text: No Authorisation to create items for Purchasing Org &1

  • Show details Hide details


  • 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_COMMON020 - No Authorisation to create items for Purchasing Org &1 ?

    The SAP error message MMPUR_REQ_COMMON020 indicates that a user does not have the necessary authorization to create items for a specific Purchasing Organization (PO). This error typically arises when a user attempts to create or modify purchase requisitions or purchase orders but lacks the required permissions.

    Cause:

    The primary cause of this error is a lack of authorization in the user's role or profile for the specific Purchasing Organization. This can happen due to:

    1. Missing Authorization Objects: The user’s role may not include the necessary authorization objects related to purchasing activities.
    2. Incorrectly Assigned Roles: The user may not have been assigned the correct roles that include permissions for the Purchasing Organization in question.
    3. Organizational Structure Changes: Changes in the organizational structure or purchasing organization settings may lead to authorization issues.
    4. User Profile Issues: The user profile may not be correctly configured to allow access to the required purchasing activities.

    Solution:

    To resolve this error, you can take the following steps:

    1. 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 object is missing.
      • Alternatively, you can use transaction SU01 to view the user’s roles and authorizations.
    2. Review and Update Roles:

      • If you have the necessary permissions, review the roles assigned to the user in transaction PFCG (Profile Generator).
      • Ensure that the roles include the necessary authorization objects for the Purchasing Organization. Common authorization objects for purchasing include:
        • M_BEST_BSA (Purchasing Document: Authorization for Purchasing Group)
        • M_BEST_EKO (Purchasing Document: Authorization for Purchasing Organization)
        • M_BEST_VKO (Purchasing Document: Authorization for Vendor)
      • If the roles do not include the necessary authorizations, you may need to modify the roles or create a new role that includes the required permissions.
    3. Consult with Security Team:

      • If you do not have the necessary access to modify roles or authorizations, contact your SAP security or basis team. They can assist in reviewing and updating the user’s authorizations.
    4. Testing:

      • After making changes to the user’s roles or authorizations, have the user log out and log back in to ensure that the changes take effect.
      • Test the transaction again to confirm that the error has been resolved.

    Related Information:

    • Transaction Codes:
      • SU53: Display Authorization Check
      • SU01: User Maintenance
      • PFCG: Role Maintenance
    • Authorization Objects: Familiarize yourself with the relevant authorization objects for purchasing to ensure that users have the correct permissions.
    • Documentation: Refer to SAP documentation or your organization’s internal guidelines for managing user roles and authorizations.

    By following these steps, you should be able to identify and resolve the authorization issue causing the MMPUR_REQ_COMMON020 error.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant