Definition of Exceptions (BOR)

You define exceptions for a method when you want to “publicize” error situations in a standardized manner in order to give the caller of the method the opportunity to react to the error situations.

Prerequisites

You can only define exceptions for synchronous methods.

Activities

To define exceptions for a method, position the cursor on the method and select Exceptions. The existing exceptions for the method are displayed and you select to create a new exception.

Give the exception an identifying number in the dialog box Add Exceptions, which is used to address it in the implementation program. The following number ranges apply:

0001-1000: Exceptions defined for interfaces
1001-7999: Application-specific exceptions, reserved for SAP development
8000-8999: Exceptions triggered by the object manager
9000-9999: Customer-defined exceptions, reserved for customers

Exceptions are classified according to error types.

Temporary error: This error type indicates that certain system resources are not available at the moment, and that it is advisable to call the method again at a later point in time. Temporary errors can also occur if the method is temporarily locked by another user for processing.
Application Error: This error type is caused within the application called in the method. A table that cannot be maintained or a document that does not exist are typical application errors.
System error: This error type shows incorrect configuration of the object manager or an inconsistency between object type definition and method call. Missing mandatory method parameters when calling a method are an example of a system error.

Specify the class and number of the message to be displayed if the exception occurs.

You must specify when the exceptions are triggered in the implementation program.

Note Note

You cannot change or delete exceptions inherited with their method from a supertype or an interface.

End of the note.

For more information, see Programming Exceptions.