Skip to content

Release Notes

This document contains the release notes for Mobile Transaction Bridge. It describes added or changed features for recording and consumption scenarios.

Version 1.3.4

Version 1.3.4 new features:

Version 1.3.3

Version 1.3.3 new features:

  • Support integration into SAP Work Zone

  • Added export functionality for Preflight Check

  • Improved recorder functionality

Version 1.3.2

Version 1.3.2 new features:

  • Support window title of modals (MODAL_WINDOW) as output

  • Improved recorder state handling

  • Improved runtime handling

Version 1.3.1

Version 1.3.1 new features:

  • Preflight Check

  • Improved UI handling in Recorder

  • Improved table paging support

Version 1.3

Version 1.3 new features:

  • /v2 API

  • Recording version handling

  • Recording export functionality

  • Support text box (SAPGUI.TextEditCtrl.1) controls as input and output

  • Improved column name configuration handling

  • Improved recording draft handling

  • Improved table paging support

  • Improved date and time parsing handling

Version 1.2 (Restricted BETA)

Version 1.2 new features:

  • Support for table paging (Skip and Top)

  • Support for table row input

  • Support for TABLEVIEW controls as output

  • Improved replay functionality for design time

  • Improved range-request handling

  • Support for multi-value inputs and single criteria options

Version 1.1 (Restricted BETA)

Version 1.1 new features:

  • New dedicated connector interface for design time

  • New dedicated runtime interface for consumption of OData services

  • Improved support for multiple selection in F4 Help controls

Version 1.0 (Restricted BETA)

Version 1.0 is the initial release of SAP Mobile Transaction Bridge.

Prerequisites SAP GUI for HTML

Main Features

Recommendations & Restrictions

SAP Transactions can be very complex and SAP GUI for HTML can have a multitude of controls. The main goal of SAP Mobile Transaction Bridge is to enable extraction of parts of the SAP Transactions, with a small number of parameters for easy consumption via OData. The full complexity of SAP GUI for HTML cannot be translated to OData in a meaningful way.

Here a few recommendations for starting with SAP Mobile Transaction Bridge:

  • Create your first recordings on simple SAP Transactions, e.g. User Maintenance (SU01)

  • Decide what needs to be recorded from the perspective of the OData service consumer (and not from the perspective of SAP GUI for HTML)

    • Choose a meaningful set of input parameters and a meaningful return values for each recording

    • The semantic of a recording has to be clear and relevant for the consumer of the OData service

  • Decide carefully how the navigation tree should look like (dependencies between recorded flows)

    • There must be at least one recording starting at the beginning of the transaction

    • Every recorded flow must be reachable

      • Either it starts at the beginning of the SAP Transaction

      • Or there are other recorded flows leading to it

  • Do not make assumptions on user specific settings, for example initial selected TAB

    • The SAP GUI for HTML saves the last selected TAB for every user

    • If the recording expects the user to be on a specific TAB, the consumption of the recording fails when the user will be on a different tab

    • Solution for this is to navigate to the intended TAB explicitly as part of a recording


Last update: September 30, 2020