You save a default variant for the filter area and the table area in app Display Line Items in General Ledger (App ID F2217). You navigate to this app from another app and expect to see default variant.
- Financial Accounting (FI)
- SAP S/4HANA Cloud
- SAP Fiori
Default variants are in place for Display Line Items in General Ledger app if the app is started via the Launchpad tile.
As soon as the app is started via navigation from another app, the standard variants are in place, enriched with the passed parameters from the calling application.
You do not have to store the variant as default again, after the navigation - it is still stored as default and will be applied, as soon as the app is started from the tile.
Also in the navigation case, if the user is interested to see the navigation result with the default table variant, there are just two clicks -> open the table variant drop-down and click on the appropriate variant name -> the variant is applied directly and the table result gets refreshed.
In general, the evaluation path is as follows:
"level 0" : user default values via launchpad settings
"level 1" : user default variants within app
"level 2" : navigation result/context, send via external app-state
"level 3" : internal app-state, which can be shared via e-mail, jam and saved as tile
"level 1" disables "level 0" in the app | "level 2" disables "level 1" in the app | "level 3" disables "level 2" in the app
So e.g. you have navigated to an application, changed some filter settings, applied a table variant and shared this state afterwards via e-mail -> in that case, the click on the link of the e-mail will bring back exactly the same screen again, with the navigation result, the changed filters and the applied variant, because this internal state is evaluated on "highest level" during the app start.
F2217, default variant, navigation, cloud, FIORI , KBA , FI-FIO-GL , Fiori UI for General Ledger Accounting , Problem