2 Replies Latest reply: Jul 10, 2012 10:54 AM by Felix Baumann RSS

Custom theme does not work with EHP5 anymore, cannot export and reimport SAP standard theme

Stefanie Krause
Currently Being Moderated

Hey community,

after upgrading from SAP ECC 6.0 EHP4 to EHP5 our custom theme doesn't work correct anymore.

Normally I would export a fresh SAP standard theme and change my properties again. But it doesn't work so easy :-(

 

Some strange behaviours:

- program WD_THEMES shows nothing but custom themes. The SAP themes, normally marked with SAP-Theme flag are totally gone.

- our custom theme works fine for most of the UI elements. But the tabstrip component and the ALV grid are broken. Tabstrip shows tabs only as text in a very big size and among each other - not usable! (see also screenshot)

 

The strange thing is, after exporting sap_standard theme (with program BSP_UPDATE_MIMEREPOS because WD_THEMES do not show any standard theme) and importing it again (without changing anything!) under a new name I can use this new theme in my WD application. But it shows the same error, tabstrips and ALVs are destroyed. Because of this fact I don't think my custom theme is too wrong and the problem is another.

I tried to change the ur version to the system ur version, but it didn't help.

Oh, and I do not use the theme in the portal, it's just for the WD applications (ABAP).

 

Does anyone have a barn-burner of an idea?

Thanks a lot for any help,

Steffi

  • Re: Custom theme does not work with EHP5 anymore, cannot export and reimport SAP standard theme
    Stefanie Krause
    Currently Being Moderated

    Problem solved after adding WDLIGHTSPEED=<blank> Parameter to WD application.

  • Re: Custom theme does not work with EHP5 anymore, cannot export and reimport SAP standard theme
    Felix Baumann
    Currently Being Moderated

    Hi,

     

    after reading your Question and the answer i would like to add something, and maybe you or somebody else could help.

    I checked the Report WD_THEMES and found an importend difference in the method refresh:

     

    OLD:

     

    METHOD refresh.
    DATA: lr_error TYPE REF TO cx_wdr_io_themes.

    CLEAR t_themes_list.

    TRY.
    r_theme_admin
    ->list_themes_in_mr( CHANGING c_themes_list = t_themes_list ).
    CATCH cx_wdr_io_themes INTO lr_error.
    MESSAGE lr_error TYPE 'E'.
    ENDTRY.

    SORT t_themes_list BY name ASCENDING.
    SORT t_themes_list BY is_sap DESCENDING.
    r_alv
    ->refresh( ).

    ENDMETHOD.

    "refresh

     

     

    NEW:

     

            METHOD refresh.
            DATA: lr_error        TYPE REF TO cx_wdr_io_themes.

            CLEAR t_themes_list.

            TRY.
                r_theme_admin->list_themes_in_mr( CHANGING c_themes_list = t_themes_list ).
              CATCH cx_wdr_io_themes INTO lr_error.
                MESSAGE lr_error TYPE 'E'.
            ENDTRY.

            " The report should only display customer style sheets.
            " SAP-Themes are either in MIME-Repository (<= 7.01 SP3)
            " or in a special zip/db
            DELETE t_themes_list WHERE is_sap = abap_true.
            SORT t_themes_list BY name  ASCENDING.

            r_alv->refresh( ).

          ENDMETHOD.                    "refresh

     

     

    Maybe someone can answer why SAP changed this coding and forgot to supply us "customers" with an new method that does the same like the old one. From the comment i understand that something has changed in the way the standard themes are stored, but in this case it would be a great thing to just redesign the method "refres

     

    h" and the "export" method in the report WD_THEMES to provide the user with the same functions as before...

     

    maybe somebody allready did this and can post his or her solution.