I am often asked about Default Values in SAP Fiori by customers in the SAP S/4HANA Customer Care/Early Adopter Care programs and others I come across in my travels. In this blog post I’m tackling the occasionally contentious synchronization with classic Set/Get Parameters. Once you understand how it works and your options you will be able to let go of some of that stress.
In this blog post you will learn how the synchronization between Default Values and Set/Get Parameters works. You will also find the answers to some FAQs, such as how to ask for additional Default Values.
TL;DR: When you move users to the Fiori launchpad, use Fiori Default Values wherever you can. Cease updating the matching classic set/get parameters directly in the backend.
The common consensus is everyone – users and administrators - like the Fiori Default Values. After all, what’s not to like?
For business users there are even more business benefits:
Hint: You can find which Default Values map to classic Set/Get Parameters, and how to apply them to your custom apps, in blog post Applying User Defaults in SAP S/4HANA section Default Values delivered by SAP.
Most customers also have a few wishes for Default Values:
In this blog post you will learn:
You can find out more about Default Values in the blog posts:
IMPORTANT: All example screenshots in this blog post were taken in a SAP S/4HANA 2022 FPS02 Fully Activated trial from SAP Cloud Appliance Library at https://cal.sap.com
Below is a summary diagram of the synchronization points and exception scenarios.
There are 2 main synchronization scenarios – shown as 1 and 2 in the diagram.
In the example below you will see what happens for a user who has never used Default Values before.
Before the user logs into the SAP Fiori launchpad, they must have a user id. The administrator can view and edit their classic set/get parameters, for example using GUI transaction SU01 Maintain Users.
There are 2 exception scenarios when no synchronization occurs.
Here you can see the user or administrator changes the parameters in transaction SU01.
There is no synchronization with the Default Values – the Default Values remain unchanged.
The other exception scenario is when the classic Set/Get parameters are locked, preventing the update.
To complete the diagram, 5 shows that even if you have had an exception scenario, any subsequent change of Default Values will restore the synchronization. That is:
User subsequently updates their Default Values and presses Save.
Now the change is reflected in the set/get parameters and the values are in synch again.
You can read the official SAP Note describing how the synchronization currently works between Default Values and classic Set/Get Parameter Ids in SAP Note 2519765 - Synchronization of Fiori User Default Values with Backend SET-/GET-Parameters
Start by checking that the set/get parameters were not locked, and were not changed directly. The user master "Changed by" fields may give you some idea of who last updated the user's details.
You may want to check with the user to ask if they have logged into the system directly, e.g. via SAP Logon or SAP Business Client.
Make sure that the Default Value they are changing has a matching set/get parameter. You can find a list of all the Default Values and their matching set/get parameters in blog post Applying User Defaults in SAP S/4HANA section Default Values Delivered by SAP
It can be helpful to simply try updating the Default Values again with the user.
If you are still having a problem, raise a SAP Incident:
You can find the designated support component in the Fiori launchpad > User Actions > About info
In the About dialog look for the component id.
Default Values are applied when:
Hint: Primary Default Values can also be applied directly to classic GUI transactions directly on launch, and indirectly via synchronization with classic set/get parameters.
Launched directly means the app is launched from a launchpad page, from the App Finder, from the Search on Apps, or from the Home navigation button.
For example, as a maintenance planner you have maintained notification type and planning plant in your default values.
When the user launches the app F5797 Find Maintenance Notifications the values for notification type and plant are immediately defaulted without the user having to select them.
It’s useful to understand that Default Values offer improved capabilities compared to Set/Get Parameters. For example, in apps such as F5797 Find Maintenance Notifications you may regularly work across multiple planning plants, and the app’s filter criteria supports multiple planning plants.
With Default Values you can maintain Additional Values to pass multiple values that you regularly use for that field. If you maintain multiple values for the Planning Plant using the Additional Values button, the button will be shown as emphasized and you simply Save your settings again.
Even better you can maintain Additional Values using logical conditions in Default Value, so your multiple values can be ranges, patterns, etc.
Then when you enter the app again your primary and additional planning plants are automatically applied to the Planning Plant filter.
When are Default Values ignored?
In app-to-app navigation, when you navigate to your app from another app, the incoming source-to-target parameter passing definition takes precedence over default values. This includes launching from Search Results.
Default Values will also be ignored if they have not been mapped to the app in the app’s launchpad app descriptor item (aka the tile/target mapping combination).
How can I check which Default Values are used by an app ?
As an administrator you can verify which apps use which Default Values by reviewing the launchpad app descriptor item for the app. For example, for app F5797 Find Maintenance Notifications shows how its parameters are mapped to the Default Values.
Often once you start to use Default Values you want more!
If you are missing Default Values, create an improvement request on the Customer Influence opportunity SAP S/4HANA Cloud for User Experience and Cross-Topics, public edition.
IMPORTANT: The Default Value needs to be applicable to at least one SAP Fiori app to be valid for inclusion in the SAP delivered Default Values.
You can use the format for the title:
<Fiori app id> – Provide Default Value for <field name>
For example: F2828 Maintenance Planning Overview – Provide Default Value for Planner Group
In your improvement request details:
In the expected benefit, include an estimate – e.g. number of users x number of times this app is used per day or per week.
It’s helpful to include a screenshot of the field you want defaulted. You can add this as an attachment to the improvement request.
Questions in this section include:
Make sure you set up their set/get parameters before they login to SAP Fiori and use Default Values for the first time. For example, using the SU01 Maintain Users, or the mass update transaction SU10.
No. An API is not possible for Default Values, as the Default Values are strictly tied to the current user. Instead you can create a public Saved Value Set to provide the correct values for your users.
Your users can then use this to reset their Default Values as recommended.
Even better, you can distribute the task of creating public Saved Value Sets to your key users - who can then follow up with their team members directly.
Refer to a full description of the technique in SAP Fiori for SAP S/4HANA – Yes Key Users can set Default Values for other Users
Classic set/get parameters can only hold a single value, so only the primary default value can be synchronized.
It’s common for a few more default values to be automatically added as part of a SAP S/4HANA release upgrade. If the default values are relevant to your apps they will automatically appear in your Default Values dialog.
What if the Default Value is empty but the set/get parameter already has a value on upgrade?
The existing set/get parameter values for any new Default Values will be proposed the first time you open Default Values after your upgrade.
After that any changes you make to your Default Values will update the matching set/get parameter values as usual. To minimize confusion, make sure you stop updating the matching set/get parameters directly.
That’s ok. There are several Default Values that are brand new for SAP S/4HANA and don’t have a classic set/get parameter. These are only maintained in Default Values and any changes don’t affect your set/get parameters.
If the Default Value is available in your SAP S/4HANA release but does not appear in your Default Values dialog, then it means you are not assigned to any apps that apply that Default Value.
Your administrator can use the Launchpad Content Manager. Navigate to the Tiles/Target Mapping tab to search across all target mappings for parameters with the value UserDefault. Select the Technical Catalog entry (look for the catalog id containing _TC_) then press Open SAP Fiori Launchpad App Manager to view the parameter details in the Launchpad App Manager.
You can see which Default Values are mapped to parameters in the Parameters tab, including whether they are mapped to the primary value (format %%UserDefault.<default value>%%) or the primary and additional values (format %%UserDefault.extended.<default value>%%).
Most likely the target mapping is missing the UserDefault parameter mapping.
Sometimes this is an oversight, e.g. where the app was created prior to the default value being made available. If you are in SAP S/4HANA 2022 or higher you (or your administrator) can add parameters using the adaptation mode in the Launchpad App Manager.
Sometimes Default Values are simply not mapped as you would wish. For example, in SAP Fiori app F4604 Manage Maintenance Notifications and Orders, in SAP S/4HANA 2022 the planning plant is mapped to default values, but the notification type is always default to the value Y1. This can be seen in the target mapping parameters in the Launchpad App Descriptor Item.
Check the app documentation for any clues before updating the parameters in the Launchpad app Manager.
You can also raise an improvement request on the Customer Influence opportunity SAP S/4HANA Cloud for User Experience and Cross-Topics, public edition to ask for the target mappings to apps to be updated.
Procurement uses many Default Values across it’s apps.
Procurement also includes a special SAP Fiori app F1995 Default settings for users to set defaults on behalf of other users. This app pre-dates the availability of Default Values and can be used to set a limited number of defaults within procurement only.
This app also provides a spreadsheet upload/download option.
Enterprise asset management includes an additional Personalization app (technical id EAM_USER) that presets some defaults for classic UIs. This app writes to its own storage area and does not synchronize with either Default Values or Set/Get Parameters. So you are welcome to use it where needed.
Enterprise Asset Management also includes several ABAP Web Dynpro apps. Check the Launchpad App Manager for the Web Dynpro Application id to see which incoming parameters are available.
Within ABAP Web Dynpro apps you can also use the “Use Current Value as Default” feature. Refer to: SAP Note 3239615 - Cannot save Default Values in user settings for Web Dynpro/ FIORI Apps
Yes you can reuse Default Values by applying them to your launchpad app descriptor items (aka tile/target mappings) in the Launchpad App Manager. Refer to blog post Applying User Defaults in SAP S/4HANA.
Yes, you can. They will continue to be used by your classic UIs only. However, to minimize confusion for your business users, you should consider asking for an equivalent Default Value to be created by raising an improvement request as described above in the section How to request more Default Values.
No, sorry. Custom Default Values are not supported.
However, you can create your own plug-in for the Settings dialog. IMPORTANT: Your new section will be separate to the section for Default Values. Refer to the SAP Help Portal – Fiori launchpad > Developer Guide > Extending the launchpad.
You’ll find much more on the community topic page for SAP Fiori for SAP S/4HANA
Other helpful links in the SAP Community:
Brought to you by the SAP S/4HANA Customer Care and RIG.
In this blog post you will learn how the synchronization between Default Values and Set/Get Parameters works. You will also find the answers to some FAQs, such as how to ask for additional Default Values.
TL;DR: When you move users to the Fiori launchpad, use Fiori Default Values wherever you can. Cease updating the matching classic set/get parameters directly in the backend.
- If you need to update values across multiple users, create a public Saved Value Set with your changes and have your users apply the Saved Value Set to their defaults.
- If you are missing Set/Get Parameters, create an improvement request on the Customer Influence opportunity SAP S/4HANA Cloud for User Experience and Cross-Topics, public edition. Make sure you include details of the SAP Fiori apps and Set/Get Parameters
The common consensus is everyone – users and administrators - like the Fiori Default Values. After all, what’s not to like?
- For a business user, Default Values improve user efficiency by minimizing data entry for your most used values across all your Fiori apps and classic UIs launched from the Fiori launchpad.
- Hint: Classic Uis include your GUI transactions, Web Dynpro ABAP apps, and Web Client UIs.
- For a technical administrator, Default Values improve performance by reducing the amount of data extracted whenever users launch apps from the launchpad, App Finder, Home navigation button, or Search on Apps.
Example of Default Values in the Settings dialog of the Fiori launchpad
For business users there are even more business benefits:
- Nothing unnecessary: You only see the default values that are relevant to the apps you use.
- Covers your forms and your reports: You can set primary values and additional values.
- The primary value is applied when you can only enter a single value, such as in a form or create app
- The primary value and additional values are applied when can enter multiple values, such as in a report filter
- Easy transition from classic set/get parameters: Default Values automatically synchronize primary values with your classic Set/Get Parameters.
- Can be used for your custom apps: You can apply Default Values to your own apps and classic UIs.
- You can do this by adding parameters to the tile/target mapping definition (aka Launchpad App Descriptor Item) that defines how to launch the app.
Hint: You can find which Default Values map to classic Set/Get Parameters, and how to apply them to your custom apps, in blog post Applying User Defaults in SAP S/4HANA section Default Values delivered by SAP.
Most customers also have a few wishes for Default Values:
- They would like more parameters included in Default Values.
- They want to understand how default values are applied to apps
- They want to better understand how the synchronization with classic Set/Get Parameter works
In this blog post you will learn:
- How the synchronization works between Default Values and Set/Get Parameters
- When are Default Values applied to apps
- How to request more Default Values
- FAQ
You can find out more about Default Values in the blog posts:
- Applying User Defaults in SAP S/4HANA
- Setting User Defaults in SAP S/4HANA
- SAP Fiori for SAP S/4HANA – Yes Key Users can set Default Values for other Users
IMPORTANT: All example screenshots in this blog post were taken in a SAP S/4HANA 2022 FPS02 Fully Activated trial from SAP Cloud Appliance Library at https://cal.sap.com
How the synchronization works between Default Values and Set/Get Parameters
Below is a summary diagram of the synchronization points and exception scenarios.
Diagram showing the sycnhronization behaviour between Default Values and Set/Get Parameters steps 1 to 5
There are 2 main synchronization scenarios – shown as 1 and 2 in the diagram.
In the example below you will see what happens for a user who has never used Default Values before.
Before the user logs into the SAP Fiori launchpad, they must have a user id. The administrator can view and edit their classic set/get parameters, for example using GUI transaction SU01 Maintain Users.
Example of a user with set/get parameters in their user master - seen here in transaction SU01 Maintain Users
- User opens their Default Values dialog for the very first time.
- The user’s current matching Set/Get Parameters are read and proposed as the default primary values of Default Values.
In the SAP Fiori launchpad, the user navigates to User Actions - Settings - Default Values for the first time.
The Default Values are proposed from their current matching set/get parameters
Notice that the user only sees parameters relevant to the apps they are assigned.
- User changes their Default Values.
- On saving their Default Values, the primary value of the default values are used to update the matching Set/Get Parameters.
The user changes their Default Values and selects Save to apply them. In this example the Planning Plant has been changed.
On Save the matching set/get parameter values are updated.
There are 2 exception scenarios when no synchronization occurs.
- User (or administrator) changes their Set/Get Parameters.
- No synchronization occurs – the Default Values are unchanged.
- This scenario holds true regardless of the transaction or API used to change the set/get parameters. For example:
- A user changing the parameters via transaction SU3
- An administrator changing the parameters via transaction SU10
- A developer changing the parameters via the API BAPI_USER_CHANGE
Here you can see the user or administrator changes the parameters in transaction SU01.
The Planning Plant set/get parameter is set to a new value directly in GUI transaction SU01 Maintain Users
There is no synchronization with the Default Values – the Default Values remain unchanged.
The Default Values are unchanged - the change to the set/get parameters is ignored
The other exception scenario is when the classic Set/Get parameters are locked, preventing the update.
- User changes their Default Values, while the Set/Get Parameters are locked.
- The set/get parameters are not updated.
- For example, if the administrator is using SU10 to update the user’s master details at the same time.
- Hint: As an administrator you can check in transaction SM12 for locked records.
To complete the diagram, 5 shows that even if you have had an exception scenario, any subsequent change of Default Values will restore the synchronization. That is:
- User changes their Default Values.
- On saving their Default Values, the primary value of the default values are used to update the matching Set/Get Parameters.
User subsequently updates their Default Values and presses Save.
The user changes their Default Values again and presses Save
Now the change is reflected in the set/get parameters and the values are in synch again.
All the matching set/get parameters are updated when the Default Values are saved
You can read the official SAP Note describing how the synchronization currently works between Default Values and classic Set/Get Parameter Ids in SAP Note 2519765 - Synchronization of Fiori User Default Values with Backend SET-/GET-Parameters
I have a scenario where the synchronization doesn’t seem to be working. What do I do?
Start by checking that the set/get parameters were not locked, and were not changed directly. The user master "Changed by" fields may give you some idea of who last updated the user's details.
You may want to check with the user to ask if they have logged into the system directly, e.g. via SAP Logon or SAP Business Client.
Make sure that the Default Value they are changing has a matching set/get parameter. You can find a list of all the Default Values and their matching set/get parameters in blog post Applying User Defaults in SAP S/4HANA section Default Values Delivered by SAP
It can be helpful to simply try updating the Default Values again with the user.
If you are still having a problem, raise a SAP Incident:
- Include the Default Value, the matching set/get parameter id, and steps to reproduce.
- Assign the SAP Incident to the designated support component of the SAP Fiori app that uses the Default Value.
You can find the designated support component in the Fiori launchpad > User Actions > About info
You access the About information from the Fiori launchpad - User Actions - About
In the About dialog look for the component id.
The designated support component of the app is shown in the About information - field Component
When are Defaults Values applied to apps
Default Values are applied when:
- An SAP Fiori app is launched directly
- An ABAP Web Dynpro app is launched directly
Hint: Primary Default Values can also be applied directly to classic GUI transactions directly on launch, and indirectly via synchronization with classic set/get parameters.
Launched directly means the app is launched from a launchpad page, from the App Finder, from the Search on Apps, or from the Home navigation button.
For example, as a maintenance planner you have maintained notification type and planning plant in your default values.
The maintenance planner user has Default Values maintained for Notification Type and Planning Plant
When the user launches the app F5797 Find Maintenance Notifications the values for notification type and plant are immediately defaulted without the user having to select them.
The Default Values are applied to the filter fields for Notification Type and Planning Plant when the Find Maintenance Notifications app is launched directly
It’s useful to understand that Default Values offer improved capabilities compared to Set/Get Parameters. For example, in apps such as F5797 Find Maintenance Notifications you may regularly work across multiple planning plants, and the app’s filter criteria supports multiple planning plants.
With Default Values you can maintain Additional Values to pass multiple values that you regularly use for that field. If you maintain multiple values for the Planning Plant using the Additional Values button, the button will be shown as emphasized and you simply Save your settings again.
When additional values have been maintained the Additional Values button is emphasized
Even better you can maintain Additional Values using logical conditions in Default Value, so your multiple values can be ranges, patterns, etc.
Example of the logical conditions available when creating Additional Values for Default Values
Then when you enter the app again your primary and additional planning plants are automatically applied to the Planning Plant filter.
Example showing primary and additional Default Values for Planning Plant applied to the app
When are Default Values ignored?
In app-to-app navigation, when you navigate to your app from another app, the incoming source-to-target parameter passing definition takes precedence over default values. This includes launching from Search Results.
Default Values will also be ignored if they have not been mapped to the app in the app’s launchpad app descriptor item (aka the tile/target mapping combination).
How can I check which Default Values are used by an app ?
As an administrator you can verify which apps use which Default Values by reviewing the launchpad app descriptor item for the app. For example, for app F5797 Find Maintenance Notifications shows how its parameters are mapped to the Default Values.
In the Launchpad App Manager you can check which Default Values are mapped to an app
How to request more Default Values
Often once you start to use Default Values you want more!
If you are missing Default Values, create an improvement request on the Customer Influence opportunity SAP S/4HANA Cloud for User Experience and Cross-Topics, public edition.
IMPORTANT: The Default Value needs to be applicable to at least one SAP Fiori app to be valid for inclusion in the SAP delivered Default Values.
You can use the format for the title:
<Fiori app id> – Provide Default Value for <field name>
For example: F2828 Maintenance Planning Overview – Provide Default Value for Planner Group
In your improvement request details:
- Include the matching set/get parameter id, if known. For example: for Planner Group the set/get parameter id is IHG.
- List any other SAP Fiori app(s) the Default Value should be applied to.
- For example, Planner Group is also an optional filter field of app F2175 Find Maintenance Orders.
- You can also list classic UIs – such as Web Dynpro apps and GUI transactions - where you would like the parameter applied.
In the expected benefit, include an estimate – e.g. number of users x number of times this app is used per day or per week.
It’s helpful to include a screenshot of the field you want defaulted. You can add this as an attachment to the improvement request.
Example of an app highlighting the field Planner Group which is missing a default value
FAQ
Questions in this section include:
- How do I preset the default values for a user moving to SAP Fiori?
- As an administrator, can I update the default values for existing users directly?
- Why aren’t the Additional Values synchronized?
- What happens after a S/4HANA release upgrade when more Default Values have been added?
- What if the Default Value doesn’t have a matching classic set/get parameter?
- Help! I can’t find the Default Value I am looking for in my Settings, why not?
- How can I find out which apps and classic UIs use a certain Default Value?
- Help! Nothing is defaulting to my app! What do I do now?
- Help! I’m in Procurement and I’m missing defaults. What do I do now?
- Help! I’m in Asset Management and I’m missing defaults. What do I do now?
- Can I pass Default Values to my custom apps and classic UIs?
- What about classic set/get parameters that are not yet mapped to Default Values? Can I still use them?
- Can I create custom Default Values?
How do I preset the default values for a user moving to SAP Fiori?
Make sure you set up their set/get parameters before they login to SAP Fiori and use Default Values for the first time. For example, using the SU01 Maintain Users, or the mass update transaction SU10.
Example showing the Set/Get Parameters maintained in transaction SU01 Maintain Users
As an administrator, can I update the default values for existing users directly?
No. An API is not possible for Default Values, as the Default Values are strictly tied to the current user. Instead you can create a public Saved Value Set to provide the correct values for your users.
Example of where to find Saved Value Sets - use Save As to create new sets
Your users can then use this to reset their Default Values as recommended.
Even better, you can distribute the task of creating public Saved Value Sets to your key users - who can then follow up with their team members directly.
Refer to a full description of the technique in SAP Fiori for SAP S/4HANA – Yes Key Users can set Default Values for other Users
Why aren’t the Additional Values synchronized?
Classic set/get parameters can only hold a single value, so only the primary default value can be synchronized.
What happens after a SAP S/4HANA release upgrade when more Default Values have been added?
It’s common for a few more default values to be automatically added as part of a SAP S/4HANA release upgrade. If the default values are relevant to your apps they will automatically appear in your Default Values dialog.
What if the Default Value is empty but the set/get parameter already has a value on upgrade?
The existing set/get parameter values for any new Default Values will be proposed the first time you open Default Values after your upgrade.
After that any changes you make to your Default Values will update the matching set/get parameter values as usual. To minimize confusion, make sure you stop updating the matching set/get parameters directly.
What if the Default Value doesn’t have a matching classic set/get parameter?
That’s ok. There are several Default Values that are brand new for SAP S/4HANA and don’t have a classic set/get parameter. These are only maintained in Default Values and any changes don’t affect your set/get parameters.
Help! I can’t find the Default Value I am looking for in my Settings, why not?
If the Default Value is available in your SAP S/4HANA release but does not appear in your Default Values dialog, then it means you are not assigned to any apps that apply that Default Value.
How can I find out which apps and classic UIs use a certain Default Value?
Your administrator can use the Launchpad Content Manager. Navigate to the Tiles/Target Mapping tab to search across all target mappings for parameters with the value UserDefault. Select the Technical Catalog entry (look for the catalog id containing _TC_) then press Open SAP Fiori Launchpad App Manager to view the parameter details in the Launchpad App Manager.
Example of using the Launchpad Content Manager to search for UserDefault. to find the technical catalog
You can see which Default Values are mapped to parameters in the Parameters tab, including whether they are mapped to the primary value (format %%UserDefault.<default value>%%) or the primary and additional values (format %%UserDefault.extended.<default value>%%).
Example showing the Parameters tab when viewing a launchpad app descriptor item in the Launchpad App Manager
Help! Nothing is defaulting to my app! What do I do now?
Most likely the target mapping is missing the UserDefault parameter mapping.
Sometimes this is an oversight, e.g. where the app was created prior to the default value being made available. If you are in SAP S/4HANA 2022 or higher you (or your administrator) can add parameters using the adaptation mode in the Launchpad App Manager.
Sometimes Default Values are simply not mapped as you would wish. For example, in SAP Fiori app F4604 Manage Maintenance Notifications and Orders, in SAP S/4HANA 2022 the planning plant is mapped to default values, but the notification type is always default to the value Y1. This can be seen in the target mapping parameters in the Launchpad App Descriptor Item.
Example of the default behaviour in SAP Fiori app F4604 Manage Maintenance Notifications and Orders
Check the app documentation for any clues before updating the parameters in the Launchpad app Manager.
You can also raise an improvement request on the Customer Influence opportunity SAP S/4HANA Cloud for User Experience and Cross-Topics, public edition to ask for the target mappings to apps to be updated.
Help! I’m in Procurement and I’m missing defaults. What do I do now?
Procurement uses many Default Values across it’s apps.
Procurement also includes a special SAP Fiori app F1995 Default settings for users to set defaults on behalf of other users. This app pre-dates the availability of Default Values and can be used to set a limited number of defaults within procurement only.
Example of SAP Fiori app F1995 Default Settings for Users for Procurement
This app also provides a spreadsheet upload/download option.
Help! I’m in Asset Management and I’m missing defaults. What do I do now?
Enterprise asset management includes an additional Personalization app (technical id EAM_USER) that presets some defaults for classic UIs. This app writes to its own storage area and does not synchronize with either Default Values or Set/Get Parameters. So you are welcome to use it where needed.
Example of the EAM_USER Personalization app for Enterprise Asset Management
Enterprise Asset Management also includes several ABAP Web Dynpro apps. Check the Launchpad App Manager for the Web Dynpro Application id to see which incoming parameters are available.
Within ABAP Web Dynpro apps you can also use the “Use Current Value as Default” feature. Refer to: SAP Note 3239615 - Cannot save Default Values in user settings for Web Dynpro/ FIORI Apps
Can I pass Default Values to my custom apps and classic UIs?
Yes you can reuse Default Values by applying them to your launchpad app descriptor items (aka tile/target mappings) in the Launchpad App Manager. Refer to blog post Applying User Defaults in SAP S/4HANA.
What about classic set/get parameters that are not yet mapped to Default Values? Can I still use them?
Yes, you can. They will continue to be used by your classic UIs only. However, to minimize confusion for your business users, you should consider asking for an equivalent Default Value to be created by raising an improvement request as described above in the section How to request more Default Values.
Can I create custom Default Values?
No, sorry. Custom Default Values are not supported.
However, you can create your own plug-in for the Settings dialog. IMPORTANT: Your new section will be separate to the section for Default Values. Refer to the SAP Help Portal – Fiori launchpad > Developer Guide > Extending the launchpad.
Becoming a SAP Fiori for SAP S/4HANA guru
You’ll find much more on the community topic page for SAP Fiori for SAP S/4HANA
Other helpful links in the SAP Community:
- Follow our tag SAP S/4HANA RIGfor more from the SAP S/4HANA Customer Care and RIG
- See all questions and answers about SAP Fiori for SAP S/4HANA
- Follow SAP Fiori for SAP S/4HANAfor more blogs and updates
- Ask a Question about SAP Fiori for SAP S/4HANA
Brought to you by the SAP S/4HANA Customer Care and RIG.
- SAP Managed Tags:
1 Comment
