# SAP S/4HANA (on-premise and Private Edition) and the battery passport: integration pattern

> How data from SAP S/4HANA (on-premise and Private Edition) (SAP) reaches the battery passport through the BatteryPass API: interfaces, workflows and when we checked them.

How data from SAP S/4HANA (on-premise and Private Edition) (SAP) reaches the battery passport through the BatteryPass API: interfaces, workflows and when we checked them.

An integration pattern, not a ready-made connector: your ERP or integration platform reads and writes through the BatteryPass API with an organisation key. The details below come from the vendor documentation and were checked on the date given.

- Vendor

  SAP

- Deployments

  On-premise (On-premise and Private Edition with the OP\_ APIs of the SAP Business Accelerator Hub)

- Checked

  vendor documentation, 24 October 2026

- Managed integration

  —

The OP\_ APIs mirror the cloud APIs; the middleware usually reaches the system through SAP Cloud Connector or a reverse proxy in the plant network, never directly from the internet.

## Interfaces

| Interface                                                                                                                  | Protocol | Sign-in                                         | Events          | Objects                                   | Checked                                         |
| -------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------------------------------------- | --------------- | ----------------------------------------- | ----------------------------------------------- |
| [OP_API_PRODUCT_SRV_0001](https://api.sap.com/api/OP_API_PRODUCT_SRV_0001/overview)Product master                          | OData V2 | Basic auth, X.509 certificate                   | none            | Product/material master                   | checked in the vendor documentation, 24/10/2026 |
| [OP_API_MATERIALSERIALNUMBER_0001](https://api.sap.com/api/OP_API_MATERIALSERIALNUMBER_0001/overview)Serial numbers        | OData V4 | Basic auth, X.509 certificate                   | none            | Batch/serial number                       | checked in the vendor documentation, 24/10/2026 |
| [OP_API_BATCH_SRV_0001](https://api.sap.com/api/OP_API_BATCH_SRV_0001/overview)Batches                                     | OData V2 | Basic auth, X.509 certificate                   | none            | Batch/serial number                       | checked in the vendor documentation, 24/10/2026 |
| [OP_API_PRODUCTION_ORDER_2_SRV_0001](https://api.sap.com/api/OP_API_PRODUCTION_ORDER_2_SRV_0001/overview)Production orders | OData V2 | Basic auth, X.509 certificate                   | none            | Production order                          | checked in the vendor documentation, 24/10/2026 |
| [OP_CUSTOMERRETURN_0001](https://api.sap.com/api/OP_CUSTOMERRETURN_0001/overview)Customer returns                          | OData V4 | Basic auth, X.509 certificate                   | none            | Return                                    | checked in the vendor documentation, 24/10/2026 |
| MATMASIDoc for the material master                                                                                         | IDoc     | Basic auth, X.509 certificate                   | Business events | Product/material master                   | community or marketing source only, 24/10/2026  |
| RAP business eventsBusiness events of the RAP model                                                                        | REST     | OAuth 2.0 client credentials, X.509 certificate | Business events | Product/material master, Production order | not checked                                     |

## Matching workflows

- Units from production

  Serial numbers from the production confirmation or goods receipt are staged as an import; members review, commit and approve before any passport appears.

- Passport links back into the ERP

  The middleware follows the change feed and writes the GS1 Digital Link and the passport status to the serial number record in the ERP, so labels and delivery papers carry it.

- Condition data from BMS and service

  A battery management system or a service tool reports measurements such as capacity fade or cycles; BatteryPass accepts newer measurements and publishes according to the organisation's policy.

- Returns and repairs as lifecycle events

  Completed repairs, inspections and component replacements from service or return orders appear as events in the unit's history.

- Product change leads to a new model version

  A change to the product master in the ERP triggers a notification; a member creates a new model version in BatteryPass. Declared data is never written automatically.

## Import presets

- SAP serial number list: A list of serial numbers from SAP S/4HANA as a middleware assembles it from the serial number API or the goods receipt from production. Assumes that the battery model's model identifier in BatteryPass is the SAP material number. The posting date of the goods receipt stands in for the manufacturing date; the plant stays unmapped (choose the facility in the import options).
- Generic CSV file: For any ERP and for files a middleware writes itself: GTIN, serial number, manufacturing date, facility (name or GLN), model version and battery status, with German and English column names.

[Guide in the developer documentation (after sign-in)](https://passport.kabin.sh/docs/en/integrations/erp/sap-s4hana-on-premise)

[← All integration patterns](https://kabin.sh/en/integrations)

Your data, a reviewed battery passport

In 30 minutes we show you how your existing spreadsheets, supplier data and serial numbers become a maintained battery passport.

[Request a demo](https://kabin.sh/en/contact)[See an example passport](https://kabin.sh/en/example-passport)