EDI Document is treated as custom when using AQ Transport

(Doc ID 868682.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Application Server Integration B2B - Version: and later   [Release: and later ]
Information in this document applies to any platform.


Using AQ Transport, B2B is treating the EDI document as custom. B2B is able to read the Queue and
dequeue the message, but is unable to understand and process the message


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