How To Fix RT258 - Average time use in network (excluding roundtrips)

SAP Error Message - Details

• Message type: E = Error

• Message class: RT - Monitoring infrastructure MSG and alert texts

• Message number: 258

• Message text: Average time use in network (excluding roundtrips)

What causes this issue?

Average frontend network time per dialog step.
During a dialog step, there can be several communication steps between
the SAP server and the local frontend.
The frontend network time is the time that is used in the network for
the first data transfer from the frontend to the SAP server, and the
last data transfer from the SAP server to the frontend (in milliseconds)
during a dialog step.

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?

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 RT258 - Average time use in network (excluding roundtrips) ?

  The SAP error message RT258, which states "Average time use in network (excluding roundtrips)," typically relates to performance issues in the SAP system, particularly concerning network communication and response times. This message is often associated with the SAP Performance Analysis tools, such as ST03N (Workload Analysis) or ST02 (Tune Summary).
  Cause:
  
  Network Latency: High latency in the network can lead to increased response times for transactions.
  System Load: If the SAP system is under heavy load, it may take longer to process requests, leading to higher average times.
  Configuration Issues: Incorrect configuration of network settings or SAP parameters can lead to inefficient communication.
  Database Performance: Slow database queries or locks can also contribute to increased response times.
  Application Logic: Inefficient coding or logic in ABAP programs can lead to longer processing times.
  
  Solution:
  
  
  Network Optimization:
  
  Check the network infrastructure for any bottlenecks or issues.
  Use tools to monitor network performance and identify latency issues.
  Consider optimizing network routes or upgrading bandwidth if necessary.
  
  
  
  System Performance Tuning:
  
  Analyze system performance using transaction codes like ST03N and ST02.
  Identify and resolve any performance bottlenecks in the application server or database.
  Adjust SAP parameters related to memory, processing, and communication.
  
  
  
  Database Optimization:
  
  Review and optimize database queries.
  Ensure that database statistics are up to date.
  Check for locks or long-running transactions that may be affecting performance.
  
  
  
  Code Review:
  
  Conduct a review of ABAP code to identify inefficient logic or processing.
  Optimize any identified performance issues in the code.
  
  
  
  Monitoring and Alerts:
  
  Set up monitoring tools to alert on performance issues before they impact users.
  Regularly review performance metrics to identify trends and potential issues.
  
  
  
  Related Information:
  
  Transaction Codes: Use ST03N for workload analysis, ST02 for memory analysis, and ST04 for database performance.
  SAP Notes: Check SAP Notes for any known issues or patches related to performance.
  Performance Tuning Guides: Refer to SAP's official performance tuning guides for best practices.
  Network Monitoring Tools: Consider using network monitoring tools to analyze traffic and identify issues.
  
  By addressing the underlying causes of the RT258 error message, you can improve the performance of your SAP system and reduce average response times in the network.