How To Fix VK058 - Condition record number & does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: VK - Pflege und Bearbeitung von Konditionen

• Message number: 058

• Message text: Condition record number & does not exist

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 VK058 - Condition record number & does not exist ?

  The SAP error message VK058 ("Condition record number & does not exist") typically occurs in the context of pricing conditions in SAP, particularly when working with sales documents, pricing procedures, or condition records. This error indicates that the system is unable to find a specific condition record that is required for pricing determination.
  Cause:
  
  
  Missing Condition Record: The most common cause is that the condition record for the specified condition type does not exist in the system. This could be due to:
  
  The condition record was never created.
  The condition record was deleted.
  The condition record is not valid for the specific combination of key fields (e.g., customer, material, sales organization, etc.).
  
  
  
  Incorrect Key Fields: The key fields used to access the condition record may not match the fields defined in the condition record. This can happen if there are changes in master data or if the pricing procedure has been modified.
  
  
  Condition Type Configuration: The condition type may not be properly configured in the pricing procedure, leading to the system not being able to find the relevant condition records.
  
  
  Solution:
  
  
  Check Condition Records: 
  
  Use transaction code VK11 (Create Condition) or VK12 (Change Condition) to check if the condition record exists for the relevant condition type.
  Ensure that the condition record is created for the correct combination of key fields.
  
  
  
  Create Missing Condition Records: If the condition record does not exist, create it using transaction code VK11. Make sure to enter all necessary details correctly.
  
  
  Review Pricing Procedure: 
  
  Check the pricing procedure assigned to the sales document type. Use transaction code V/08 to review and adjust the pricing procedure if necessary.
  Ensure that the condition type is included in the pricing procedure and that it is configured correctly.
  
  
  
  Check Validity Dates: Ensure that the validity dates of the condition record are correct. If the record is valid only for a specific period, make sure the current date falls within that range.
  
  
  Debugging: If the issue persists, consider debugging the pricing procedure to identify where the condition record lookup is failing.
  
  
  Related Information:
  
  
  Transaction Codes:
  
  VK11: Create Condition Record
  VK12: Change Condition Record
  VK13: Display Condition Record
  V/08: Maintain Pricing Procedures
  
  
  
  Condition Types: Familiarize yourself with the condition types relevant to your pricing strategy (e.g., discounts, surcharges, taxes).
  
  
  Master Data: Ensure that the master data (customer, material, etc.) is correctly maintained and that there are no inconsistencies.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to condition records and pricing.
  
  
  By following these steps, you should be able to resolve the VK058 error and ensure that the necessary condition records are in place for pricing determination in SAP.