NetWeaver Enhancement Package 1 & Themes

[Former Member]

We are pursuing this through a support message, but I figured Iu2019d ask the SDN community too.

When using a 7.01 Web Dynpro ABAP with lightspeed rendering, it appears to not support a normal Portal theme developed with the Portal theme editor.

- This thread states that lightspeed rendering does NOT support custom themes:

[|]

- SAP Note #1177457 states: u201CSince EhP1 is classic-rendering not supported anymore. Only Lightspeed-rendering will be supported.u201D

Does this mean that 7.01 essentially does not support custom themes? Seems like a significant oversight. Are other folks running a 7.01 NetWeaver for their Web Dynpro ABAP applications dealing with this somehow?

[Former Member · Accepted solution]

If your OS is windows then try the following, it might sort the problem out.

The problem is that the complete path to

certain image files on your file system is too long

for MS Windows (the path length has to be < 256 characters).

With 701 SAP introduced a new theme called sap_tradeshow_plus. This

theme name can lead in some cases to a path that is longer than 256

characters.

To check that this is also the reason in your case please navigate to:

System Adminsitration >

Support >

Portal Content Directory >

PCD Inspector

In the PCD Inspector navigate (by clicking on "Browse into link") to:

portal_content >

themes

Mark all standard SAP themes (_chrome, _hcb, _highcont, _standard,

_tradeshow and tradeshowplus)

delete them by clicking the delete icon in the top left of the screen.

These themes will be automatically regenerated after a restart.

Now stop the J2EE and in the file system navigate to:

\usr\sap\<SID>\<InstID>erver0\apps\sap.com\irj\servlet_jsp

\irj\root\WEB-INF\portal\portalapps\com.sap.portal.design.portaldesigndata\config\themes\its\designs\sap_tradeshow_plus\webgui\wa\webgui\images\table\

and delete the files "table_row_button_downstate_radio.gif" and

"table_row_button_upstate_radio.gif" (or move them to a backup folder

location). Restart your J2EE engine.