How To Fix ICC-FI079 - Error in batch counter; &1 records expected, &2 read

ICC-FI079 - Overview

• Message type: E = Error

• Message class: ICC-FI - Dunning (Sweden)

• Message number: 079

• Message text: Error in batch counter; &1 records expected, &2 read

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.

ICC-FI079 - Details

• The SAP error message ICC-FI079 indicates that there is a discrepancy between the expected number of records and the actual number of records read during a batch processing operation. Specifically, the message states that the system expected a certain number of records (indicated by &1) but only read a different number (indicated by &2). This can occur in various contexts, such as during data uploads, batch jobs, or processing of financial documents.
  Causes:
  
  Data Inconsistency: The source data may be incomplete or corrupted, leading to a mismatch in the expected and actual record counts.
  
  Configuration Issues: Incorrect configuration settings in the batch processing job or in the related modules can lead to this error.
  Program Logic Errors: There may be bugs or logical errors in the custom ABAP programs or scripts that handle the batch processing.
  File Format Issues: If the data is being read from an external file, the file format may not match