How To Fix ED808 - Include not saved. It was only expanded for display

SAP Error Message - Details

• Message type: E = Error

• Message class: ED - ABAP/4 Editor messages

• Message number: 808

• Message text: Include not saved. It was only expanded for display

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 ED808 - Include not saved. It was only expanded for display ?

  The SAP error message ED808 ("Include not saved. It was only expanded for display") typically occurs when you are trying to edit or save an include program in the ABAP Workbench (SE80 or SE38) but the system does not allow you to save changes because the include is not in a modifiable state. This can happen for several reasons:
  Causes:
  
  Display Mode: You may have opened the include in display mode rather than in change mode. This means you can view the code but cannot make any changes.
  Transport Request: The include might be locked for changes because it is part of a transport request that is currently being processed or is in a different status.
  Authorization Issues: You may not have the necessary authorizations to modify the include.
  System Lock: The include might be locked by another user or process, preventing you from saving changes.
  
  Solutions:
  
  Switch to Change Mode: Ensure that you are in change mode. You can do this by selecting the "Change" option in the menu or using the appropriate transaction code (e.g., SE38 or SE80).
  Check Transport Request: If the include is part of a transport request, check the status of that request. If it is locked, you may need to wait until it is released or contact your transport administrator.
  Review Authorizations: Verify that you have the necessary authorizations to modify the include. You may need to contact your SAP security administrator to check your roles and permissions.
  Check for Locks: Use transaction code SM12 to check if the include is locked by another user. If it is, you may need to wait for that user to release the lock or contact them to resolve the issue.
  Use the Correct Environment: Ensure you are working in the correct development environment (e.g., Development system) where you have the rights to make changes.
  
  Related Information:
  
  Transaction Codes: SE80 (Object Navigator), SE38 (ABAP Editor), SM12 (Display and Delete Locks).
  SAP Notes: Check for any relevant SAP Notes that might address specific issues related to this error message.
  Documentation: Review SAP documentation for more details on working with includes and transport requests.
  
  If you continue to experience issues after trying these solutions, it may be helpful to consult with your SAP Basis team or a more experienced ABAP developer for further assistance.