Showing results for 
Search instead for 
Did you mean: 

EHS - Import Specifications/Phrases/Reports/etc. - Error code: UTF8_2_UTF16_CONVERSION

Former Member
0 Kudos


We are working to import specification data from CG33.

We have followed this link: which is indicated in:

In the first link have seen, that recording it’s not supported to EHS. It also indicates that there are other ways to import specification data.

We are using CG33, but we are having issues. We can upload files with CG3Z, but when we try to import data, from CG33, the following error appears: “Error code: UTF8_2_UTF16_CONVERSION”

Our system is in S/4HANA, then it’s in UNICODE. The note: “610695 - Export/import with R/3 systems with Unicode” indicates that it’s not possible to export phrases in format UTF-8.

We are not trying, now, to export anything and our system is not in R/3, but we understand that is more or less the same, that is, we want to import specifications in a Unicode system.

We have created one .dat file, but we don’t have a clear example to know if it’s written correctly.

We don’t know in which character standard we have to upload and import the file so that it does not have errors.

In addition, we have followed the following link:

And we have upload the example transfer file for specifications from sap help, but when we want to import data, we see the same error.

We have followed all the indications in the customization.

Could someone help us with this? We have to follow the indications indicated in the note? Could someone help us with an example of how to create a .dat file?

View Entire Topic
0 Kudos

Dear Viktoriya,

I got the same unicode error when trying to import phrases to our SAP system. Reviewing the .dat file on the server I could see that instead of an ü (umlaut/diaresis) there was a # in the file. Well the .txt file was saved as a unicode file but it seems the original excel file was corrupt. I changed the font type for the whole excelsheet ( in Arial), saved it and created a new txt and dat file afterwards. And this time I could import the phrases without any errors.

So my experience is that a lot of problems are caused by excel and that is not always obvious.

Active Contributor
0 Kudos

Dear Ute

I agree to your general statement. If you have "externak sources" of data (e.g. via database, EXCEl or whatever) there exist a 2 "handling risk" in SAP Unicode based EHS systems. On the top: the dat file must have the "right" values (Unicode mode).

So many pitfalls exists in the "data migration approach"; depending on the size (amount) of data to be mirated, a 100% control is never possible; especially not in the EHS sector. E.g. if you migrate from legacy system or SAP system: At least you need to consider may be 10000 REAL_SUB; may be 2000 LIST_SUB etc., Per specificaiotn at least at minimum 50 propertieswil get data (on top: identifier etc.)

Nobody can "control" this amount of data (on top phrases) in detail. According to excperience;

In most cases "Identifiers" and "user define texts" can be problematic (regarding the Unicode topic); but clearly if you have a lot of "eastern languages" to support than "phrases" can be an issue as well.


E.g.may be "" could be of interest