How To Fix TD585 - No authorization to change form &1 &2

SAP Error Message - Details

• Message type: E = Error

• Message class: TD - SAPscript: Text editor, composer, forms, styles and fonts

• Message number: 585

• Message text: No authorization to change form &1 &2

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 TD585 - No authorization to change form &1 &2 ?

  The SAP error message TD585 "No authorization to change form &1 &2" typically occurs when a user attempts to modify a form (such as a print form or layout) in SAPscript or Smart Forms but lacks the necessary authorizations to do so. This error is related to the authorization objects that control access to various functions within SAP.
  Cause:
  
  Lack of Authorization: The user does not have the required authorization to change the specified form. This could be due to missing roles or authorizations in their user profile.
  Form Locking: The form might be locked by another user or process, preventing changes.
  Transport Requests: If the form is part of a transport request, the user may not have the necessary permissions to modify objects in that transport.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to see which authorization check failed.
  Review the user's roles and authorizations in transaction SU01 or PFCG to ensure they have the necessary permissions to change forms.
  
  
  
  Assign Missing Authorizations:
  
  If the user lacks the required authorizations, a security administrator can assign the necessary roles or specific authorizations related to form changes. The relevant authorization objects may include:
  
  S_SFREQ (for Smart Forms)
  S_SCRIP (for SAPscript)
  
  
  Ensure that the user has the appropriate activity (e.g., 02 for change) for the specific form.
  
  
  
  Check Form Locking:
  
  Verify if the form is currently locked by another user. You can check this in transaction SE71 (for SAPscript) or SMARTFORMS (for Smart Forms) by trying to access the form.
  If it is locked, you may need to wait until the other user has finished or contact them to unlock it.
  
  
  
  Transport Request Permissions:
  
  If the form is part of a transport request, ensure that the user has the necessary permissions to modify objects within that transport. This may involve checking the transport request's status and the user's role in the transport management process.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SE71: SAPscript form maintenance
  SMARTFORMS: Smart Forms maintenance
  SU01: User maintenance
  PFCG: Role maintenance
  SU53: Display authorization check
  
  
  
  Authorization Objects:
  
  S_SFREQ: Authorization for Smart Forms
  S_SCRIP: Authorization for SAPscript
  S_TCODE: Authorization for transaction codes
  
  
  
  Documentation: Refer to SAP's official documentation or help portal for detailed information on authorization management and troubleshooting authorization issues.
  
  
  If the issue persists after checking the above points, it may be necessary to consult with your SAP Basis or security team for further investigation.