Describing SAP Gateway

SAP Gateway originated in the need for mobile access to business data. Watch the video to understand what started this development.

Without a standard how to access business data in a mobile environment, development efforts were not transferable to other scenarios they were built for. Watch the video to see how OData took over this role and where SAP Gateway came into play.

The most important point is that the OData service forms a kind of contract between the non-SAP side and the SAP side, helping to bring together developers on both sides.

Based on Representational State Transfer (REST), OData provides compelling benefits for SAP application development, which include the following:

The tasks of SAP Gateway are split into a hub and back-end framework. This makes it possible to operate each framework in a separated system: A front-end server (FES) (also known as hub) and back-end server (BES). The systems communicate via RFC (Remote Function Call), which is the most efficient communication between ABAP systems. Such a deployment is called a hub deployment because of the FES acting as a hub for the BES(s).

Every Application Server (AS) ABAP since 7.40 provides both, the front-end and back-end framework, from scratch. So it is perfectly fine – and even recommended for SAP S/4HANA – to run both frameworks in the same system. Such a deployment is then called an embedded deployment.

SAP Fiori is the central user experience for the most broadly and frequently used SAP software functions (such as SAP S/4HANA) that can be accessed from mobile and desktop devices.

SAP Fiori offers the following key features and capabilities:

• SAP Fiori applications are designed for increased productivity, for example:
  • Tasks are pulled together in one view
  • A relevant context is provided, making it easier to make decisions on the spot
  • Gesturing for quick approvals is possible
  • Access to contact information is provided
• Applications can be assigned by specific roles so that users get only what they need
• Users can personalize the order of the applications
• Applications can be adapted and aligned to corporate branding
• Additional workflow scenarios are easily added
• Responsive design allows for the same application to be available for different form-factors

Let's see the SAP Fiori launchpad in action, the frame for running SAP Fiori apps. Keep in mind that all data shown in the apps and in the SAP Fiori launchpad itself are provided by SAP Gateway services:

SAP Multichannel Foundation for Utilities and Public Sector is a customer-facing solution based on SAP Gateway. It allows utility companies to interact with their customers through different communication channels, for example, the Web (online self-services), mobile, and social networks. SAP Multichannel Foundation for Utilities and Public Sector provides a set of standardized and reusable OData services that are used by end user applications to access data and processes from SAP Business Suite for Utilities, all on an attractive and adjustable HTML5 user interface and OData services layer.

The minimum release is IS-U 6.04 (EhP4) and CRM 7.0 (EhP0).

The core functions allow you to perform the following actions:

• Register for an account
• Observe a single view of interactions
• Update account and payment information
• Maintain communication preferences
• Enter meter reading
• View bills
• Sign up for a new product
• View contracts
• Submit and view inquiries

SAP Mobile Start was introduced in August 2021. It is a mobile application for Apple iOS and Google Android integrated with SAP S/4HANA and further SAP solutions, leveraging the SAP Business Technology Platform (BTP). The SAP Build Work Zone, Standard Edition, Notification Service, and Mobile Services of BTP work together to provide web sites and apps for mobile usage. SAP Mobile Start integrates with mobile operating system features like notifications, spotlight search, and widgets running on smartphones, watches, and tablets.

Let's see SAP Mobile Start in action:

The Mobile Development Toolkit (MDK) enables developers to quickly build mobile apps with a native look and feel in a visual and declarative way. The SAP Mobile Services provides the runtime whereas the SAP Business Application Studio (BAS) provides the development environment.

The generic client for running MDK apps on Apple iOS and Google Android is the SAP Mobile Services Client. It is the frame for running complex cross platform native apps such as field services or asset maintenance.

Let's see SAP Mobile Services Client in action: