How To Fix /ACCGO/TSDB123 - Validity start date overlaps with existing record

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/TSDB -

• Message number: 123

• Message text: Validity start date overlaps with existing record

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 /ACCGO/TSDB123 - Validity start date overlaps with existing record ?

  The SAP error message /ACCGO/TSDB123 Validity start date overlaps with existing record typically occurs in the context of managing time series data, particularly when dealing with master data records that have validity periods. This error indicates that the validity start date you are trying to enter for a new record overlaps with an existing record's validity period.
  Cause:
  
  Overlapping Dates: The new record's validity start date is set to a date that falls within the validity period of an existing record. For example, if an existing record is valid from January 1, 2023, to December 31, 2023, and you try to create a new record with a start date of June 1, 2023, this will trigger the error.
  Incorrect Data Entry: There may be a mistake in the data entry, such as entering the wrong start date or not considering the existing records.
  Data Migration Issues: If data is being migrated from another system, there may be conflicts in the validity periods of the records.
  
  Solution:
  
  Check Existing Records: Review the existing records in the system to identify the validity periods that are causing the overlap. You can do this by querying the relevant database table or using transaction codes that allow you to view the records.
  Adjust Dates: Modify the validity start date of the new record to ensure it does not overlap with existing records. This may involve changing the start date to a later date or adjusting the end date of the existing record if appropriate.
  Delete or Archive Old Records: If the existing records are no longer needed, consider deleting or archiving them to free up the validity period for new entries.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidelines on managing time series data and validity periods.
  Use Transaction Codes: Utilize relevant transaction codes (like SE16 or SE11) to view and manage the records in the database.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes related to the specific module you are working with (e.g., /ACCGO for accounting).
  Data Model: Understand the data model and how validity periods are structured in your SAP system.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Authorization: Ensure you have the necessary permissions to modify records in the system.
  
  By following these steps, you should be able to resolve the error and successfully manage the validity periods of your records in SAP.