How To Fix /SCMTMS/FAG_MSG135 - Start of validity must not overlap with end of val. of another val. per.

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/FAG_MSG -

• Message number: 135

• Message text: Start of validity must not overlap with end of val. of another val. per.

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 /SCMTMS/FAG_MSG135 - Start of validity must not overlap with end of val. of another val. per. ?

  The SAP error message /SCMTMS/FAG_MSG135 indicates that there is a conflict in the validity periods of two or more entries in the system. Specifically, it means that the start date of a new validity period overlaps with the end date of an existing validity period for the same object or entity. This is a common issue when managing time-dependent data in SAP, such as master data or configuration settings.
  Cause:
  
  Overlapping Validity Periods: You are trying to create or modify a record (like a transportation lane, rate, or other configuration) where the start date of the new record overlaps with the end date of an existing record.
  Incorrect Date Entries: The dates entered may not be correctly aligned, leading to overlaps.
  Multiple Records: There may be multiple records for the same object that have overlapping validity periods.
  
  Solution:
  
  Check Existing Records: Review the existing records for the object you are trying to create or modify. Look for any records that have overlapping validity periods.
  Adjust Dates: Modify the start or end dates of the new or existing records to ensure that there is no overlap. Ensure that the new record starts after the existing record ends.
  Delete or Archive Old Records: If the existing records are no longer needed, consider deleting or archiving them to avoid conflicts.
  Consult Documentation: Refer to the SAP documentation or help resources for guidance on managing validity periods in the specific module you are working with (e.g., SAP Transportation Management).
  Use Transaction Codes: Utilize relevant transaction codes (like /SCMTMS/TRANSPORT_LANE for transportation lanes) to view and manage the records.
  
  Related Information:
  
  SAP Notes: Check for any SAP Notes related to this error message for additional insights or patches that may address the issue.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  Testing: After making changes, test the functionality to ensure that the error does not reoccur and that the system behaves as expected.
  
  By following these steps, you should be able to resolve the error and ensure that your validity periods are correctly configured in SAP.