How To Fix E4054 - Referenced includes cannot be deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: E4 - Program maintenance functions within development system

• Message number: 054

• Message text: Referenced includes cannot be deleted

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 E4054 - Referenced includes cannot be deleted ?

  The SAP error message E4054, which states "Referenced includes cannot be deleted," typically occurs when you attempt to delete an include program that is still being referenced by other programs or objects in the SAP system. This is a common issue when working with ABAP programs, function modules, or other development objects that utilize include files.
  Cause:
  
  Active References: The include you are trying to delete is still being used in one or more ABAP programs, function modules, or other includes.
  Dependencies: The include may have dependencies that are not immediately visible, such as being part of a larger program or being included in multiple places.
  Transport Requests: If the include is part of a transport request that is still active or not fully released, it may prevent deletion.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check References:
  
  Use transaction code SE80 (Object Navigator) or SE11 (Data Dictionary) to check where the include is being used.
  You can also use the Where-Used List feature (right-click on the include and select "Where-Used List") to find all the programs or objects that reference the include.
  
  
  
  Remove References:
  
  If you find any programs or objects that reference the include, you will need to either modify those objects to remove the reference or delete the objects if they are no longer needed.
  
  
  
  Transport Requests:
  
  Ensure that there are no active transport requests that include the include you are trying to delete. If there are, you may need to release or adjust those requests.
  
  
  
  Check for Active Locks:
  
  Sometimes, objects can be locked by other users or processes. Ensure that no one else is currently editing or using the include.
  
  
  
  Delete After Cleanup:
  
  Once all references have been removed and any locks cleared, you should be able to delete the include without encountering the error.
  
  
  
  Related Information:
  
  Transaction Codes: SE80 (Object Navigator), SE11 (Data Dictionary), SE37 (Function Modules), SE38 (ABAP Programs).
  ABAP Development: Understanding how includes work in ABAP programming is crucial. Includes are often used to modularize code and can be shared across multiple programs.
  Documentation: Refer to SAP Help documentation for more details on includes and their management in the ABAP Workbench.
  
  If you continue to face issues after following these steps, consider reaching out to your SAP Basis or development team for further assistance.