Technical Articles
Applying User Defaults in SAP S/4HANA
Update 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.
Update 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).
Update 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).
Update January 2021: Correcting a typo. The technical name of the Plan Category parameter is PlanningCategory (and not PlanCategory).
Latest update August 2020: New User Defaults added for 2008 and 2011. Please check your 2020 FPS00 and higher systems for these.
- Grant
- Technical Object
- Notification Type
- Order Type
- Planning Plant
- Maintenance Plant
Latest update April 2020: New User Defaults added for 2002 and 2005. Please check your 1909 FPS01 and higher systems for these.
- Service Document Type
- G/L Account Hierarchy
- Plan Category
Latest Update: Updated for SAP S/4HANA 1909. New user defaults as of SAP S/4HANA 1909 are now listed. The following User Defaults have been added:
- Ship-to Party
- Treasury Valuation Area
- Accounting Principle
- Operating Concern
- Sales Document Type
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:
- Know the technical ID of the Default Value
- Know the technical ID of the app parameter you want to set
- 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
- 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.
- 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.
Default Value | Technical ID | Equivalent to SET/GET Parameter ID | Area | Underlying Data Element | Available since Cloud/OP |
Account Assignment Category | AccountAssignmentCategory | KNT | MM | KNTTP | |
Accounting Principle | AccountingPrinciple | ACCOUNTING_PRINCIPLE | FI | ACCOUNTING_PRINCIPLE | 1908/1908 |
Activity Type | ActivityType | LAR | CO | LSTAR | |
Activity Type Group | ActivityTypeGroup | LSG | CO | LAGRU | |
Application | SEPAMandateApplication | SEPA_ANWND | FI | SEPA_ANWND | 2102 |
Asset Class | AssetClass | ANK | FI | ANLKL | |
Asset Depreciation Area | AssetDepreciationArea | AFB | FI | FIS_AFABE_D | 1802 |
Asset Main Number | MasterFixedAsset | AN1 | FI | ANLN1 | |
Asset Subnumber | FixedAsset | AN2 | FI | ANLN2 | |
Bank | Bank | BNK | FSCM | FCLM_BAM_BANK_KEY | |
Bank Account | BankAccount | BKT | FSCM | FCLM_BAM_ACC_NUM | |
Bank Country | BankCountry | BKL | FSCM | BANKS | |
Bill-to party | BillToParty | VRE | SD | KUNRE | |
BOM Application | BOMExplosionApplication | CSA | PLM | CAPID | 1802 |
BOM Usage | BillOfMaterialVariantUsage | CSV | PLM | STLAN | |
Budget Entry Document Type | BudgetEntryDocumentType | DOTY | PSM | BUED_DOCTYPE | |
Budget Period | BudgetPeriod | BUDPER | PSM | FM_BUDGET_PERIOD | |
Budget Version | BudgetVersion | BP2 | PSM | BUKU_VERSION | |
Business Area | BusinessArea | GSB | FI | GSBER | |
Business Process | BusinessProcess | KWP | CO | CO_PRZNR | |
Change Number | ChangeNumber | AEN | PLM | AENNR | |
Chart of Accounts | ChartOfAccounts | KPL | FI | KTOPL | |
Collection Group | CollectionGroup | UDM_GROUP | FSCM | UDM_COLL_GROUP | |
Collection Segment | CollectionSegment | UDM_SEGMENT | FSCM | BDM_COLL_SEGMENT | |
Collection Specialist | CollectionSpecialist | UDM_SPECIALIST | FSCM | BDM_COLL_SPECIALIST | |
Commitment Item | CommitmentItem | FPS | PSM | FM_FIPEX | |
Company Code | CompanyCode | BUK | FI | BUKRS | |
Controlling Area | ControllingArea | CAC | CO | KOKRS | |
Cost Center | CostCenter | KOS | CO | KOSTL | |
Cost Center Group | CostCenterGroup | KSG | CO | KSGRU | |
Cost Center Hierarchy | CostCenterHierarchy | CO | FIS_CCTR_HRYID_42 | 2208 | |
Cost Element | CostElement | KAT | CO | KSTAR | |
Cost Element Group | CostElementGroup | KAG | CO | KAGRU | |
Cost Object | CostObject | KTR | CO | KSTRG | |
Country | Country | LND | General | LAND1_GP | 2108 |
Credit Segment | CreditSegment | UKM_SEGMENT | FSCM | UKM_CREDIT_SGMNT | |
Customer | Customer | KUN | SD | KUNNR | |
Customer Group | CustomerGroup | VKD | SD | KDGRP | |
Display Currency | DisplayCurrency | FWS | FI | VDM_V_DISPLAY_CURRENCY | |
Distribution channel | DistributionChannel | VTW | SD | VTWEG | |
Division | Division | SPA | SD | SPART | |
Document Type | AccountingDocumentType | BAR | FI | BLART | |
Exchange Rate Type | ExchangeRateType | KUT | FI | KURST | |
Financial Management Area | FinancialManagementArea | FIK | PSM | FIKRS | |
Financial Statement Version | FinancialStatementVariant | BIL | FI | FIS_FSVERSN | |
Fiscal Year | FiscalYear | GJR | FI | GJAHR | |
Functional Area | FunctionalArea | FBE | CO | FKBER | |
Fund | Fund | FIC | PSM | BP_GEBER | |
Funded Program | FundedProgram | FM_MEASURE | PSM | FM_MEASURE | |
Funds Center | FundsCenter | FIS | PSM | FM_FICTR | |
G/L Account | GLAccount | SAK | FI | FIS_RACCT | |
G/L Account Group | GLAccountGroup | FCOM_GL_ACCT_GRP | FI | KTOKS | |
G/L Account Hierarchy | GLAccountHierarchy | FCOM_GL_ACCT_HIER | FI | FINCS_USEL_SAKNR_HRYID | 2005 |
G/L Ledger | Ledger | GLN | FI | RLDNR | |
Grant | GrantID | GM_GRANT_NBR | PSM | GM_GRANT_NBR | 2008 |
House Bank | HouseBank | FARP_HBKID | FSCM | FIS_HBKID | |
House Bank Account | HouseBankAccount | FARP_HKTID | FSCM | FAC_HKTID | |
Is Period Based Balance Reporting | IsPeriodBasedBalanceReporting | FINS_FIS_FICO_BAL | FU | FIS_PERIOD_BASED_REPORTING | 1805 |
Internal Order | InternalOrder | ANR | CO | AUFNR | |
Key Figure Group | AssetAccountingKeyFigureSet | FI | FAA_KEY_FIGURE_SET | ||
LCM: Company Code | LglCntntMMainOrgCoCode | LCM | LCM_MAINORG_COMP_CODE | 1811/1809 | |
LCM: Governing Law | LglCntntMGovLaw | LCM | LCM_LT_GOV_LAW | 1811/1809 | |
LCM: Legal Context | LglCntntMContext | LCM | LCM_LT_CONTEXT_ID | 1811/1809 | |
LCM: Language of Legal Documents | LglCntntMLanguage | LCM | LCM_LANGUAGE | 1811/1809 | |
LCM: Purchasing Organization | LglCntntMMainOrgPurOrg | LCM | LCM_MAINORG_PURCH_ORG | 1811/1809 | |
LCM: Sales Organization | LglCntntMMainOrgSalesOrg | LCM | LCM_MAINORG_SALES_ORG | 1811/1809 | |
Ledger Fiscal Year | LedgerFiscalYear | (GJR) | FI | FIS_RYEAR | |
Ledger Group | LedgerGroup | GLDGRP_FLEX | FI | FAGL_LDGRP | |
Maintenance Plant | MaintenancePlant | SWK | PLM | SWERK | 2011 |
Material Group | MaterialGroup | MKL | MM | MATKL | 1708 |
Material Number | Material | MAT | MM | MATNR | |
Material Type | MaterialType | MTA | MM | MTART | 1708 |
Notification Type | NotificationType | QMR | PLM | QMART | 2011 |
Operating Concern | OperatingConcern | ERB | CO | ERKRS | 1911/1909 |
Order Type | OrderType | AAT | PLM | AUFART | 2011 |
Payer | PayerParty | KRG | SD | KUNRG | |
Plan Category | PlanningCategory | CO | FCOM_CATEGORY | 2005 | |
Planning Plant | MaintenancePlanningPlant | IWK | PLM | IWERK | 2011 |
Plant | Plant | WRK | MM | WERKS_D | |
Profit Center | ProfitCenter | PRC | CO | PRCTR | |
Profit Center Hierarchy | ProfitCenterHierarchy | CO | FIS_PRCTR_HRYID_42 | 2208 | |
Project | Project | PSP | CO | PS_PSPID | |
Project Profile | ProjectProfileCode | PWS | EPPM | PROFIDPROJ | 1805 |
Purchasing Group | PurchasingGroup | EKG | MM | BKGRP | |
Purchasing Organization | PurchasingOrganization | EKO | MM | EKORG | |
Responsible Cost Center | ResponsibleCostCenter | KOS | EPPM | PS_FKSTL | 1805 |
Sales Document Type | SalesDocumentType | AAT | SD | AUART | 1911/1909 |
Sales Group | SalesGroup | VKG | SD | VKGRP | |
Sales Office | SalesOffice | VKB | SD | VKBUR | |
Sales Order | SalesOrder | AUN | SD | VBELN_VA | |
Sales Order Type | SalesOrderType | AAT | SD | AUART | 1802 |
Sales Organization | SalesOrganization | VKO | SD | VKORG | |
Segment | Segment | FUCN_SEG | FI | FB_SEGMENT | |
Service Document Type | ServiceDocumentType | CRM_PROCESS_TYPE | CRM | CRMT_PROCESS_TYPE | 2002 |
Shipping Point | ShippingPoint | VST | LE | VSTEL | |
Ship-to Party | ShipToParty | KWE | SD | KUNWE | 1905/1909 |
Sold-to party | SoldToParty | VAG | SD | KUNAG | |
Statistical Key Figure | StatisticalKeyFigure | STA | CO | STAGR | |
Statistical Key Figure Group | StatisticalKeyFigureGroup | PC5 | CO | STAGRGRP | |
Storage Location | StorageLocation | LAG | MM | LGORT_D | |
Supplier (Vendor) | Supplier | LIF | MM | VDM_LIFNR | |
Tax Is Calculated Automatically | TaxIsCalculatedAutomatically | XTX | FI | XMWST | |
Technical Object | TechnicalObject | PLM | EAMS_TEC_OBJ | 2011 | |
Treasury Valuation Area | TreasuryValuationArea | TPM_VAL_AREA | FSCM | TPM_VAL_AREA | 1908/1909 |
Valuation Type | ControllingValuationType | BWT | CO | BWTAR_D | |
WBS Element (external Number) | WBSElement | PRO | CO | PS_POSID | |
Warehouse | Warehouse | /SCWM/LGN | MM | /SCWM/LGNUM | 1808/1809 |
Warehouse Work Center | WarehouseWorkCenter | /SCWM/WST | MM | /SCWM/DE_WORKSTATION | 1808/1809 |
Work Center | WorkCenter | AGR | MM | ARBPL |
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.
Hello,
I already have the changes and the catalogs and the new groups, but there are no inclusions in the transport order. previous days I achieved but I only carry the groups.
What am I doing wrong, why are not my changes included in the order?
thank you very much
regards
Hi Yessenica, I take it this is not a comment on the blog but a question on (I think) how to use the Launchpad Designer tool? In which case please post a question in answers.sap,com using the tag SAP Fiori for S/4HANA
If you can include some screenshots with your question that would help us understand what might be going wrong. We would also need to know whether you are using scope mode CONF (client independent) or CUST (client dependent when you call your Launchpad Designer.
Look forward to see your question in answers.sap.com
Rgds,
Jocelyn
Great Blog Jocelyn...Thank you!!
Hi Jocelyn,
Nice blog..! Do we have provision to add custom default values ?
Thanks,
Naga
Hi Naga,
Not yet sorry.
Rgds,
Jocelyn
Hi,
Very helpful information, Thanks.
Althogh How do we know Default values delivered S41610 or 1709 version. I was adding StorageLocation as default value but it is not visible. Other value such as plant were visible.
Thanks,
Vinod
Great Blog Jocelyn, Thanks
Hi Jocelyn Dart ,
Thanks for the blog.
I have followed the steps, but default values whatever I set in the ME area are not reflecting when I launch the application in launchpad.
I tried to set default values for DisplayCurrency field for standard fiori application "Value contract Consumption".
I attached few screenshots here. Kindly check and let me know whats the issue here.
Added parameter for Display Currency in target mappings.
Set the Display currency as INR
Value is still in EUR in the application
Thanks,
Vasantham
Hi Vasantham,
Please raise all questions in answers.sap.com - blog comments are only for direct comments on the blog. Asking your question in answers.sap.com increases the speed with which you get an answer... rather than waiting for only the blog author to find it.
Just because the value has been passed (open the smart filter bar to check) doesn't mean the app will use it... there are a hierarchy of overrides and analytical apps have some further considerations.
If you need more please post a question in answers.sap.com with the Fiori for S/4HANA tag - you can always use an @ mention to let me know.
Rgds
Jocelyn
Hello Jocelyn,
I have a doubt here. By adding the default values in the settings in ME Area, will it reflect in the parameters section of User profile (SU01) in the Backend System?
Regards
Roopa
Good question Roopa! You will find how the user parameters interact in SAP Note 2519765 - Synchronization of Fiori User Default Values with Backend SET-/GET-Parameters
Hi Jocelyn,
Do we have any further blogs explaining technical ID of the app parameter as I am unable to find the appropriate parameter name from my custom SAPUI5 application.
I have a custom SAPUI5 application with Smart filter Bar similar to Manage Journal Entries, but I am unable to pull the user specific default values in such case, while custom applications similar to Trial Balance, I was able to transfer default values in the application using above mentioned FLPD Configuration.
Thank You.
Hi Soham
you need to list the technical names of the parameters you want to use in the manifest.json of your custom Fiori(SAPUI5) app.
Examine the code of a SAP delivered Fiori app via txn SE80 using the BSP application & technical name of the app given in the Fiori apps library
also check the SAPUI5 SDK
thanks
Jocelyn
Hi Jocelyn,
Thanks for the amazing blog but is there a central SAP note which lists down all the default value options that we have and what business roles should be assigned to have the appropriate option enables in me area?We have a requirement to set default values for “Manage Business Partner Master Data” for attributes like Language, Customer Classification but i could not find the business role for this in your list for business partner master data.
Has SAP provided any provision for default values for business partner master data app?
https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/Apps('F1765')/S15OP
Regards,
Navya
Excellent Blog, specially the part I was looking for was Default Values Delivered by SAP.
Thank you!
Umang Rustagi
Hello ,
I have a question about the setting the Default Parameters in SU01 >> Parameters section. Can we use SU01 set parameters option for mass users to reflect the default parameters in the Fiori Launchpad.
Generally speaking yes when you initially move from Set/Get parameters to Fiori launchpad. However there are some prerequisites and considerations which are covered in SAP Note 2519765 - Synchronization of Fiori User Default Values with Backend SET-/GET-Parameters
Hello
Thank you for the top-interesting blog.
Default Values work in Standard SAP Apps (e.g. Display Line Items). In custom analytical Queries the Default Values-Parameter won't be set. It doesn't work. Are there any restrictions for applying User Default Values in custom analytical Queries?
Our report works with User Variables (e.g. CostCenter).
Target-Mapping
Best regards
Reto
Hi Reto,
Yes there are some restrictions. For starters mostly they only accept single values only, and the default values are set in the query tool itself.
If you would like to see this feature please raise a request to application component BC-SRV-APS-EXT-AQD
Best
Jocelyn
P.s. Also please do not use Fiori Design Studio for these sorts of apps as this is deprecated. Please use Web Dynpro Grid instead. Refer to https://blogs.sap.com/2021/03/18/six-reasons-why-web-dynpro-is-better-than-design-studio-in-sap-s-4hana-cloud/