How To Fix GD064 - Too many log entries. Transfer will be terminated. &1. &2.

SAP Error Message - Details

• Message type: E = Error

• Message class: GD - EDT: External data transfer

• Message number: 064

• Message text: Too many log entries. Transfer will be terminated. &1. &2.

What causes this issue?

(&V1&) log entries have been made already. A maximum of (&V2&) is
permitted. More entries could lead to an
uncontrolled termination.

System Response

The system carries out a controlled termination.

How to fix this error?

A restart of the terminated transfer can lead repeatedly to the same
reason for the termination, since no further entries are possible in
the log.
In the log, determine to which record the entry data has been written
to the database. Carry out another transfer run. The entry data should
not include the data that has been processed already.
Ensure that the number of log entries is not too high. You could, for
example, disable the warning and information notifications. Check, as
far as possible, that your entry data is correct.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GD064 - Too many log entries. Transfer will be terminated. &1. &2. ?

  The SAP error message GD064 ("Too many log entries. Transfer will be terminated. &1. &2.") typically occurs when there are too many log entries generated during a data transfer process, such as during a batch input session or data upload. This can happen in various scenarios, including data migration, system upgrades, or when using tools like LSMW (Legacy System Migration Workbench).
  
  Cause:
  
  Excessive Log Entries: The system has a limit on the number of log entries that can be created during a transfer. If this limit is exceeded, the process will be terminated to prevent performance issues.
  Large Data Volume: If you are processing a large volume of data, it can lead to a high number of log entries.
  Configuration Settings: The configuration settings for logging in the specific transaction or process may be set to a level that generates too many logs.
  
  
  Solution:
  
  Reduce Data Volume: If possible, try to split the data into smaller