> ## Documentation Index > Fetch the complete documentation index at: https://docs.germainux.com/llms.txt > Use this file to discover all available pages before exploring further. # KPIs for SAP > GermainUX provides KPIs for monitoring the user experience, performance, errors, business processes, and availability of SAP applications. Components [`Agent`](https://docs.germainux.com/main/germainux-agent) [`Engine`](https://docs.germainux.com/main/germain-ux-engine) [`JS Profiler`](https://docs.germainux.com/main/germain-ux-js-profiler) [`Mobile App`](https://docs.germainux.com/main/germain-ux-mobile-app) [`RPA Bot Recorder`](https://docs.germainux.com/main/germain-ux-rpa-bot-recorder) [`RUM Windows`](https://docs.germainux.com/main/germainux-rum-windows) Availability 2026.2 or later > [card] [User-Experience KPIs](#user-experience-kpis) > > Segment by role and page > [card] [Business-Process KPIs](#business-process-kpis) > > Monitor login and order flows > [card] [Infrastructure KPIs](#infrastructure-kpis) > > Correlate infrastructure with users > [card] [Components](#components) > > Collection methods for SAP ## Overview GermainUX provides KPIs for monitoring the user experience, performance, errors, business processes, and availability of SAP applications. The available KPIs depend on the deployed GermainUX components and configured data sources. Monitoring can cover: * SAP Fiori * SAPUI5 * SAP Web GUI * SAP portals and custom web applications * SAP Commerce Cloud * APIs and integrations > [accordion] Show all 9 > > * Application logs > * Hosts, services, processes, and databases > * Synthetic user scenarios GermainUX does not natively profile ABAP code. SAP backend metrics and diagnostics are available only when collected through an accessible log, API, database, file, or custom integration. ## User-Experience KPIs These KPIs are collected from compatible browser-based SAP applications using GermainUX RUM JS. | KPI | Description | | - | - | | User Session | Captures the duration, activity, and context of a user session | | User Session Replay | Reconstructs captured user activity for investigation | | Page View | Records pages, routes, or application views visited | | User Click | Captures user interactions with links, buttons, and other controls | | User Action | Measures configured user interactions and their duration | | Browser Event | Captures browser events affecting the user experience | | JavaScript Console Event | Records configured JavaScript errors and console messages | | Outbound HTTP Request | Measures browser requests, response time, and status | | Resource Load | Measures the loading of scripts, stylesheets, images, and other resources | | User Feedback | Captures user ratings, comments, and related session context | These KPIs can be segmented by application, environment, user, role, page, browser, device, location, release, or other configured attributes. ## Performance KPIs Common performance measurements include: * Page and view load time * User-action duration * Network-request duration * Resource-load duration * Business-process duration * Individual process-step duration > [accordion] Show all 9 > > * API and integration response time > * Synthetic transaction duration > * Server, service, and database response time Analyze averages together with percentiles and affected-user counts. Averages alone can hide severe performance problems experienced by a smaller group of users. ## Error KPIs GermainUX can monitor errors visible through the configured data sources, including: * JavaScript errors * Browser console errors * Failed resources * HTTP errors * Network timeouts * Functional errors returned with HTTP success statuses > [accordion] Show all 11 > > * Visible application error messages > * Failed business-process steps > * API and integration failures > * Application-log errors > * Synthetic transaction failures Errors can be categorized by type, severity, application, process, message, user impact, and recurrence. ## Business-Process KPIs GermainUX can monitor SAP business processes when their steps are observable through browser activity, application events, logs, APIs, or synthetic scenarios. | KPI | Description | | - | - | | Process Started | Number of process instances initiated | | Process Completed | Number of successfully completed processes | | Process Failed | Number of processes ending in failure | | Process Abandoned | Number of processes started but not completed | | Completion Rate | Percentage of initiated processes completed | | Failure Rate | Percentage of process instances that failed | | Abandonment Rate | Percentage of process instances abandoned | | Process Duration | End-to-end execution time | | Step Duration | Time spent on an individual process step | | Lost Productivity | Time associated with errors, delays, repetition, or inefficient execution | | Process Overrun | Additional time above the expected process duration | Examples include login, order creation, approvals, customer-service workflows, purchase-to-pay activities, and SAP Commerce Cloud checkout. ## SAP Commerce Cloud KPIs For SAP Commerce Cloud, formerly SAP Hybris, GermainUX can monitor the complete digital customer journey. ### Product discovery * Product searches * No-result searches * Product-list views * Product-detail views * Search response time * Product-selection activity ### Cart and checkout * Add-to-cart events * Remove-from-cart events * Cart updates * Checkout starts * Checkout-step completion * Checkout errors > [accordion] Show all 9 > > * Cart abandonment > * Checkout abandonment > * Checkout duration ### Conversion * Confirmed orders * Conversion rate * Funnel completion * Drop-off by journey stage * Conversion by device, browser, region, campaign, or customer segment * Revenue and order value when authoritative transaction data is integrated Use server-side order data as the authoritative source for confirmed orders and revenue. Browser events provide evidence about the customer journey but may not confirm that a transaction was finalized. ### Commerce experience * Storefront performance * JavaScript and browser errors * Failed network requests * Third-party service failures * Customer feedback * Frustration indicators * Synthetic browse, login, cart, and checkout success ## Synthetic-Monitoring KPIs GermainUX RPA bots can continuously validate critical SAP transactions. | KPI | Description | | - | - | | Scenario Availability | Whether the complete scenario succeeded | | Scenario Duration | End-to-end execution time | | Step Duration | Time required for each recorded step | | Scenario Failure | Failed validation, action, or expected result | | Error Message | Application or execution error encountered by the bot | | Execution Location | Engine or location from which the scenario ran | Synthetic monitoring detects issues even when no real users are active. ## Application and Integration KPIs The GermainUX Engine can collect application and integration KPIs from accessible interfaces, including: * Endpoint availability * HTTP response time and status * Request and transaction volume * Timeout and retry volume * API failure rate * Application-log error volume > [accordion] Show all 10 > > * Queue depth or backlog > * Scheduled-job duration and status > * Service and process availability > * Database connectivity and response time The exact KPIs depend on the SAP architecture and configured integrations. ## Infrastructure KPIs Where the required access is available, GermainUX can monitor: * CPU utilization * Memory utilization * Disk and filesystem utilization * Host availability * Process and service state * Network response time > [accordion] Show all 9 > > * Database performance > * Connection utilization > * Server and container health Infrastructure KPIs can be correlated with user activity, application errors, synthetic failures, and business-process performance. ## Recommended KPI Views Configure dashboards for: * SAP user experience * Errors affecting users * Application and integration performance * Business-process effectiveness * SAP Commerce Cloud conversion * Synthetic availability * Infrastructure health For each KPI, consider displaying: * Count * Average * Median * Percentiles * Minimum and maximum * Error or success rate > [accordion] Show all 11 > > * Unique users > * Affected sessions > * Trend compared with the previous period > * Deviation from a baseline > * Breakdown by relevant dimensions ## Alerts and Reports Configure SLAs and alerts for important conditions such as: * Application unavailability * Increased error rate * Slow user actions * API or integration failure * Failed business processes * SAP Commerce Cloud checkout failures > [accordion] Show all 9 > > * Conversion decline > * Synthetic transaction failure > * Host, service, or database degradation Scheduled reports can summarize KPI values, trends, affected users, business impact, and changes compared with the previous period. ## Components SAP KPIs can be collected using: * GermainUX [RUM JS](https://docs.germainux.com/main/germain-ux-rum-js.md) * GermainUX [JS Profiler](https://docs.germainux.com/main/germain-ux-js-profiler.md) * GermainUX [Engine](https://docs.germainux.com/main/germain-ux-engine.md) * GermainUX [RPA Bot Recorder](https://docs.germainux.com/main/germain-ux-rpa-bot-recorder.md) * GermainUX [Code Profiler](https://docs.germainux.com/main/germain-ux-code-profiler.md) for supported customer-controlled Java services * [Custom data-source](https://docs.germainux.com/main/other-plugins.md) integrations ## Additional Resources > [card] [Pivot and Measures for SAP KPIs](https://docs.germainux.com/main/kpis.md) > > Read more > [card] [Create your KPIs](https://docs.germainux.com/main/manage-kpis.md) > > Read more ## Get Help > [card] [Contact GermainUX Support](https://docs.germainux.com/main/support.md) > > The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes. > [card] Can't find what you need? > > Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing. The content of this document is proprietary to GERMAIN SOFTWARE. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.