SOLMAN issue maintenance problem

[Former Member]

After installation of support packages, the buttons (Save, Expert Mode, Cancel, etc.) at the bottom of the issue maintenance screen in transacton Solution_Manager have stopped working in our SolMan 4.0 system. They do work when using transaction Solution_manager_BSP and accessing thru the webbrowser interface.

Has anyone else seen this problem? They used to work. Any suggestions?

These are our current add-on support package levels. (Sorry the column formatting didn't keep.)

BI_CONT 703 0004 Business Intelligence Content

CPRXRPM 400 0007 SAP xRPM/cProjects/cFolders 4.00 (ABAP)

PI_BASIS 2005_1_700 0010 PI_BASIS 2005_1_700

SAP_AP 700 0007 SAP Application Platform

SAP_BW 700 0010 SAP NetWeaver BI 7.0

ST 400 0009 SAP Solution Manager Tool

ST-A/PI 01I_CRM500 0000 Application Servicetools for CRM 500

ST-ICO 150_700 0007 SAP Solution Manager Implementation Cont

ST-PI 2005_1_700 0003 SAP Solution Tools Plug-In

ST-SER 700_2006_1 0007 SAP Solution Manager Service Tools

Thanks,

Bob

[raguraman_c · Accepted solution]

Hi,

Stopped working means???

do yo u get any error????

Please be specific when you post any problem. It would help everyone to understand and provide solutions at the earliest.

Feel free to revert back.

--Ragu

[Former Member · Accepted solution]

If someone else had the same problem, I think they would recognize from my description, however:

Stopped working means - press any of the buttons at the bottom of the issue maintenance screen, (or the the green arrow back, at the top of the screen) and nothing happens, except maybe a very brief delay before the screen returns to input mode. Another clue: Although the screen is open for input, any changes, such as changing status Open to In Processing, or modifying text are undone. However, the other tabs can be selected.

The Exit (Yellow up arrow) and Cancel (Red X) at the top of the screen do work, to exit to the SAP Menu

[DoloresCorrea · Accepted solution]

Hello Bob,

Please apply note 1008717, just in case it fix the issue...

Best regards,

Dolores

[Former Member · Accepted solution]

Thank you Delores!

Note 1008717 corrected the problem.