cancel
Showing results for 
Search instead for 
Did you mean: 

Customer configuration: change texts of column header or search criterion

Former Member
0 Kudos

Hi experts,

I have two issues here:

1. I overwrote the <DEFAULT><DEFAULT><DEFAULT><DEFAULT> configuration of BP_HEAD_SEARCH/MainSearch via BSP component workbench by adding three new standard attributes: RELTYP, REL_PARTNER1 and REL_PARTNER2. As the last two have the same description by standard, I changed the text directly in the configuration but this does not come to the UI. Ther I still see the standard text.

2. I overwrote the <DEFAULT><DEFAULT><DEFAULT><DEFAULT> configuration of BP_HEAD_SEARCH/SearchHelpResult via BSP component workbench by adding new standard columns to the table e.g. LIQUIDATIONDATE. There I have the same issue as in 1. I changed the column headers in the config but only the standard texts come up to the UI.

Does any body has an idea how to overwrite the standard texts without enhancing the views?

Thank you very much!

BR

Mireille

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member192716
Contributor
0 Kudos

Hi,

Check whether the view displayed in web ui screen is the same configuration you changed.

If yes, then execute report BSP_DLC_DELETE_PERSONALIZATION and pass your component and view name.

Regards,

Arun

Former Member
0 Kudos

HI Arun,

thanks for that report. It works for the table headers but not for the search criteria. They still have the standard text.

Do you have another suggestion?

Thx!

Mireille

former_member192716
Contributor
0 Kudos

Hi,

Fields REL_PARTNER1 and REL_PARTNER2 have the same description Business Partner. Better check whether the view configuration you modified and the one displayed in the screen are the same. If yes, then try executing the bsp i mentioned and pass the correct view name or just the component name will do.

As a final step, put a breakpoint in controller method GET_POSSIBLE_FIELD and check the return parameter rt_result. It will show the fields and the descriptions entered in the view configuration.

Regards,

Arun

.

Former Member
0 Kudos

Hi Arun,

yes the config is defenitely the correct one. Executing the report says: no personalization found for view MAINSEARCH. In the workbench, the description in the configuraion is correct but stillt not in UI.

I debugged the method, get_possible_fields and also found the standard field description.

I also tried design layer and entered descriptions like this:

UI-Object-Type: BP_ACCOUNT

Design Object: BP_SEARCH

BOL Object Name: BuilHeaderAdvancedSearch

REL_PARTNER1 BuilHeaderAdvancedSearch REL_PARTNER1 Beziehung: BP ID von

REL_PARTNER2 BuilHeaderAdvancedSearch REL_PARTNER2 Beziehung: BP ID nach

Still does not work. Do I use the correct objects here? I'm not yet familiar with design layer at all.

So last possibility would be to redefine the above controller method. Or do you have any suggestions for the design layer?

Thanks a lot!

Mireille