How To Fix OO621 - The exception class & is derived from CX_NO_CHECK

OO621 - Overview

• Message type: E = Error

• Message class: OO - Class Builder/API

• Message number: 621

• Message text: The exception class & is derived from CX_NO_CHECK

What causes this issue?

You cannot specify exception classes derived from CX_NO_CHECK in the
interface of a method.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message OO621 - The exception class & is derived from CX_NO_CHECK ?

  The SAP error message OO621 indicates that an exception class is derived from CX_NO_CHECK, which means that the exception is not intended to be caught or handled in the usual way. This is a specific type of exception in the ABAP programming language that is used to signal that an error has occurred, but it is not meant to be handled by the calling program.
  
  Cause:
  The primary cause of this error is that the program or function module is trying to catch an exception that is derived from CX_NO_CHECK. Since exceptions of this type are not meant to be caught, the ABAP runtime environment raises this error to indicate that the exception handling mechanism is being misused.
  
  Solution:
  To resolve this issue, you should:
  
  
  Review Exception Handling: Check the code where the exception is being caught. Ensure that you are not trying to catch exceptions that are derived from CX_NO_CHECK. Instead, you should allow