How To Fix CNV737 - &2 records read and &3 records inserted in table &1

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV - Conversion: Messages for Conversion Services (CNCC)

• Message number: 737

• Message text: &2 records read and &3 records inserted in table &1

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 CNV737 - &2 records read and &3 records inserted in table &1 ?

  The SAP error message "CNV737 &2 records read and &3 records inserted in table &1" typically occurs during data migration or data transfer processes, particularly when using SAP's Data Migration tools or during the execution of a conversion program. This message indicates that a certain number of records were read from a source but not all of them were successfully inserted into the target table.
  Cause:
  
  Data Quality Issues: The records being read may contain invalid data or data that does not meet the constraints of the target table (e.g., data type mismatches, missing mandatory fields).
  Mapping Errors: There may be issues with the mapping of fields from the source to the target table, leading to failed inserts.
  Database Constraints: Constraints such as primary keys, foreign keys, or unique constraints in the target table may prevent certain records from being inserted.
  Technical Errors: There could be technical issues such as database locks, connection problems, or insufficient authorizations.
  
  Solution:
  
  Check Logs: Review the detailed logs generated during the migration process to identify specific records that failed to insert and the reasons for their failure.
  Data Validation: Validate the data in the source to ensure it meets the requirements of the target table. This may involve cleaning or transforming the data.
  Adjust Mapping: Ensure that the mapping of fields from the source to the target table is correct and that all necessary fields are included.
  Review Constraints: Check the constraints on the target table and ensure that the data being inserted complies with these constraints.
  Error Handling: Implement error handling in the migration process to capture and log errors for further analysis.
  Testing: Conduct thorough testing with a smaller dataset to identify and resolve issues before performing a full migration.
  
  Related Information:
  
  Transaction Codes: Depending on the context, you may be using transaction codes like LSMW (Legacy System Migration Workbench), or other data migration tools.
  SAP Notes: Check SAP Notes for any known issues related to the specific migration tool or process you are using.
  Documentation: Refer to SAP documentation for guidelines on data migration and best practices to avoid common pitfalls.
  
  If the issue persists after following these steps, it may be beneficial to consult with SAP support or a technical consultant who specializes in data migration.