How To Fix CONNECT_PRC_SAPCND058 - &1 (&4) exceeds upper limit &2 (&4) of record with condition type &3

SAP Error Message - Details

• Message type: E = Error

• Message class: CONNECT_PRC_SAPCND -

• Message number: 058

• Message text: &1 (&4) exceeds upper limit &2 (&4) of record with condition type &3

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 CONNECT_PRC_SAPCND058 - &1 (&4) exceeds upper limit &2 (&4) of record with condition type &3 ?

  The SAP error message CONNECT_PRC_SAPCND058 typically indicates that a certain value associated with a condition record has exceeded a predefined upper limit. This error is often encountered in the context of pricing conditions in SAP, particularly when working with condition types in pricing procedures.
  Cause:
  The error message can occur due to several reasons:
  
  Exceeding Limits: The value being processed (e.g., a discount, surcharge, or price) exceeds the maximum limit defined for the specific condition type in the pricing procedure.
  Configuration Issues: The condition type may have been configured with incorrect limits or thresholds in the pricing procedure.
  Data Entry Errors: Incorrect data entry in the transaction that leads to a value exceeding the allowed limit.
  Master Data Issues: The master data (like customer or material master) may have settings that conflict with the pricing conditions.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Condition Records:
  
  Go to the condition records for the specific condition type (using transaction codes like VK11, VK12, or VK13).
  Verify the values and ensure they do not exceed the defined limits.
  
  
  
  Review Pricing Procedure:
  
  Check the configuration of the pricing procedure (transaction code V/08).
  Look for the condition type in question and review its settings, including any upper limits defined.
  
  
  
  Adjust Limits:
  
  If necessary, adjust the upper limit for the condition type in the pricing procedure to accommodate the required values.
  
  
  
  Data Validation:
  
  Ensure that the data being entered in the transaction is correct and does not exceed the limits set in the system.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or consult with your SAP functional consultant to understand the specific configuration and limits for the condition type.
  
  
  
  Testing:
  
  After making changes, perform tests to ensure that the error no longer occurs and that the pricing behaves as expected.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11 (Create Condition), VK12 (Change Condition), VK13 (Display Condition), and V/08 (Pricing Procedure).
  Condition Types: Understand the specific condition types used in your pricing procedure and their configurations.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  
  If the issue persists after following these steps, it may be beneficial to engage with your SAP support team or a consultant for further investigation.