Known Issues for SAP Mobile WorkSpace – Mobile Business Object Development

Learn about known issues and apply workarounds for SAP Mobile WorkSpace and mobile business object (MBO) development.

Issue #	Description
SMPONP-7499	Inconsistency between refreshed structures and unrefreshed arguments/client parameters. When multiple MBOs/operations reference the same EIS structure, if the structure changes in the EIS and the MBO Developer refreshes one of the MBOS/operations, the structure is also refreshed in SAP Mobile WorkSpace. But the arguments/client parameters for other MBOs/operations are not refreshed, leading to inconsistency between the structure and the arguments/client parameters that are not refreshed. Workaround: Manually refresh all MBOS/operations that reference the same structure to maintain consistency. This inconsistency does not affect deployment.
SMPONP-5418	Unhandled event loop exceptions may be thrown when the MBO Developer deletes an operation from the mobile application diagram when the Input Mapping tab of the Operation Properties view is open. Workaround: Do not open the Input Mapping tab of the Operation Properties view when deleting an operation from the mobile application diagram.
SMPONP-3086	Deployment fails if a class or interface name in the java.lang package is used as a project package name. Workaround: Change the package name to something not in the java.lang package.
N/A	When a cache group is defined with an "EIS managed" cache group policy with the "Notify EIS to fetch operation" option selected, if the EIS REST Web service requires authentication, define the credentials during package deployment or from SAP Control Center. Workaround: If the Web service pointed to by the REST connection profile requires HTTP authentication, supply the credentials (technical user name and password) either: During package deployment – when deploying the package to the SAP Mobile Server, select the REST Web service connection to which you are mapping, if one exists, or <New Server Connection...> to create a new one from the Server Mapping Connection screen and define the User and Password properties. From SAP Control Center – any EIS connections defined here, display during package deployment.
RTC-411	SAP Mobile WorkSpace no longer automatically generates client parameter definitions and mappings to operation arguments. Prior to SAP Mobile Platform version 2.2 SP02, SAP Mobile WorkSpace automatically generated client parameter definitions and mappings to operation arguments. In SAP Mobile Platform version 2.2 SP02 and later, when you create a new MBO operation, the client parameter is not automatically created, except for operations of type "Other". Workaround: If the MBO developer wants to map the client parameters to operation arguments, drag and drop the operation argument to the Client Parameters folder in the Input Mapping page in the MBO Operation wizard or Input Mapping tab in the Properties view.
RTC-350	An MBO that is modeled and bound to a data source, then has all attributes deleted from the MBO at a later point, fails to deploy to SAP Mobile Server. Workaround: Use the Bind data source later option to create an MBO that has no attributes.
CR-713043	Foreign key constraint violation error message. You see a foreign key constraint violation error message if you create an MBO by dragging and dropping a table in which the foreign key and the primary key are both "identity" types. Workaround: The MBO is created, and you can safely ignore these error messages.
CR-705643	SAP Mobile WorkSpace does not refresh the attributes of a MBO based on a stored procedure after the stored procedure definition has been changed in the EIS. Workaround: After changing the stored procedure definition in the EIS, re-create the JDBC MBO.
CR-703200	MBO operations that include old value arguments that use large object types should be ignored, but SQL clauses still include the old value arguments. SAP Mobile WorkSpace automatically creates an MBO with old value arguments for operations. If the datasource includes operation arguments with large object types (BigString/BigBinary), SAP Mobile WorkSpace shows a warning message that says the old value argument with large object types are ignored, but the SQL definition generated still includes the old value argument with the large object type. Workaround: Manually remove any SQL clauses that include old value arguments with large object types.
CR-689859	The SAP Mobile WorkSpace Welcome page moves to standby mode after Eclipse is started. This is due to a known Eclipse 3.7 bug (https://bugs.eclipse.org/bugs/show_bug.cgi?id=355560). In standby mode, the Welcome page is docked to the right as a view in the Mobile Development perspective, since the Problem view is part of the Mobile Development perspective. Workaround: Double-click the docked Welcome page to extend it to full screen.
CR-689707	Default runtime values requirements. For an MBO operation, a non-nullable argument must get its runtime value from one of the following: client parameter, personalization key, default value, or fill-from-attribute. If a non-nullable argument already uses a fill-from-attribute or client parameter, its default value is ignored. SAP Mobile WorkSpace still allows the user to input a default value. Workaround: In this case, you need not set the default value, because it is not used during runtime.
CR-688576	The Oracle datatype NCLOB is not supported. Workaround: Convert the `CLOBS` datatype to a `varchar` datatype. There are two ways to do this: Create a stored procedure and call it from the MBO. In the stored procedure, convert the `CLOBS` to `varchar`: Create this Transact-SQL® statement, which fetches 4000 bytes of the `CLOB`: `select dbms_lob.substr( x, 4000, 1 ) from T`. The maximum varchar length allowed in Transact-SQL statements is 4000 bytes. You can increase this to 32KB. SAP recommends that you use a stored procedure to process the `BLOB` in this way. For example: declare my_var long; begin for x in ( select X from t ) loop my_var := dbms_lob.substr( x.X, 32000, 1 );
CR-676634	For Web Service and other data sources with complex structures and deeply nested element trees, `StackOverflow` or `OutOfMemory` messages may occur, or some of the operation input parameters may not be generated properly. In some cases, you see this error: The assigned stack size and/or heap size is not sufficient for the attempted operation. Workaround: Increase the stack and heap size of the Eclipse runtime parameter in UnwiredWorkSpace.bat with -Xmx, -Xms, -Xss arguments, or reduce the complexity or nested level of the Web Service definition of the MBO operation.
CR-642942	Cannot generate code with Javadoc option enabled to a folder containing Chinese characters. When using the Code Generation wizard, if you enable the option to generate Javadoc, you cannot generate the code to a folder containing Chinese characters without first changing the language for non-Unicode programs to Chinese. Workaround: Select Start > Settings > Control Panel. Double-click Regional and Language Options, then click the Advanced tab. From the drop-down list, select Chinese, and click Apply. Click OK.