How To Fix >2586 - No graduated charges found for amount from &2 &3 in returns reason &1

SAP Error Message - Details

• Message type: E = Error

• Message class: >2 -

• Message number: 586

• Message text: No graduated charges found for amount from &2 &3 in returns reason &1

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 >2586 - No graduated charges found for amount from &2 &3 in returns reason &1 ?

  The SAP error message 2586 ("No graduated charges found for amount from &2 &3 in returns reason &1") typically occurs in the context of returns processing, particularly when dealing with graduated charges or pricing conditions in the SAP system. This error indicates that the system could not find any graduated charge conditions that match the specified criteria for the return reason.
  Cause:
  
  Missing Condition Records: The most common cause of this error is that there are no condition records defined for the graduated charges in the pricing procedure for the specified return reason.
  Incorrect Return Reason: The return reason specified may not be correctly configured to allow for graduated charges.
  Configuration Issues: There may be issues in the configuration of the pricing procedure or the condition types related to graduated charges.
  Data Entry Errors: Incorrect data entry in the return order or related documents can also lead to this error.
  
  Solution:
  
  
  Check Condition Records:
  
  Go to the transaction code VK11 (Create Condition) or VK12 (Change Condition) to check if the condition records for graduated charges exist for the relevant pricing condition type.
  Ensure that the condition records are maintained for the specific return reason and the relevant amount ranges.
  
  
  
  Review Return Reason Configuration:
  
  Check the configuration of the return reason in the system. Ensure that it is set up to allow for graduated charges.
  You can do this in the configuration settings under Sales and Distribution > Sales > Sales Documents > Return > Define Return Reasons.
  
  
  
  Verify Pricing Procedure:
  
  Ensure that the pricing procedure assigned to the sales area and the document type includes the necessary condition types for graduated charges.
  You can check this in the configuration under Sales and Distribution > Basic Functions > Pricing > Pricing Control.
  
  
  
  Data Entry Validation:
  
  Review the return order or document for any data entry errors. Ensure that the amounts and return reasons are correctly entered.
  
  
  
  Consult Documentation:
  
  If the issue persists, consult SAP documentation or reach out to your SAP support team for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: VK11, VK12, VOTXN (for checking return reasons), and V/08 (for pricing procedure).
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  Testing: After making changes, perform a test return to ensure that the error no longer occurs.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.