How To Fix OA979 - No authorization to create

SAP Error Message - Details

• Message type: E = Error

• Message class: OA - SAP ArchiveLink: Messages for SAP ArchiveLink

• Message number: 979

• Message text: No authorization to create

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 OA979 - No authorization to create ?

  The SAP error message OA979 "No authorization to create" typically indicates that the user does not have the necessary permissions to create a specific object or record in the SAP system. This can occur in various contexts, such as when trying to create a purchase order, sales order, or any other transactional data.
  Cause:
  
  Missing Authorization Roles: The user may not have the appropriate authorization roles assigned to their user profile.
  Authorization Object Restrictions: The authorization objects related to the transaction may not be properly configured, leading to insufficient permissions.
  User Profile Issues: The user profile may not be set up correctly, or the user may be using a different profile that lacks the necessary permissions.
  Transaction-Specific Restrictions: Certain transactions may have additional restrictions based on organizational levels, such as company codes or plants.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to see which authorization check failed. This will provide insight into what specific authorization is missing.
  Alternatively, you can use transaction SU01 to view the user’s roles and authorizations.
  
  
  
  Review Authorization Roles:
  
  Ensure that the user has the correct roles assigned that include the necessary authorizations for the transaction they are trying to perform.
  If roles are missing, they may need to be assigned by a system administrator.
  
  
  
  Modify Authorization Objects:
  
  If the user has the correct roles but still encounters the error, the authorization objects associated with those roles may need to be modified to include the necessary permissions.
  This typically requires the involvement of a security administrator.
  
  
  
  Consult with Security Team:
  
  If you are not an administrator, contact your SAP security team or system administrator to investigate and resolve the authorization issue.
  
  
  
  Testing:
  
  After changes are made, have the user log out and log back in to ensure that the new authorizations take effect.
  Test the transaction again to confirm that the issue is resolved.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SU53: Display Authorization Check
  SU01: User Maintenance
  PFCG: Role Maintenance (to manage roles and authorizations)
  
  
  
  Documentation: Refer to SAP documentation or your organization’s internal guidelines for managing user roles and authorizations.
  
  
  Best Practices: Regularly review user roles and authorizations to ensure they align with current job functions and compliance requirements.
  
  
  By following these steps, you should be able to identify and resolve the authorization issue causing the OA979 error in SAP.