Converting an MBO-based application to an OData application requires that you first develop the OData entity data model (EDM). MBO models are similar to OData EDMs, both are entity-relationship models.
In SAP Mobile Platform 2.<x>, you can use the Mobile Application Diagram to create MBOs from different data sources, such as databases, Web services, and Business Application Programming Interfaces.
In SAP Mobile Platform 3.0, the entity data model defines the service contract, which is independent of how the service is implemented. A number of different techniques exist for using SAP tools to implement services for contracts.
|MBO Model||OData Model||Notes|
|MBO Collection||Entity Collection|
|CRUD operations||N/A||CRUD operations are not part of the OData model; OData follows the HTTP REST pattern for CRUD.|
|Other operations||Function imports|
|Relationship||Association, navigation||Associations are equivalent to MBO relationships, and incorporate cardinality. To use OData associations, you must define additional navigation entities.|