My Oracle Support Banner

B2B-50549 for Trading Partners Sharing Interchange ID (Doc ID 1628200.1)

Last updated on AUGUST 17, 2018

Applies to:

Oracle SOA Suite - Version 11.1.1.7.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.1.7.0 version, B2B Engine

When attempting to process an inbound TA1 document for a trading partner that shares an interchange ID with another trading partner, the following error occurs.

ERROR
-----------------------
Error -: B2B-50549: Cannot uniquely identify a trading partner. The trading partners BLFSHOP, BLFINDV have the same set of identifications.[[
at oracle.tip.b2b.tpa.RepoDataAccessor.filterTradingPartner(RepoDataAccessor.java:1933)
at oracle.tip.b2b.tpa.RepoDataAccessor.identifyTPByCfg(RepoDataAccessor.java:1851)
at oracle.tip.b2b.tpa.RepoDataAccessor.processParty(RepoDataAccessor.java:1808)
at oracle.tip.b2b.tpa.RepoDataAccessor.queryAgreementMO(RepoDataAccessor.java:712)
at oracle.tip.b2b.tpa.RepoDataAccessor.getAgreementDetails(RepoDataAccessor.java:415)
at oracle.tip.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:465)
at oracle.tip.b2b.tpa.TPAProcessor.processIncomingTPA(TPAProcessor.java:242)
at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:2560)
at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1751)
at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:4258)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3856)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3309)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:637)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:214)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
 Error -: B2B-50549: Cannot uniquely identify a trading partner. The trading partners BLFSHOP, BLFINDV have the same set of identifications.
at oracle.tip.b2b.tpa.RepoDataAccessor.filterTradingPartner(RepoDataAccessor.java:1933)
at oracle.tip.b2b.tpa.RepoDataAccessor.identifyTPByCfg(RepoDataAccessor.java:1851)
at oracle.tip.b2b.tpa.RepoDataAccessor.processParty(RepoDataAccessor.java:1808)
at oracle.tip.b2b.tpa.RepoDataAccessor.queryAgreementMO(RepoDataAccessor.java:712)
at oracle.tip.b2b.tpa.RepoDataAccessor.getAgreementDetails(RepoDataAccessor.java:415)
at oracle.tip.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:465)
at oracle.tip.b2b.tpa.TPAProcessor.processIncomingTPA(TPAProcessor.java:242)
at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:2560)
at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1751)
at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:4258)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3856)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3309)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:637)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:214)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)

]]


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1) Copy the TA1 data file to the listening channel folder.
2) Go to B2B Console -> Reports -> Business Message and you find MSG_ERROR occurred for the TA1 document.
3) Click the Details icon and you find error B2B-50549.

 

Cause

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
Symptoms
Cause
Solution


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.