How To Fix /SAPCND/TST_CUS_CONS098 - &1 &2 is not available. Please choose a valid one

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/TST_CUS_CONS -

• Message number: 098

• Message text: &1 &2 is not available. Please choose a valid one

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/TST_CUS_CONS098 - &1 &2 is not available. Please choose a valid one ?

  The SAP error message /SAPCND/TST_CUS_CONS098 &1 &2 is not available. Please choose a valid one typically indicates that there is an issue with the condition records or the configuration settings in the SAP system. This error often arises in the context of condition management, such as pricing, discounts, or other condition-based functionalities.
  Cause:
  
  Missing Condition Records: The specific condition record that is being referenced in the error message does not exist in the system.
  Incorrect Configuration: The configuration settings for the condition type may not be set up correctly, leading to the system not being able to find the required data.
  Data Inconsistency: There may be inconsistencies in the data, such as missing entries in the relevant tables.
  Authorization Issues: The user may not have the necessary authorizations to access the condition records.
  
  Solution:
  
  
  Check Condition Records:
  
  Go to the relevant transaction (e.g., VK11 for creating condition records) and verify if the condition record exists for the specified condition type.
  If it does not exist, create the necessary condition record.
  
  
  
  Review Configuration:
  
  Check the configuration settings for the condition type in the customizing settings (transaction SPRO).
  Ensure that the condition type is properly defined and linked to the relevant pricing procedure.
  
  
  
  Data Consistency Check:
  
  Use transaction codes like SE16 or SE11 to check the relevant database tables for any missing or inconsistent data.
  Ensure that all necessary entries are present and correct.
  
  
  
  Authorization Check:
  
  Verify that the user has the necessary authorizations to access and modify condition records.
  If needed, consult with your SAP security team to ensure proper roles and permissions are assigned.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific condition type or error message for additional insights or known issues.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11, VK12, VK13 (for condition records), and SPRO (for configuration).
  SAP Notes: Search for SAP Notes related to the specific error message or condition type for any patches or updates that may resolve the issue.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution.