Dump CREATE_OBJECT_CLASS_NOT_FOUND with BADI in MM_MATBEL archiving object

Question

Hi all,
I have searching the error for this dump, the dump is in report RM07MARCS for the BADI 'ARC_MM_MATBEL_CHECK'. In SE19 I called it like ZARC_MM_MATBEL_CHECK, but this time it return me a dump in report CL_EXITHANDLER================CM001 when SAP create with CREATE OBJECT sentence.
The text for the dump is :
Anál.errores / Analysis of errors
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_CREATE_OBJECT_ERROR',
     was neither
    caught nor passed along using a RAISING clause, in the procedure "GET_INSTANCE"
     "(METHOD)"
    Since the caller of the procedure could not have expected this exception
     to occur, the running program was terminated.
    The reason for the exception is:
    The class entered dynamically at CREATE OBJECT
     ("CLASS=CL_EX_ARC_MM_MATBEL_CHECK") cannot be found,
    neither locally. nor as a global class in the system.
Notas para corregir errores / Notes to correct errors
    Either the name of the class is wrong, or the class does not exist.
    Probably the only way to eliminate the error is to correct the program.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "CREATE_OBJECT_CLASS_NOT_FOUND" CX_SY_CREATE_OBJECT_ERRORC
    "CL_EXITHANDLER================CP" or "CL_EXITHANDLER================CM001"
    "GET_INSTANCE"
I've checked it in SE18/SE19/SE24 and so on, but I don't find the origin of problem.
Any suggestion or advice is wellcomed.
Thanks in advance.
Best Regards,
Eduardo

Answer 1

Hi,
Thanks by your reply, it has been so useful for me. I copy the report of archiving to a Zreport and I change it in AOBJ.
Why? Two reasons:
- In OSS notes I have found some notes about program error and I dont want that in the future SAP deny us support because the BADI is register in SCCR (prudential reasons), and I dont want to write a message to SAP because it's urgent.
- It's so easy to replace the call to BADI with the module function that I had wrote in the BADI, so:
  BAdI ARC_MM_MATBEL_CHECK, Methode CHECK
   IF NOT check_exit IS INITIAL.
      LOOP AT mkpf_tab INTO ls_mkpf.
        CLEAR: lv_veto, lv_detail_text.
       CALL METHOD check_exit->check
         EXPORTING
           im_mkpf        = ls_mkpf
         CHANGING
           ch_veto        = lv_veto
           ch_detail_text = lv_detail_text.
        CALL FUNCTION 'Z_ARCHIV_MM_MATBEL_CHECK_001'
          EXPORTING
            i_mkpf              = ls_mkpf
          IMPORTING
            E_VETO              = lv_veto
            E_DETAIL_TEXT       = lv_detail_text.
        IF NOT lv_veto IS INITIAL.
          IF lv_detail_text IS INITIAL.
            lv_detail_text = text-e04.
          ENDIF.
          DELETE mkpf_tab.
          CONCATENATE     ls_mkpf-mblnr ls_mkpf-mjahr       "v_n833784
            INTO          mkpf_tab_entry
            SEPARATED BY  space.
          CALL FUNCTION 'ARCHIVE_PROTOCOL_COLLECT_APPL'
            EXPORTING
              i_object  = mkpf_tab_entry
              i_msgtype = 2
              i_text    = lv_detail_text.                   "^_n833784
        ENDIF.
      ENDLOOP.
   ENDIF.
Thanks newly by your time.
Regards.
Eduardo