After Upgrade - CREATE_OBJECT_CLASS_NOT_FOUND - CL_IM_SIC_NOTIFY_ILN

[former_member183872]

Dear Gurus,

We have done upgrade of our Netweaver 7.3 system to 7.4.

After the upgrade, when we are trying to create a new user in system, we are getting the runtime error "CREATE_OBJECT_CLASS_NOT_FOUND", with short text as "CREATE OBJECT: Class "\CLASS=CL_IM_SIC_NOTIFY_ILN" not found.".

When i did an analysis i found that with the import of "SAPK740HEC" the class was deleted.

I looked for any relevant SAP Notes for this issue, but did not find any.

I have raised it to SAP as well, but thought of raising it here as well, if someone has already resolved it and can help me.

Thank you.

Regards,

Anuj

[Former Member · Accepted solution]

I'm getting this same issue. We upgraded NW from 7.3 to 7.4.

Has anybody found a solution for this issue? Seems a OSS message with SAP is imminent.

[Former Member · Accepted solution]

Problem solved.

This dump occurs because there is a BAdi activated but not implemented, or the BAdi is present but inactive.

In my case, the BAdi was activated but not implemented.

I compared the BAdi  "CL_IM_SIC_NOTIFY_ILN" in our Release track system with our Support track system.

BAdi "CL_IM_SIC_NOTIFY_ILN' needed to be deactivated.

- se19 

- Under Edit Implementation choose Classic Badi

- Insert BAdi name "SIC_NOTIFY_ILN"

- Click Display

- Use display/change mode to deactivate.

[former_member183872 · Accepted solution]

Hello Alex,

Thanks for your reply.

SAP has also released a note 1948120 - ILN Cleanup for the same.

Best Regards,

Anuj Nigam

[Former Member]

Hi,

can you try to regenearte the code again.

Thanks

Rishi Abrol

[former_member183872]

Thanks for your reply Rishi.

I regenrated the code, but no luck. 🙂

[Former Member]

Hi,

I just check one of my system and cant find the CL_IM_SIC_NOTIFY_ILN.

What is the ABAP patch level you are at. In the current system is at SAPKA74003.

Can you check the exact dump where the code is failing in St22.

click on the source code in st22.

Thanks

Rishi Abrol

[former_member183872]

Yes, its on SAPKA74003.

I am pasting the excerpt of the dump, which i missed putting in my first post.

Category               ABAP Programming Error

Runtime Errors         CREATE_OBJECT_CLASS_NOT_FOUND

Except.                CX_SY_CREATE_OBJECT_ERROR

ABAP Program           CL_EXIT_MASTER================CP

Application Component  BC-DWB-CEX

Date and Time          11.10.2013 14:39:53

Error in the ABAP Application Program

The current ABAP program "CL_EXIT_MASTER================CP" had to be
terminated because it has come across a statement that unfortunately cannot be executed.

Error analysis

    An exception has occurred which is explained in more detail below. The exception is assigned to class 'CX_SY_CREATE_OBJECT_ERROR' and was not caught in procedure  "INSTANTIATE_IMP_CLASS" "(METHOD)", nor was it 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 is:

    The class dynamically specified in CREATE OBJECT (class   "\CLASS=CL_IM_SIC_NOTIFY_ILN") is not defined in the system as a local or global class, or is shadowed by a local data type of the same name.

If the error occurs in a non-modfied SAP program, you might be able to find a solution in the SAP Notes system. If you have access to the SAP Notes system, check there first using the following keywords:

"CREATE_OBJECT_CLASS_NOT_FOUND" CX_SY_CREATE_OBJECT_ERROR
"CL_EXIT_MASTER================CP" bzw. CL_EXIT_MASTER================CM002
"INSTANTIATE_IMP_CLASS"

Information on where terminated
    The termination occurred in ABAP program "CL_EXIT_MASTER================CP",
     in "INSTANTIATE_IMP_CLASS". The main program
    was "SAPMSUU0                                ".

    In the source code, the termination point is in line 15 of (Include)
    program "CL_EXIT_MASTER================CM002".
    The termination is due to exception "CX_SY_CREATE_OBJECT_ERROR" occurring in
     procedure "INSTANTIATE_IMP_CLASS" "(METHOD)".
    This exception was not handled locally or declared in the RAISING
    clause in the procedure's signature however.
    The procedure is in program "CL_EXIT_MASTER================CP        ". The
     source code begins in line 1 of
    (include) program "CL_EXIT_MASTER================CM002     ".

   13     CONCATENATE '\CLASS=' imp_class INTO abs_type_classname.

   14 *****  dynamic object creation     *******************************

>>>>>     CREATE OBJECT instance TYPE (abs_type_classname).

   16 ******************************************************************

[Former Member]

Hi,

Was there any enhancement done in your system or and user exit or customising done in your system.

did you see any of the above program or class in SPAU ore SPDD.

Thanks

Rishi Abrol