B2B 11g: Failed RosettaNet Transactions do not Show up as ERROR in Oracle B2B Reports
(Doc ID 1517275.1)
Last updated on MARCH 04, 2019
Applies to:Oracle B2B 10g (Business to Business) - Version 10.1.2.0.0 and later
Information in this document applies to any platform.
On B2B 22.214.171.124.0 version
Incoming transactions to B2B server behave differently between versions 126.96.36.199 and 188.8.131.52
Payload with encoding issue shows wire message as PROCESSING in 184.108.40.206 when it should have gone to ERROR as it does in 220.127.116.11.
Payload with encoding issue shows wire message as PROCESSING in 18.104.22.168
Payload with encoding issue should should show wire message as ERROR in 22.214.171.124
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