Latest Update: 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. The following User Defaults have been added:

• Asset Depreciation Area
• BOM Application
• Is Period Based Balance Reporting
• LCM: Company Code
• LCM: Governing Law
• LCM: Legal Context
• LCM: Language of Legal Documents
• LCM: Purchasing Organization
• LCM: Sales Organization
• Project Profile
• Responsible Cost Center
• Sales Order Type
• Warehouse
• Warehouse Work Center

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:

• How to apply Default Values to app parameters in the Launchpad Designer
• Which Default Values are delivered by SAP

Let’s get to it!

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 tile catalog that contains the target mapping for the app
   • You are only permitted to change custom tile 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.

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 Fiori Launchpad Administration Guide in the section Configuring Navigation Parameters with User-Specific Default Values.

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.

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.

Default Values Delivered by SAP   

These are the currently available default values delivered by SAP as at September 2018, up to and including SAP S/4HANA Cloud 1808 and SAP S/4HANA 1809.

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.

Becoming a SAP Fiori for SAP S/4HANA guru

You’ll find much more on our SAP Fiori for SAP S/4HANA wiki

Brought to you by the S/4HANA RIG