Exception Subprocess for IDoc Receiver Adapter

[SiddharthaKanjilal]

Hi,

We are developing a scenario, where we have an ECC system receiving IDoc from Cloud Integration through Cloud Connector. We use a request-reply shape with IDoc receiver adapter. We have an exception subprocess wrapped around the IDoc receiver adapter. However, we observe that when the call has failed (IDoc data issue, or Cloud connector is down, for example), the flow does not get into the exception subprocess; rather it simply fails at the IDoc adapter step. Screenshot of our configuration is given below. We have tried to wrap the IDoc receiver into a separate local integration process, as per suggestion from this link, to no avail. We tried to go through the help documentation, but there is no mention of this behavior as well. Any hint on this behavior will be appreciated.

Thanks,

Sid

[SiddharthaKanjilal]

Actually, solved it ourselves just now. The trick was to set the "Send HTTP Response as Header" checkbox in the adapter. This forced the IDoc adapter to go into the exception subprocess after an error.

[SiddharthaKanjilal]

Actually, just now solved it ourselves. The trick was to set the "Return HTTP Response Code as Header" checkbox in the receiver adapter. This forced the IDoc receiver adapter to go into the exception subprocess.

Thanks,

Sid