B2B picking wrong agreement
Hi All,
I have a trading partner that is set up for 855 "EDI X12 over Generic Exchange" transaction and the same trading partner set up for 856 "EDI X12 over Internet" - AS2.
I have the following setup - we cannot put all transactions in one agreement since the 997s come over different delivery channels.
Agreement 1: EDI 856 (out) and 997 (in) - AS2
Agreement 2: EDI 855 (out) and 997 (in) - EDI/VAN
The 997 for 856 is coming in fine and is being processed successfully. The 997 for 855 is coming back and failing since its finding wrong agreement.
Is this a bug? Shouldn't the processing continue trying to find the correct agreement?
If I quiesce Agreement 1 then the 997s flow through. But this is a manual workaround.
ERROR CODE - AIP-50523
ERROR DESCRIPTION - Machine Info: Description: Document Exchange protocol name "Generic" in message is different from document exchange protocol name "AS2" in agreement StackTrace: Error -: AIP-50523: Document Exchange protocol name "Generic" in message is different from document exchange protocol name "AS2" in agreement at oracle.tip.adapter.b2b.tpa.MessageValidator.validateDocExchange(MessageValidator.java:245) at oracle.tip.adapter.b2b.tpa.MessageValidator.validateMessage(MessageValidator.java:131) at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:769) at oracle.tip.adapter.b2b.tpa.TPAProcessor.processIncomingTPA(TPAProcessor.java:240) at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1833) at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574) at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444) at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399) at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527) at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374) at java.lang.Thread.run(Thread.java:534)
Thanks.