| Overview | Backend | App Configuration | Android | iOS |
| MBO Model | OData Model |
The EPM case study
For the purpose of demonstrating migration techniques this document will use the Enterprise Procurement Management (EPM) Model. The EPM model essential consist of Business Partners, Sales Order and Sales Order Items. In addition we have MBOs for Products and Productdetails.
- BusinessPartner MBO
Mapped to BAPI_EPM_BP_GET_LIST
Load Argument: COUNTRY mapped to Synchronization Parameter SP_Country
Relationship: 1 to many SalesOrders MBO
Create Operation:
Mapped to BAPI_EPM_BP_CREATE
Output Value: BP_ID
- SalesOrder and SalesOrderItem MBO
Mapped to BAPI_EPM_SO_GET_LIST
SalesOrder = SOHEADERDATA
SalesOrderItem = SOITEMDATA
1 to many relationship between SalesOrder and SalesOrderItems MBO
- Product MBO
Mapped to BAPI_EPM_PRODUCT_GET_LIST
1 to 1 relationship to ProductDetails MBO
- ProductDetails MBO
Mapped to BAPI_EPM_PRODUCT_GET_DETAIL
Load Argument: PRODUCT_ID
- Cache Groups
CG_Product with cache policy: Scheduled 8h
CG_Sales with cache policy: On demand
- Synchronization Groups
Parent Topic: Migration Overview
Next Topic: Migration of MBO Applications to Offline oData Applications – OData Model