CALL_METHOD_NOT_IMPLEMENTED SAP ABAP Runtime Error call method not implemented

CALL_METHOD_NOT_IMPLEMENTED is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.

Short Dump Classification: A - ABAP Programming Error

You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.

Also check out the Comments section below to view or add related contributions and example screen shots.

CALL_METHOD_NOT_IMPLEMENTED ABAP Runtime Error

Class <runtime parameter> must implement method <runtime parameter>. Please see program correction for more details about the possible cause of this runtime error and how it could be avoided.

Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.

Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.

Non-implemented method or kernel method called. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

An attempt was made in class <runtime parameter> to call non-implemented method <runtime parameter>.

How can this happen?

1. Implementation of global interfaces

If a class implements a global interface, not all methods have to be implemented. This does not result in a syntax error. Instead, the system issues a warning for the implementing class. A runtime error only occurs once a non-implemented method is called. This has happened here.

This functionality makes it possible to add a method to an interface that can be implemented step by step by the implementing classes. A runtime error only occurs once a non-implemented method is called.

2. Abstract method called in the constructor

When the CONSTRUCTOR of a class is being processed, no 'late binding' of the methods takes place. This means that redefined methods are not called, and only the specific methods of the class (or any superclass) are called. The might result in the system trying to call an abstract method. This situation can only be detected at runtime and produces this error message.

3. Kernel method called with FAIL implementation

When a kernel method is defined, a list of C modules can be specified. If FAIL is specified as the last C module, and all other C modules in the list do not exist in the kernel, this exception occurs at runtime. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.