After EHP3 Upgrade Component BP_HEAD as default value

[Former Member]

Hello Experts,

befor upgrading the system on EHP3 the component BPFS_HEAD was set as default. After upgrading it seems to be different and the default value changed to BP_HEAD.

Usually i set the default value in do_config_determination, but there is the same code as before. Can anyone give some help, where i can find the point for changing or setting default component values?

Regards,

Peter

[Former Member]

Hello,

thanks for your help. I´m a beginner, thats why my desciption is not so exactly, but I will try it again.

We create some fields with AET to enhance the standard. Most of them we create befor we switch to EHP3, but we also created a couple after upgrading the system.

Now we faced to the problem that some fields are not visible in AET, but in AXTSHOW the fields still existing.

We did a quick analysis on the problem and found out that the extended BO-object was “ACCOUNT” before EHP3 and now it is “ACCOUNT_FS”. This leads to the missing fields on UI level, as the respective select statement (class: CL_AXT_EXTENSION_PERSISTENCE, method: SEARCH_BY_BO) only selects fields for BO “ACCOUNT_FS”.

Regards,

Peter

[corrine_guan]

Here is my understanding of your problem:

Before upgrade to EPH3, you created AET fields. They belong to BO object 'ACCOUNT'.

After upgrade, you also created some new AET fields. They belong to BO object 'ACCOUNT_FS'.

Now you found the AET fields which were created before upgrade are not visible on webui any more because UI page are looking for AET fields of BO object 'ACCOUNT_FS', instead of 'ACCOUNT'. Is my understanding correct?

It seems expected behavior.  But I would like to confirm it further. Would you please provide all the steps of how you created the AET fields before and after EHP3 upgrade both?

1. Please specify the business roles(better standard roles),

2. menus you used on navigation bars, operations like displaying/creating accounts etc,

3. components /views where you created your AET fields, etc.

4. component/views where you want to display the AET fields you created before upgrade.

5. component/views where you want to display the AET fields you created after upgrade.

It's better to be clear descriptions so that can follow and repeat.

[corrine_guan]

Are you talking about creating a FS BP?

Here is a blog which explains the reason why it changes to view BP_HEAD instead of BPFS_HEAD after EHP3, it also provides a way to reuse the previous component:

http://scn.sap.com/community/crm/webclient-ui-framework/blog/2015/02/13/the-change-of-the-componentv...

Would you please let us know more details like:

Which class the do_config_determination belongs to, and what is the default value you set? What's the purpose to set default value? To determine your own configuration? or to determine the target view and make it to be BPFS_HEAD?