Could not find attribute MOPZ_NEWS_VISIBLE

[kenneth_lukongodo]

Pelase assist,

In Version 701, AP EHP 1 for SAP Solution Manager 7.0

Error while creating new maintenance transaction.

The URL http://xxx.xxxx.xxx:8000/sap/bc/webdynpro/sap/wda_mopz_plan was not called due to an error.

Note

The following error text was processed in the system P16 : Could not find attribute MOPZ_NEWS_VISIBLE

The error occurred on the application server ptasm_P16_00 and in the work process 0 .

The termination type was: RABAX_STATE

The ABAP call stack was:

Method: IF_WD_CONTEXT_NODE_INFO~GET_ATTRIBUTE of program CL_WDR_CONTEXT_NODE_INFO======CP

Method: IF_WD_CONTEXT_ELEMENT~GET_ATTRIBUTE of program CL_WDR_CONTEXT_ELEMENT========CP

Method: GET_ATTRIBUTE_INTERNAL of program CL_WDR_VIEW_ELEMENT_ADAPTER===CP

Thanks in advance.

Ken

[former_member296748]

Hi Kenneth,

Had you got a red status when you implemented note 1590226 ?

If yes could you please to execute following procedure :

- De-implement note 1590226.

- Activate via TCODE = SE80 Web dynpro Component = WDC_MOPZ_PLAN

- Implement note 1590226.

Best regards

[Former Member]

My problem is solved after re implementing above note.

Thank you.

[Former Member]

Have you performed all the required Post Inst Tasks?

like SOLMAN Preparation, Activating the Services, running SIAC_PUBLISH_ALL_INTERNAL After the activating the services in SICF?

Thanks

Srikanth M

[kenneth_lukongodo]

Morning,

We have successfully created new maintenance transactions before. This happened after a package update do we need to run it again?

Thanks

[mateus_pedroso]

Remove completely note 1590226 and reimplement the latest version of this note.

This dump is pointing that there's something wrong with this note. This attribute is deployed in version 5 of note 1590226.

[Paul_Babier]

Hello,

Is there a short dump also being created at the same time?

If there is, this may have more pertainent information in it.

Regards,

Paul

[kenneth_lukongodo]

Hi this is what it says.

Runtime Errors UNCAUGHT_EXCEPTION

Exception CX_WD_CONTEXT

Date and Time 07.10.2011 17:25:29

Short text

An exception occurred that was not caught.

What happened?

The exception 'CX_WD_CONTEXT' was raised, but it was not caug

the call hierarchy.

Since exceptions represent error situations and this error wa

adequately responded to, the running ABAP program

'CL_WDR_CONTEXT_NODE_INFO======CP' has to be

terminated.

Runtime Errors UNCAUGHT_EXCEPTION

Exception CX_WD_CONTEXT

Date and Time 07.10.2011 17:25:29

Code Extract..

14 read table me->attributes->* into attribute_info with table key name = name.

15 if sy-subrc <> 0.

>> raise exception type cx_wd_context exporting textid = cx_wd_context=>attribute_not_f

17 endif.

18 else.

19 raise exception type cx_wd_context exporting textid = cx_wd_context=>attribute_not_fou

20 endif.

21 endif.