How To Fix CNV_CMIS160 - Importing table is empty; incorrect separator possibly used

CNV_CMIS160 - Overview

• Message type: E = Error

• Message class: CNV_CMIS - Message class for CMIS

• Message number: 160

• Message text: Importing table is empty; incorrect separator possibly used

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.

CNV_CMIS160 - Details

• The SAP error message CNV_CMIS160 indicates that there is an issue with importing data into a table, specifically that the table is empty. This often occurs when the data import process cannot find any valid records to import, which can be due to an incorrect separator being used in the data file.
  Causes:
  
  Incorrect Separator: The most common cause is that the data file uses a different separator than what the import process expects (e.g., using a comma instead of a semicolon, or vice versa).
  Empty Data File: The data file being imported might be empty or not properly formatted.
  File Encoding Issues: The file might be encoded in a format that is not compatible with the import process (e.g., UTF-16 instead of UTF-8).
  Data Format Issues: The data might not conform to the expected format, such as missing required fields or incorrect data types.
  
  Configuration Issues: The import configuration settings in SAP might not be