Content Conversion receiver adapter UTF-8 issue

[Former Member]

Hi gurus,

we have following input xml file;

<ns1:GLACC>

  <ns1:BUKRS>0012</ns1:BUKRS>

  <ns1:DESCR>Köstner</ns1:DESCR>

  <ns1:KTOPL>BLHP</ns1:KTOPL>

  <ns1:SAKNR>0600110040</ns1:SAKNR>

</ns1:GLACC>

after content conversion we got following response;

0012,K?stner,BLHP,0600110040

How can we transfer as "Köstner" ?

Kind Regards,

PM

[rajasekhar_reddy14 · Accepted solution]

change encoding type..Köstner is having some spanish character(not sure).you have to use relevel encoding type to solve this problem/;

[diogo_awaihara · Accepted solution]

As Raja said, UTF-8 does not support "ö" character. Try using ISO-8859-1 instead.

[Former Member · Accepted solution]

German Character!

File receiver adapter hasn't encode type section to choose.

[Former Member · Accepted solution]

Hi,

"Try using ISO-8859-1 instead."

where can i customize it on receiver file adapter?

Regards,

PM

[diogo_awaihara · Accepted solution]

Hi Peter.

It is on File encoding.

Please refer to this doc: http://help.sap.com/saphelp_nwpi71/helpdata/en/44/6830e67f2a6d12e10000000a1553f6/content.htm.

Regards,

Diogo

[diogo_awaihara · Accepted solution]

Select file type BINARY and add the module:

Name = AF_Modules/XMLAnonymizerBean

Type = Local Enterprise Bean

Module Configuration:

Parameter name= anonymizer.acceptNamespaces

Parameter value = <include all prefixes here like: namespace1 ns1 namespace2 ns2>

Parameter name = anonymizer.encoding

Parameter value = = ISO-8859-1

[stefan_grube · Accepted solution]

 File receiver adapter hasn't encode type section to choose. 

Of course it has!

Tab "Processing", set "File Type" = text, then you can apply "File Encoding".

Before you set an encoding, ask the requester of the file, which encoding should be used.

Do not just use any encoding you like, otherwise the file cannot be read by the receiving system.

[former_member184681]

Hi Peter,

Let me add a few words to the discussion. Of course UTF-8 does support the character "ö", see a confirmation in Wikipedia here: http://en.wikipedia.org/wiki/%C3%96#Codes_for_computing

Before you make any changes to your configuration, make sure that when you open the FCC-processed flat file, it is displayed properly by the application you are using. Some tools like Windows' Notepad might not be able to display the file in different encodings, but Notepad++ should do this properly, so make sure to use the right tool and display mode. If you don't change the encoding manually in the receiver CC, it should stay Unicode

Regards,

Greg