SAP Basis Tech Supports

Symptom
Release restrictions of SAP NetWeaver 2004s – Usage Type Mobile Infrastructure (MI)
Other terms
MI, NW, NetWeaver
Reason and Prerequisites
At the time of the release of SAP NetWeaver 2004s limitations existed concerning the productive usage of certain functions of the usage type Mobile Infrastructure. This note provides customer information on these restrictions.
Restrictions regarding the availability of SAP NetWeaver 2004s on specific platforms are documented in the Product Availability Matrix. Please find details about operating systems, databases, and browsers supported by SAP NetWeaver 2004s on SAP Support Portal:
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000651812&
Solution

Open Limitation(s)

BC-MOB

Release with restrictions
Setup package creation only supported on MS Windows 32-bit based platforms
Creation of setup packages is currently only possible on server installations based on MS Windows 32-bit operating systems.
( Changed at 19.05.2008 )
Synchronization monitor shows wrong numbers
The “Synchronization Montor” function in the NetWeaver Mobile Administrator shows wrong values. This has been fixed in 7.01 SP03 and 7.0 SP18
( Changed at 01.09.2008 )
Related SyncBOs are not downloaded to device for specific scenario
This is applicable only if the parent SyncBO is of type T01/T51 and the relationship is from item to header. “Related SyncBOs are not downloaded to device for Specific scenario” If there is an item to header relationship and the child SyncBO is not present in RDB at the time of downloading the parent, the corresponding item and the child SyncBO will never be downloaded (even if the child SyncBO is present in RDB after some time) unless the parent is modified again from the backend.
( Changed at 19.05.2008 )
Setup package creation only supported on MS Windows 32-bit based platforms
Creation of setup packages is currently only possible on server installations based on MS Windows 32-bit operating systems.
( Changed at 22.08.2008 )
Synchronization monitor shows wrong numbers
The “Synchronization Montor” function in the NetWeaver Mobile Administrator shows wrong values.
( Changed at 22.08.2008 )
Related SyncBOs are not downloaded to device for specific scenario
This is applicable only if the parent SyncBO is of type T01/T51 and the relationship is from item to header. “Related SyncBOs are not downloaded to device for Specific scenario” If there is an item to header relationship and the child SyncBO is not present in RDB at the time of downloading the parent, the corresponding item and the child SyncBO will never be downloaded (even if the child SyncBO is present in RDB after some time) unless the parent is modified again from the backend.
( Changed at 22.08.2008 )
Mobile components with the same classnames in the same package cannot run on one mobile client
If two applications having the same classnames and under the same package are being run on MI, then there can be problems in class loading . The problem occurs since the JVM would have already loaded the class from the 1st application and the class from the 2nd application will not get loaded. For example, MAU and MAM have classes with same names and both place these classes under the same package.
( Changed at 22.08.2008 )
Setup package creation only supported on MS Windows 32-bit based platforms
Creation of setup packages is currently only possible on server installations based on MS Windows 32-bit operating systems.
( Changed at 16.04.2009 )
Related SyncBOs are not downloaded to device for specific scenario
This is applicable only if the parent SyncBO is of type T01/T51 and the relationship is from item to header. “Related SyncBOs are not downloaded to device for Specific scenario” If there is an item to header relationship and the child SyncBO is not present in RDB at the time of downloading the parent, the corresponding item and the child SyncBO will never be downloaded (even if the child SyncBO is present in RDB after some time) unless the parent is modified again from the backend.
( Changed at 16.04.2009 )
Mobile components with the same classnames in the same package cannot run on one mobile client
If two applications having the same classnames and under the same package are being run on MI, then there can be problems in class loading . The problem occurs since the JVM would have already loaded the class from the 1st application and the class from the 2nd application will not get loaded. For example, MAU and MAM have classes with same names and both place these classes under the same package.
( Changed at 16.04.2009 )
Registry Agent history setting is not working
Device Configurations are assigned to devices so as to maintain central standard settings. History Information about these standard settings are not available using registry agent in the middleware.
( Changed at 19.05.2008 )
Create and modify BAPI wrapper for SyncBOs with only multi language items is not possible
Create and modify BAPI wrapper for SyncBOs with only multi language items is not possible. In the following scenario a SyncBO having at least one item structure is required: – Multi-language handling of SyncBO instance data – Use of create and modify BAPI wrappers This means a SyncBO with only a TOP/header structure is not possible.
( Changed at 13.05.2008 )
Two smart sync application sharing same java class names cannot be used on one device in parallel
Two smart sync application sharing same java class names cannot be used on one device in parallel. Two smart sync applications which have identical java class names cannot be used in parallel. If, for instance, you are trying to use the SAP applications MAM and MAU in parallel, since they both share the same java class names, once a class of one application is loaded by the JVM on the client, the class file of the other application will not be loaded. This creates a problem when the user tries to use the second application and the class file of the first application will be invoked instead, because of the same name.
( Changed at 30.09.2008 )
Template-Based Basic Configuration (Configuration Template for Usage Type MI) not functional
The configuration template for Mobile Infrastructure is currently not functional. Please execute the post-installation steps manually.
( Changed at 19.05.2008 )
Secure Storage feature not working properly
Secure Storage feature not working properly…
( Changed at 02.09.2008 )
Mobile components with the same classnames in the same package cannot run on one mobile client
If two applications having the same classnames and under the same package are being run on MI, then there can be problems in class loading . The problem occurs since the JVM would have already loaded the class from the 1st application and the class from the 2nd application will not get loaded. For example, MAU and MAM have classes with same names and both place these classes under the same package.
( Changed at 03.12.2007 )

No release
Mobile Administrator cannot be accessed using the Firefox Internet Browser
Mobile Administrator cannot be accessed using the Firefox Internet Browser
( Changed at 19.05.2008 )
MI client cannot be used with Firefox Internet Browser
The JSP versions of the MI client require certain functions of internet browsers. It does currently not work with Firefox Internet Browser.
( Changed at 19.05.2008 )
Mobile Administrator cannot be accessed using the Firefox Internet Browser
Mobile Administrator cannot be accessed using the Firefox Internet Browser
( Changed at 22.08.2008 )
MI client cannot be used with Firefox Internet Browser
The JSP versions of the MI client require certain functions of internet browsers. It does currently not work with Firefox Internet Browser.
( Changed at 22.08.2008 )
Mobile Administrator cannot be accessed using the Firefox Internet Browser
Mobile Administrator cannot be accessed using the Firefox Internet Browser
( Changed at 16.04.2009 )
MI client cannot be used with Firefox Internet Browser
The JSP versions of the MI client require certain functions of internet browsers. It does currently not work with Firefox Internet Browser.
( Changed at 16.04.2009 )

Fixed Limitation(s)

BC-MOB

Release with restrictions
Generation of Setup Packages does not work yet
The generation of setup packages (the assembly of device installations on server side which includes MI client, applications, addons, etc.) is currently not working.
This restriction is no longer valid.
Refer to SAP Note 0000902815
( Changed at 30.12.2005 )
Initial Data Download / Sync is not working
Initial Data Download / Sync is not working
This restriction is no longer valid.
Refer to SAP Note 0000853508
( Changed at 11.07.2006 )
Application assignments to specific mobile devices is only applied to known users
For a specific device, applications can only be assigned to users who have already synchronized with the MI server. For details see SAP Note 884422.
This restriction is no longer valid.
Refer to SAP Note 0000853508
( Changed at 04.08.2006 )
MI Client Download Page does not show Java Virtual Machine (CrEme)
The MI client download page currently not shows Java Virtual Machine (CrEme) in case of MS Pocket PC platform. A temporary workaround is available – please check SAP Note 886352.
This restriction is no longer valid.
Refer to SAP Note 0000902815
( Changed at 19.05.2008 )
Setup package along with Startup Agent is not working
Creation of setup package along with startup agent is not possible.
This restriction is no longer valid.
Refer to SAP Note 0000853508
( Changed at 17.05.2007 )
Initial Data Download / Sync is not working
Initial Data Download / Sync is not working
This restriction is no longer valid.
Refer to SAP Note 0000853508
( Changed at 22.08.2008 )
Application assignments to specific mobile devices is only applied to known users
For a specific device, applications can only be assigned to users who have already synchronized with the MI server. For details see SAP Note 884422.
This restriction is no longer valid.
Refer to SAP Note 0000853508
( Changed at 22.08.2008 )
MI Client Download Page does not show Java Virtual Machine (CrEme)
The MI client download page currently not shows Java Virtual Machine (CrEme) in case of MS Pocket PC platform. A temporary workaround is available – please check SAP Note 886352.
This restriction is no longer valid.
Refer to SAP Note 0000902815
( Changed at 22.08.2008 )
Setup package along with Startup Agent is not working
Creation of setup package along with startup agent is not possible.
This restriction is no longer valid.
Refer to SAP Note 0000853508
( Changed at 22.08.2008 )
Mobile Infrastructure is currently not functional
Mobile Infrastructure is currently not functional within SAP NetWeaver 2004s.(IT-Scenario “Mobilizing Business Processes, IT-Scenario Variant “Enabling Mobile Applications for Occasional Connection”).
This restriction is no longer valid.
( Changed at 27.03.2006 )
MDK: Links to MI client home page are not working in some example programs
Application is working fine but for the ME Home link for 3 MDK applications: MDK_persistence_query_sortJSP, MDK_persistence_queryJSP and MDK_persistence_simpleJSP.
This restriction is no longer valid.
Refer to SAP Note 0000853508
( Changed at 17.05.2007 )
SSO not working on Windows Mobile 2005 in JSP mode
SSO not working on Windows Mobile 2005 in JSP mode. Impact: Single-Sign-On (SSO) feature is not available with ABAP Sync service and Sync servlet.
This restriction is no longer valid.
fixed
( Changed at 30.09.2008 )
Cascade delete for combination of T01 as parent SyncBO and S01 as Child SyncBO is not available
Cascade delete for combination of T01 as parent SyncBO and S01 as Child SyncBO is not available. Impact: For the related SyncBOs with T01 as parent SyncBO and S01 as Child SyncBO, data for the child syncBO will not be deleted even after synchronization when data for parent syncBO is deleted which can lead to data inconsistency between the client and the backend system.
This restriction is no longer valid.
Refer to SAP Note 0001014489
The correction is shipped with SAPKA64020 for SAP_ABA 640 .
The correction is shipped with SAPKB70012 for SAP_BASIS 700 .
( Changed at 17.05.2007 )
Creation of setup packages not possible when synchronization is executed via internet
When synchronization is executed via the internet using a web dispatcher or reverse proxy, the “WEBSERVER” attribute value of every mobile component is adapted to the external server name. At setup package creation this value is used to download the archive into the setup package. It might be that the external server is not reachable from the server where the setup package creation is executed. This will lead to an error.
This restriction is no longer valid.
Refer to SAP Note 0000853508
( Changed at 13.11.2006 )
Special characters in password not possible with ABAP sync
Currently the use of special characters in the password of the mobile end user can lead to synchronization problems.
This restriction is no longer valid.
Refer to SAP Note 0000979356
The correction is shipped with SAPKA64019 for SAP_ABA 640 .
The correction is shipped with SAPKA64020 for SAP_ABA 640 .
The correction is shipped with SAPKA64023 for SAP_ABA 640 .
The correction is shipped with SAPKB70010 for SAP_BASIS 700 .
The correction is shipped with SAPKB70012 for SAP_BASIS 700 .
( Changed at 13.11.2006 )
Device removal search does not indicate device with multiple users
The “Device Removal” task in the NetWeaver Mobile Administrator tool provides search capability to search for devices which have not synced in a certain timeframe. Currently this search displays every device which has at least one user who hasnt synced in the selected timeframe. Using this list, device information can be easily deleted. Of course it is wanted that device information is deleted which is not necessary any more. Currently the search does not indicate devices with more than one user. Therefore it can happen that device data is deleted which is in fact still necessary.
This restriction is no longer valid.
Refer to SAP Note 0000997817
The correction is shipped with SAPKA64020 for SAP_ABA 640 .
The correction is shipped with SAPKA64021 for SAP_ABA 640 .
The correction is shipped with SAPKB70011 for SAP_BASIS 700 .
The correction is shipped with SAPKB70013 for SAP_BASIS 700 .
Refer to SAP Note 0001019406
The correction is shipped with SAPKA64020 for SAP_ABA 640 .
The correction is shipped with SAPKB70012 for SAP_BASIS 700 .
( Changed at 17.05.2007 )

No release
Row Based Error Conflict Handling is not working for T01(Timed Two Way) and T51(Server Driven) Sync
1. For S01 sync type SyncBOs the Row Based Error Conflict handling is enabled irrespective of the Flag being checked in the MEREP_PD. 2. If there is any change in Header data in backend and any change in the data in the client it always results in a conflict even if the Row Comparison Flag is checked in the MEREP_PD. This behaviour is not visible across syncbos of type T01 and T51. SyncBO types: T01 – Timed Two Way T51 – Server Driven S01 – Two way
This restriction is no longer valid.
Refer to SAP Note 0000853508
( Changed at 13.11.2006 )
Secure Storage is not available for MI Client
Secure Storage is not available for MWD Client and MI Client
This restriction is no longer valid.
Refer to SAP Note 0000853508
( Changed at 17.05.2007 )
Row Based Error Conflict Handling is not working for T01(Timed Two Way) and T51(Server Driven) Sync
1. For S01 sync type SyncBOs the Row Based Error Conflict handling is enabled irrespective of the Flag being checked in the MEREP_PD. 2. If there is any change in Header data in backend and any change in the data in the client it always results in a conflict even if the Row Comparison Flag is checked in the MEREP_PD. This behaviour is not visible across syncbos of type T01 and T51. SyncBO types: T01 – Timed Two Way T51 – Server Driven S01 – Two way
This restriction is no longer valid.
Refer to SAP Note 0000853508
( Changed at 22.08.2008 )
Secure Storage is not available for MI Client
Secure Storage is not available for MWD Client and MI Client
This restriction is no longer valid.
Refer to SAP Note 0000853508
( Changed at 22.08.2008 )