SAP Knowledge Base Article - Preview

3524665 - CALL_FUNCTION_NOT_ACTIVE runtime error in MIGO transaction

Symptom

Below runtime error occurs when using MIGO transaction. 
Runtime error details shows that the issue occurred when calling the FM /MERP/PM_INSP_LOT_SAVE_EX

"Category               Installation error
Runtime Errors         CALL_FUNCTION_NOT_ACTIVE
Except.                CX_SY_DYN_CALL_ILLEGAL_FUNC

Error analysis   

An exception has occurred in class "CX_SY_DYN_CALL_ILLEGAL_FUNC". This
     exception was not caught
    in procedure "IF_EX_INSPECTIONLOT_UPDATE~CREATE_BEFORE_UPDATE" "(METHOD)" or
     propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated this
    exception, the current program was terminated.
    The reason for the exception occurring was:
    The reason for the exception is:
    An attempt was made to execute the CALL FUNCTION statement in program
    "/MERP/CL_PM_INSP_LOT_EXCH_IMPLCP". The name of the function module to be
     called is "/MERP/PM_INSP_LOT_SAVE_EX".
    ""/MERP/PM_INSP_LOT_SAVE_EX" cannot be found in its function group though.

    Possible causes:
    a) Function module "/MERP/PM_INSP_LOT_SAVE_EX" has not been activated. This
     means that it
    cannot be found at runtime.

    b) The function library contains an incorrect entry for
     "/MERP/PM_INSP_LOT_SAVE_EX".

    c) The function module does not contain any code at all. Even FUNCTION
    ... ENDFUNCTION is missing."


Read more...

Environment

SAP S/4HANA

Product

SAP S/4HANA all versions

Keywords

KBA , MOB-APP-MAO-ERP , S4MERP/SMERP-Mobile Add-On integration to S4/ERP , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.