Developer

Comparing MBO Models to OData Entity Data Models

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.

The following table illustrates the general mappings between structures in an MBO diagram and structures in an OData EDM diagram. There is not always a direct mapping from MBO model elements to OData model elements. In MBOs, create, read, update, and delete (CRUD) operations are synchronized database transactions. Since an OData EDM is used as a contract in an HTTP REST pattern, CRUD operations are performed using HTTP verbs, such as GET, POST, PUT, DELETE and MERGE.
MBO Model OData Model Notes
MBO Collection Entity Collection  
MBO Entity  
Attributes Properties  
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.