How-toSAP S/4HANAAnalytics / Fiori / Embedded Analytics

SAP S/4HANA Standard Reports: Fiori, Embedded Analytics and CDS Views

Question
sap standard reports s4 hana

Also searched as

  • sales report in sap s4 hana
  • group reporting in sap s4hana finance
  • sap s4hana embedded analytics reports
  • sap fiori reports list

Short answer

In S/4HANA, standard reports are mostly Fiori apps built on CDS views, with classic transactions still available for many lists. Find them in the Fiori Apps Reference Library, and extend them using Custom Analytical Queries or by building on released CDS views.

Applies to: SAP S/4HANA on-premise (recent releases) and S/4HANA Cloud private edition; some app names vary by release

How to find and use standard reports in S/4HANA

  1. 1Open the Fiori Apps Reference Library and search by business role or keyword such as sales or financial statements. It lists each app, its required roles and the underlying CDS views.
  2. 2Confirm the app is activated on your system and that the user has the PFCG role containing its catalog. Without it, the tile does not appear.
  3. 3For sales, use the sales apps in the Sales Order Processing area, or classic VA05 and VA05N lists of sales orders when you need them.
  4. 4For finance, use apps based on the universal journal (table ACDOCA), such as G/L line item displays and balance displays, or classic FBL3N and FAGLB03.
  5. 5For ad hoc analysis, open the View Browser and Query Browser to explore CDS-based analytical queries, then build your own in Custom Analytical Queries.
  6. 6For group reporting, use the Group Reporting apps, which work on consolidation data rather than local ledgers.

How S/4HANA reporting is layered

Under every modern report is a CDS view. Interface views (prefix I_) expose business data, consumption views (prefix C_) shape it for an app, and analytical queries add measures and dimensions. Embedded analytics means these queries run live on the S/4HANA database with no separate warehouse.

Because data is not copied, the reports always reflect current postings. The cost is that heavy reports compete with transactions for database resources, which matters on busy on-prem systems.

The old LIS and SAP Query tools still exist and work, but new reports are expected to use CDS and Fiori.

Sales reporting examples

For open orders and fulfilment, use sales order and delivery apps, or VA05N for the classic list. Billing lists come from VF05N, and credit and blocked items from the relevant sales apps or VKM transactions.

For a sales volume report by customer or material, build a custom analytical query on a released sales CDS view, with customer, product and period as dimensions and net amount as the measure. This is more flexible than the classic sales information system.

If you still use SIS (S001 to S0xx), keep it only if it is already in use; new build is better placed on CDS.

Finance and group reporting

The universal journal ACDOCA combines financial accounting, controlling and asset postings in one table, so apps for G/L, cost center and profit analysis all read the same data. This is why period-end reconciliations are simpler than in ECC.

Group Reporting is the consolidation solution in S/4HANA Finance. It uses its own consolidation data, which includes data collected into table ACDOCU, and has apps for consolidation monitoring and consolidated statements. It is separate from local company-code reporting.

Both areas require the right roles. If a finance user cannot see an app, check the business catalog before assuming the app is missing.

Try it here, free

ABAP CDS View Skeleton Generator

Open full tool

Fill in table, fields, aliases and one association to get CDS view DDL in both the classic DDIC-based and the view entity syntax.

Common pitfalls

  • !The Fiori Apps Reference Library lists apps for all releases. Check the release column before promising an app.
  • !Apps need activated OData services and ICF nodes. A tile that opens an error often means the service is not activated.
  • !Custom analytical queries on very large tables can slow the system. Test with filters first.
  • !Reading tables directly in custom code skips authorisations that the CDS view enforces.
  • !Group Reporting data does not equal local ledger data. Reconcile before comparing.

How an ERP-grounded AI assistant handles this

Instead of finding the right app, a user can ask a grounded assistant a question in plain language and get the answer plus the underlying view or query. For regulated manufacturers this works best on-prem, so the assistant, the model and the financial data all remain in your own environment, with SAP roles respected.

Frequently asked questions

Where are standard reports in S/4HANA?

Mostly in Fiori apps listed in the Fiori Apps Reference Library, built on CDS views. Many classic transactions such as VA05N and FBL3N also still work.

What is embedded analytics?

It is reporting that runs directly on live S/4HANA data through CDS-based analytical queries, so no separate data warehouse is needed for operational reports.

Can I still use classic SAP Query?

Yes, SQ01 and SQVI still work, but new reports are expected to be built on CDS views and Custom Analytical Queries.

What is Group Reporting in S/4HANA?

It is the consolidation component of S/4HANA Finance, used for intercompany eliminations and consolidated financial statements. It runs on consolidation data separate from local ledgers.

Related

How-to

SAP S/4HANA upgrade steps: a runbook for manufacturers

An S/4HANA move runs in phases: assess with the readiness check and simplification items, clean up and adapt custom code, plan the stack in Maintenance Planner, run the technical conversion or upgrade with SUM in a sandbox, test business processes, rehearse the cutover and go live. Most of the effort is in custom code, data and testing, not the tool.

Advanced

SAP S/4HANA API Documentation: Where It Is and How to Use It

S/4HANA API documentation lives on the SAP Business Accelerator Hub (api.sap.com), under the S/4HANA Cloud or S/4HANA on-premise package. Most APIs are OData (v2, and v4 for newer ones) plus SOAP for some integrations. In public cloud you authorize an external caller with communication arrangements; on-premise you activate the service in the Gateway and use basic, OAuth or certificate authentication.

How-to

SAP SE16N vs SQVI: Table Browser vs Ad Hoc Query

SE16N is a single-table browser: fast filtering, formatted display, and export from one table at a time, with an optional edit function for authorized users. SQVI (Quick Viewer) builds ad hoc queries that join multiple tables without writing ABAP, and can be saved as a reusable report. Use SE16N for a quick look at one table; use SQVI when you need data joined across two or more tables.

CIO briefing

SAP ECC 2027: what mid-size manufacturers should actually do

SAP's mainstream maintenance for ECC 6.0 ends in 2027, with extended maintenance available at additional cost typically through around 2030 depending on the specific agreement. Mid-size manufacturers have three real options: migrate to S/4HANA (on-prem or cloud) before 2027, pay for extended maintenance to buy 2-3 more years, or move off SAP entirely. With limited internal SAP resourcing, most mid-size manufacturers should already be past discovery and into a scoped S/4HANA conversion plan by now, or actively budgeting for extended maintenance as a deliberate bridge, not a default.

Error fix

SAP M7 021: Deficit of SL Stock Quantity

M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.

Error fix

SAP IDoc Status 51: Application Document Not Posted

Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.

AI for ERP

AI for SAP S/4HANA, Running On-Prem or in Your Private Cloud

Run AI on SAP S/4HANA without sending ERP data to a public API. On-prem and private-cloud architecture, CDS views, OData, and honest deployment trade-offs.

AI for ERP

SAP Joule or a Private LLM Beside SAP: An Honest Comparison

An honest comparison of SAP Joule and Business AI against a private, self-hosted LLM beside SAP: what each covers, where they overlap, and where CIOs run both.

Stuck on SAP S/4HANA?

Talk to engineers who work inside SAP S/4HANA every week, and who build private AI that answers these questions from your own ERP data.

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

Guides

AI on your ERP

Integrations

Comparisons

Software