SAP Service and Asset Manager is an offline-enabled mobile application. Offline capabilities in MDK application is provided by Offline OData SDK. OData Offline supports the use of custom HTTP headers to be included in offline transaction data creation, and uploaded during client synchronization with SAP back-end OData service.
There are several custom headers used by SAP Service and Asset Manager. These are detailed in the following table:
| Header Name | Type | Description | Example Use Case |
|---|---|---|---|
OfflineOData.RemoveAfterUpload | Boolean | Removes the record after uploading. | Work Order Create: The local work order is removed from the offline DB during sync and back end sends a new, replacement record. |
OfflineOData.TransactionID | String | Gives a named Transaction ID to a given OData transaction. | Used for forcing requests to be sent in the same batch. Transactions with the same OfflineOData.TransactionID name are sent together in one OData batch. This is sometimes necessary as the gateway may need to see several operations simultaneously before processing. |
OfflineOData.NonMergeable | Boolean | Forces transaction to not be merged. | Used extensively in Mobile Statuses. By default, Offline OData will combine multiple updates to an entity into one request wherever possible. This prevents that behavior from occurring. |
Transaction.Ignore | Boolean | Tells the Cloud Platform to ignore this particular transaction. | Used for altering records for display purposes only. |
Transaction.omdo_id | String | Tells back-end to send data to specific oMDO (entity set) instead of the one specified by the Action. | Used specifically in Meter component for meter readings creation. Install/Remove/Replace readings must be sent to one BAPI whereas Aperiodic meter readings are sent to another one. |