on 04-26-2006 2:43 PM
Hello,
we have a problem with the IDOC Adapter and special characters in the Idoc content.
we sent an idoc from an 4.6c R/3 to XI, in the idoc content we have special characters (e.g. ö ä ü ...),
the Idoc adapter leave the characters untouched, but writes in the "XML-Idoc-Message" encoding=utf-8.
So the receiver adapter like soap would convert the characters incorrectly.
Does anyone have an idea ?
thanks for any help
Thorsten
Message was edited by: Thorsten Stork
Message was edited by: Thorsten Stork
Hi Thorsten,
Did you ever find a solution for the IDoc encoding?
I am faced with the same issue myself in PI 7.3
Regards,
Treasure
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Torsten,
if you only want to change the prolog attriute value from UTF-8 to ISO-8859-1 then just execute a simple ABAP mapping:
Create a string with function ecatt_conv_xstring_to_string.
Replace with normal ABAP.
Create again XSTRING with function ecatt_conv_string_to_xstring
Regards,
Udo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> Stork
>
> Check this urls and configure accordingly:
>
> adID=111712&messageID=1245987
> SAP Notes: 821267
> adID=128690&messageID=1439108
>
> ---Mohan
Hi,
thanks for it, but there is a way described for the JMS Adapter and not a solution for the incoming IDOC adapter(sender).
If you have a solution that I can solve it at the receiver soap adapter, it would beok for me. But I could not conclude to the solution from the JMS Adapter to an other one,sorry.
Regards
Thorsten
hi,
change the encoding of <xml version ... > to ,
<b>ISO-8859-1</b>.
UTF-8 does not recognise those special characters.
Regards,
Bhavesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Thorsten,
Your SAP R/3 system has to be Unicode complaint for them to handle this data.
IF the data is coming from file to R/3 then you can give the correct encoding (ISO-8859-1) in the file adapter and it will handle the data.
Hope in your TCP/IP connections like AI_RUNTIME_JCOSERVER etc you have mentioned unicode in special option tab.
Regards
Vijaya
Message was edited by: vijaya kumari
> Hi Thorsten,
>
> Your SAP R/3 system has to be Unicode complaint for
> them to handle this data.
>
> IF the data is coming from file to R/3 then you can
> give the correct encoding (ISO-8859-1) in the file
> adapter and it will handle the data.
>
> Hope in your TCP/IP connections like
> AI_RUNTIME_JCOSERVER etc you have mentioned unicode
> in special option tab.
>
>
> Regards
> Vijaya
>
>
> Message was edited by: vijaya kumari
Hi,
as I mentioned the SAP R/3 is a 4.6c and there is no option for unicode in the RFC-destinations.
for AI_RUNTIME_JCOSERVER the unicode is activated.
But we get the message via IDOC so the file adpter doesn not help.
Regards
Thorsten
HI Thorsten,
Please see this pdf if its of any help
Also, I hope your LCRSAPRFC and SAPSLDAPI TCP/IP are defined as unicode in both ABPA and Java stack.
Regards
Vijaya
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.