B2B 11g - Checking Missing Segments, Loops or Elements in a Transaction Does Not Throw Expected Error (Doc ID 1938078.1)

Last updated on OCTOBER 25, 2016

Applies to:

Oracle SOA Suite - Version 11.1.1.7.0 to 11.1.1.7.0 [Release 11gR1]
Information in this document applies to any platform.

Symptoms

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.

Cause

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