SAP Basis Tech Supports

Symptom
Information on release restrictions for SAP Mobile Infrastructure 2.5
Other terms
Release Restrictions, MI 2.5
Reason and Prerequisites
The statements made here, especially those referring to availability dates, reflect current planning and can be changed without prior notice
Solution

BC-MOB

Release with approval of SAP or after consultation with SAP
The integration of non-SAP backend systems is not supported
The SAP Mobile Infrastructure does not support the integration of non-SAP Systems. You can always integrate SAP backend-systems using RFC.
( Changed at 19.08.2005 )
Redundant API subset of client-side error and conflict handling not supported
The following documented client API for Error and Conflict Handling is not supported: – com.sap.ip.me.api.smartsync.PositionStatusType – com.sap.ip.me.api.smartsync.ProcessingStatusType – com.sap.ip.me.api.smartsync.SyncBoResponseLog – com.sap.ip.me.api.smartsync.SyncBoResolver – com.sap.ip.me.api.smartsync. ErrorConflictInbox#getSyncBoResponse(SyncBoDescriptor, String) – com.sap.ip.me.api.smartsync.SyncBoResponse#getCurrentLog() – com.sap.ip.me.api.smartsync.SyncBoResponse#getSyncBoResolver() – com.sap.ip.me.api.smartsync.SyncBoResponse#getSyncKey() Alternative API functionality is documentet in corresponding JavaDoc.
( Changed at 08.12.2008 )
Exception occurs when Test setting button in MDK is clicked
Exception occurs when Test setting button in MDK is clicked
( Changed at 08.12.2008 )

Release with restrictions
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 29.06.2007 )
MAXDB on Mobile Devices not supported
SAP Mobile Infrastructure does currently not support MAXDB.
( Changed at 08.12.2008 )
Multiple Client Scenario not supported for Smart Sync Applications
Smart Synchronization stores its data in SAP-Client independent database tables. Therefore it is not possible to configure a SyncBO (same ID) differently in separated SAP Clients of one Web AS (MI server).
( Changed at 08.12.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 17.05.2007 )
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 08.12.2008 )
Synchronization monitor shows wrong numbers
Synchronization monitor shows wrong numbers The “Synchronization Montor” function in the NetWeaver Mobile Administrator shows wrong values.
( Changed at 08.12.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 08.12.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 17.05.2007 )
Secure Storage feature not working properly
In case you use secure storage on a device, creation of a second user on a device does currently not work.
( 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 )

Fixed Limitation(s)

BC-MJC

Release with restrictions
Native Device Drivers are not supported
Mobile Infrastructure does not support native Device Driver for peripheral devices (e.g. printer). Mobile Applications cannot apply public MI APIs in order to use those peripheral devices.
This restriction is no longer valid.
This limitation was fixed with NW04 SP Stack 09
( Changed at 19.08.2005 )
Support Packages of the MI Client are not applied using the Client Installer mechanism
With Mobile Infrastructure 2.5 SP09 the Client Installer mechanism was introduced. At the moment only DB2e patches are created and deployed using this mechanism. The current SPs (SP10 and SP11) are delivered and deployed using the Add-On mechanism.
This restriction is no longer valid.
( Changed at 19.08.2005 )
Limit of inbound container size in case of File-I/O
In case of using File-I/O as persistence a size limit for the inbound container applies. Please check SAP Note 740096 to find out how much data can be processed during one single synchronization cycle.
This restriction is no longer valid.
( Changed at 19.08.2005 )
Suppressed Download not supported on the JSP Framework for Win32
Suppressed Download feature is not available on the JSP Framework for Win32.
This restriction is no longer valid.
( Changed at 19.08.2005 )

BC-MOB

Release with restrictions
MI Client (AWT Version) does not display asian characters on Windows Mobile 2003
At the moment the MI Client (AWT Version) on Windows Mobile/PocketPC 2003 is not able to display characters of following languages: – Simplified Chinese – Traditional Chinese – Korean – Japanese
This restriction is no longer valid.
Fixed with SP14
( Changed at 29.08.2005 )

Release with restrictions
Installation Toolkit can not be used at all
Installation Toolkit can not be used at all. This feature is replaced by a feature called “Creation of Setup Packages”. This feature is currently evaluated in the MI 2.5 SP15+ Pilot Program.
This restriction is no longer valid.
Refer to SAP Note 0000717510
( Changed at 20.04.2006 )
Setup package generation for use on several devices (MDI) does currently not work
It is currently not possible to create a setup package that can be installed on several devices. This feature is activated by checking the checkbox 揗DI?(Multiple Device Image) when you generate a setup package. Currently it is only possible to generate a setup package for use on one device.
This restriction is no longer valid.
Refer to SAP Note 0000916444
( Changed at 03.02.2006 )
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 )
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 0000717510
( Changed at 17.05.2007 )
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.
This restriction is no longer valid.
fixed
( Changed at 02.10.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 0000717510
( Changed at 30.04.2007 )
No mixed mode support between Non-Unicode and Unicode systems
A mixed mode landscape (unicode backend system & non-unicode MI server) is possible, if the exchanged data characters are available in both systems’ code pages. In this case, RFC is able to do the text conversion properly. For further details, check the RFC documentation: http://help.sap. com/saphelp_nw04/helpdata/en/22/5a981cfbaa06428abdfa32b81423d2/frameset. htm
This restriction is no longer valid.
Refer to SAP Note 0000717510
( Changed at 30.04.2008 )
Installation toolkit can not be used with Firefox
Installation Toolkit does not work with Firefox. This feature is replaced by a feature called “Creation of Setup Packages”. This feature is currently evaluated in the MI 2.5 SP15+ Pilot Program.
This restriction is no longer valid.
Refer to SAP Note 0000717510
( Changed at 20.04.2006 )
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 0000717510
( Changed at 13.11.2006 )
SSO not possible with MI client (JSP version) on PocketPC
The Single-SignOn feature is currently not functional for following MI client version: PocketPC JSP.
This restriction is no longer valid.
Refer to SAP Note 0000916444
( Changed at 23.02.2006 )
ABAP Sync Service: Unspecific error messages are shown when ABAP sync is used
When synchronization problems occur, error messages are normally shown which indicate whether the user has entered are wrong password or has insufficient authorizations or that there is a connectivity problem. Currently when ABAP sync is used, the error messages shown on the client are unspecific. Therefore the end user might not see what the problem is.
This restriction is no longer valid.
Refer to SAP Note 0000717510
( Changed at 13.11.2006 )
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 30.04.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 0000717510
( 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 30.04.2007 )

No release
New Device Management (SPS15) features (incl. ABAP Sync Service) only released for pilot projects
SPS15 contains new features in the area of device management and setup: – Mobile Administrator – Hierarchy Grouping – ABAP Sync Service – Setup Package Generation For further information about the new feature set, follow this link: http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000671237& In order to ensure quality, the features are evaluated in a pilot program. Therefore the use of these functions is currently restricted to pilot projects. In case you want to participate in the pilot program, please contact wolfgang.hegmann@sap.com.
This restriction is no longer valid.
Pilot Program was finished with shipment of SP18.
( Changed at 05.09.2006 )

CA-ME

No release
Unicode is not supported
Mobile Infrastructure does not support UNICODE.
This restriction is no longer valid.
This limitation was fixed with NW04 SP Stack 09
( Changed at 19.08.2005 )
SmartSync API with IBM DB2 Everyplace storage solution
The following restrictions apply, if SmartSync API is used with IBM DB2 Everyplace storage solution: – Only SyncBOs with less than 13 child structures are supported. – In one SmartSync Transaction only 25 structures of different row type are supported (including linked rows). This restriction is changed with NetWeaver 04 SP Stack 04 to 26 child structures per SyncBO.
This restriction is no longer valid.
This limitation was fixed with NW04 SP Stack 10
( Changed at 19.08.2005 )

CA-ME-CLN-DB-DB2E

No release
DB2e on Mobile Devices not supported
SAP Mobile Infrastructure does currently not support IBM DB2 Everyplace.
This restriction is no longer valid.
This limitation was fixed with NW04 SP Stack 02
( Changed at 19.08.2005 )

CA-ME-CLN-PER

No release
Some classes of the public API Persistence Layer are not supported
The following classes are not supported in the public API Persistence Layer: – com.sap.ip.me.api.persist.core.TransactionManager2 – com.sap.ip.me.api.persist.core.Entity2 – com.sap.ip.me.api.persist.core.PersistedObject2
This restriction is no longer valid.
This limitation was fixed with NW04 SP Stack 02
( Changed at 19.08.2005 )
Persistence Layer API with IBM DB2 Everyplace storage solution
The following restrictions apply, if Persistence Layer API is used with IBM DB2 Everyplace storage solution: – In one PersistenceTransaction (between PersistenceManager.beginTransaction() and PersistenceManager.commit() or rollback()) only PersistableEntities of 14 different ClassTypes can be processed. This includes linked PersistableEntities.
This restriction is no longer valid.
This limitation was fixed with NW04 SP Stack 02
( Changed at 19.08.2005 )
FileIO is not supported with SmartSync Transactions
The following restriction applies, if Smart Sync抯 transactions (class com.sap.ip.me.smartsync.SmartSyncTransactionManager) are used: FileIO is not supported. Use instead a JDBC implementation.
This restriction is no longer valid.
This limitation was fixed with NW04 SP Stack 09
( Changed at 19.08.2005 )

CA-ME-CLN-PI

No release
Some classes are not supported in Transaction API
The following classes are not supported in the public Transaction API: com.sap.ip.me.api.smartsync.SmartSyncTransactionManager The following methods are not supported in the public Transcation API: com.sap.ip.me.api.smartsync.SyncBoDataFacade method public SmartSyncTransactionManager getSmartSyncTransactionManager() throws SmartSyncException;
This restriction is no longer valid.
This limitation was fixed with NW04 SP Stack 09
( Changed at 19.08.2005 )

CA-ME-SER-J2EE

No release
The Disc synchronization does not support Double-Byte Character
The SAP Mobile Infrastructure provides an additional synchronization channel via file where an http(s) connection between MI Client and MI Server is not possible. You can save the synchronization data in a file format on any storage medium, like Disc. SAP Mobile Infrastructure does not support Double-Byte character data for synchronization via file or Disc.
This restriction is no longer valid.
This limitation was fixed with NW04 SP Stack 09
( Changed at 19.08.2005 )