How To Fix 1G058 - Condition no longer exists

SAP Error Message - Details

• Message type: E = Error

• Message class: 1G - BKK: Konditionen

• Message number: 058

• Message text: Condition no longer exists

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 1G058 - Condition no longer exists ?

  The SAP error message 1G058 - Condition no longer exists typically occurs in the context of pricing and conditions in SAP, particularly when dealing with sales documents, purchase orders, or pricing conditions. This error indicates that the system is unable to find a valid condition record for the pricing or discount that is being applied to a transaction.
  Causes:
  
  Condition Record Deletion: The condition record that was previously valid has been deleted or marked for deletion.
  Validity Period: The condition record may have a validity period that has expired, meaning it is no longer applicable for the current transaction date.
  Incorrect Condition Type: The condition type being referenced may not be set up correctly or may not exist in the system.
  Master Data Issues: There may be issues with the master data (e.g., customer, material) that are affecting the pricing conditions.
  Configuration Changes: Recent changes in configuration or updates to the pricing procedure may have affected the availability of certain condition records.
  
  Solutions:
  
  Check Condition Records: Use transaction codes like VK11 (Create Condition), VK12 (Change Condition), or VK13 (Display Condition) to check if the condition record exists and is valid.
  Review Validity Dates: Ensure that the validity dates of the condition records cover the date of the transaction you are processing.
  Recreate Condition Records: If the condition record has been deleted, you may need to recreate it using the appropriate transaction.
  Check Configuration: Review the pricing procedure configuration to ensure that the condition types are correctly set up and linked to the appropriate pricing procedure.
  Master Data Verification: Verify that the relevant master data (customer, material, etc.) is correctly maintained and that there are no inconsistencies.
  Consult Documentation: Refer to SAP documentation or help resources for specific details related to the condition types and pricing procedures in your system.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11, VK12, VK13, and others related to pricing and conditions.
  Pricing Procedure: Understand how pricing procedures work in SAP and how they relate to condition types and records.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Authorization: Ensure that you have the necessary authorizations to view and modify condition records.
  
  If the issue persists after checking these areas, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in pricing and conditions.