Skip to Content

Migration of MBO Applications to Offline oData Applications – The MBO Model

May 26, 2015 | 73 Views |
 former jive document
Follow
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.

MBOModel.jpg

  • BusinessPartner MBO

          Mapped to BAPI_EPM_BP_GET_LIST

  BPMBO.jpg

Load Argument:    COUNTRY mapped to Synchronization Parameter SP_CountryBPMBOLoad.jpg

Relationship:    1 to many SalesOrders MBO

BPSORel.jpg

Create Operation:

    Mapped to BAPI_EPM_BP_CREATE

            Output Value: BP_ID

CreateBP.jpg

  • SalesOrder and SalesOrderItem MBO

Mapped to BAPI_EPM_SO_GET_LIST

SalesOrder = SOHEADERDATA

SalesOrderItem = SOITEMDATA

SalesOrderMBO.jpg

1 to many relationship between SalesOrder and SalesOrderItems MBO

SOItemRel.jpg

  • Product MBO

Mapped to BAPI_EPM_PRODUCT_GET_LIST

ProductMBO.jpg

1 to 1 relationship to ProductDetails MBO

ProdDetailsRel.jpg

  • ProductDetails MBO

Mapped to BAPI_EPM_PRODUCT_GET_DETAIL

Load Argument: PRODUCT_ID

ProductDetailMBO.jpg

  • Cache Groups

CG_Product  with cache policy:      Scheduled 8h

CG_Sales with cache policy:          On demand

CacheGroups.jpg

  • Synchronization Groups

SyncGroups.jpg

Parent Topic: Migration Overview

Next Topic: Migration of MBO Applications to Offline oData Applications – OData Model

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply