How To Fix /PRA/VL_SD059 - Invalid dated record set found

SAP Error Message - Details

• Message type: E = Error

• Message class: /PRA/VL_SD -

• Message number: 059

• Message text: Invalid dated record set found

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 /PRA/VL_SD059 - Invalid dated record set found ?

  The SAP error message /PRA/VL_SD059 Invalid dated record set found typically occurs in the context of SAP's Sales and Distribution (SD) module, particularly when dealing with pricing or condition records that have date validity issues. This error indicates that there is a problem with the date validity of the records being processed, which can prevent the system from correctly determining the applicable pricing or conditions for a transaction.
  Causes:
  
  Invalid Date Ranges: The condition records may have overlapping or invalid date ranges. For example, a record might have a start date that is after its end date.
  Missing Records: There may be no valid condition records for the specified date range, leading to the system being unable to find applicable pricing.
  Incorrect Configuration: Configuration settings in the pricing procedure or condition types may not be set up correctly, leading to issues with how date validity is handled.
  Data Inconsistencies: There may be inconsistencies in the master data or transaction data that affect the validity of the records.
  
  Solutions:
  
  
  Check Condition Records: Review the condition records in the relevant condition tables (e.g., KONV) to ensure that the date ranges are valid and do not overlap incorrectly.
  
  Use transaction codes like VK11 (Create Condition) or VK12 (Change Condition) to check and modify the records.
  
  
  
  Adjust Date Ranges: If you find any records with invalid date ranges, adjust them to ensure that the start date is before the end date and that there are no overlaps with other records.
  
  
  Review Pricing Procedure: Check the pricing procedure configuration to ensure that it is set up correctly and that the condition types are properly defined with respect to date validity.
  
  
  Check for Missing Records: Ensure that there are valid condition records for the date range you are trying to process. If necessary, create new records to cover the required dates.
  
  
  Data Consistency Checks: Run consistency checks on the master data and transaction data to identify any discrepancies that may be causing the issue.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the specific error message for additional guidance and troubleshooting steps.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11, VK12, VK13 (Display Condition), and VK31 (Mass Maintenance) for managing condition records.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for notes in the SAP Support Portal.
  User Forums: Consider visiting SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  If the problem persists after following these steps, it may be beneficial to consult with your SAP support team or a technical consultant who can provide deeper insights into the specific configuration and data setup in your SAP environment.