Documentation Index

Fetch the complete documentation index at: https://docs.dataddo.com/llms.txt

Use this file to discover all available pages before exploring further.

SAP S4/Hana

Prev Next

SAP S/4HANA is SAP's ERP suite for large enterprises, covering finance, sales, procurement, manufacturing, and supply chain processes. The Dataddo SAP S/4HANA connector extracts data from your S/4HANA system through its OData services, which are generated from CDS (Core Data Services) views. This lets you replicate business objects - sales orders, deliveries, materials, financial documents, and any other CDS view you expose - into your destination of choice.

The connector supports both full-table replication and incremental (change-tracking) extraction, so you can sync only the records that changed since the last successful run.

Prerequisites

This step is mandatory. Until the ABAP scripts are deployed, the connector cannot list or extract any data.

Before you can create a connection, the Dataddo ABAP scripts that define the required CDS views must be deployed to your SAP S/4HANA system. These scripts:

  • Create the CDS views you want to extract.
  • Register a catalog service that lets Dataddo discover which CDS views are exposed as active OData services.

The scripts will be provided by your Dataddo Account Manager.

You will also need:

  • The hostname of your SAP S/4HANA system (without the protocol, e.g. myserver.company.com).
  • A username and password of a service user that has authorization to read the relevant OData services. We recommend a dedicated technical/service user rather than a personal account.

Authorize Connection to SAP S/4HANA

The connector authenticates to the OData services using HTTP Basic authentication.

In SAP S/4HANA

  1. Make sure the Dataddo ABAP scripts (see Prerequisites) are deployed and the CDS views are activated as OData services.
  2. Confirm that the service user you intend to use has read authorization for those OData services.

In Dataddo

  1. Go to the Authorizers page and click Add new Service.
  2. Select SAP S/4HANA from the list.
  3. Fill in the form:
    • Label - a name to help you recognize this connection later.
    • Server IP or Hostname - the hostname of your SAP S/4HANA system, without the protocol (e.g. myserver.company.com).
    • Username - the service user for HTTP Basic authentication.
    • Password - the password for that user.
  4. Click Save. Dataddo verifies the credentials by calling the catalog service.
DATADDO TIP

If saving fails, the most common causes are an incorrect hostname, a user without authorization for the OData services, or the ABAP scripts not yet being deployed. See Troubleshooting.

How to Create a SAP S/4HANA Data Source

  1. On the Sources page, click Create Source and select the SAP S/4HANA connector.
  2. Connection
    • Select the SAP S/4HANA authorization you created above.
  3. Data selection
    • Data source name - a name for your new data source.
    • CDS View - select the CDS view (OData entity) you want to extract. The list is populated from the views your ABAP scripts exposed as active OData services.
    • Columns - choose the specific columns to extract from the selected view. Select as many as you need.
    • Change Tracking Column (optional) - see Incremental Loading below.
  4. (Optional) Adjust the snapshotting / date range settings.
  5. Preview the data to confirm it looks correct, then click Save.

Congratulations, your new data source is ready!

Didn't find your CDS view?

Only CDS views that are exposed as active OData services appear in the dropdown. If a view is missing, verify that its OData service is activated in SAP and that your service user can access it.

Incremental Loading (Change Tracking Column)

To extract only records that changed since the last successful run, select a Change Tracking Column when creating the source.

  • The dropdown lists only the columns that SAP exposes as interval filters on the selected CDS view - typically a timestamp such as the last-changed date/time of the row.
  • During each sync, Dataddo applies a time-based filter on this column so that only rows newer than the last successful run are extracted.
  • Leave the field empty to perform a full extraction of the view on every run.

You can perform a complete refresh of your data at any time using the Full Data Resync feature.

DATADDO TIP: Time-based filtering is handled automatically through the selected Change Tracking Column. You do not need to add any manual time filter.

Limitations

  • CDS views must be exposed as OData services. Only views that your deployed ABAP scripts expose as active OData services can be extracted. Tables and views without an active OData service are not visible to the connector.
  • Incremental loading requires a suitable column. A view can only be extracted incrementally if it exposes a column as an interval filter. Views without one can only be fully replicated.
  • Authorization is per service user. The connector can only see and extract the OData services that the configured user is authorized to read.

Troubleshooting

No CDS views appear in the dropdown.

  • Confirm the Dataddo ABAP scripts are deployed and the catalog service is active.
  • Confirm the relevant CDS views are activated as OData services.
  • Confirm the service user has read authorization for those services.

Saving the authorizer fails / connection test fails.

  • Check the hostname - it should not include https:// or any path, only the host (e.g. myserver.company.com).
  • Check the username and password.
  • Confirm the SAP system is reachable from Dataddo and that the catalog service responds.

A column I need is missing from the Columns list.

  • The Columns list reflects the fields exposed by the selected CDS view's OData metadata. If a field is missing, it is not exposed by that view - adjust the CDS view definition in your ABAP scripts.

The Change Tracking Column dropdown is empty.

  • The selected CDS view does not expose any column as an interval filter. Either choose a different view or extend the view definition so a suitable timestamp column is filterable. Until then, the view can only be fully replicated.