SAP Internet of Things FAQ

Do you have a question about SAP IoT? You're in the right place! Start here to find answers to some of our most frequently asked questions.

SAP Internet of Things (IoT) FAQ

What is the definition of Capacity Unit?

A Capacity Unit is an abstract measurement unit. For SAP IoT it refers to the metric for licensing. SAP IoT Services have different “weight” in terms of Capacity Units. Depending on sizing and use case a calculation of required capacity units is possible. Once a customer buys a number of Capacity Units when buying SAP IoT it can be used against any of the available SAP IoT services dynamically. For more information, visit this link.

How does a typical SAP IoT architecture/landscape look like?

To find out more about the architecture of SAP IoT, including the different layers and components and how they interact with other software layers as well as real-world devices in a sample system landscape, visit our SAP Help Portal.

Is there a place to access an updated SAP IoT APIs Postman collection?

We do offer Postman collections for a subset of APIs in the sample code repositories provided at GitHub and in particular in this one.

How can I tell if the sensor data my devices sent have successfully been received and processed?

First indication is the return code received in the device firmware from MQTT or REST ingestion. 200 or 202 is good. Next thing to look at is the device connectivity component - here logs are only visible for edge gateways on the edge - in the cloud the logs of the cloud gateway are only visible to SAP support. From there the data flows into the SAP managed Kafka dedicated to SAP IoT. The next type of logs available are then shown in the ingestion error log app in the SAP IoT Launchpad. If there is a logical error or mismatch, then it would show up here. For everything that goes through successfully the queries against raw data will show the data first, then comes the aggregate APIs (at least after 2 minutes). It is a good idea to use the documented E2E ingestion monitoring to understand the current ingestion delay relative to your tenant.

Can we control how long IoT time series data shall reside in each of the different SAP IoT storage types?

You can define the retention time in warm store for raw data to be different then 3 months (this will increase or decrease your costs). For cold store you can purge unused data via APIs. For the hot store there is no way to purge data selectively or change the retention yet.

Is there a particular order in which my IoT devices need to send time series data?

Within the default 3-month retention period data can be sent with timestamps all over the board and it will be correctly inserted, and the aggregates correctly (re-)calculated.