OData Source configuration reference

This page describes every field in the OData Source configuration dialog. For conceptual background, see OData Source. For step-by-step procedures, see OData Source: How-to Guides.

General

Name

Unique identifier for this OData Source within the system. Apps in the App Designer reference the OData Source by this name. Choose a name that makes the target service and system identifiable at a glance (for example, S4_PURCHASE_ORDERS_V2).

Description

Free-text description of the OData Source and the service it connects to. Use this to record the purpose, the target system, and any notes relevant to other developers or administrators.

Package

Optional ABAP package assignment.

Assigning a package is recommended when the OData Source is part of a transported development object set.
OData Sources are not transported via standard TMS transports. They are deployed using Deployment → Export and Deployment → Import in the Cockpit.

Connection

Enable Proxy

Enables the Neptune server-side proxy for this OData Source. Enable this setting whenever the target OData service is on a different host than Neptune DXP - SAP Edition to prevent Cross-Origin Resource Sharing (CORS) errors in the browser.

Leave this disabled for same-system calls (for example, SAP Gateway or RAP services on the local ABAP system).

Proxy Version

Selects the proxy implementation to use. This field is only relevant when Enable Proxy is active.

Version Description

Version 1

Retained for backward compatibility with OData Sources created before Neptune DXP - SAP Edition 24.

Deprecated — do not use for new OData Source entries.

Limitations:

  • No OData V4 support

  • No update support for OData V2 sources

  • No special handling of SAP session cookies

Version 2

Current implementation. Use this for all new OData Sources.

Capabilities:

  • OData V2 and V4 support

  • Enhanced stability

  • URL query string pass-through

  • Improved CSRF handling

  • Compatibility with SAP and non-SAP systems

  • Session-less operation on SAP on-premise and SAP Rise

  • Extensibility via custom proxy classes
OData Version

Specifies the OData protocol version of the target service.

  • V2 — for classic SAP Gateway and older ABAP OData services.

  • V4 — for RAP-based services, modern SAP APIs, and third-party OData V4 services. Requires Proxy Version 2.

Service URL

The path or full URL of the OData service endpoint.

  • For same-system services (no proxy) or services accessed via an HTTP Destination, enter the relative path only. Do not include the hostname.

    Example: /sap/opu/odata4/iwbep/all/cdi_cds/sap/i_purchasingdocumentstatustext/0001/

  • For external services accessed without an HTTP Destination, include the full URL with protocol, hostname, and port.

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

    Value help: When the destination is fully defined (proxy disabled, or Authentication Type set to HTTP Destination), you can select the value help icon to browse the target system’s OData catalog and select a service interactively. The catalog returns services matching the selected OData Version.

    Static query parameters (Proxy Version 2 only): Query parameters appended to the Service URL are included in every request made through the proxy.

Proxy Version 2 settings

These fields are visible only when Enable Proxy is active and Proxy Version is set to Version 2.

No CSRF handling

Disables the automatic CSRF token fetch that Proxy Version 2 performs before write operations.

Enable this flag for services that do not implement a CSRF token endpoint, as the preflight request will otherwise produce an error.
Authentication Type

Determines how Neptune authenticates to the target system.

Option Description

No Authentication

No credentials are sent. Use for publicly accessible services.

HTTP Destination (recommended)

Connection parameters and credentials are read from an SM59 entry of connection type G. This is the recommended approach for all productive remote system connections. See How to connect to a remote system via HTTP Destination.

Basic Authentication

A username and password are stored directly in the OData Source record. Convenient for prototyping; not recommended for productive use.
HTTP Destination
Visible when Authentication Type is HTTP Destination.

The SM59 RFC Destination entry to use for this connection. Use the value help to search for and select an available destination.

Disable SAML2 / Disable OIDC

When the target system is configured to enforce SAML2 or OIDC authentication, enabling these checkboxes instructs Neptune to bypass those mechanisms and use the basic credentials stored in the SM59 entry instead.

Username / Password
Visible when Authentication Type is Basic Authentication.

Login credentials for the target OData service. Stored in the OData Source record.

Destination System Type

Controls how the proxy handles HTTP headers for the target system.

Option Description

Backend SAP System (On Premise/Rise)

Adds SAP-specific HTTP headers to suppress unnecessary SAP session creation.

Use this for any SAP on-premise or SAP Rise system.

Other

No special header or cookie handling.

Use this for non-SAP targets.
SAP Cloud Destination

The name of an SAP BTP destination to use when an app built with this OData Source is exported and deployed to SAP BTP. On SAP BTP, this field is used in place of the Service URL field.

Custom Proxy Class Name

Allows a custom ABAP class to intercept and manipulate proxy requests and responses at the backend.

Use this field only when standard proxy behavior is insufficient, for example, to work around non-standard service behavior (see the Northwind example in How-to Guides).

Requirements for the custom class:

  • Must implement the interface /NEPTUNE/IF_PROXY_HANDLER.

  • Inheriting from /NEPTUNE/CL_PROXY_ODATA is recommended; it provides the default OData proxy logic and the interface implementation, so you only need to override the specific behavior you want to change.

    Custom proxy classes may require adjustment during Neptune DXP upgrades. Use this option only when necessary.

    Neptune ships the following example class:

    Class Purpose

    /NEPTUNE/CL_PROXY_ODATA_NORV4

    Strips the non-standard trailing semicolon from the OData-Version response header returned by the public Northwind V4 demo service.

Related topics