We’re transitioning to S/4HANA 2020 and evaluating whether to adopt Fiori analytics apps for general ledger reporting or continue with classic SAP GUI transactions like FAGLB03, FS10N, and FBL3N that our finance team knows well.
Fiori analytics usability looks impressive in demos - the visual dashboards and drill-down capabilities are modern and intuitive. However, our controllers are concerned about losing the detailed filtering and export capabilities they rely on in classic GUI transactions.
From an audit compliance perspective, we need to ensure that whatever reporting approach we choose maintains complete audit trails, supports period-end close validations, and provides the granular transaction-level detail auditors require.
What’s been your experience with the classic GUI feature set compared to Fiori analytics? Are there functional gaps that force you to maintain dual approaches, or can Fiori truly replace GUI-based reporting for finance operations?
From an audit compliance standpoint, both approaches are adequate if configured correctly. Fiori analytics apps maintain the same underlying authorization concepts and audit logging as GUI transactions. The critical requirement is ensuring Fiori apps use the same CDS views and authorization objects as their GUI counterparts. We audit S/4HANA systems using both interfaces and haven’t found compliance gaps, but you must verify that user access controls are consistently applied across both UIs.
We’ve fully transitioned to Fiori for GL reporting and the usability improvement is substantial. The Display Line Items app (F1731) replaces FBL3N with better filtering, saved variants, and Excel export. The key is proper user training - finance teams initially resist because Fiori works differently, but once they understand the new navigation patterns, productivity actually increases. We’re seeing 20-30% faster month-end reporting.
Consider the mobile access advantage of Fiori. Our CFO and controllers can now review GL reports, approve journal entries, and monitor financial metrics from tablets during travel. This wasn’t possible with GUI. The audit compliance aspect actually improves because Fiori apps can embed workflow approvals and comments directly in the reporting interface, creating better documentation than separate email chains that often accompany GUI-based reporting.
Performance is another consideration. Fiori analytics apps leverage CDS views and HANA optimization, making them faster for large data volumes. We’ve seen GL line item queries that took 2-3 minutes in FBL3N complete in under 30 seconds with the Fiori Display Line Items app. However, this assumes your CDS views are properly designed and HANA is well-tuned. Poor CDS view design can make Fiori slower than GUI.
The transition challenge is more about change management than technical capability. Finance teams have decades of muscle memory with GUI transactions. We found that focusing on specific use cases rather than wholesale replacement works better. Start with high-frequency reports that benefit most from Fiori’s visualization (variance analysis, budget vs actuals), keep GUI for edge cases and complex troubleshooting scenarios. Over time, as Fiori coverage expands, GUI usage naturally declines.
There are still functional gaps that frustrate our power users. Complex multi-dimensional filtering that’s straightforward in SAP GUI requires multiple clicks in Fiori. The classic GUI feature set for mass data exports with custom layouts is more flexible than Fiori’s predefined export options. We maintain both interfaces - Fiori for day-to-day operational reporting and management dashboards, GUI for detailed analysis and troubleshooting. This dual approach isn’t ideal but it’s necessary for now.