B2B 11g - Checking Missing Segments, Loops or Elements in a Transaction Does Not Throw Expected Error
(Doc ID 1938078.1)
Last updated on JANUARY 23, 2020
Applies to:Oracle SOA Suite - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 11gR1]
Information in this document applies to any platform.
Trying to error a transaction if the specific loop is missing. Below is what is used to check if the Loop 2300 is missing in SeverityConfig.xml
However, the transaction does not error out as expected. It should error out if Loop 2300 is missing.
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