How To Fix EI362 - You do not have authorization to create record

SAP Error Message - Details

• Message type: E = Error

• Message class: EI - Foreign Trade: Gen. Output

• Message number: 362

• Message text: You do not have authorization to create record

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 EI362 - You do not have authorization to create record ?

  The SAP error message EI362, which states "You do not have authorization to create record," typically indicates that the user attempting to perform an action does not have the necessary permissions to create a record in the system. This can occur in various SAP modules, such as SAP ERP, SAP S/4HANA, or others, depending on the context of the action being performed.
  Cause:
  
  Missing Authorization Object: The user’s role may not include the necessary authorization object that allows for the creation of records in the specific transaction or module.
  Role Assignment: The user may not be assigned the correct role that includes the required permissions.
  Profile Issues: The user’s profile may not be updated or may be incorrectly configured.
  Transaction-Specific Restrictions: Certain transactions may have additional restrictions that are not covered by the general roles assigned to the user.
  
  Solution:
  
  
  Check User Roles:
  
  Go to transaction SU01 (User Maintenance) and enter the user ID.
  Check the roles assigned to the user and ensure that the necessary roles for creating records in the relevant module are included.
  
  
  
  Review Authorization Objects:
  
  Use transaction SU53 immediately after the error occurs to see which authorization check failed. This will provide insight into which specific authorization object is missing.
  Consult with your SAP security team to determine if the user needs additional authorizations.
  
  
  
  Modify Roles:
  
  If the user lacks the necessary authorizations, the SAP security administrator can modify the user’s roles or create a new role that includes the required authorizations.
  Ensure that the role includes the relevant authorization objects for the transaction being executed.
  
  
  
  Testing:
  
  After making changes to 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 issue is resolved.
  
  
  
  Documentation:
  
  Document any changes made to user roles or authorizations for future reference and compliance.
  
  
  
  Related Information:
  
  Transaction Codes: Common transaction codes related to user authorization include SU01 (User Maintenance), PFCG (Role Maintenance), and SU53 (Authorization Check).
  SAP Notes: Check SAP Notes for any known issues or updates related to authorization errors.
  Security Best Practices: Regularly review user roles and authorizations to ensure compliance with security policies and to minimize the risk of unauthorized access.
  
  If the issue persists after following these steps, it may be necessary to consult with your SAP Basis or security team for further investigation.