Skip to content

Testing OData Destinations

You can test destination links for OData applications from the Connections window, via a test wizard.

The destination's SSO Basic Authentication must be configured with a technical user. If the icon does not appear, the OData application destination may not be configured correctly, or may not be supported for the SSO method used.

This test tool enables an Admin User to verify an OData service, and provides a way to browse metadata information and preview back-end data.

If you do not see the OData application test destination icon, or it is grayed out, it may indicate that testing is not supported for the destination.

If Allowed Paths is enabled for the destination, you are prompted to select one of the paths.

  1. In SAP mobile service cockpit, select Mobile Applications > Native/MDK.

  2. Select an application, navigate to the Settings tab, and select Connectivity.

  3. Under Actions, click the OData application test destination icon show-edit .

    If Allowed Paths is enabled, select one of the options from the Relative OData Service Path list, and select Get Data. If connected, the data appears in the Entity Data section. If not connected, "No data is being received from the server" appears instead.

  4. View the basic information about the application and destination. You can enter the relative OData path of the destination URL, and check the OData metadata definition.

  5. View the OData service entities, the properties and data of the entities; and the JSON raw data and XML raw data of each entity.

Testing OData Destination Quality

OData destination quality testing ensures data accuracy and reliability. It is essential for ensuring that OData connections are functioning properly and delivering high-quality data for use in various applications and systems.

The Offline Access feature must be enabled for the application.

OData quality refers to how well an OData service is supported by the Mobile Offline Access feature. A new browser tab launches to perform the OData quality check and display the results.

Note

You may find it useful to enable the Allow Omitting Max Length property in the application configuration file. When enabled, no maximum length is imposed. For more information, see Step 4: Endpoint Properties in the Editing the Application Configuration File.

It is not possible for OData quality checks to identify issues that could only be detected through Create, Update, Delete (CUD) operations. This limitation may be revisited once the new feature, Dry-run of data modification requests, is implemented in OData V4.02.

  1. In SAP mobile service cockpit, select Mobile Applications > Native/MDK.

  2. Select an application, navigate to the Settings tab, and select Connectivity.

  3. In the Actions column, choose the OData Destination Quality Test. This launches a new browser tab, using a modified destination URL.

  4. In the Welcome screen, log in using your SAP ID user name and password.

    After you have logged in, the OData Quality Check Results screen appears in the browser window. On this screen, the Check OData Quality progress bar displays details about ongoing checks, including:

    • Metadata Check

    • Service Doc Check

    • Schema Creation Check

    • Data Check

    Once the checks are completed, choose Close to continue.

    Note

    • If you check the browser URL, you will see that the URL has changed and ?auth=uaa has been appended. This indicates that the destination was tested through the app-router.

    • If an entity set is marked as "sap:addressable=false", it should not be checked in OData Checker.

  5. In the OData Quality Check Results, you can review the quality check results and recommendations for the selected application.

    Quality Check Properties

    Property Description
    Code An identifier for reference.
    Severity The impact of the condition (High, Medium, Low - are color-coded for clarity). High-severity issues prevent offline synchronization when using the reported entity set. Medium and Low-severity issues only affect performance.
    Description A detailed explanation of the issue.
    Solution Additional information about what needs to be done by the administrator or developer to resolve the issue. This could involve making adjustments to the back end, the offline configuration, and so forth.
    References Provides links to all the relevant documentation, help, notes, and so forth.

    To download the test results in CSV format, choose Download.

Pinging a Destination

Test whether a destination is accessible.

Keep in mind that the ping option is not available for SAP Destination Service, or for some SSO methods, such as OAuth2 User Token Exchange, Cloud Connector SSO, and Forward Authentication. One exception is that if Forward Authentication is used in combination with endpoint address names that end with /SampleServices/ESPM.svc/v2 or /SampleServices/ESPM.svc/v4, the ping test is available. If you do not see the ping icon, or it is grayed out, ping is not supported for the destination.

  1. In SAP mobile service cockpit, select Mobile Applications > Native/MDK.

  2. Select an application, navigate to the Settings tab, and select Connectivity.

  3. Select a destination and click Ping.

    You see either:

    • Ping Successful – connection is accessible.

    • Ping Failed – connection is not accessible. Click Show Details to see more information.

Testing Destinations in a Browser

You can test destination connectivity for all authentication types and for OData applications from a web browser.

In this scenario, a new browser tab is launched using the mobile application URL, the same URL that the application uses to interact with the destination. The URL is modified (the parameter, ?auth=uaa, is appended), and the request is routed through AppRouter. This is the same way that a mobile application that is used by an end user interacts with the destination.

If Allowed Paths is enabled for the destination, you are prompted to select one of the paths.

  1. In SAP mobile service cockpit, select Mobile Applications > Native/MDK.

  2. Select an application, navigate to the Settings tab, and select Connectivity.

  3. Select a destination and click popup-window . If Allowed Paths is enabled for the destination, the tool tip indicates "Launch Allowed Path in Browser"; otherwise the tool tip indicates "Launch in Browser". This launches a new browser tab, using a modified destination URL.

  4. In the Welcome screen, log in using your SAP ID user name and password.

    Upon successful authentication, the destination's data appears in the browser window. You can retrieve entity data.

    Note

    If you check the browser URL, you will see that the URL has been changed and ?auth=uaa has been appended. This indicates the destination was tested through the AppRouter.

  5. Close the web browser window when ready.

Last update: July 3, 2025