Difference between config in administration mode and expert mode

[Former Member]

Hi,

We can make changes to FPM-based component configuration via administration mode (SE80, menu bar Web Dynpro Configuration > test > Execute in Administration Mode) or expert mode (user parameter FPM_CONFIG_EXPERT = X), to, for example, add a new tab (main view) to a sap standard application (after enhancing the sap std component config).

I understand that in expert mode any changes are regarded by the system as modifications (as opposed to customisation with administration mode) and hence these modifications could be overwritten by future support pack application. Correct?

Is there any advantage to using expert mode over administration mode, given that expert mode config could be overwritten?

Thanks in advance,

JP.

[luisguereca]

1. FPM_CONFIG_EXPERT = A

To call up administrator mode or key user, you need the S_DEVELOP or S_WDR_P13N authorization profile.

All users in client.

Changes to the Web Dynpro built-in and component-defined configurations are stored in administrator mode as delta information in the Customizing layer of Web Dynpro ABAP. Changes in administrator mode are modification-free changes. This is because when a new release or enhancement package is imported, only the Web Dynpro development layer is affected.

2. FPM_CONFIG_EXPERT = X

For UI development by developer as part of design,you need the S_DEVELOP authorization profile.

All users in all clients.

In expert mode , changes to the component-defined configurations are stored directly in the Web Dynpro ABAP development layer . Changes made in expert mode are modifications that are overwritten when a new release or enhancement package is imported. Expert mode allows configuration for an application to be launched from that application.