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 NOVEMBER 03, 2016

Applies to:

Oracle B2B (Business to Business) - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

The Trading Partner is using hex85 characters as a segment delimiter, and even with the property "b2b.binaryEncodingList", the files are not properly processed.

Cause

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