B2B 11g: Getting " Invalid delimiters encountered" Error

(Doc ID 1545564.1)

Last updated on NOVEMBER 03, 2016

Applies to:

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


When sending an outbound 4010-810 document, it is working fine if we set the segment delimiter value as 0x15 , but when we are setting the value of segment delimiter as 0x5E i.e. ^ ; it is giving the following error in the log:

Error -: B2B-51507: Payload validation error.
at oracle.tip.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2754)
at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1622)
at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:1090)
at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1539)
at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:801)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3879)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3205)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:677)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:211)

 Following error is seen in B2B console:

Error Code B2B-51507
Error Description Machine Info: (xxxx.xx.oracle.com) Description: Payload validation error.
Error Severity ERROR
Error Text Error Brief : Invalid delimiters encountered.

Following values are passed in XML form via SOA layer:
ElementDelimiter: 0x2A
SubelementDelimiter: 0x3E
SegmentDelimiter: 0x5E



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