Migrate Mobile Business Objects

You must complete the steps below to migrate 2.2 SP02 mobile business objects (MBOs) to SAP Mobile Platform version 2.3.

If you are migrating from a version earlier than 2.2 SP02, see Developer Guide: Migrating to SAP Mobile SDK 2.2 SP02, and its updates, on Product Documentation, the Migrate Mobile Business Object section: http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01857.0222/doc/html/mqu1352843142355.html

Migrate 2.2 SP0x Mobile Business Objects to 2.3

You must migrate 2.2 SP0x Mobile Business Objects (MBOs) to SAP Mobile Platform version 2.3.
  1. From Eclipse, point to the existing MBO project's workspace.
  2. Ensure connection profiles referenced by the MBO projects are in place or imported, and enterprise information system (EIS) data sources associated with those connection profiles can be connected.
  3. Once SAP Mobile WorkSpace is started, open the Mobile Application Diagram. This automatically triggers the Mobile Application project migration.

Additional Steps to Migrate MBOs

  • In versions earlier than SAP Mobile Platform version 2.2 SP02, SAP Mobile WorkSpace allowed mapping of operations with multiple MBO arguments (Filled from Attribute, client parameter, and personalization key) at the same time, even though it might not work properly on the device application during runtime.

    With version 2.2 SP02, when adding a mapping of an operation argument, SAP Mobile WorkSpace now allows only one of the three sources (MBO attribute, client parameter, personalization key) to map into the operation argument at one time; that is, the argument value sources are mutually exclusive.

    However, when migrating the Mobile Application project from earlier versions, SAP Mobile WorkSpace preserves the original MBO operation argument value assignment choices the developer made, to retain backward compatibility with the project in the earlier version. SAP Mobile WorkSpace does not remove any mappings when migrating a project.

    In a migrated project, if an operation argument is mapped to a client parameter as well as an attribute or personalization key, this warning appears: 
    Client parameter parameterName might not be used,  as the mapped argument has 'Fill from Attribute' or 'Personalization Key' specified.
    The developer must adjust the MBO model so that an operation argument maps to only one source.
    Note: The developer can provide a default value for the operation argument, regardless of how the argument is mapped.

  • Starting with SAP Mobile Platform version 2.3 SP03, SAP Mobile WorkSpace no longer allows you to set default values at the structure wrapper node levels (the structure node which contains only a single structure element). For a project that was created before 2.3 SP03, SAP Mobile WorkSpace removes the default value of wrapper level argument and disables it, then moves the original default values at the wrapper level to the structure fields of its single child structure node.

    In MBO Preview and MBO Operation's Test execute, SAP Mobile WorkSpace uses the wrapper argument's child element's default value to preview and test execution; check "Save as default value" to save the wrapped child argument's default value.

Note: In releases prior to 2.2 SP02, SAP Mobile WorkSpace automatically created client parameters definition and mapped them to the related operation arguments. After migration, those client parameters and mapping would stay. For Other operation types, client parameters are created and mapped to arguments automatically. In case the users want to have the client parameters and the mappings to the operation arguments, they can drag and drop an operation argument to the Client Parameters folder in the Input mapping page from the MBO operation wizard or Properties view's Input tab.