10.1 SAP Fiori Sales Apps, Smart Business Monitoring, and Embedded Analytics

SAP Fiori Sales Apps, Smart Business Monitoring, and Embedded Analytics

For three decades, Order-to-Cash processing in SAP ERP Central Component (ECC) was defined by the monolithic SAP Graphical User Interface (SAP GUI). Customer service representatives, billing clerks, and shipping coordinators navigated dense dynpro screens through transaction codes like VA01, VA02, VL01N, and VF01. While powerful, this interface has a steep learning curve for occasional users.

In SAP S/4HANA, the commercial user experience has been completely transformed through the SAP Fiori design system. Moving far beyond cosmetic interface modernization, SAP Fiori introduces an insight-to-action operational paradigm where exception-based workbenches, stateful draft handling, and real-time embedded analytics replace manual report cross-referencing and transaction code hunting.

---

The UX Transformation: From SAP GUI Monoliths to SAP Fiori Launchpad

The SAP Fiori design paradigm is anchored on five principles: Role-Based, Adaptive, Simple, Coherent, and Delightful (section 10.2).

┌────────────────────────────────────────────────────────────────────────┐
│                     CLASSICAL SAP GUI (TRANSACTIONAL)                  │
│  • Monolithic Dynpro Screen (VA01 / VA02 / VF01)                       │
│  • Many fields and tabs on one screen                                  │
│  • One transaction per task, found by transaction code                 │
│  • Manual navigation to VA05 / V.02 / VKM1 to discover issues          │
└────────────────────────────────────────────────────────────────────────┘
                                    │
                                    ▼
┌────────────────────────────────────────────────────────────────────────┐
│                    MODERN SAP FIORI LAUNCHPAD (INSIGHT-TO-ACTION)      │
│  • Role-Based Workspaces (Internal Sales Rep, Billing Specialist)      │
│  • Draft Handling in Transactional Apps                                │
│  • Monitoring Apps: Track Sales Orders, Sales Order Fulfillment        │
│  • Real-Time Embedded Analytics via SAP HANA In-Memory CDS Views       │
└────────────────────────────────────────────────────────────────────────┘

Business Drivers of the Fiori Transformation

1. Role-Based Tailoring: Rather than exposing an internal sales representative to every master data field and financial configuration screen, Fiori provides curated apps containing only the fields, actions, and key performance indicators (KPIs) relevant to that specific job persona.
2. Adaptive Execution: Built on SAPUI5 (HTML5), most SAP Fiori apps adapt to desktop, tablet, and mobile screens.
3. Less Switching Between Transactions: In classic SAP GUI, resolving an order problem often meant switching between VA03 (order display), MM03 (material master), and MD04 (stock/requirements list). In SAP Fiori, contextual links and object pages connect these objects.

---

The Three SAP Fiori Application Typologies in S/4HANA Sales

Every application deployed on the SAP Fiori Launchpad belongs to one of three distinct architectural typologies, each serving a targeted operational purpose within the Order-to-Cash process.

1. Transactional Applications

• Functional Scope: Creating, changing, approving, and releasing business documents.
• Examples from the sales learning journey: Create Sales Orders, Manage Sales Orders, Create Outbound Deliveries From Sales Orders, Create Billing Documents - Billing Due List Items, Manage Billing Documents, and Manage Prices - Sales.
• Draft Handling: Many SAP Fiori transactional apps keep unsaved entries as a draft, so a user can interrupt the work and continue later instead of losing the entries as in a classic SAP GUI session.

2. Analytical Applications

• Functional Scope: Built on SAP Smart Business, these apps combine KPIs, charts, and flexible drill-downs.
• Example from the official course: Incoming Sales Orders, used to build multidimensional reports and to compare actual values with sales plans.
• Analytical Capabilities: Users drill down by dimensions such as sales organization, distribution channel, sold-to party, product, or period and navigate from a figure into the underlying documents.

3. Fact Sheet / Object Page Applications

• Functional Scope: Show one business object, such as a sales order, outbound delivery, billing document, or customer, with its key data, related documents, and status.
• Intent-Based Navigation (IBN): Object pages use semantic objects (for example SalesOrder or Customer) and actions (for example #SalesOrder-display), so a click on a document or customer number opens the related object page directly.

Fiori Sales Application Mapping Reference

---

SAP Smart Business: Monitoring and Analytical Apps in the Official Course

The S46000 course groups the sales monitoring and analysis tools under SAP Smart Business. The apps cover all core sales processes, from quotations and contracts through sales orders and their fulfillment to invoices, and they offer insight to action: from a KPI or an issue list you navigate directly into the business document. The course names two kinds of apps:

• Monitoring apps such as Track Sales Orders and Sales Order Fulfillment, to check whether an order was fulfilled and whether the related tasks were done on time.
• Analytical apps such as Incoming Sales Orders, to analyze the current sales situation and prepare forecasts.

Track Sales Orders

Track Sales Orders shows the fulfillment status of a sales order with a process flow and a tree structure of the order and its follow-on documents. From there, Track Sales Order Details visualizes the status of a specific order and its subsequent documents in more detail.

Sales Order Fulfillment

When an order cannot be processed, the Sales Order Fulfillment app lists all sales orders that are blocked for one or more reasons. According to the official course, it supports the user by highlighting the impediments, providing supporting information, and offering specific options to resolve the issues. This replaces the reactive work with classic lists such as VA05 or V.02.

                  Sales Order Fulfillment: typical issue types
   Incomplete data | Credit block | Delivery block | Billing block | Availability

Typical Issues the App Highlights

The app lists the blocked orders together with the reasons that stop them, for example:

1. Incomplete data: required fields such as payment terms, Incoterms, or a partner are missing (section 9.2).
2. Credit block: the order failed the credit check and waits for a credit decision.
3. Delivery block: a delivery block at header or schedule line level stops shipping (section 3.2).
4. Billing block: the order or delivery cannot be billed until the block is removed.
5. Availability: items are not confirmed, or not confirmed on the requested date (chapter 6).

For each issue, the app shows supporting information and offers options to resolve it, for example by navigating to the document to complete or release it. This is the insight to action idea of SAP Smart Business: the user moves from the list straight to the fix.

---

Analytical Apps and Embedded Analytics on CDS Views

In the analytical apps, sales representatives use key performance indicators and flexible drill-downs, from conversion rates of quotations and contracts to incoming orders, back orders, delivery performance, and sales volume. With sales plans they enter target values for dimensions such as sales employee or product category and compare them with actual data. Incoming Sales Orders, for example, builds multidimensional reports. Technically, these apps run on embedded analytics: CDS views that read the transactional tables directly instead of separate statistics tables such as the Logistics Information System (LIS).

┌────────────────────────────────────────────────────────────────────────┐
│                 LEGACY REPORTING (SAP ECC LIS ARCHITECTURE)            │
│  Transactional Tables (VBAK, VBAP)                                     │
│          │                                                             │
│          ▼ Asynchronous V2/V3 Statistical Updates                      │
│  LIS Info Structures: S001 (Customer), S002 (Sales Office), S004 (Matl)│
│          │                                                             │
│          ▼ Statistical setup when needed                               │
│  Reporting on separate statistics tables                               │
└────────────────────────────────────────────────────────────────────────┘

┌────────────────────────────────────────────────────────────────────────┐
│            MODERN REPORTING (S/4HANA EMBEDDED ANALYTICS)               │
│  Primary Source Tables: VBAK, VBAP, VBRK, VBRP, ACDOCA (In-Memory)     │
│          ▲                                                             │
│          │ Direct Live Execution (Zero Duplication)                    │
│  Basic CDS Interface Views: I_SalesOrder, I_SalesOrderItem             │
│          │                                                             │
│          ▼ Semantic Enrichment                                         │
│  Composite and cube views (sales order items)                          │
│          │                                                             │
│          ▼ OData Exposure                                              │
│  Consumption CDS Views (C_ prefix) exposed as OData services           │
│          │                                                             │
│          ▼ Displayed in the SAP Fiori app                              │
│  SAP Fiori Analytical Dashboards & Smart Business KPIs                 │
└────────────────────────────────────────────────────────────────────────┘

Why Embedded Analytics Replaces Statistics Tables

In SAP ECC, sales reporting relied heavily on the Logistics Information System (LIS): when a sales document was saved, a statistics update wrote aggregated figures into info structures such as S001 (customer) or S004 (material).

• The figures were redundant copies of the document data and could lag behind it when the update ran asynchronously.
• After changes to the update rules or data problems, the statistics had to be rebuilt with setup programs, for example OLI7, OLI8, and OLI9 for sales orders, deliveries, and billing documents.

The Virtual Data Model (VDM) over Core Data Services (CDS)

In SAP S/4HANA, the in-memory column store of SAP HANA can aggregate large volumes on the fly, so embedded analytics on CDS views is the recommended reporting approach for sales. The classic LIS is no longer the target architecture for operational reporting.

Instead, reporting is driven by Core Data Services (CDS) Views structured into a three-tier Virtual Data Model (VDM):

1. Basic / Interface Views (I_):
   • Examples: I_SalesOrder, I_SalesOrderItem, I_BillingDocument.
   • Mirror primary transactional tables (VBAK, VBAP, VBRK, VBRP), applying standardized business names, associations, and row-level authorization checks (DCL).
2. Composite and Cube Views:
   • Example: cube views that combine sales order items with their dimensions.
   • Combine business entities (joining orders, shipping points, customer master records, and profit centers) and define analytical dimensions and measures (such as Net Sales Value, Billed Quantity, Margin).
3. Consumption Views (C_):
   • Form the top layer of the VDM. They include analytical annotations (such as @Analytics.query: true) and expose OData services directly to SAP Fiori applications.

Benefits of S/4HANA Embedded Analytics

• Current data: Aggregations are calculated when the user opens the app, so reports reflect the documents as they are saved.
• No redundant statistics tables: Reporting reads the transactional data directly.
• Actionable Context: In Fiori analytical apps, users can click on any data bar or outlier and jump directly into the underlying transactional sales order to execute remediation.