B2B fails to preserve special characters in custom files
(Doc ID 2196130.1)
Last updated on SEPTEMBER 05, 2018
Applies to:Oracle SOA Suite - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
In B2B 22.214.171.124, 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.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document