B2B 11g: Failed RosettaNet Transactions do not Show up as ERROR in Oracle B2B Reports
Last updated on OCTOBER 25, 2016
Applies to:Oracle SOA Platform – B2B (Business to Business) - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 11gR1]
Information in this document applies to any platform.
On B2B 184.108.40.206.0 version
Incoming transactions to B2B server behave differently between versions 220.127.116.11 and 18.104.22.168
Payload with encoding issue shows wire message as PROCESSING in 22.214.171.124 when it should have gone to ERROR as it does in 126.96.36.199.
Payload with encoding issue shows wire message as PROCESSING in 188.8.131.52
Payload with encoding issue should should show wire message as ERROR in 184.108.40.206
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