B2B fails to preserve special characters in custom files
Last updated on OCTOBER 24, 2016
Applies to:Oracle SOA Suite - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
In B2B 126.96.36.199, a custom file is configured to be treated as binary that is to be SFTP'd outbound to a trading partner. The file itself contains a special character (i.e.Reneé) that is getting converted but it should stay preserved.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms