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

SAP Error Message - Details

• 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.

Smart SAP Assistant

• What is the cause and solution for SAP error message ICC-FI079 - Error in batch counter; &1 records expected, &2 read ?

  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 the expected structure, causing the system to read fewer records.
  Database Locks or Issues: Database locks or issues with the underlying database can prevent the system from reading all the expected records.
  
  Solutions:
  
  Check Source Data: Verify the integrity and completeness of the source data. Ensure that all expected records are present and correctly formatted.
  Review Configuration: Check the configuration settings for the batch job or process. Ensure that all parameters are set correctly and that they match the expected input.
  Debug Custom Programs: If the error occurs in a custom ABAP program, debug the program to identify any logical errors or issues in the record processing logic.
  Validate File Formats: If the data is being imported from a file, ensure that the file format matches the expected structure. Check for any discrepancies in delimiters, headers, or data types.
  Check Database Status: Investigate the database for any locks or issues that may be preventing the reading of records. Ensure that the database is functioning correctly and that there are no connectivity issues.
  
  Related Information:
  
  Transaction Codes: Depending on the context of the error, you may want to check transaction codes related to batch processing, such as SM37 (Job Monitoring) or SE38 (ABAP Program Execution).
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  Logs and Traces: Review application logs (transaction SLG1) and system logs (transaction SM21) for any additional error messages or warnings that may provide more context about the issue.
  Testing: If possible, replicate the issue in a test environment to better understand the conditions that lead to the error.
  
  By following these steps, you should be able to identify the root cause of the ICC-FI079 error and implement an appropriate solution.