General comments
Language
When a user logs into the Fiori Launchpad, a language is selected.
In order for the language selected in Fiori to appear, the following conditions must have been met:
In SAP, a default language has not been entered for the background user of the RFC connection.
In SAP, a default language has not been entered for the user who is logging in.
The following applies to the use of languages.
When a default language has been entered in SAP for the background user, this language will always be used.
The user's default language and the Fiori login language will be ignored.
When a default language has been entered in SAP for the user but not for the background user, this language will always be used.
The Fiori login language will be ignored.
Accessibility
SAPUI5 framework elements are used to improve accessibility. Some of these elements require SAPUI5 Version 1.78 or higher.
If the necessary SAPUI5 framework version is used, the corresponding changes will be activated automatically. Separate customizing is not required.
Notice
In Version 1.78., SAP significantly improved accessibility in the SAPUI5 framework. If the issue of accessibility is relevant, this SAPUI5 version or higher should be used.
Calendar Type
The (primary) calendar type in the xSuite Apps is always "Gregorian." All other calendar types (e.g. "Persian" or "Japanese") are only supported as secondary calendar types.
To display a secondary calendar type, specify this in the xSuite Base Library in the settings.json file via the secondaryCalendarType parameter.
The primary calendar type cannot be changed, not even by using the SAPUI5 URL parameter sap-ui-calendarType.
Multi-Back-End
When multi-back-end functionality is used, not just one, but multiple back-ends are accessed within an xSuite App.
When using the multi-back-end mode, the functionality of the individual xSuite Apps may differ from the functionality in the single back-end mode.
The following xSuite Apps for SAP Fiori support multi-back-end functionality:
xSuite Invoice Monitor App
xSuite Invoice App
xSuite Check Customizing App
The multi-back-end mode can only be used if all of the following conditions apply:
Notice
If one of these conditions does not apply, only one back-end will be addressed by the xSuite App (i.e., single back-end mode).
The xSuite App offers general support of the multi-back-end functionality.
The necessary customizing of the front-end has been completed.
The necessary customizing of the back-end that is addressed by the xSuite App has been completed and it is the master system (not a slave system).
Multi-back-end — Data sources
In multi-back-end mode, user settings are always loaded from the master system and stored there as well. TCURX data is also only loaded from the master system.
F4 input help; saving, deleting and loading templates; and the toolbar buttons all always address the respective back-end of the document, search, etc., not necessarily the master system.
In single-back-end mode, user settings are always loaded from the respective back-end and stored there as well.