How To Fix 1G645 - start date of markup condition < start date of base condition

SAP Error Message - Details

• Message type: E = Error

• Message class: 1G - BKK: Konditionen

• Message number: 645

• Message text: start date of markup condition < start date of base condition

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 1G645 - start date of markup condition < start date of base condition ?

  The SAP error message 1G645 indicates that there is a conflict in the date settings for markup conditions in pricing. Specifically, the error message states that the start date of the markup condition is earlier than the start date of the base condition. This typically occurs in the context of pricing procedures where conditions are defined with specific validity periods.
  Cause:
  
  Date Overlap: The markup condition has a start date that is set before the start date of the base condition. This can happen if the conditions are not properly aligned in terms of their validity periods.
  Incorrect Configuration: There may be an error in the configuration of the pricing conditions in the SAP system, leading to inconsistencies in the date settings.
  Manual Entry Errors: If the conditions were manually entered or modified, it is possible that the dates were incorrectly set.
  
  Solution:
  
  
  Check Condition Records: Review the condition records for both the markup condition and the base condition. Ensure that the start date of the markup condition is not earlier than the start date of the base condition.
  
  You can do this by navigating to the condition records in the relevant transaction (e.g., VK11 for creating conditions, VK12 for changing conditions).
  
  
  
  Adjust Dates: If you find that the dates are incorrectly set, adjust the start date of the markup condition to be equal to or later than the start date of the base condition.
  
  
  Review Pricing Procedure: Ensure that the pricing procedure is correctly configured and that the conditions are set up in a logical order. This may involve checking the sequence of conditions and their dependencies.
  
  
  Test Changes: After making adjustments, test the pricing procedure to ensure that the error no longer occurs and that the pricing is calculated correctly.
  
  
  Consult Documentation: If you are unsure about the configuration or the implications of changing condition dates, consult SAP documentation or reach out to your SAP support team for guidance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11, VK12, and VK31 for managing condition records.
  Pricing Procedure: Understand how pricing procedures work in SAP, including the sequence of conditions and how they interact with each other.
  SAP Notes: Check for any SAP Notes related to pricing conditions and error messages for additional insights or patches that may address known issues.
  
  By following these steps, you should be able to resolve the error message 1G645 and ensure that your pricing conditions are correctly configured.