How To Fix CFD_RUNTIME061 - Get_additional_data in class &1 for BAdI def &2: wrong number of records

SAP Error Message - Details

• Message type: E = Error

• Message class: CFD_RUNTIME - Custom Fields: Runtime Data

• Message number: 061

• Message text: Get_additional_data in class &1 for BAdI def &2: wrong number of records

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 CFD_RUNTIME061 - Get_additional_data in class &1 for BAdI def &2: wrong number of records ?

  The SAP error message CFD_RUNTIME061 typically indicates an issue with a Business Add-In (BAdI) implementation, specifically related to the method Get_additional_data. This error occurs when the number of records being processed does not match the expected number of records defined in the BAdI implementation.
  
  Cause:
  
  
  Mismatch in Record Count: The error usually arises when the BAdI implementation is trying to process a different number of records than what is expected. This could be due to:
  
  Incorrect logic in the BAdI implementation that alters the number of records.
  Data inconsistencies or unexpected data formats being passed to the BAdI.
  Changes in the data model or structure that the BAdI is not accounting for.
  
  
  
  
  Configuration Issues: Sometimes, the configuration settings related to the BAdI might not be set up correctly, leading to discrepancies in the expected data.
  
  
  Coding Errors: There may be errors in the ABAP code of the BAdI implementation that lead to incorrect handling of data.
  
  
  
  Solution:
  
  
  Review BAdI