How To Fix /SAPCND/MAINTENANCE058 - There are no tables with &2 for condition type &1

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/MAINTENANCE -

• Message number: 058

• Message text: There are no tables with &2 for condition type &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 /SAPCND/MAINTENANCE058 - There are no tables with &2 for condition type &1 ?

  The SAP error message /SAPCND/MAINTENANCE058 indicates that there are no tables associated with the specified condition type (&1) for the specified condition table (&2). This error typically occurs in the context of condition maintenance, particularly when working with pricing or other condition-based functionalities in SAP.
  Cause:
  
  Missing Configuration: The condition type may not be properly configured to use the specified condition table. This can happen if the condition type is not assigned to any tables in the configuration settings.
  Incorrect Condition Type or Table: The condition type or condition table specified in the error message may be incorrect or may not exist in the system.
  Transport Issues: If the configuration was recently transported from another system, there may have been issues during the transport that resulted in missing or incomplete data.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view or access the condition tables.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the transaction code V/06 (for condition types) or V/07 (for condition tables) and verify that the condition type is correctly assigned to the condition table.
  Ensure that the condition type is configured to use the correct access sequence.
  
  
  
  Verify Condition Type and Table:
  
  Double-check the condition type and condition table names to ensure they are correct and exist in the system.
  Use transaction V/03 to display the condition type and confirm its settings.
  
  
  
  Transport Check:
  
  If the issue arose after a transport, check the transport logs for any errors or warnings related to the condition type or tables.
  Ensure that all necessary objects were included in the transport request.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to access and maintain condition types and tables. This can be checked with the help of your SAP security team.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help files related to condition maintenance for any additional insights or steps that may be required.
  
  
  
  SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  V/06: Maintain Condition Types
  V/07: Maintain Condition Tables
  V/03: Display Condition Types
  V/02: Change Condition Types
  
  
  
  Access Sequences: Ensure that the access sequence associated with the condition type is correctly defined and includes the necessary condition tables.
  
  
  SAP Community: Consider searching or posting in the SAP Community forums for additional insights from other users who may have encountered similar issues.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.