This content has been marked as final. Show 3 replies
It may not be an issue with EDI char set but it could be an issue with the character encoding of inbound payload and character encoding of your B2B server. Few questions -
1. Exactly which version of B2B are you working with and what is the patch level (opatch -lsinventory output)?
2. Is message security (signing/encryption) enabled in your case?
3. What is the character encoding of inbound payload?
4. What is the character encoding of your B2B server (by default B2B works with UTF-8 encoding but it can be changed globally by setting B2B EM property b2b.encoding)
You may be a hitting a known product bug so would suggest to file a SR with support, in parallel.
Thanks for your reply.
About your questions:
1.Version of B2B is 126.96.36.199,without any patch.
2.I did not use singing/encryption
3.The character encoding of inbound payload is UTF-8
4.The property b2b.encoding in em is UTF-8
Edited by: Jacky NM on 2013-1-15 下午6:44
Can you please mail across a sample payload and your B2B agreement export to my id (in my profile)? Would like to verify once. Not sure but, either the input payload is not actually UTF-8 encoded or you are hitting a known bug.