How To Fix 69590 - Last condition item reached

SAP Error Message - Details

• Message type: E = Error

• Message class: 69 - Central Functions of Financial Asset Management

• Message number: 590

• Message text: Last condition item reached

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 69590 - Last condition item reached ?

  The SAP error message "69590 Last condition item reached" typically occurs in the context of pricing in sales documents, such as sales orders or billing documents. This message indicates that the system has processed all the condition items for a particular pricing procedure, and there are no more condition records to evaluate.
  Cause:
  
  Pricing Procedure Configuration: The pricing procedure may be configured in such a way that it has reached the last condition item without finding any applicable condition records.
  Missing Condition Records: There may be missing condition records for the relevant pricing conditions in the master data (e.g., customer master, material master).
  Condition Exclusion: Certain conditions may be excluded based on the configuration or the specific transaction being processed.
  Incorrect Sequence: The sequence of condition types in the pricing procedure may not allow for further conditions to be applied.
  
  Solution:
  
  Check Condition Records: Verify that the necessary condition records exist for the pricing conditions being used. You can do this by using transaction codes like VK13 (Display Condition) to check the relevant condition types.
  Review Pricing Procedure: Ensure that the pricing procedure assigned to the sales document is correctly configured. You can check this in the configuration settings (transaction code SPRO).
  Adjust Condition Types: If certain condition types are not needed, consider adjusting the pricing procedure to remove or modify them.
  Debugging: If the issue persists, you may need to debug the pricing logic to see how the conditions are being processed. This can help identify if there are any logical errors in the pricing procedure.
  Consult Documentation: Review SAP documentation or notes related to pricing procedures and condition types for any specific guidance or known issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) for managing condition records.
  Pricing Procedure Configuration: Understand how to navigate to the pricing procedure configuration in SPRO, specifically under Sales and Distribution > Basic Functions > Pricing > Pricing Control.
  SAP Notes: Check for any SAP Notes that may address specific issues related to pricing and condition records.
  
  If the problem continues after checking these areas, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.