SAP Basis Tech Supports

Symptom
This note contains patch-wise information about the fixes provided in each patch for NW Mobile Client 7.10 in SP07. The latest patch available on Service Market Place is Patch 05.
Other terms
NW Mobile Client 7.1, SP07, Patch 05, Client Framework for Laptop, Client Framework for PDA, CFS, OCA
Reason and Prerequisites
You are using SAP Netweaver Mobile Client 7.10 SP07 Laptop or PDA Client
The following steps are mandatory when upgrading to SP07 Patch 05 using Full/Delta patch for PDA devices.These steps are NOT required when doing Full installation of PDA devices or upgrading Laptop devices:
1. Apply the note 1346873 to DoE.
2. Only for PDA Devcies – Assign the following Agent parameter to the device:
Name: MI.ClientInstaller.StaticCommandLine.PDA
Value: -classpath %CI_HOME%\\MICI.jar com.sap.ip.mi.ci.ClientInstaller -home\:%CI_HOME%
3. Only for PDA Simulator – Assign the following Agent parameter to the device:
Name: MI.ClientInstaller.StaticCommandLine.Laptop
Value: -classpath “%CI_HOME%\\MICI.jar” com.sap.ip.mi.ci.ClientInstaller -home\:”%CI_HOME%”
4. Sync the device.
Note: Both of these agent are not standard SAP Netweaver Mobile agents.These agents have to be created in DoE and assigned to the standard CONFIG Agent.

Solution
Following issues have been solved with SP07 Patch 05:
Laptop Client – Duplicate Key errors when upgrading an application with a higher version, which has data model changes that are compatible with the older version of the application.The Old child level application tables are not dropped in the client.This isue is resolved in this patch.The full/delta patch should be applied first and then the application should be upgraded.PDA eSWT runtime – When the client container is exited from the Menu>Exit option, multiple error popups come up.This issue is resolved in this patch.PDA eSWT runtime – A new functionality, Restart of the client has been introduced.The Client restarts automatically after the Sync is finished.This functionality can be enabled/disabled by setting configuration property com.sap.tc.mobile.wdlite.restartclient.aftersync to TRUE/FALSE respectively.PDA eSWT runtime – A new API restartClient() has been added to the class WDLite.When this API is called, the client is shutdown and then started.This is a forced restart and all unsaved changes are lost.AWT PDA runtime – If Auto logon feature is enabled on the client, the deployed applications are not shown on the Home Page when the client is started and user is logged in automatically.This issue is resolved in this patch.AWT PDA runtime – The Client does not allow creation of username starting with a digit for ex ‘1SAPUser’.This issue is resolved in this patch.
Following issues have been solved with SP07 Patch 04:
NOTE: When upgrading from SP04 Patch 07, FIRST apply the delta patch attached with the note and then apply the SP07 P04 Full Patch.
NumberFormatException occurs while creating/updating the child details of a header record after local re-deployment of application. This happens only when the application was rebuilt with change in the position of the columns of the header record (as a result of reimport of the data model from DOE server).This issue is resolved in this patch.When Windows is installed in non-English language, the launch of JSP application from Mobile container fails.This issue is resolved in this patch.PDA eSWT runtime – Height of the Interactive form remains fixed though it was changed in the NWDS IDE.This issue is resolved in this patch.PDA eSWT runtime – Table item lead selection is not cleared when the lead selection is set to -1.This issue is resolved in this patch.PDA eSWT runtime – While the sync is in progress, the message is not clearly visible.This issue is fixed in this patch.PDA eSWT runtime – With Autologonapplicaiton enabled, when user runs sync from the home page, the client doesnt load the autologon application after the sync is over.Instead, it goes to application launcher view.This issue is resolved in this patch.A runtime exception occurs when calling the client APIs acceptClientVersion() and acceptServerVersion().This issue is resolved in this patch.For clients using DB2e Database, there is an exception when storing data of size more than 5 MB to a table blob column.For new tables created after applying this patch, the data storage capacity for blob column will be the maximum capacity supported by DB2e.However, for existing tables, the maximum data storage in blob column will still be 5MB.

Following issues have been solved with SP07 Patch 03:
PDA eSWT runtime – View was not refreshing to show controls which are made visible from invisible state on some application action.PDA eSWT runtime – The Application icon and icons inside the application are not visible even though icons are imported to the Applications folder in the UI component.PDA eSWT designtime – Methods <<asyncExec>> & <<syncExec>> are added to the WDLite class. These methods will be visible only if a new workspace is created and the existing components are imported into the new workspace.Functioning of PDA AWT client and PDA JSP client on storage card is supported from SP7 Patch 3 onwards only for new installations of the client. The feature is supported with the latest MINDB available within the patch and the most recent and updated version of DB2E 9.1.3 available in SMP. Please refer to note number 1319135 for detail instructions on installation and usage of PDA clients on the storage card of a PDA device.
Following issues were solved with SP07 Patch 02:
Some of the function keys (such as Up, Down, Left and Right) were not functioning as expected in the eSWT runtimeDuring import of model into eSWT design time, an additional index called “ObjectState” was being created which is only expected on import of backward compatible model – this is resolved.To resolve this issue, the following steps are mandatory:Update the mobile plugins for ‘Mobile Applications for Laptop’ and ‘Mobile Applications for Handheld’ perspectiveRestart Netweaver Developer Studio.Delete existing Data model on the Client and reimport the same from DOE.Rebuild the Service component for Handheld perspective and UI component for Laptop perspective and deploy the component to the client runtime.Synchronization time from PDA eSWT client had considerably increased during download of data to the client – this is resolvedCreation of new instances of SyncBO of type Device Local, fails with error “objectState attribute descriptor not found”. To resolve this, replace the com.sap.tc.mobile.dt.cfswrap plugin of the NWDS plugins folder with the same plugin from patch 05. Restart of NWDS is required for the changes to take effect. Also, deletion of the old model and reimport of the model is a must to resolve the issue.Data transfer from the client to backend is possible without the need to launch the backward compatible SmartSync application ( atleast once before synchronization ), if the following parameter is set to true in the client: com.sap.tc.mobile.cfs.compat.smartsync.DataTransferWithoutAppLaunch=trueIf backward compatible Generic Sync and Smart Sync applications are simultaneously available on a client, it is possible to disable transfer of data for the Smart Sync application, if the following parameter is set to true in the client: MobileEngine.Sync.SyncOnlyGenericSyncApplication=true
Following issues were solved with Patch 01:
Handling of bulk delete messages on the client has been added as a new featureUpgrade from SP6 Patch 04 to SP7 Patch 00 was an issue, which is resolved in SP7 Patch 01Upgrade of DB2E from 9.1.2 to 9.1.3 by applying the DB2E_PATCH mobile component to the device, had an issue, which is resolved