OData Source: How-to guides
This section covers the most common OData Source tasks. Each guide is self-contained, but they follow a natural sequence: setting up a source, finding a service, and then building an app against it.
For the background on the concepts behind these tasks, see OData Source. For a complete field reference, see OData Source configuration reference.
Set up a new OData Source
How you create an OData Source depends on where the target service lives relative to your Neptune DXP - SAP Edition system.
Same-system service
Use this when the OData service, for example, an SAP Gateway or RAP service, runs on the same ABAP system as Neptune DXP - SAP Edition. No proxy configuration is required, and the setup is minimal.
Remote system via HTTP Destination
Use this when the OData service runs on a different system, for example, a remote SAP system, SAP BTP, or an external API. This approach uses an SM59 HTTP Destination to store the target host and credentials securely in the ABAP system, and is the recommended method for all productive remote connections.
Find and select a service
Once you have defined a destination, you can use the value help on the Service URL field to query the target system’s OData catalog and select a service interactively, rather than entering the URL manually. This applies to both same-system and remote HTTP Destination setups.
Use an OData Source in an app
After you have configured and saved an OData Source, reference it in the App Designer by attaching an OData model to your app’s resources and binding UI controls to entity sets.
End-to-end walkthrough example
See the configurations come together in a complete walkthrough: from creating an OData Source for the public Northwind OData V4 service, through configuring proxy and authentication settings, to building and running a table app that displays live data — without writing a single line of code.
A useful reference if you are new to OData Sources or want to see all the moving parts in context.