Transactional Apps
Let users perform essential tasks such as travel requests and employee leave on supported mobile and desktop experiences. Other scenarios depend on the relevant back end and application.
Role-based mobile experience
SAP Fiori®: Elevating User Experience
SAP Fiori is a suite of applications and design patterns intended to provide a modern, engaging user experience for key SAP processes across supported desktop and mobile devices.
Fiori can act as a unified access point for relevant SAP functions, helping teams streamline interactions around the role and task. Productivity, usability, access, and performance depend on the chosen applications, process design, data, services, devices, security, connectivity, accessibility, and operating model.
Fiori application patterns
Fiori App Categories
Fiori applications are commonly organized into three established categories. Exact availability and technical prerequisites should be verified for the organization’s SAP release and landscape.
Factsheets
Give authorized users quick access to critical business information or statistics about specific objects without requiring every traditional SAP GUI navigation path or transaction code.
Analytical Apps
Support analysis of approved datasets and current business conditions through connected SAP information. Actionable insight and real-time behavior depend on data quality, semantics, integration, architecture, and responsible interpretation.
Legacy integration context
HANA Cloud Integration (HCI)
HANA Cloud Integration is historical product terminology. Current SAP integration products, capabilities, licensing, and transition paths must be verified before using this legacy architecture in a new design.
HCI addressed integration between cloud and on-premise platforms. The enduring requirement is to connect applications and data through governed interfaces that address security, semantics, monitoring, error handling, reconciliation, release change, and accountable support.
Key Features of HCI
Unified Integration
Connect approved cloud and non-cloud platforms through an integration model that supports controlled data exchange and process alignment.
SaaS Model
Evaluate software-as-a-service integration against infrastructure responsibility, subscription scope, security, connectivity, environments, observability, scale, cost, and support instead of assuming automatic savings.
Streamlined Processes
Use integration to improve data flow across systems while preserving business rules, approvals, controls, exception routing, reconciliation, and process ownership.
Legacy mobile platform
SAP Mobile Platform (SMP)
SAP Mobile Platform, formerly associated with Sybase Unwired Platform, supported B2B, B2E, and B2C mobile application development. SMP 3.0 components should be assessed for current use, supportability, security, dependencies, and modernization options rather than treated as a recommended new platform.
Key Components of SMP 3.0
Syclo Agentry
Historical tooling for designing, deploying, and managing mobile application lifecycles and complex workflows. Confirm active applications, back-end dependencies, client support, and transition requirements.
SAP Management Cockpit
Administrative context for deploying, managing, and monitoring native, hybrid, and Agentry applications. Verify which operational functions remain active and who owns them.
SMS Toolkit
Historical support for short-message-service mobile applications. Validate any remaining communication workflows, providers, security, consent, records, and replacement needs.
Integration Gateway
Legacy gateway context for converting supported back-end sources such as SOAP services, JPA, or JDBC data into OData. Confirm current interfaces, data contracts, security, monitoring, and target architecture.
Plan SAP mobility