B2B B2b.binaryEncodingList And 85 - X12 Inbound Messages That Contain 0x85 As A Delimiter Get Truncated In Oracle B2B And Incorrectly Processed
(Doc ID 1600663.1)
Last updated on MARCH 27, 2019
Applies to:Oracle B2B 10g (Business to Business) - Version 10.1.2.0.0 and later
Information in this document applies to any platform.
The Trading Partner is using hex85 characters as a segment delimiter, and even with the property "b2b.binaryEncodingList", the files are not properly processed.
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