How To Fix 61736 - Threshold values not maintained correctly

SAP Error Message - Details

• Message type: E = Error

• Message class: 61 - Fehlermeldungen fuer Bedarfsplanung

• Message number: 736

• Message text: Threshold values not maintained correctly

What causes this issue?

The threshold value for non-critical delays in sales orders (@5B@ green
icon) must be smaller than or equal to the threshold value for critical
delays (@5D@ yellow icon). The threshold value for critical delays must
be smaller than or equal to the threshold value for highly critical
delays (@5C@ red icon).
Non-critical delay =< critical delay =< highly critical delay.

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?

Adjust the threshold values accordingly.

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 61736 - Threshold values not maintained correctly ?

  The SAP error message 61736, "Threshold values not maintained correctly," typically occurs in the context of SAP's monitoring and alerting systems, particularly in relation to performance management or system monitoring. This error indicates that the threshold values for certain metrics or parameters have not been set up correctly, which can lead to issues in monitoring system performance or generating alerts.
  Cause:
  
  Incorrect Configuration: The threshold values for specific metrics may not have been defined or may have been defined incorrectly in the system.
  Missing Values: Required threshold values might be missing entirely, leading to the inability of the system to evaluate performance against these thresholds.
  Data Type Mismatch: The values set for thresholds may not match the expected data types (e.g., setting a string value where a numeric value is expected).
  System Updates: Changes in system configuration or updates may have led to the loss or corruption of previously defined threshold values.
  
  Solution:
  
  Check Configuration: Navigate to the relevant configuration settings in SAP where threshold values are defined. This could be in transaction codes like RZ20 (CCMS Monitoring) or RZ21 (Alert Monitoring).
  Define Thresholds: Ensure that all necessary threshold values are defined correctly. This includes setting appropriate limits for performance metrics such as CPU usage, memory usage, and response times.
  Review Documentation: Consult SAP documentation or help resources to understand the expected values and formats for the thresholds you are configuring.
  Test Changes: After making changes to the threshold values, test the configuration to ensure that the error message no longer appears and that monitoring functions as expected.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide guidance on threshold configuration.
  
  Related Information:
  
  Monitoring Tools: Familiarize yourself with SAP monitoring tools such as CCMS (Computing Center Management System) and Solution Manager, which can help in setting and managing thresholds.
  Performance Management: Understanding the importance of performance thresholds in maintaining system health and performance can help in configuring them correctly.
  SAP Community: Engage with the SAP Community forums for insights and shared experiences from other users who may have encountered and resolved similar issues.
  
  If the problem persists after following these steps, it may be beneficial to reach out to SAP support for further assistance.