How To Fix E2035 - Internal error trying to call the where-used list

SAP Error Message - Details

• Message type: E = Error

• Message class: E2 - DE Data Dictionary

• Message number: 035

• Message text: Internal error trying to call the where-used list

What causes this issue?

In deleting a Dictionary object, the system found that it is used.
This error message occurs when you display a where-used list.
Cause:
The object is still used indirectly. When the system deletes an object,
it searches for both direct and indirect uses. If it finds that the
obje is used, a dialog box appears, from which the user can start the
where-used list function. However, the where-used list function only
searches for direct use of the object. If it cannot find a direct use,
this error message appears.
The object is used in generated programs.
The where-used list filters generated programs.
There is an inconsistency.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Start the ABAP Dictionary maintenance transaction and use the
where-used list function to search for indirect occurrences of the
object you want to delete. Once you have deleted the uses of the
object, you can delete the object itself.
If the object for deletion is only used in programs, and the where-used
list does not return any programs as users of the object, you can
delete it.
If the object has no indirect use, use the where-used list for direct
uses instead.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message E2035 - Internal error trying to call the where-used list ?

  The SAP error message E2035, which states "Internal error trying to call the where-used list," typically indicates that there is an issue with the system's ability to retrieve or display the where-used list for a particular object. This can occur in various contexts, such as when working with materials, BOMs (Bill of Materials), or other master data.
  Causes:
  
  System Bugs: There may be a bug in the SAP system that is causing the error when trying to access the where-used list.
  Data Inconsistencies: Inconsistencies or corruption in the database can lead to errors when the system attempts to retrieve related data.
  Authorization Issues: Lack of proper authorizations for the user trying to access the where-used list can also trigger this error.
  Configuration Issues: Incorrect configuration settings in the SAP system can lead to problems when generating the where-used list.
  Performance Issues: If the system is under heavy load or if there are performance issues, it may fail to generate the list.
  
  Solutions:
  
  Check for System Notes: Look for any SAP Notes related to this error message. SAP frequently releases notes that address known issues and provide patches or workarounds.
  Data Consistency Check: Run consistency checks on the relevant data. For example, you can use transaction codes like SE11 (Data Dictionary) or SE14 (Database Utility) to check for inconsistencies.
  User Authorizations: Ensure that the user has the necessary authorizations to access the where-used list. You can check this in transaction SU53 or by consulting with your security team.
  System Restart: If the issue is related to performance, consider restarting the relevant application server or the entire SAP system if feasible.
  Debugging: If you have access to debugging tools, you can try to debug the transaction to identify where the error is occurring.
  Contact SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP Support for assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE14 (Database Utility), and SE80 (Object Navigator) for troubleshooting.
  SAP Notes: Regularly check the SAP Support Portal for notes related to your version of SAP and the specific error message.
  System Logs: Review system logs (transaction SM21) for any additional error messages or warnings that may provide more context about the issue.
  Performance Monitoring: Use transaction ST22 (Dump Analysis) to check for any short dumps that may be related to the error.
  
  By following these steps, you should be able to diagnose and potentially resolve the E2035 error in SAP.