How To Fix 1G630 - Condition category &1 already has a condition until &2

1G630 - Overview

• Message type: E = Error

• Message class: 1G - BKK: Konditionen

• Message number: 630

• Message text: Condition category &1 already has a condition until &2

What causes this issue?

Create a new condition header for a condition category. Note that there
is already a condition header for the condition category from &v1& until
&v2&. Check that the time periods of the condition headers do not
overlap.

How to fix this error?

Maintain the conditions for the &v1& category according to your business
requirements, ensuring that none of the time periods overlap.

Error message extract from SAP system. Copyright SAP SE.

1G630 - Details

• The SAP error message 1G630 indicates that there is a conflict with a condition record in the pricing procedure. Specifically, it means that a condition category (denoted by &1) already has a condition record valid until a specified date (&2). This typically occurs when you are trying to create or change a condition record that overlaps with an existing record's validity period.
  
  Cause:
  
  Overlapping Validity Periods: You are attempting to create or modify a condition record for a condition type that already has an existing record with a validity period that overlaps with the new record you are trying to create.
  Incorrect Dates: The start or end dates of the new condition record may not be set correctly, leading to a conflict with existing records.
  Multiple Records: There may be multiple records for the same condition type that are not properly managed.
  
  
  Solution:
  
  
  Check Existing Condition Records:
  
  Use transaction code VK13 (Display Condition) to check existing condition