ALE/JCO/IDOC: Differently encoded content parts in one fixlength IDOC

[former_member1374967]

Hello community,

I have the following situation:

- Partner has custom IDOCs to exchange

- Encoding settings for the Interface: Non-Unicode: "Detect client code page, based on logon at runtime"

- EDI Client with latest JCO 3.x

Problem:

- EDI Client sends 1100 and gets IDOC with the data partly encoded as 1100 and partly as unicode

Correct behavior:

- All segments are delivered to communication partner in 1100

Workaround:

Cast fixlength IDOC as unicode and then convert it to target LATIN1 Encoding. Has potential risks of unconverted chars, thus suboptimal.

Any idea what could be the reason?

Thanks,

Yefym.

[Former Member]

Thank you for visiting SAP Community to get answers to your questions. Since you're asking a question here for the first time, I recommend that you familiarize yourself with: https://community.sap.com/resources/questions-and-answers, as it provides tips for preparing questions that draw responses from our members.

For example, you can:

- outline what steps you took to find answers (and why they weren't helpful)

- share screenshots of what you've seen/done

- make sure you've applied the appropriate tags

- use a more descriptive subject line

The more details you provide, the more likely it is that members will be able to respond. Feel free to also take our Q&A tutorial at: https://developers.sap.com/tutorials/community-qa.html

Should you wish, you can revise your question by selecting Actions, then Edit.

By adding a picture to your profile you encourage readers to respond: https://developers.sap.com/tutorials/community-profile.html

Questions on how to draw responses from members? Check out this discussion on how to improve questions. https://groups.community.sap.com/t5/welcome-corner-discussions/advice-from-sap-champions-questions-a...