OData for S/4HANA, CAP and RAP.
The OData plugin1 turns RequestTailor into a client that knows how SAP services behave: it reads $metadata, fetches CSRF tokens, keeps ETags, builds $batch and runs draft actions. Your requests stay plain files.
Optional, and your choice. The plugin ships with the app but is active only if you choose SAP and OData at first start. The core contains no SAP knowledge2; the plugin uses the same public plugin API as any other.


Three kinds of SAP services.
| Service | Typical root | Protocol |
|---|---|---|
| SAP Gateway services on S/4HANA | /sap/opu/odata/sap/<SERVICE>/ | OData V2 |
| RAP business services | /sap/opu/odata4/sap/<service>/srvd_a2x/…/0001/ | OData V4, with draft |
| CAP services | /odata/v4/<service>/, V2 adapter /odata/v2/<service>/ | OData V4 with draft, and V2 |
What you would otherwise do by hand.
- EntitiesReads
$metadataof V2 (EDMX 1.0) and V4 and shows entity sets, types, keys, navigation properties and operations. The model is cached per service root. - Query builder
$filter,$expand,$select,$orderby,$top,$skipand$count(V4) or$inlinecount(V2), offered from the model and written back into the request URL. - CSRF tokensBefore writing requests the plugin fetches an
X-CSRF-Tokenin the same session and sets it; after a403withX-CSRF-Token: Requiredit fetches a new one. - ETags and If-MatchRemembers ETags per entity and sets
If-Matchon updates and deletes that do not have one. - $batchBuilds
$batchwith read parts and changesets: multipart for V2 and V4, JSON batch for V4. The response is shown part by part. - DraftsEdit, Prepare, Activate and Discard in RAP;
draftEdit,draftPrepare,draftActivateanddiscardin CAP. - DEV, QAS, PRDCreates one environment per system from a template: host,
sapClient,sapLanguage, user, and the password as a secret without a value. Addssap-clientandsap-languageto every URL that lacks them. - ImportCreates requests from a
$metadatafile: list, read by key, create, update and delete as the entity set allows, plus its operations. Also reads API specifications downloaded from the SAP Business Accelerator Hub (EDMX, or OpenAPI withx-sapextensions).
Environments are files too.
The same requests run against DEV, QAS and PRD. Only host, client and user differ; passwords stay in your keychain3.
# environments/QAS.yml
name: QAS
variables:
- name: baseUrl
value: https://s4-qas.example.com
- name: sapClient
value: "200"
- name: sapLanguage
value: EN
- name: user
value: JDOE
- secret: true
name: password
OData over HTTP. No more, no less.
- No RFC, no BAPI, no SOAP, no SAP GUI.The plugin speaks OData over HTTP.
- No SAP software, no SAP data.The test services in the repository are written from the public OData specifications and documented SAP Gateway behaviour; all data is made up.
- Sign-in with the core's methods.Basic, OAuth 2.0 including SAML 2.0 bearer, and client certificates.4
- BTP service keys and destinations In the worksSAP comfort belongs to Pro and is in the works.5 The OData basics on this page stay in Free.
SAP, S/4HANA, SAP Gateway, ABAP and other SAP products named here are trademarks or registered trademarks of SAP SE in Germany and other countries. RequestTailor is not offered, endorsed or sponsored by SAP SE. If you want to start with the plugin on your own system: write to us.
Sources on this page
The superscript numbers in the text point here. Tap one to see the source right where it is used; all sources of this website are listed on one page.
- 1
OData plugin for S/4HANA, CAP and RAP ↑Product · RequestTailor core repository, plugins/odata, website/sap, website/docs/odata · checked on 2026-11-22
- 2
Plugins only as WebAssembly, with permissions ↑Product · RequestTailor core repository, crates/rt-plugin/API.md, plugins/README.md · checked on 2026-11-22
- 3
Secrets in the keychain and from external vaults ↑Product · RequestTailor core repository, CLAUDE.md (Produktprinzip 3), crates/rt-cli/README.md (externe Secrets), website/docs/environments · checked on 2026-11-22
- 4
OAuth 2.0, AWS SigV4, client certificates ↑Product · RequestTailor core repository, crates/rt-core (model::auth), crates/rt-format/src/auth, testdata/sigv4 · checked on 2026-11-22
- 5
Free, Pro, Team and Enterprise editions (concept) ↑Product · RequestTailor product concept (internal), section “Editions and prices” · checked on 2026-11-22
Questions about SAP and OData.
- Which SAP services does the OData plugin understand?
- SAP Gateway services on S/4HANA with OData V2, RAP business services with OData V4 and drafts, and CAP services with OData V4 and through the V2 adapter. The plugin reads $metadata of V2 (EDMX 1.0) and V4.
- Do I have to use the SAP plugin?
- No. It ships with the app but is active only if you choose SAP and OData at first start. If you don't, you see nothing of SAP. The RequestTailor core contains no SAP-specific code.
- How does RequestTailor handle the CSRF token?
- Before a POST, PUT, PATCH, MERGE or DELETE, the plugin fetches an X-CSRF-Token in the same session as the request and sets it. After a 403 with X-CSRF-Token: Required, it fetches a new one.
- Can I call RFC, BAPI or SOAP?
- No. The plugin speaks OData over HTTP. RFC, BAPI calls, SOAP services and SAP GUI are not covered.
- What about BTP service keys and destinations?
- That is SAP comfort for Pro and in the works. Today you sign in with the core's methods: basic, OAuth 2.0 including SAML 2.0 bearer, and client certificates.
Your question isn’t here? Talk to me: +43 664 1964199 office@clouddna.at Get in touch