Runtime error CALL_METHOD_NOT_IMPLEMENTED

[Former Member]

Hi,

We are facing following issue in SCM 5.0.

When background job (Macro) is running and same time data is
lock by the user (Demand Planner) in planning book. The job generates following
ABAP dump and job error out. In this case, I can't found why the job failed;
dump or error messages from job not give any hit about data lock or issue to fail
the job.

I think Job should error out with error message Data currently
lock by user XXXX, it shouldn't give ABAP dump (are you agree?).

Around 6 months back we did Kernel upgrade.

We are getting following dump. Please help me solve the issue.

Runtime Errors         CALL_METHOD_NOT_IMPLEMENTED

Exception              CX_SY_DYN_CALL_ILLEGAL_METHOD

Please let me know if you need detail of ABAP dump.

[sourabh_jain66 · Accepted solution]

Hi Swapnil,

Please check following thread with similar issue.

https://scn.sap.com/thread/1538794.

SAP note no. 1355300 and 1364859 might help you here.

Rgds

Sourabh

[Former Member · Accepted solution]

Hi Sourabh,

Thanks for respond.

I check both notes. Looklike notes are not relevant to the issue. I'm getting dump in SCM - Demand Planning. And background job have Macro, which copy data from one keyfigure to another keyfigure in DP planning area.

ABAP dump detail:

Runtime Errors         CALL_METHOD_NOT_IMPLEMENTED

Exception              CX_SY_DYN_CALL_ILLEGAL_METHOD

Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_METHOD', was
     not caught and
    therefore caused a runtime error.
    The reason for the exception is:
    It was tried to call a not-implemented method
     "/SAPAPO/IF_EX_SDP_BATCH~SET_MESSAGE_TYPE" in the class
     "/SAPAPO/CL_EX_SDP_BATCH".

    How can this occur?

    1. Implementation of Global Interfaces

    If a class implements a global interface, not all methods must be
    implemented. Then there will be no syntax error, but a warning at the
    implementing class. A runtime error only occurs when a not-implemented
    method is called. This is what happened here.

    This technique allows to add a method in an interface that can be
    implemented bit by bit. A runtime error only occurs as early as a
    not-implemented method is called.

    2. Calling abstract Methods in the Contructor

    When the CONSTRUCTOR of a class is running, no 'late binding' of the
    methods occurs, that means, over-defined methods are not called, but
    only the own methods of the class (or of superclasses). This can lead to
     the situation that it is tried to call an absolute method. This
    situation can only be detected at runtime and causes this error message.

3. Calling a Kernel Method with the Implementation FAIL

When defining a Kernel method, it is possible to specify a list of C
modules. If FAIL is specified as last C module and all C modules in the
list do not exist in the Kernel, an exception is raised at runtime.

How to correct the error
    The class "/SAPAPO/CL_EX_SDP_BATCH" must implement the method
     "/SAPAPO/IF_EX_SDP_BATCH~SET_MESSAGE_TYPE".

    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:

    "CALL_METHOD_NOT_IMPLEMENTED" "CX_SY_DYN_CALL_ILLEGAL_METHOD"
    "/SAPAPO/TS_BATCH_RUN" or "/SAPAPO/TS_BATCH_RUN"
    "END-OF-SELECTION"

    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:

    1. The description of the current problem (short dump)

       To save the description, choose "System->List->Save->Local File
    (Unconverted)".

    2. Corresponding system log

       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".

[sourabh_jain66 · Accepted solution]

Hi Swapnil,

Please check the below thread carefully similar issue is been discussed in this in detail and been resolved.

https://scn.sap.com/thread/1538794.

Rgds

Sourabh