How To Fix FSH_MSG_CL_VAS216 - Validity period of condition ID &1 and condition ID &2 overlap

SAP Error Message - Details

• Message type: E = Error

• Message class: FSH_MSG_CL_VAS - Message Class for Value Added Services

• Message number: 216

• Message text: Validity period of condition ID &1 and condition ID &2 overlap

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 FSH_MSG_CL_VAS216 - Validity period of condition ID &1 and condition ID &2 overlap ?

  The SAP error message FSH_MSG_CL_VAS216 indicates that there is an overlap in the validity periods of two condition IDs in the context of the SAP Fashion Management (FSH) module, specifically related to the Value Added Services (VAS) functionality. This error typically arises when you are trying to create or modify conditions that have overlapping validity dates, which is not allowed in the system.
  Cause:
  The error occurs due to the following reasons:
  
  Overlapping Validity Periods: Two condition records have been defined with overlapping validity periods. For example, if Condition ID &1 is valid from January 1 to January 31, and Condition ID &2 is valid from January 15 to February 15, this will trigger the error.
  Incorrect Data Entry: During the creation or modification of conditions, incorrect dates may have been entered, leading to overlaps.
  Configuration Issues: There may be issues in the configuration of the condition types or the way the validity periods are set up in the system.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Validity Periods:
  
  Go to the condition records for both condition IDs mentioned in the error message.
  Verify the validity periods for both conditions and identify the overlapping dates.
  
  
  
  Adjust Validity Periods:
  
  Modify the validity period of one or both condition records to eliminate the overlap. Ensure that the periods do not intersect.
  You can either extend or shorten the validity period of one of the conditions as necessary.
  
  
  
  Delete or Archive Unused Conditions:
  
  If one of the conditions is no longer needed, consider deleting or archiving it to prevent future overlaps.
  
  
  
  Review Configuration:
  
  If the issue persists, review the configuration settings for the condition types in the SAP system to ensure they are set up correctly.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for more detailed guidance on managing condition records and validity periods.
  
  
  
  Testing:
  
  After making adjustments, test the changes by attempting to create or modify the conditions again to ensure that the error no longer occurs.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like VK11 (Create Condition), VK12 (Change Condition), or VK13 (Display Condition) to manage condition records.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  User Roles: Ensure that you have the necessary permissions to modify condition records in the system.
  
  By following these steps, you should be able to resolve the FSH_MSG_CL_VAS216 error and manage your condition records effectively.