SAP BW Application Server Python API Docs | dltHub

Build a SAP BW Application Server-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

SAP BW OData API is an OData-based REST interface for querying SAP BW data, executing BEx queries, and accessing InfoProviders. The REST API base URL is https://<host>:<port>/sap/opu/odata/sap/ and Requests require a CSRF token fetched via an initial authenticated call and maintained via session cookies..

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading SAP BW Application Server data in under 10 minutes.


What data can I load from SAP BW Application Server?

Here are some of the endpoints you can load from SAP BW Application Server:

ResourceEndpointMethodData selectorDescription
bw_queries/RSOD_BW_QUERY_SRV/QueriesGETdRetrieve a list of all BW queries available in the system.
query_metadata/RSOD_BW_QUERY_SRV/Queries('{queryName}')GETRetrieve metadata of a specific BW query.
query_results/RSOD_BW_QUERY_SRV/Queries('{queryName}')/ResultsGETdRetrieve the result set of a BW query.
execute_query/RSOD_BW_QUERY_SRV/Queries('{queryName}')/ExecutePOSTExecute a BW query with variable values.
service_catalog/sap/opu/odata/sap/GETRetrieve available OData services.

How do I authenticate with the SAP BW Application Server API?

Authentication typically requires an initial request with Basic Auth to fetch a CSRF token (passing 'X-CSRF-Token: Fetch'), which is then returned in the response headers and must be provided in the 'X-CSRF-Token' header for subsequent stateful operations. Cookie-based session management is also common for maintaining the session state.

1. Get your credentials

SAP BW does not use a standard 'API key' dashboard for REST access. Access is typically managed through the SAP NetWeaver AS ABAP. 1. Create a dedicated technical user in SAP (transaction SU01) with appropriate roles for the specific OData service or Information Access (InA) service. 2. Ensure the required SICF services (e.g., /sap/bw/ina or OData services created via SEGW) are active in transaction SICF. 3. Authenticate using Basic Authentication (Username and Password) or by exchanging a token if using SAP's XSRF-protected APIs (requires a initial GET request to fetch an X-CSRF-Token).

2. Add them to .dlt/secrets.toml

[sources.sap_bw_application_server_source] username = "your_sap_username" password = "your_sap_password" base_url = "https://<your-abap-server-host>:<port>" client_id = "your_client_id"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI harness:

dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

dlthub ai toolkit rest-api-pipeline install

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the SAP BW Application Server API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

python sap_bw_application_server_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline sap_bw_application_server_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset sap_bw_application_server_data The duckdb destination used duckdb:/sap_bw_application_server.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline sap_bw_application_server_pipeline show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads /sap/bw/ina/GetServerInfo and /v1/logon/token from the SAP BW Application Server API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def sap_bw_application_server_source(x_csrf_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<host>:<port>/sap/opu/odata/sap/", "auth": {"type": "bearer", "token": x_csrf_token}, }, "resources": [ {"name": "bw_queries", "endpoint": {"path": "RSOD_BW_QUERY_SRV/Queries", "data_selector": "d"}}, {"name": "query_results", "endpoint": {"path": "RSOD_BW_QUERY_SRV/Queries('{queryName}')/Results", "data_selector": "d"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="sap_bw_application_server_pipeline", destination="duckdb", dataset_name="sap_bw_application_server_data", ) load_info = pipeline.run(sap_bw_application_server_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("sap_bw_application_server_pipeline").dataset() sessions_df = data.bw_queries.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM sap_bw_application_server_data.bw_queries LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("sap_bw_application_server_pipeline").dataset() data.bw_queries.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load SAP BW Application Server data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
dlthub ai toolkit data-exploration install dlthub ai toolkit dlthub-platform install

Was this page helpful?

Community Hub

Need more dlt context for SAP BW Application Server?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines