Connect to a remote system via HTTP Destination

Use this procedure when the OData service runs on a different system, for example, a remote SAP system, SAP BTP, or an external API.

The HTTP Destination approach stores the target host, port, protocol, and login credentials in an SM59 entry of connection type G. This keeps credentials in the ABAP system rather than in the OData Source record itself, and is the recommended method for all productive remote connections.

For same-system services on the local ABAP system, see Create an OData Source for a same-system service instead.

Prerequisites

  • You have access to transaction SM59 in the target ABAP system.

  • You have the hostname, port, and login credentials for the remote OData service.

Procedure

Step 1 — Create an SM59 HTTP Destination

SM59 entries are system-local and must be maintained separately in each landscape: development, QA, and production.

  1. Open transaction SM59.

  2. Select Create.

  3. Set Connection Type to G - HTTP Connection to External Server.

  4. In RFC Destination, enter meaningful technical name, for example, S4IDES_ODATA_TEST. This is the name you will select from the Cockpit. In Description, enter a plain-text description of the target system and purpose.

    odata source remote connection type

  5. On the Technical Settings tab, enter the following:

    Field Value

    Target Host

    The hostname only — do not include the protocol prefix. Example: <my-s4-system.example.com>

    Service No.

    TCP port of the target service. Typically 443 for HTTPS.

  6. Switch to the Logon & Security tab:

    • Enter the User and Password for the target system, or configure ticket-based authentication if applicable.

    • Set SSL to Active for HTTPS connections.

      odata source remote active

  7. Save the SM59 entry.

Step 2 — Create the OData Source in Neptune Cockpit

  1. In the Cockpit, go to Connectivity → OData Source.

  2. Select Create.

  3. Enter a unique name and select Create OData Source.

  4. Enter an optional Description and Package assignment.

  5. In the Connection section, select Enable Proxy.

  6. Leave Proxy Version at Version 2. This is the default and the recommended setting for all new OData Sources.

  7. Set Authentication Type to HTTP Destination.

    odata source remote http destination

    Result: A new HTTP Destination (SM59) field appears.

  8. Select the value help icon in the HTTP Destination (SM59) field.

    odata source remote value help

    Enter a search term if needed, select Search, and select the SM59 entry created in Step 1. Select OK.

    odata source remote value help search

  9. If the target system enforces SAML2 or OIDC authentication, and you need to override this with the SM59 basic credentials, enable Disable SAML2 (force Basic Auth.) and/or Disable OIDC (force Basic Auth.) as appropriate.

  10. Set Destination System Type:

    • Backend SAP System (On Premise/Rise): for any SAP on-premise or SAP Rise system.

    • Other: for non-SAP targets.

  11. Set OData Version to V2 or V4 to match the target service.

    odata source remote odata version

  12. In the Service URL field, either:

  13. Select Save.

  14. Select Display Metadata to verify that the connection is established and the service metadata document loads correctly.

Result

  • The OData Source is configured to route requests through the Neptune proxy using the SM59 destination for host resolution and authentication. The metadata display confirms end-to-end connectivity.

    OData Sources are not transported via TMS transports. Use Deployment → Export and Deployment → Import in the Cockpit to move OData Sources between system landscapes.

Next steps

Related topics