Show TOC

Procedure documentationCreating a Fault Message Type Locate this document in the navigation structure

 

You use fault message types in the following scenarios:

  • In the synchronous case, when an application-specific error occurs on the inbound side, instead of sending a response message back to the sender, the application can send a fault message to handle the error.

  • The fault message of the application for an asynchronous ABAP server proxy is persisted for monitoring. In the case of asynchronous Java server proxies, the fault message is part of a negative application acknowledgement.

    More information: Acknowledgments

Prerequisites

Familiarize yourself with the basics of fault message types.

More information: Fault Message Type

Procedure

  1. Create a fault message type on the design maintenance screen of the ES Builder.

    More information: Creating an Object

  2. Enter a description for your fault message type.

  3. The default setting for XML Namespace is the Repository namespace. If the message type has been copied to another namespace, overwrite the default setting.

  4. In the default setting, the fault message only comprises the standard data part. If you require the additional data part, specify a data type in the Additional Data input field. The data type can be in the same software component version or in a sub-software component version.

  5. Save your changes.