Intermittent B2B-50547 Errors Occuring for Active Agreement
(Doc ID 1528447.1)
Last updated on AUGUST 08, 2018
Applies to:Oracle SOA Suite - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
***Checked for relevance on 18-July-2014***
On : 220.127.116.11.0 version, B2B Engine
Out of a 1000 successful 997 documents sent by a trading partner, 1 or 2 failures are seen in B2B with errors, B2B-50036, B2B-50037, or B2B-50547.
1) In one scenario, the first time trading partner send a 997, it fails with B2B-50036. The second attempt to send the same 997 fails with B2B-50037.
2) In another scenario, the first time the trading partner sends a 997, it fails B2B-50036 but the second attempt to send the same 997 fails with B2B-50547. In this case, a negative MDN is generated but never sent to the trading partner, and ends up in the IP_IN_QUEUE as an error.
The issue can be reproduced at will with the following steps:
1. Remote trading partner sends 997.
2. B2B generates error B2B-50036 for the document.
3. Trading partner resends the same 997, and a B2B-50037 or B2B-50547 error occurs.
4. For a B2B-50547, a negative MDN is created but never sent to the trading partner.
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