How To Fix 0S130 - Not all call locations can be displayed

SAP Error Message - Details

• Message type: E = Error

• Message class: 0S - Messages for the SQL trace

• Message number: 130

• Message text: Not all call locations can be displayed

What causes this issue?

Program names are not specified in the trace log record. Therefore, the
call point in the program cannot be specified.

System Response

The system continues processing.

How to fix this error?

The performance trace is not currently configured to specify the
calling point.
The call might come from the R/3 kernel.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 0S130 - Not all call locations can be displayed ?

  The SAP error message 0S130 ("Not all call locations can be displayed") typically occurs in the context of ABAP programming, particularly when you are trying to analyze or display the call hierarchy of a program or function module. This error indicates that the system is unable to display all the call locations due to certain limitations or issues.
  Causes:
  
  Missing Source Code: The source code for some of the called programs or function modules may not be available in the system.
  Authorization Issues: The user may not have the necessary authorizations to view certain programs or function modules.
  Inactive Objects: Some of the called objects might be inactive or not properly activated in the system.
  Transport Issues: If the program or function module was transported from another system, there might be inconsistencies or missing objects.
  Performance Limitations: In some cases, the system may limit the number of call locations displayed for performance reasons.
  
  Solutions:
  
  Check Source Code Availability: Ensure that all the called programs and function modules are available in the system. You can do this by checking the object list in the ABAP Workbench (SE80).
  Review Authorizations: Verify that the user has the necessary authorizations to access all the relevant programs and function modules. You may need to consult with your security team to ensure proper roles are assigned.
  Activate Inactive Objects: If any of the called objects are inactive, activate them using transaction SE80 or SE38.
  Check Transport Consistency: If the program was transported, ensure that all dependent objects were also transported correctly. You may need to re-transport missing objects.
  Use Alternative Tools: If the issue persists, consider using alternative tools or transactions for analyzing call hierarchies, such as transaction SE37 for function modules or SE80 for programs.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes like SE80 (Object Navigator), SE37 (Function Module), and SE38 (ABAP Editor) for further investigation.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Documentation: Review the official SAP documentation for more details on call hierarchy analysis and related ABAP programming concepts.
  
  If the problem continues after trying the above solutions, it may be beneficial to consult with your SAP Basis or ABAP development team for further assistance.