How To Fix SD_DT060 - Maximum number of segregate by conditions &1 is exceeded

SAP Error Message - Details

• Message type: E = Error

• Message class: SD_DT - DD: Messages for Tuning Objects

• Message number: 060

• Message text: Maximum number of segregate by conditions &1 is exceeded

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 SD_DT060 - Maximum number of segregate by conditions &1 is exceeded ?

  The SAP error message SD_DT060, which states "Maximum number of segregate by conditions &1 is exceeded," typically occurs in the context of pricing or condition records in the Sales and Distribution (SD) module. This error indicates that the number of condition records that can be processed for a specific pricing procedure or condition type has exceeded the predefined limit.
  Cause:
  
  Exceeding Limits: Each condition type in SAP has a maximum number of allowed condition records (segregate by conditions). When the number of records exceeds this limit, the error is triggered.
  Configuration Settings: The limit is defined in the configuration settings of the pricing procedure. It may be set too low for the business requirements.
  Complex Pricing Procedures: If your pricing procedure is complex and involves many condition types, it may lead to exceeding the limit.
  
  Solution:
  
  Review Condition Records: Check the number of condition records for the specific condition type that is causing the error. You can do this by navigating to the condition records in the SAP system.
  Adjust Configuration: If necessary, adjust the configuration settings for the pricing procedure to increase the limit for the number of condition records. This can be done in the SPRO transaction under:
  
  Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Condition Types.
  
  
  Consolidate Condition Records: If possible, consolidate condition records to reduce the total number. This may involve merging similar records or reviewing the necessity of each condition.
  Check for Redundant Conditions: Identify and remove any redundant or obsolete condition records that may not be needed anymore.
  Consult Documentation: Refer to SAP documentation or consult with your SAP Basis or SD consultant for specific guidance on adjusting limits and best practices.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) to manage condition records.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on handling condition records.
  Performance Considerations: Be mindful that increasing the limit may have performance implications, especially if the system processes a large number of transactions.
  
  If the issue persists after trying the above solutions, it may be beneficial to engage with SAP support or a qualified SAP consultant for further assistance.