SAP Knowledge Base Article - Preview

2222241 - Offline Odata synchronization error with Edm.Time not being formatted properly


When Android client edits data from Android Native application , data writes to local offline store successfully. After editing, client synchronizes with odata producer using FLUSH process .

Back-end (SAP ECC) return http status code 400 - Bad request payload or mapping error.

Caused by: org.apache.olingo.odata2.api.edm.EdmSimpleTypeException: The literal 'P0Y0M0DT5H1M1.0S' is not formatted properly.



  • SAP Moblie Platform 3.0 SP08
  • SAP Mobile Platform 3.0 SDK SP09


SAP Mobile Platform 3.0 ; SAP Mobile Platform SDK 3.0


Edm.Time, format, offline odata, synchronization, smp, sync, http status code 400 - Bad request payload or mapping error , KBA , odata , format , MOB-SUP-RT , SUP Runtime , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.