How To Fix /PLMI/PRT_BO016 - Creation not possible; you do not have create authorization

SAP Error Message - Details

• Message type: E = Error

• Message class: /PLMI/PRT_BO -

• Message number: 016

• Message text: Creation not possible; you do not have create authorization

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 /PLMI/PRT_BO016 - Creation not possible; you do not have create authorization ?

  The SAP error message /PLMI/PRT_BO016 Creation not possible; you do not have create authorization indicates that the user attempting to create a certain object (likely related to Production Resource Tools or similar) does not have the necessary authorization to perform that action. This is a common issue in SAP systems where user roles and authorizations are strictly managed.
  Cause:
  
  Missing Authorization: The user does not have the required authorization object assigned to their user profile to create the specific object.
  Role Configuration: The role assigned to the user may not include the necessary permissions for the action they are trying to perform.
  Authorization Object: The specific authorization object related to the creation of the object may not be included in the user's role.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs. This will show you the last authorization check and can help identify which specific authorization is missing.
  
  
  
  Review User Roles:
  
  Go to transaction code SU01 to check the user’s roles. Ensure that the user has the appropriate roles assigned that include the necessary authorizations for the action they are trying to perform.
  
  
  
  Modify Roles:
  
  If the user is missing the required authorization, you may need to modify the role using transaction code PFCG:
  
  Find the role assigned to the user.
  Add the necessary authorization objects that allow for the creation of the specific object.
  Generate the profile after making changes.
  
  
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary permissions to change roles or authorizations, contact your SAP security team or administrator. Provide them with the error message and the context in which it occurred.
  
  
  
  Testing:
  
  After changes are made, have the user log out and log back in to ensure that the new authorizations take effect. Then, attempt the action again to see if the issue is resolved.
  
  
  
  Related Information:
  
  Authorization Objects: In SAP, authorization objects are used to control access to various functions. Common authorization objects related to creation might include S_TCODE (Transaction Codes), S_USER_AUTH (User Authorizations), or specific objects related to the module in use.
  Documentation: Refer to SAP documentation or your organization’s internal documentation for specific roles and authorizations related to the module you are working with.
  Audit Logs: If necessary, check audit logs to see if there are any other related issues or patterns that might indicate broader authorization problems.
  
  By following these steps, you should be able to identify and resolve the authorization issue causing the error message.