End-to-end example: Northwind V4 demo service

This example walks through the full configuration process, from creating an OData Source for the publicly available Northwind OData V4 demo service, to configuring proxy and authentication settings, to building and running a table app that displays live customer data — without writing a single line of code.

It is a useful reference if you are new to OData Sources, want to try things out in a safe environment, or want to see all the configuration decisions in a single connected context.

The Northwind service also introduces two configuration details that you may encounter with other non-standard services:

disabling CSRF handling
using a custom proxy class

Prerequisites

You have Internet access from the Neptune application server to services.odata.org.

Procedure

Part 1 - Create the OData Source

In the Cockpit, go to Connectivity → OData Source and select Create.
Enter a name, for example, NORTHWIND_V4, and select Create OData Source.
Enter a Description.
Optionally, assign a Package.

OData Sources are deployed between landscapes via Deployment → Export and Deployment → Import, not by TMS transports.
Select Enable Proxy.

The Northwind service is an external host. Without the proxy, the browser would block the request due to CORS restrictions.
Leave Proxy Version at Version 2.

Enable No CSRF handling.

The Northwind service does not implement a CSRF token endpoint. Leaving CSRF handling active causes a failed preflight request before every write operation. Because this is a read-only demo, it is safe to disable it here; apply the same setting to any other service that does not support CSRF.

Set Authentication Type to No Authentication.

The Northwind service is publicly accessible and requires no credentials.
Set Destination System Type to Other.

Northwind is not an SAP system, so no SAP-specific session handling is needed.
Set OData Version to V4.

In Service URL, enter:

https://services.odata.org/v4/northwind/northwind.svc/

Select Save, then select Display Metadata.

If the metadata document loads successfully, proceed to Part 2.

If you receive the following error, continue with the next step before proceeding:
```
Error: Expected 'OData-Version' header with value '4.0' but received value '4.0;'
```
Why this error occurs

The Northwind service appends a non-standard trailing semicolon to its OData-Version response header. SAPUI5 strictly validates this header and rejects the response when the value is 4.0; instead of 4.0. Neptune ships a sample custom proxy class (/NEPTUNE/CL_PROXY_ODATA_NORV4) that intercepts the response and strips the semicolon before it reaches the app. This is the intended use case for Custom Proxy Class Name: correcting minor deviations from the OData standard in services you do not control.
In Custom Proxy Class Name, enter:
```
/NEPTUNE/CL_PROXY_ODATA_NORV4
```
Select Save and select Display Metadata again to confirm the metadata now loads without error.

Part 2 - Build a table app in App Designer

Build a table app in the App Designer by following the instructions in Use an OData Source in the App Designer.

Result

You have connected Neptune DXP - SAP Edition to an external OData V4 service and built a working data display app with no code required.

The same sequence of decisions (proxy on, CSRF off or on, authentication type, destination system type) applies to any other external OData service; the Northwind walkthrough above makes each choice explicit and explains why.