How To Fix TN502 - Call of &1 not permitted

SAP Error Message - Details

• Message type: E = Error

• Message class: TN - Support Package Manager (SPAM) Messages

• Message number: 502

• Message text: Call of &1 not permitted

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 TN502 - Call of &1 not permitted ?

  The SAP error message TN502 "Call of &1 not permitted" typically occurs in the context of SAP's transport management system (TMS) or when dealing with transport requests. This error indicates that there is an issue with the authorization or configuration that prevents the system from executing a specific function or transaction.
  Causes:
  
  Authorization Issues: The user may not have the necessary authorizations to perform the action associated with the transport request or the specific function being called.
  Transport Configuration: There may be a misconfiguration in the transport landscape or the transport routes that restrict the execution of certain calls.
  System Settings: Certain system settings or parameters may be preventing the execution of the function.
  Transport Request Status: The transport request may be in a status that does not allow it to be processed (e.g., it might be locked or not released).
  
  Solutions:
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to perform the action. This can be done by checking the user's roles and authorizations in transaction SU53 or SUIM.
  If necessary, consult with your SAP security team to grant the required permissions.
  
  
  
  Review Transport Configuration:
  
  Check the transport routes and configuration in transaction STMS. Ensure that the transport domain and landscape are correctly set up.
  Verify that the transport layer is correctly defined and that there are no inconsistencies.
  
  
  
  Check Transport Request Status:
  
  Use transaction SE09 or SE10 to check the status of the transport request. Ensure that it is released and not in a locked state.
  If the request is locked, you may need to unlock it or resolve any issues that are causing the lock.
  
  
  
  System Settings:
  
  Review any relevant system settings that might restrict the execution of the function. This may involve checking system parameters or consulting with your Basis team.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message. There may be known issues or patches available.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as STMS (Transport Management System), SE09/SE10 (Transport Organizer), SU53 (Authorization Check), and SUIM (User Information System).
  SAP Documentation: Refer to SAP Help documentation for detailed information on transport management and authorization concepts.
  SAP Community: Engage with the SAP Community forums for insights and solutions from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to involve your SAP Basis team or reach out to SAP support for further assistance.