Dump at ticket creation & display after Solman SP12 upgrade

[Former Member]

Hello,

We recently upgraded our Solution Manager 7.1 from SP8 to SP12.

When trying to create or display a standard or specific transaction type normal / urgent change (ZMMJ or ZMHF or SMMJ or SMHF), the following dump appears:

We found the following knowledge article with the same symptom/cause:

https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F6465...

Then we tried to implement the mentioned SAP Note 1892574 - Wrong Binding CustomerH context node in Charm area but it cannot be implemented in the system.

We performed the manual post actions mentioned in the SAP Note 1892574 but the issue still persists.

Did anyone already encounter this kind of issue?

Thanks and Regards

Louise B.

[Former Member · Accepted solution]

Thank you Christoph and Vikram for your inputs.

In fact the issue was due to a specific enhancement set made in SP08 and not working anymore in SP12.
So we just deactivated it as it was not useful.

Best Regards

Louise B.

[VJain]

Hi Louise,

check

1909351 - dump during enhancing the context node BTQRLEADDOC

Thanks

Vikram

[Former Member]

Hi Louise,

i guess it is a problem with your enhancement of ui componente AIC_CMCD_H.

To check this, set the user parameter WCF_IGNORE_ENHANCEMT to A for your user and open the web ui with role SOLMANPRO.

If the error has now vanished, the problem lies within your enhancement.

There are several possible reasons:
1.

Call transaction BSP_WD_CMPWB with component AIC_CMCD_H.

In view AICCMCDHeaderEF check the class of context node BTCUSTOMERH:

Here the superclass should be CL_AIC_CMCD_AICCMCDHEADER_CN05, i guess in your case it is CL_SRQM_RFC_REQUESTFORCH0_CN26:

2.
Please check the view layout AICCMCDHeaderEF.htm:

Here check the class for attribute BTCUSTOMERH:

3.

Please check the *_CTXT class for the class assigned to attribute BTCUSTOMERH:

Somewere in the mentioned places you will find class CL_SRQM_RFC_REQUESTFORCH0_CN26, which causes your error. For Z-classes also check the super class for this class name.

Hope this helps,

Christoph