The Escalation End event is the specific iFlow step designed to intentionally stop the main integration process and throw a BPMNError exception. This action effectively halts the standard message processing path and signals an error condition. The thrown exception can then be caught and handled by a dedicated Exception Subprocess, which is typically initiated by an Error Start event. This mechanism allows developers to explicitly manage and route error scenarios within the integration flow.

A. Terminal Message: This is not a recognized or standard step type within the SAP Cloud Integration iFlow designer palette.

B. Error Start: This event does not throw an exception; instead, it catches an exception to initiate an Exception Subprocess for error handling.

C. Error End: This event is used at the end of an Exception Subprocess to terminate the flow and set the final message status to "Error".

1. SAP Help Portal

Cloud Integration - Escalation End Event: "You use an escalation end event to stop the processing of a process and to throw an exception that can be caught by an exception subprocess."

2. SAP Help Portal

Cloud Integration - Define Exception Handling: "To throw an exception

you can use an escalation end event. The escalation end event stops the processing of the process and throws an exception that can be caught by an exception subprocess."

3. SAP Help Portal

Cloud Integration - Error Start Event: "An error start event is triggered when an exception is thrown in the main integration process." This confirms it is a catcher

not a thrower.