SAP Fiori Variant Management details and relevant settings.
How does it work with default system settings
Creating Variant
To create a variant first set your relevant filters using ‘Adapt Filters’, relevant columns using the Setting button on the list and specify any filter criteria. After you are happy with it, press the dropdown next to the variant name and click on Save as.
On the dialog box enter a variant name and press Save. Variant will then be added to your favourite list.
Creating Public Variant
Variant if marked Public will be available for other users. Tick the Public checkbox to make a variant available for other users. The system will prompt you to either specify Transport request or select Local Object. Click on Local Object, press OK and then press Save on the next screen. Variant is now available for you (added to your favorite) and other users.
Note public variants can be edited by other users.
Public Variant
To use the Public variant created by others, add the variant to the favourite list.
Click on Manage to see a list of all variants.
Click on the Star icon to add variant to your favourite list, press OK.
Its now available for you.
Note for Admin/Basis : With default setting/install everyone is allowed to create variants. Everyone of allowed to create public variants.
Using Launchpad Configuration Parameter
Using launchpad configuration parameter UI5FLEX_ENABLE_VARIANTS default behaviour can be changed. The parameter specifies if users are allowed to create and adapt views and whether they’re allowed to share them.
There are three options:
- PUBLIC (default) – Users are allowed to create and adapt new views. By selecting the Public checkbox, they can also share them with other users.
- PRIVATE – Users are allowed to create and adapt new views, but the Public checkbox is not displayed, preventing users from sharing views.
- NONE – Users are not allowed to create or adapt views. They can still set a view as favourite and change their default view. Optionally, they can also choose whether a view should be applied automatically, meaning a search should immediately be triggered when the view is selected.
Transaction /UI2/FLP_SYS_CONF and /UI2/FLP_CUS_CONF to set/change Launchpad Configuration Parameter.
This setting supersedes the authorisation setting described below. If you have implemented authorisation check you need to revert it for this launchpad configuration parameter to have an effect.
Enabling Authorisation Check for Public Variant (note 2658662)
- Call transaction SE38
- Fill program name ‘/UIF/SET_KU_CHECK_FOR_VARIANT’ into field ‘Program’
- Press ‘Execute’ (F8)
- If you want to activate the key user check for CUSTOMER views check the ‘Active’ checkbox
- Press ‘Execute’ (F8)
- You get a success message when the report executed without problem
After this you need /UIF/KEYU of authorization object /UIF/FLEX.
Transporting Variants
Public variants can also be created in the development system, saved in transport and moved across to the production system. This could be one option to control the creation of public variants in combination with the above two settings. Especially with the Launchpad configuration parameter set to NONE, transport remains the only way to have variants for users. Variants imported in production using transport can not be edited. It behaves like a development object.
Reference note 2929291 2658662
Report variants are also supported in WDA List and ALV List. Both these technologies use authorisation object to restrict the creation of public variants.
WDA List Report
No option to transport variants. Controlled using authorisation object S_WDR_ADM with WD_ACTVT = 06.
ALV Report
No option to transport variants. Controlled using authorisation object S_ALV_LAYO with ACTVT = 23.