SAP Dispute Management Python API Docs | dltHub
Build a SAP Dispute Management-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
SAP Dispute Management API allows integration with S/4HANA dispute cases for management, retrieval, and creation tasks. The REST API base URL is The base URL is specific to the customer tenant, typically in the format https://<hostname>/sap/opu/odata/sap/API_DISPUTE_MANAGE_0001 and supports Basic Authentication or X.509 client certificate (mTLS) via communication arrangements.
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 add "dlt[hub]" and start loading SAP Dispute Management data in under 10 minutes.
What data can I load from SAP Dispute Management?
Here are some of the endpoints you can load from SAP Dispute Management:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| dispute_case | dispute_caseSet | GET | Retrieve a list of dispute cases | |
| dispute_case | dispute_caseSet | POST | Create a new dispute case | |
| dispute_case | dispute_caseSet('{guid}') | GET | Retrieve a specific dispute case | |
| dispute_case | dispute_caseSet('{guid}') | PUT | Update an existing dispute case | |
| dispute_case | dispute_caseSet('{guid}') | DELETE | Delete a dispute case |
How do I authenticate with the SAP Dispute Management API?
Authentication is managed via SAP S/4HANA communication arrangements using a communication user. Standard methods include Basic Authentication (username and password) or mTLS (SSL client certificate).
1. Get your credentials
To obtain credentials for SAP S/4HANA Cloud REST APIs, you must perform the following steps in the SAP S/4HANA Cloud system: 1. Navigate to the 'Communication Management' area. 2. Create a 'Communication User' with the necessary minimal authorizations required for the specific API tasks. 3. Define a 'Communication System' and assign the previously created Communication User to it. 4. Create a 'Communication Arrangement' for the specific scenario (e.g., related to Dispute Management or OData services). 5. Within the Communication Arrangement, the system will generate the necessary credentials (such as the username, password, or OAuth Client ID and Client Secret) required to authenticate API calls.
2. Add them to .dlt/secrets.toml
[sources.sap_dispute_management_source] sap_username = "your_communication_user" sap_password = "your_communication_password" sap_client_id = "your_oauth_client_id" sap_client_secret = "your_oauth_client_secret" sap_base_url = "https://<your-s4hana-host>:<port>"
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 init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run 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:
uv run dlthub ai toolkit install rest-api-pipeline
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 Dispute Management 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:
uv run python sap_dispute_management_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline sap_dispute_management_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset sap_dispute_management_data The duckdb destination used duckdb:/sap_dispute_management.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub 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 dispute_caseSet and ServiceOrder (or equivalent OData entities exposed via your configured Communication Arrangement) from the SAP Dispute Management 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_dispute_management_source(auth_user=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "The base URL is specific to the customer tenant, typically in the format https://<hostname>/sap/opu/odata/sap/API_DISPUTE_MANAGE_0001", "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": auth_user}, }, "resources": [ {"name": "dispute_case", "endpoint": {"path": "dispute_caseSet"}}, {"name": "dispute_case_create", "endpoint": {"path": "dispute_caseSet"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="sap_dispute_management_pipeline", destination="duckdb", dataset_name="sap_dispute_management_data", ) load_info = pipeline.run(sap_dispute_management_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_dispute_management_pipeline").dataset() sessions_df = data.dispute_caseSet.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM sap_dispute_management_data.dispute_caseSet LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("sap_dispute_management_pipeline").dataset() data.dispute_caseSet.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 Dispute Management data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for SAP Dispute Management?
Request dlt skills, commands, AGENT.md files, and AI-native context.