How To Fix FG668 - No authorization to delete change documents

SAP Error Message - Details

• Message type: E = Error

• Message class: FG - Program Error Messages

• Message number: 668

• Message text: No authorization to delete change documents

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 FG668 - No authorization to delete change documents ?

  The SAP error message FG668, which states "No authorization to delete change documents," typically occurs when a user attempts to delete change documents but lacks the necessary authorizations to perform this action. This error is related to the authorization checks in SAP, which are designed to ensure that users can only perform actions for which they have been granted permission.
  Cause:
  
  Authorization Issues: The user does not have the required authorization object to delete change documents. This could be due to missing roles or permissions in their user profile.
  Role Configuration: The roles assigned to the user may not include the necessary permissions for the specific transaction or object type related to change documents.
  Change Document Settings: The system settings or configurations may restrict certain users from deleting change documents.
  
  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 code SU01 to view the user's profile and roles.
  
  
  
  Modify Roles:
  
  If you have the necessary administrative rights, you can modify the user's roles to include the required authorization objects. The relevant authorization object for change documents is typically S_CHANGE_DOC or similar, depending on the specific context.
  Ensure that the role includes the necessary activity (e.g., delete) for the relevant object types.
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary permissions to change roles, contact your SAP security or basis team. Provide them with the details of the error and the transaction you were trying to perform.
  
  
  
  Review Change Document Settings:
  
  Check the configuration settings related to change documents in the relevant module (e.g., MM, SD, etc.) to ensure that there are no restrictions in place that prevent deletion.
  
  
  
  Related Information:
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects and their fields. This can help in understanding what permissions are required for specific actions.
  SAP Notes: Check SAP Notes for any known issues or updates related to this error message. Sometimes, there may be patches or updates that address specific authorization issues.
  Documentation: Review SAP documentation or training materials related to user authorizations and role management to better understand how to manage and troubleshoot authorization issues.
  
  By following these steps, you should be able to identify the cause of the FG668 error and implement a solution to resolve it.