Looking for the list of all current Default Values? Skip to section Default Values Delivered by SAP   

Latest Updates:

• August 2023: Re-organized to make the Default Values Delivered by SAP the first section. Added some examples from Launchpad App Manager as this is the recommended tool for changes to parameters in releases SAP S/4HANA 2020 and higher.
• June 2023: Added parameters coming soon in 2308. A few parameters recategorized – PLM parameters reassigned to AM (asset management)
• July 2022: We occasionally get asked which parameters are available in current on-premise and private cloud edition releases.  All parameters added up to March 2021 are confirmed available in SAP S/4HANA 2021.
• March 2022: For your planning, 2 new parameters added: Cost Center Hierarchy and Profit Center Hierarchy. Will be available with SAP S/4HANA Cloud 2208 and expected for SAP S/4HANA 2022 (On premise and Private cloud edition).
• March 2021: 2 new parameters added: SEPA Mandate Application and Country. These are confirmed as available in SAP S/4HANA 2021 (on premise and private cloud edition).
• January 2021: Correcting a typo. The technical name of the Plan Category parameter is PlanningCategory (and not PlanCategory).
• August 2020: New User Defaults added for 2008 and 2011. Please check your 2020 FPS00 and higher systems for these.
• April 2020: New User Defaults added for 2002 and 2005. Please check your 1909 FPS01 and higher systems for these.
• 2019: Updated for SAP S/4HANA 1909. New user defaults as of SAP S/4HANA 1909 are now listed. 
• 2018: Updated for SAP S/4HANA 1809. New User Defaults as of SAP S/4HANA 1809 are now listed. Links have been updated to the Fiori Launchpad Administration Guide for S/4HANA 1809.

As a User Experience Lead, Launchpad Content Administrator, or Developer you may want to apply Default Values to your own custom apps, or adjust how default values are applied to delivered SAP Fiori apps or classic User Interfaces.  This blog explains how Default Values work and what to do.

Most SAP S/4HANA apps have certain input fields where a business user usually or always enters the same information. The information is typically even not limited to the single app, but also relevant for other apps.

It makes sense to enable users to maintain a default value for this field in a central place, and then let the app prefill the relevant input fields with the default value, provided no other value is provided explicitly, such as by navigation from another app.

In SAP S/4HANA this central place is Default Values.  Business users can set their own default values as explained in Setting Default Values for SAP S/4HANA.

NOTE: As a prerequisite the Default Values dialog needs to be activated and assigned to the user as explained in Activating Default Values for SAP S/4HANA.

TIP: If you are coming from a SAP Business Suite or Suite on HANA system, you may be familiar with an older similar concept called SET/GET Parameter IDs.  Why don’t we use these in SAP S/4HANA? SET/GET Parameter IDs depend on a stateful paradigm where values are passed in ABAP memory.  Web-based apps are typically stateless, so we need something more flexible.  The good news is that we can pass Default Values to both stateless Fiori apps, and stateful classic user interfaces such as SAPGUI transactions. 

Controlling how Default Values are applied across your SAP S/4HANA solution is typically part of the User Experience Lead or Launchpad Content Administrator role.  Developers, basis experts, and other administrators may occasionally also be involved.

In this blog you will learn:

• Which Default Values are delivered by SAP
• When are Default Values applied
• The format of Default Value parameters
• How to apply Default Values to app parameters in the Launchpad App Manager 
  • Use this approach if you are on SAP S/4HANA 2020 or higher
• How to apply Default Values in the Launchpad Designer
  • Use this approach if you are on SAP S/4HANA 1909 or lower

Let’s get to it!

Default Values Delivered by SAP   

These are the currently available default values delivered by SAP as at August 2023.

If you are coming from SAP Business Suite or Suite on HANA, you may want to map these to the equivalent SET/GET Parameter ID you know from SAPGUI so you can see those also.

And if you need to check the data type or length or other field-specific restrictions you can see the underlying Data Element id, so you can cross check that in the ABAP Dictionary e.g. using SAPGUI transaction SE11.

How Default Values are Applied

The default value will be passed to the app parameter whenever the app is launched provided there is no overriding parameter value passed, e.g. during navigation from another app.

So typically you use default values to preset the defaults when launching an app from:

• Launchpad page
• App Finder
• Home button navigation
• Search on Apps.

How to format Default Value Parameters

The format for the Default Value assignment is:

• %%UserDefault.<parameterName>%% for single value parameters
• %%UserDefault.extended.<parameterName>%% for extended values, i.e. where the user has maintained additional values and the app parameter accepts multiple values or value ranges.

You can find further details in the SAP Fiori launchpad Administration Guide in the section Maintaining Launchpad App Descriptor Items and Configuring Navigation Parameters with User-Specific Default Values

Applying Default Values in the Launchpad App Manager

Applying default values in the Launchpad App Manager is straightforward.

NOTE: You will need to know how to use the Launchpad App Manager tool.  You can find out more about configuring Launchpad content using the Launchpad App Manager in the Fiori Launchpad Administration Guide in the section Setting Up Technical Catalogs with the SAP Fiori Launchpad App Manager.

You will need to:

1. Know the technical ID of the Default Value
2. Know the technical ID of the app parameter you want to set
3. Open the Launchpad App Manager tool in your web browser
   • You can access the Launchpad App Manager from the Fiori Administrator role.
   • This role (by default named Z_FIORI_FOUNDATION_ADMIN) is generated by the Fiori launchpad activation task list SAP_FIORI_FOUNDATION_S4. Refer to SAP Fiori for SAP S/4HANA – Activate SAP Fiori in 1 day or less – the video playlist

4. Find the Technical catalog that contains the target mapping for the app
   • You can find the app via the Launchpad App Descriptor Items tab of the Launchpad App Manager
   • You can search on the Fiori app id, GUI tcode, Web Dynpro application, etc.

Searching for Fiori app F1345 in the Launchpad App Descriptor Items tab of the Launchpad App Manager

5. Configure the Parameters of the app to set the parameter value to the Default Value. You do this in the Parameters section of the Launchpad App Descriptor Item.
   • If you are using your own custom technical catalog you can maintain the parameters.
   • If the technical catalog is delivered by SAP, and you are in SAP S/4HANA 2022 or higher, you can use adaptation mode to add new parameters directly to the SAP technical catalog entry.
   • Otherwise, you should copy the technical catalog entry to a custom technical catalog, and maintain the parameters in your custom technical catalog.

Example of the entry for app F1345 showing the Parameters tab with the User Defaults maintained

IMPORTANT:

• You are only permitted to change custom technical catalogs directly.
• You can use adaptation mode to add parameters to SAP delivered catalog. Refer to SAP Fiori Launchpad: New Fast and Easy Option to Adapt SAP-delivered Launchpad Content (for On-Premise and Cloud, Private Edition)
• If you need to change existing parameters, or you don’t have the adaption mode (available from SAP S/4HANA 2022), you can copy launchpad app descriptor items from SAP delivered technical catalogs to your custom technical catalogs.
• For SAP delivered apps the original Technical Catalog is also listed as part of the Implementation Information of the SAP Fiori app in the SAP Fiori apps reference library.
• Do NOT put original entries into business catalogs. Only use business catalogs to gather references to entries in technical catalogs, and assign your business catalogs to your business roles.

Applying Default Values in the Launchpad Designer

Applying default values in the Launchpad Designer is straightforward.

NOTE: You will need to know how to use the Launchpad Designer tool.  You can find out more about configuring Launchpad content using the Launchpad Designer in the Fiori Launchpad Administration Guide.

You will need to:

1. Know the technical ID of the Default Value
2. Know the technical ID of the app parameter you want to set
3. Open the Launchpad Designer tool in your web browser
   • You can do this using SAPGUI transaction /UI2/FLPD_CUST to launch the Fiori app
   • Or you can enter the Launchpad Designer URL in your web browser, specifying the relevant host and port of your SAP S/4HANA solution https://<host>:<port>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html
4. Find the Technical catalog that contains the target mapping for the app
   • You are only permitted to change custom catalogs.
   • If the target mapping is in a SAP delivered Business Catalog or Technical Catalog you will first need copy a reference to the target mapping into a custom tile catalog where you can configure it.
   • NOTE: For SAP delivered apps the original Business Catalog or Technical Catalog will be listed as part of the Implementation Information of the SAP Fiori app in the SAP Fiori apps reference library.
5. Configure the Target Mapping of the app to set the parameter value to the Default Value. You do this in the Parameters section of the Target Mapping.

Applying the Default Value in a Target Mapping

In this example, you can see how the target mapping for the Post Incoming Payments app is configured with the default values for Company Code, Fiscal Year, Accounting Document Type, and Ledger Group.

You can see the format of the Default Value for Company Code in this close-up of the Parameters section.

If you set a default value for Company Code in Settings:

Then the default is applied to the Post Incoming Payments app.

Applying Additional Values in a Target Mapping

Some app parameters support extended values, where multiple values or value ranges can be provided for the same app parameter. In this example, you can see how the target mapping for the Manage Journal Entries app is assigned to extended default values for Company Code, Fiscal Year, and Accounting Document Type.

If you set Additional Values in Default Settings for Company Code:

Then the default value and the Additional Values are applied to the Manage Journal Entries app.

NOTE: If you have only maintained Additional Values and not a default value then just the Additional Values will be passed.

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 RIG for 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.