How To Fix 27117 - Saving changes to classes

SAP Error Message - Details

• Message type: E = Error

• Message class: 27 - API-specific configuration/master data messages

• Message number: 117

• Message text: Saving changes to classes

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 27117 - Saving changes to classes ?

  The SAP error message 27117 typically occurs when there are issues related to saving changes to ABAP classes or other development objects in the SAP system. This error can arise due to various reasons, including authorization issues, transport requests, or system settings.
  Causes of Error 27117
  
  
  Authorization Issues: The user may not have the necessary authorizations to save changes to the class or object. This is common in environments with strict role-based access controls.
  
  
  Transport Request Issues: If the changes are being made in a development environment, there may be issues with the transport request. For example, the transport request may not be released, or there may be conflicts with other requests.
  
  
  Locking Issues: The object may be locked by another user or process, preventing changes from being saved.
  
  
  System Settings: Certain system settings or configurations may prevent saving changes, especially in systems with specific development guidelines or restrictions.
  
  
  Syntax Errors: If there are syntax errors in the code, the system may prevent saving until those errors are resolved.
  
  
  Solutions to Error 27117
  
  
  Check Authorizations: Ensure that the user has the necessary authorizations to modify and save the class. This can be done by checking the user's roles and authorizations in transaction SU53 or SUIM.
  
  
  Review Transport Requests: Make sure that the transport request is correctly set up and released. You can check the status of the transport request in transaction SE09 or SE10.
  
  
  Check for Locks: Use transaction SM12 to check if the object is locked by another user. If it is, you may need to wait for the lock to be released or contact the user who has locked it.
  
  
  Correct Syntax Errors: If there are syntax errors in the code, resolve them before attempting to save again. You can use the syntax check feature in the ABAP editor (transaction SE80 or SE38) to identify and fix errors.
  
  
  Consult System Administrator: If the issue persists, it may be necessary to consult with a system administrator or BASIS team to check for any system-level issues or configurations that may be affecting the ability to save changes.
  
  
  Related Information
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE80 (Object Navigator), SE38 (ABAP Editor), SE09/SE10 (Transport Organizer), and SM12 (Lock Entries).
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to error 27117. You can search for notes in the SAP Support Portal.
  Documentation: Review SAP documentation for best practices in managing ABAP development and transport requests.
  
  By following these steps, you should be able to identify and resolve the cause of the SAP error message 27117 when saving changes to classes.