SAP NetWeaver Mobile 7.1 : Version Management

[Former Member]

Dear Friends

We have the following condition:

Data Object : MAM_CE_CUSTOM with Nodes A, B , C  as VERSION 001 ( mboTrans ABC)

Data Object : MAM_CE_CUSTOM with Nodes A, B , C, D, E  as VERSION 002  ( mboTrans DEF)

Application : MAU v1.0 which contains the metadata containing MAM_CE_CUSTOM , VERSION 001

Application : MAU v2.0 which contains the metadata containing MAM_CE_CUSTOM , VERSION 002

Now, the entire field users have MAU v1.0; We deploy the metadata changes to MAM_CE_CUSTOM and upload the corresponding SDA to middleware containing MAU v2.0.

The issue we observe is MAU v1.0 now contains data sent from Middleware with mboTrans DEF.

This essentially forces the field to migrate to MAU v2.0 and makes MAU v1.0 unusable as the application fails to persist any message due to MBOTRANS exception.

Is there a way out for this, please?

Many thanks

Devendra

[former_member185875]

Hi Devendra,

I faced similar kind of issue in custom client implementation around 4 years back.

I am not sure but try below option

Unzip SDA  file edit MCD.xml added old MBO trans id.

• Replace Date and Time with current DATE and TIME under <mcd_create_date> and <mcd_create_time> tags
• Replace CreadeUser with valid DOE username in tag <mcd_created_by> .
• Specify the swcv guid in SWCV_NAME
• Replace MAM_CE_CUSTOM  with your Data object name. You can add multiple <mbo_dependencies> tag as per the need of your application.
• Specify the old MBO TRANS guid in <mbo_transguid>which has a working application
• Save the MCD.xml

upload sda file to DOE using SDOE_UPLAOD_ARCHIVE

Try assign new app and check