How To Fix /ACCGO/TSDB270 - Record with same effective and validity period exists

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/TSDB -

• Message number: 270

• Message text: Record with same effective and validity period exists

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/TSDB270 - Record with same effective and validity period exists ?

  The SAP error message /ACCGO/TSDB270 Record with same effective and validity period exists typically occurs in the context of the SAP General Ledger or Asset Accounting modules. This error indicates that there is an attempt to create or modify a record (such as a transaction or master data) that overlaps with an existing record that has the same effective date and validity period.
  
  Cause:
  
  
  Duplicate Records: The most common cause is that there is already a record in the system with the same effective date and validity period. This can happen if:
  
  A user is trying to create a new record that is identical to an existing one.
  A record was inadvertently created twice.
  There is a data migration or upload process that has resulted in duplicate entries.
  
  
  
  
  Configuration Issues: Sometimes, configuration settings in the system may lead to this error if they are not set up correctly to handle overlapping periods.
  
  
  
  Solution:
  
  
  Check Existing Records: 
  
  Use transaction