Show TOC

Modeling Exceptions with Error End or Escalation End EventsLocate this document in the navigation structure

Prerequisites

  • You have opened the Process Development perspective in the SAP NetWeaver Developer Studio and have expanded your project in the Project Explorer view.

  • You have created the necessary triggers for the error end or escalation end events. For more information, see Creating Reusable Event Triggers.

Context

An error end event triggers a WSDL fault that is defined in a service interface definition you have in your project. An escalation end event represents a business error that occurs in the process. The escalation end event has an escalation trigger which is associated with an XSD type. With the XSD type you define which information does the escalation end event transport from the place it is thrown to the place where it is handled.

Procedure

  1. Expand Process Modeling, then expand Processes.
  2. In the context menu of a process, choose Open.
  3. Expand Flow Objects from Palette.
  4. Select Error End or Escalation End from the end events dropdown list and click the modeling surface to place the end event in the process.
    Alternatively, you can drag a fault or an escalation trigger from the Project Explorer view to the modeling surface, to create an end event with the respective trigger assigned to it.
  5. On the General tab page in the Properties view, specify a name for the error end or escalation end event in the Name field.
  6. (Optional) Specify a description of the error end or escalation end event in the Documentation field.
  7. On the Event Trigger tab page in the Properties view, select an event trigger from the Trigger dropdown list to change the default trigger that is assigned.
    The trigger type is preselected depending on whether you model an error end or an escalation end event.
  8. On the Input Mapping tab page in the Properties view, define the input mapping for the error end or escalation end event.