59
SAP ® NetWeaver Mobile 7.1 Target Audience Techonology consultants Software Developers Document version: 1.0 June, 2009 PUBLIC Frequently Asked Questions

Sap Netweaver Faq1

Embed Size (px)

Citation preview

Page 1: Sap Netweaver Faq1

 

SAP® NetWeaver

Mobile 7.1

Target Audience  

Techonology consultants   Software Developers    

 

Document version: 1.0  –   June, 2009  

PUBLIC

Frequently Asked Questions

Page 2: Sap Netweaver Faq1

© Copyright 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or

transmitted in any form or for any purpose without the

express permission of SAP AG. The information contained

herein may be changed without prior notice.

Some software products marketed by SAP AG and its

distributors contain proprietary software components of

other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are

registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel

Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,

OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,

Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,

i5/OS, POWER, POWER5, OpenPower and PowerPC are

trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader

are either trademarks or registered trademarks of Adobe

Systems Incorporated in the United States and/or other

countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered

trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame,

WinFrame, VideoFrame, and MultiWin are trademarks or

registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or

registered trademarks of W3C®, World Wide Web

Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems,

Inc., used under license for technology invented and

implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP

NetWeaver, and other SAP products and services

mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in

Germany and in several other countries all over the world.

All other product and service names mentioned are the

trademarks of their respective companies. Data contained

in this document serves informational purposes only.

National product specifications may vary.

These materials are subject to change without notice.

These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes only,

without representation or warranty of any kind, and SAP

Group shall not be liable for errors or omissions with

respect to the materials. The only warranties for SAP

Group products and services are those that are set forth in

the express warranty statements accompanying such

products and services, if any. Nothing herein should be

construed as constituting an additional warranty.

These materials are provided “as is” without a warranty of

any kind, either express or implied, including but not

limited to, the implied warranties of merchantability,

fitness for a particular purpose, or non-infringement.

SAP shall not be liable for damages of any kind including

without limitation direct, special, indirect, or consequential

damages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of the

information, text, graphics, links or other items contained

within these materials. SAP has no control over the

information that you may access through the use of hot

links contained in these materials and does not endorse

your use of third party web pages nor provide any warranty

whatsoever relating to third party web pages.

SAP NetWeaver “How-to” Guides are intended to simplify

the product implementation. While specific product

features and procedures typically are explained in a

practical business context, it is not implied that those

features and procedures are the only approach in solving a

specific business problem using SAP NetWeaver. Should

you wish to receive additional information, clarification or

support, please refer to SAP Consulting.

Any software coding and/or code lines / strings (“Code”)

included in this documentation are only examples and are

not intended to be used in a productive system

environment. The Code is only intended better explain and

visualize the syntax and phrasing rules of certain coding.

SAP does not warrant the correctness and completeness of

the Code given herein, and SAP shall not be liable for

errors or damages caused by the usage of the Code, except

if such damages were caused by SAP intentionally or

grossly negligent.

Disclaimer

Some components of this product are based on Java™. Any

code change in these components may cause unpredictable

and severe malfunctions and is therefore expressively

prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is only

to be used by SAP’s Support Services and may not be

modified or altered in any way.

Page 3: Sap Netweaver Faq1

Typographic Conventions Type Style Description

Example Text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, graphic titles, and table titles

Example text

File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text

User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text>

Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT

Keys on the keyboard, for example, F2 or ENTER.

Icons Icon Meaning

Caution

Note / Important

Example

Recommendation / Tip

Page 4: Sap Netweaver Faq1

FAQs

1. Introduction ...................................................................................3 1.1 Naming Conventions .......................................................................4 1.2 Additional Information.....................................................................5 

2. Mobile Setup/Software..................................................................6 3. SAP NetWeaver Developer Studio (IDE) ...................................12 

3. SAP NetWeaver Mobile Client ....................................................20 

4. Data Orchestration Engine (DOE)..............................................31 

5. SAP NetWeaver Mobile Administrator ......................................50 

6. IDoc ..............................................................................................56 

Page 5: Sap Netweaver Faq1

FAQs

1. Introduction SAP NetWeaver Mobile provides a platform for ready-made and custom-developed scenarios for all popular devices in both connected and occasionally connected environments. SAP NetWeaver Mobile is completely integrated in SAP NetWeaver and provides the base technology for applications working in a disconnected environment. It thus supports offline applications, which assure that time-critical processes can be carried out, even when no direct connection to the corporate systems are available.

This document provides a comprehensive list of frequently asked questions, right from setup and installation to administration.

Page 6: Sap Netweaver Faq1

FAQs

1.1 Naming Conventions Terms and Abbreviations

The following terms and abbreviations are used in this document:

Term Explanation

30BDOE Data Orchestration Engine

NWDS NetWeaver Developer Studio

34BNWM NetWeaver DOE Administration & Monitoring

36BPDA Personal Digital Assistant

38BRFC Remote Function Call

Page 7: Sap Netweaver Faq1

FAQs

1.2 Additional Information

Location of documentation & patches on SAP Service Marketplace: 1. You can find the installation and upgrade guides at:

http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver Mobile 7.1 Installation Installation – SAP NetWeaver Systems

2. You can find the Product Availability Matrix at:

ttp://service.sap.com/pam h -> SAP NetWeaver

3. You can find all the patches at:

http://service.sap.com/patches

ou can find the client-side patches at:

AP Support Packages Entry by Application Group Support Packages and

4. You can find the NW Mobile Developers Guide at

b/0b674240449c60e1000000

Y S

Patches SAP NetWeaver SAP NETWEAVER SAP NETWEAVER

MOBILE 7.1 NW Mobile Client Setup 7.10

http://help.sap.com/saphelp_nwmobile71/helpdata/en/80a1550b0/frameset.htm

5. You can find documentation about developing mobile applications for laptops at: ttp://help.sap.com/saphelp_nwmobile71/helpdata/en/67/c3deab08754a878dae015d

h9b5d70f5/frameset.htm 7. You can find documentation about developing mobile applications for PDAs at:

ttp://help.sap.com/saphelp_nwmobile71/helpdata/en/45/c9b47db88b5591e1000000 h0a1553f7/frameset.htm

Page 8: Sap Netweaver Faq1

FAQs

2. Mobile Setup/Software 1. Where can we find to find NWMCLIENTSETUP.ZIP setup files and IDE plug-ins

on Service Market Place?

2. Why should we perform a patch upgrade? How do we perform a patch upgrade?

3. If the mobile client is upgraded from a lower version to a higher version, should we uninstall the current SAP NetWeaver Mobile Client 7.1, the Current Max DB for Mobile and the current SAP Web Dynpro client for Java components? Will this result in any loss of data?

4. How can we make sure that the patch is applied correctly or that the upgrade is successful?

5. Can we use SAP NetWeaver Mobile 7.1 functions with the new SAP NetWeaver CE 7.1 trial version? Can we create SAP NetWeaver Mobile 7.1 applications on SAP NetWeaver CE 7.1?

6. Is there any new version that is compatible with Windows Vista and Windows 2000?

7. When .NET is specified as an Addon, while creating setup package installation, should it be specified as a pre-installation or post-installation mobile component to the JRE mobile component?

8. Which devices does SAP NetWeaver 7.1 support?

9. SAP NetWeaver Mobile 7.1 requires a SAP NetWeaver WAS 710 engines. With customers recently upgrading to ECC6 which is based on WAS 700, is it really required to install SAP NetWeaver Mobile 7.1 on a separate instance (ABAP and JAVA) or can we use an existing instance?

10. Installing MaxDB on system to use it along with SAP NetWeaver Mobile Laptop Client 7.1?

11. What are the different types of UI elements that SAP NetWeaver Mobile 7.1 supports? Which is the best one to use and what benefits does it have compared with the others?

12. Can you explain more about eSWT, how can we design UI elements using this? Can you provide me some helpful links regarding all the UI elements in SAP NetWeaver Mobile 7.1? What is meant by compatibility applications JSP and AWT for backward compatibility applications?

13. If we deploy our application on an emulator under NWDS or MDA Pro, everything works fine. Now we want to run our application on Skeye pad XSL with Windows CE .NET 4.20 and ARM-XScale - Processor.

Page 9: Sap Netweaver Faq1

FAQs

Q.1) Where can we find NWMCLIENTSETUP.ZIP setup files and IDE plug-ins on SAP Service Marketplace?

A.1) The software can be found at the location specified below:

http://service.sap.com/swdc Download Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP NETWEAVER MOBILE 7.1 NW MOBILE CLIENT SETUP 7.10 NWMCLIENTSETUP.ZIP Click the Win32 link, then scroll down the page, and you should be able to find the software.

For SAP NetWeaver Composition Environment, download from the link below:

https://nwds.sap.com/swdc/downloads/updates/netweaver/nwds/ce

Q.2)

1. Why should we perform a patch upgrade?

2. How do we perform a patch upgrade? A.2) Answer 1: Reason 1: To obtain the new features introduced in the SPS that is being used. Reason 2: To get an up-to-date record of all the changes that were made for the particular SPS that is being used. Answer 2: 1) Download the patches from SAP Service Marketplace.

( http://service.sap.com/patches ….. You can find the client-side patches at: SAP Support Packages Entry by Application Group Support Packages and

Patches SAP NetWeaver SAP NETWEAVER SAP NETWEAVER MOBILE 7.1 NW Mobile Client Setup 7.10)

With every patch release, two types of patches are delivered: • Full patch: This contains an up-to-date record of all the changes.

To upgrade between patches that belong to different SPSs, you must apply the full patch on the mobile client.

• Delta patch: This contains only the changes from a particular SPS release. To upgrade between patches that belong to the same SPS, you must apply this patch. This patch is a cumulative patch, which means it contains all the changes from a particular SPS release.

To help understand the use of each sort of patch, see the following example.

If your mobile client is on SPS 02 Patch 2, and:

You want to upgrade to: You must apply:

SPS 02 Patch 3 Delta patch of SPS 02 Patch 3

SPS 02 Patch 5 Delta patch of SPS 02 Patch 5

SPS 04 Patch 2 Full patch of SPS 04 Patch 2

Page 10: Sap Netweaver Faq1

FAQs

Note: If there are any UI changes, then you must apply the full patch. 2) Upload the patches to the Data Orchestration Engine (DOE).

For more information on how to do this, see the link below: http://help.sap.com/saphelp_nwmobile71/helpdata/en/fc/694d1175904bde904cfd7326fa9122/frameset.htm

3) After uploading the software component archives (SCAs), assign the related mobile component descriptors (MCDs) to the device that is to be upgraded. For more information on how to do this, see the link below:

http://help.sap.com/saphelp_nwmobile71/helpdata/en/55/58c995e656459d86cc88a027709447/frameset.htm

4) When synchronization is performed on the mobile client, the MCDs are deployed on the mobile client and the mobile client is upgraded.

Note: In the event of an OCA client upgrade, we recommend maintaining the same version of NWDS and client.

Q.3) If the mobile client is upgraded from a lower version to a higher version, should we uninstall the current SAP NetWeaver Mobile 7.1 Client, the current Max DB for Mobile, and the current SAP Web Dynpro Mobile client for Java components? Will this result in any loss of data?

A.3) If the “mobile client is upgraded from a lower version to a higher version", you do not need to uninstall any of the components. The patches can be applied directly and the mobile client can be upgraded. Performing the upgrade process will not result in any loss of data or registration with the DOE server or any configuration. Note: In the event of an OCA client upgrade, we recommend maintaining the same version of NWDS and client.

Q.4) How can we make sure that the patch is applied correctly or that the upgrade is successful?

A.4) You can check that the patch is applied correctly using one of the following options:

Option 1: By looking at the deployment status of the MCDs that were assigned to the device in the NWM portal. If there are any problems with the upgrade, the status Error in installation is displayed; if the upgrade was successful, the status Installed is displayed.

Option 2: In SAP NetWeaver mobile client, go to the Information tab → Installed

Page 11: Sap Netweaver Faq1

FAQs

Applications. Here the patch that is applied and the status of the upgrade are displayed

Option 3: In addition, you can check in ‘BuildNo.txt’ file (located in the SAP NetWeaver mobile client home folder). In this text file, the version of the patch to which the mobile client was upgraded is reflected.

Q.5) Can we use SAP NetWeaver Mobile 7.1 functions with the new SAP NetWeaver CE 7.1 trial version? Can we create SAP NetWeaver Mobile 7.1 applications on SAP NetWeaver CE 7.1? A.5) Yes, SAP NetWeaver Mobile 7.1 functions can be used with SAP NetWeaver CE 7.1 and SAP NetWeaver Mobile 7.1 applications can be created on SAP NetWeaver CE 7.1. For more information about installations, choose the link below: http://help.sap.com/saphelp_nwmobile71/helpdata/en/dd/9427535e5040faa26aa0afd6f0bf87/content.htm Q.6) Is there a new version that is compatible with Windows Vista and Windows 2000?

A.6) Windows Vista is supported by SAP NetWeaver 7.1 from 2008 onwards. However, SAP NetWeaver 7.1 does not support Windows 2000. For more information about supported operating systems, see the Product Availability Matrix (PAM) at http://service.sap.com/pam

Q.7) When .NET is specified as an add-on, while creating setup package installation, should it be specified as a pre-installation or post-installation mobile component to the JRE mobile component?

A.7) It should be specified as a post-installation mobile component to the JRE mobile component.

Q.8) Which devices does SAP NetWeaver Mobile 7.1 support?

A.8) The devices supported by SAP NetWeaver Mobile 7.0 are also supported by SAP NetWeaver 7.1. For more information about which devices are supported by SAP NetWeaver Mobile 7.1, see SAP Note 853397).

Q.9) SAP NetWeaver Mobile 7.1 requires a SAP NetWeaver WAS 710 engine. With customers recently upgrading to ECC6, which is based on WAS 700, is it really necessary to install SAP NetWeaver Mobile 7.1 on a separate instance (ABAP and JAVA) or can we use an existing instance?

A.9) Yes, you must install SAP NetWeaver Mobile 7.1 on a separate instance and you cannot use existing 7.0 instances because SAP NetWeaver Mobile 7.1 requires SAP Basis 7.1. In addition, you do not require a Java instance for SAP NetWeaver Mobile 7.1 because the server part is completely in ABAP, whereas SAP NetWeaver Mobile 7.0 was ABAP and Java.

Q.10) Installing MaxDB on system to use it with SAP NetWeaver Mobile Laptop Client 7.1:

Step 1: We install SAP NetWeaver Mobile Laptop Client 7.1. Normally, it checks for MaxDB in the system and if this is not present, the installation asks for SDBINST.exe. We specified the path but the system says that the installation failed and asks us to install it manually. Step 2: We install MaxDB separately (manually) before installing the client. We

Page 12: Sap Netweaver Faq1

FAQs

chose Server + Client → Install S/w and create DB instance → MaxDB installed → Install client 7.1 → checks MaxDB and gets an instance → asks for the DB password. What password should we specify during installation?

A.10)

Step 1: Before you install MaxDB during the SAP NetWeaver Mobile 7.1 installation, ensure the following prerequisites have been fulfilled:

• All the instances of MaxDB have been uninstalled.

• There should not be any folders such as Drive:\SAPDb or Drive:\program files\SDB.

Once the above steps are completed, run the Mobile Laptop Client 7.1 installation and you should be able to install Max DB successfully.

Step 2: You can enter the password of your choice during installation.

Q.11) What are the different types of UI elements that SAP NetWeaver Mobile 7.1 supports? Which is the best one to use and what benefits does it have compared with the others?

A.11) SAP NetWeaver Mobile 7.1 supports four different types of UI:

a) Web Dynpro for Java for laptop applications

b) eSWT for PDA applications

c) JSP and AWT for backwards-compatibility applications

Q.12) Can you explain more about eSWT, how can we design UI elements using this? Can you provide some helpful links regarding all the UI elements in SAP NetWeaver Mobile 7.1? What is meant by JSP and AWT for backward compatibility applications?

A.12) In SAP NetWeaver Mobile 7.1, custom UI controls can be developed using eSWT for PDA applications. It is an open-source technology for native UIs.

For the list of supported Web Dynpro controls, properties, and events, see the link below:

http://help.sap.com/saphelp_nwmobile71/helpdata/en/46/03b234add73482e10000000a1553f6/content.htm

With regard to the AWT/JSP applications, you can run SAP MI 7.0 applications on the SAP NetWeaver Mobile 7.1 client using the backwards-compatibility mode. This means that there is a small component translating all 7.0 APIs to the corresponding 7.1 APIs. In addition, there is no need to rewrite the application for SAP NetWeaver Mobile 7.1.

Q.13) If we deploy our application on an emulator under NWDS or MDA Pro, everything works fine. Now we want to run our application on Skeye pad XSL with Windows CE .NET 4.20 and ARM-XScale-Processor.

Therefore we prepared the device by installing the following:

• CrEme 4.12 (CrE-ME412_ARM_CE40_HPC.CAB)

• minDB (mindb.CAB)

• pda_eswt_container.CAB

• pda_runtime_wince.CAB

An example application that comes with CrEme can be started and runs fine:

(→ Programs → CrEme → Cube)

Page 13: Sap Netweaver Faq1

FAQs

But after starting SAP NetWeaver Mobile on the Skeye pad, we receive the following error message: *SAP NetWeaver Mobile is not a valid Windows CE application. What could be the reason?

A.13) It is because SAP NetWeaver Mobile runs on the Java platform and does not support the .net platform.

For more information, see the Product Availability Matrix (PAM) at:

https://service.sap.com/pam

SAP NetWeaver → SAP NetWeaver Mobile → SAP NetWeaver Mobile 7.1.

Page 14: Sap Netweaver Faq1

FAQs

3. SAP NetWeaver Developer Studio (IDE) 1. Can we launch the simulator if the mobile client has already registered with DOE?

2. When we open NWDS and start a new Mobile Service Project for Handheld, then select Demo - local development an error – “Software Component does not support …..” appears. How should be proceed?

3. Is it possible to use an NWDI7.0 to develop applications for SAP NetWeaver Mobile 7.1?

4. The Repair function for importing data objects to eSWT design time is not changing the version of the data object in the IDE. What can we do?

5. How can we create new records in the database (Mobile WebDynpro Offline for Laptops)?

6. We are installing mobile plug-ins in the IDE. In this phase we are not able to extract the com.sap.mobile.ap.ecp file. How do we extract the .ecp file?

7. We are looking for documentation of the rejection API for mobile handhelds -

- Rejection repository

- Rejections

- Rejection info

Are any examples and documentation available?

8.

a) I have developed a mobile application for handhelds on NWDS SP3 PATCH8 and the Mobile Client I am using is of SP6 P2. When the Mobile Client SP06 patch is deployed on the device, everything works fine, but when the emulator is used for running the application, the emulator crashes. What could be the reason for this?

b) I am trying to deploy the driver deployer for win32 to emulator, so that I can deploy the connector later, and use the PIOS.printer API for testing on the emulator. The deployment ends with errors. What could be the reason for this?

9. Which file do we need to upload for the application? Is it the .SDA file or .ear file? How do we create an .sda file in the IDE?

10. There is a default calendar for input fields of type java.sql.Date. I want to change the format of the date, which is mm/dd/yy by default. How can we do this?

11. We are using SAP NetWeaver Developer Studio 7.1. In the application being developed, we require the cursor to be on the data entry field. In the SAP NetWeaver Developer Studio, we could not call up the 'SetFocus' API.Currently the user has to tap on the field for the cursor to appear on it. How can we solve this?

12. We launch NWDS with the -clean option to reload plug-in registration and apply the valid default.confdef.xml file. Then when we start to create a new project Local Development itself is not visible, as shown below .How can we proceed?

13. We have tried to configure the NWDI track to develop SAP NetWeaver Mobile 7.1 applications for laptops. We have followed the instructions on help.sap.com, but when we try to activate the mobile DC from the CBS activation view in NWDS, the following error appears in cbs-build.log:

“java.lang.UnsupportedClassVersionError: com/sap/tc/buildplugin/DefaultPlugin (Unsupported major.minor version 49.0)” What is the cause of this error?

Page 15: Sap Netweaver Faq1

FAQs

14. We have configured the NWDI server as the development runtime system for deployment, but when we try to deploy the .SDA file, we receive an error stating that it cannot find a suitable container for deployment. What could be the reason for this?

15. Is it possible to import the DO model in a local project?

Page 16: Sap Netweaver Faq1

FAQs

Q.1) Can we launch the simulator if the mobile client has already registered with the DOE?

A.1) Yes, the simulator can be launched even if the mobile client has already registered with the DOE.

Note:

1. You cannot run the simulator client and the installed client simultaneously.

2. You can register the simulator client with the DOE as well but it will be registered under a separate device name.

Q.2) When we open NWDS and start a new Mobile Service Project for Handheld, then select Demo - local development, an the error “ Software Component does not support …..” appears. How should we proceed?

A.2) Go to the Development Infrastructure perspective. In Component Browser → Local Development, check whether there are any DCs under NWMCLIENT and XOCA. This problem may occur if there are no required DCs under NWMCLIENT and XOCA.

One solution is to create a new workspace and create the required components. Alternatively, you can copy the contents of NWMCLIENT and XOCA from the folder IDE → design time → eclipse → plugins → com.sap.tc.ap_{version} → comp to the folders you are referring to.

Q.3) Is it possible to use NWDI 7.0 to develop applications for SAP NetWeaver Mobile 7.1?

A.3) Yes, you can use NWDI 7.0 to develop with NWDS 7.1, provided NWDI contains the relevant archives.

Q.4) The repair function for importing data objects to the eSWT design time is not changing the version of the data object in the IDE; what can we do?

A.4) This problem is solved with SPS0 6 Patch 04. For more information, see SAP Note 1225246 (SAP NetWeaver Mobile Client 7.1 SPS 06 Patches).

Q.5) How can we create new records in the database (Mobile Web Dynpro Offline for Laptops)?

A.5)

Page 17: Sap Netweaver Faq1

FAQs

Creating records for the header node: Add a Create button or any other UI element that has an action related to it. <Write Model name> model = <write Model name>.get Instance (); => no need to repeat this if already done before. <Name of your node> mead = model. Create<node name>; model.addTo<node name> (mhead); You have already written a bind in the supply function so there is no need for an explicit bind here. Creating records for the item node: Create a button for the item and an action. <Header node> shead2 = wdContext.current<header>Element ().model Object () ; <item node> item = shead2.createNew<item node>; shead2.addTo<item node> (item); For more information about how to develop with Mobile Web Dynpro Offline for Laptops, see:

http://help.sap.com/saphelp_nwmobile71/helpdata/en/67/c3deab08754a878dae015d9b5d70f5/frameset.htm

Q.6) We are installing mobile plug-ins in the IDE. In this phase, we are not able to extract the com.sap.mobile.ap.ecp file. How do we extract the .ecp file?

A.6) To extract the com.sap.mobile.ap.ecp file, open this file with winRAR archive and then copy the contents of the folder to a local folder.

Q.7) We are looking for documentation of the rejection API for mobile handhelds.

- Rejection repository

- Rejections

- Rejection information

Are any examples and documentation available?

A.7) See SAP Note 1259580, which contains an attachment on rejection-handling scenarios in SAP NetWeaver Mobile 7.1.

Q.8)

a) I have developed a mobile application for handhelds on NWDS SP3 PATCH8 and the Mobile Client I am using is of SP6 P2. When the Mobile Client SP06 patch is deployed on the device, everything works fine, but when the emulator is used for running the application, the emulator crashes. What could be the reason for this?

b) I am trying to deploy the driver deployer for win32 to emulator, so that I can deploy the connector later and use the PIOS printer API for testing on the emulator. The deployment ends with errors. What could be the reason for this?

A.8) The problems described above are fixed as part of SPS06 Patch 03:

a) PDA eSWT emulator crashes on a menu click - this has been solved with SPS 06 Patch 03.

b) PIOS emulator has been included with SPS 06 Patch 03

Note: For more information, see SAP Note 1225246 (SAP NetWeaver Mobile Client 7.1 SPS 06 Patches).

Page 18: Sap Netweaver Faq1

FAQs

Q.9) Which file do we need to upload for the application? Is it the .SDA file or .EAR file? How do we create an .SDA file in the IDE?

A.9) The file that you have to upload for the application is only the .SDA file, not the .EAR or any other file.

In your IDE, work through the following steps to create the .SDA file:

1. Right-click your project.

2. Select the development component.

3. Choose the Build option from the menu.

4. Check if the .SDA file is created in...\gen\default\deploy\folder.

5. Upload this .SDA file (inner SDA) to the DOE.

Q.10) There is a default calendar for input fields of type java.sql.Date. I want to change the format of the date, which is mm/dd/yy by default. How can we do this?

A.10) Support for different date formats on PDA eSWT client has been provided as of SPS 06 Patch 03. For more information, see SAP note 1225246 (SAP NetWeaver Mobile Client 7.1 SP06 Patches).

Q.11) We are using SAP NetWeaver Developer Studio 7.1. In the application being developed, we require the cursor to be on the data entry field. In the SAP NetWeaver Developer Studio, we could not call up the SetFocus API. Currently; the user has to tap the field for the cursor to appear in it. How can we solve this?

A.11) A SetFocus API that can be used within PDA eSWT (OCA) applications is made available as part of SPS 06 Patch 03. For more information, see SAP Note 1225246 (NetWeaver Mobile Client 7.1 SP06 Patches).

Q.12) We launch NWDS with the -clean option to reload plug-in registration and apply the valid default.confdef.xml file. Then when we start to create a new project Local Development itself is not visible, as shown below. How can we proceed?

Page 19: Sap Netweaver Faq1

FAQs

A.12) This might occur if there is no local development track on the system. In order to create a local development, follow the steps below (by default, one is always created automatically, but you can create more by following the steps below):

Step 1

Select this option to create new local development track

Select this option to create new local development track

Step 2

Select this option to create new local development track

Select this option to create new local development track

Step 3

Put a name for the track and Press finishPut a name for the track and Press finish

If the archive pool does not contain a My Component SC, follow the steps described above, and then complete the wizard. Now go to the DTR perspective to check whether or not the SC has been created.

Page 20: Sap Netweaver Faq1

FAQs

Q.13) We have tried to configure the NWDI track to develop SAP NetWeaver Mobile 7.1 applications for laptops. We have followed the instructions on help.sap.com, but when we try to activate the mobile DC from the CBS activation view in NWDS, the following error appears in cbs-build.log:

“java.lang.UnsupportedClassVersionError: com/sap/tc/buildplugin/DefaultPlugin (Unsupported major.minor version 49.0)”. What is the cause of this error?

A.13) This error occurs when you try to run Java classes that were built using JDK 1.5 in a JRE of version 1.4.

To solve this issue, change some settings in the Component Build Service (CBS) of NWDI and adapt the 7.1 tracks:

1. Change the build_tool_jdk_home for the CBS to point to a JDK 1.5.

2. If not yet set, set the default jdk_home_path to a 1.4 JDK so that all 1.4 tracks work as well.

3. Add another jdk_home_path, for example JDK1.5_home=C: \..., to the jdk_home_paths.

4. In CMS WebUI Landscape Configurator, edit the build variant for all tracks relevant for 7.10 and add the build option com.sap.jdk.home_path_key to point to the defined JDK1.5_home.

The following document contains some descriptions on how to do this:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7014086d-3fd9-2910-80bd-be3417810c6f

For points one to three above, use step 3.2 in the document and for point four, use step 4.4 (as mentioned in the above document).

When all these steps have been followed, the CBS works for 7.10 tracks and 7.00 tracks.

For more information, see the following documents:

http://help.sap.com/saphelp_nw70/helpdata/EN/53/75b3407e73c57fe10000000a1550b0/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/EN/b5/7a5e4088dc0272e10000000a155106/content.htm

Q.14) We have configured the NWDI server as the development runtime system for deployment, but when we try to deploy the .SDA file, we receive an error stating that it cannot find a suitable container for deployment. What could be the reason for this?

A.14) You have to deploy NWMADMIN.sca to your target runtime system in order to provide the Mobile container.

For more information, see the following document:

http://help.sap.com/saphelp_nwmobile71/helpdata/en/c3/e21f7e4aa34b36bf3b0730bdc98764/content.htm

Note: Check if NWMADMIN.sca is deployed in the target system.

Q.15) Is it possible to import the DO model to a local project?

A.15) Importing the DO model to a local project is not supported. You need to create a DC project first and then import the model.

Page 21: Sap Netweaver Faq1

FAQs

For more information about why the DO model cannot be imported to a local project, see SAP Note 1077196.

Page 22: Sap Netweaver Faq1

FAQs

3. SAP NetWeaver Mobile Client 1. If the application has been installed successfully, what are the conditions under

which the deployed application link is not visible on the home page of SAP NetWeaver 7.1 Mobile Client?

(Or)

We have developed a PDA application and done the server deployment. The application is visible on the emulator but not on the physical device. What could be the cause of this?

2. When MI_RUNNING is set to False in Install.XML (both laptop and PDA), the error message Connection aborted is displayed even after successful deployment. Why does this happen?

3. How can we enable synchronization logs on the SAP NetWeaver Mobile 7.1 client (both laptop and PDA)?

4. How can we transfer documents or pictures from the front end to an SAP R/3 system in SAP NetWeaver Mobile 7.1 (both laptop and PDA)?

5. How can we check for registered devices in SAP NetWeaver Mobile Client folder (both laptop and PDA)?

6. Where do we maintain the registration parameters required for the mobile client (both laptop and PDA) to set up the connection with the DOE?

7. We are using SAP NetWeaver Mobile 7.1 for laptops and MaxDB. We are checking our application but unfortunately we cannot see any data from the client side. How can we check that the data from the middleware was added to the MaxDB on the client? How can we identify why it is not displayed?

8. Is it possible to deploy two different applications within a single synchronization?

9. After the application has been uninstalled on the mobile client, is there a message to inform the mobile client that there is an application pending or installation?

10. Is it possible to different version of the same application during a single synchronization?

11. In SAP NetWeaver Mobile 7.1 (on PDA), the screen automatically goes to the application launcher after completion of the synchronization. We want to return to the original screen. How can we do this? For example: The user enters the data on the screen, chooses Save, and then selects Synchronize. After clicking Done on the Synchronization screen, the screen should return to the data entry screen instead of the application launcher screen.

12. We want to make a table element invisible while another operation happens and then make it visible again, once that operation has been completed. This logic is not executing as expected. The table is still displayed during the operation and then disappears when the operation is completed. What do we need to change?

13. How should we model our views using the OCA layout?

14. How can we log on to the system without going through the dialog box that prompts the user to enter a user name and password every time an administrator screen is launched?

15. How can we configure Single Sign-On on the SAP NetWeaver Mobile PDA Client?

16. Is the Time-Controlled Synchronization feature supported for both laptops and PDAs in SAP NetWeaver Mobile 7.1?

Page 23: Sap Netweaver Faq1

FAQs

17. If an enhanced version of a client application exists in a production landscape, is it necessary to install the enhanced version on all existing productive devices?

18. What happens when you try to create and assign a newer version of an application to existing devices?

19. When users choose the Synchronize button, is it possible to automatically trigger GPRS connection?

20. When an application is launched from the desktop SAP NetWeaver Mobile client icon, a socket exception is shown and the application is not displayed at all. Why does this happen?

21. What happens when multiple devices run multiple versions of an application?

22. Is it necessary to define a new version of the application if the application only requires additional distribution patterns to be defined on the new node attributes?

23. When a new version of a client application is available, what kind of approach should customer follow to roll out the application?

24. Currently the device has status "Registered". We return it to the "Initial" status and then try to register it with the same physical client that it was registered with before. When we perform the synchronization with the client, we receive the error message "Logon failed. Device ID or physical ID invalid". After this happens, the only thing we can do is completely uninstall the client and then install it from the beginning again. What is causing this?

25. When applying any patch to a PDA client, automatic shutdown and restart of client is not happening?

26. What new parameters are being introduced for hiding menu options, buttons and links on a laptop client?

27. How does the data reset work in the SAP NetWeaver Mobile 7.1 Client?

28. When attempting to import data from the storage device in interactive mode, the system cannot upload the files from the data carrier to the mobile client. The following error message is displayed Invalid source location: Disk meta file not present at C:\Program Files\SAP\SAP NetWeaver Mobile Client\DISC_SYNC. What is causing this and how can we solve it?

29. I followed the instructions in the migration guide and imported the data objects. The mi_meta.xml file is created and the merepmeta.xml is changed. We uploaded the generated .SDA file and installed it on the SAP NetWeaver Mobile 7.1 client. When we clicked the application link, nothing happened. We restarted the client (using shutdown.bat and startserver.bat) and clicked the same link. A Java error occurred: ServletException with rootcause NoClassDefFoundError. What is causing this error?

30. In which file should we add the configurations parameters for laptops and PDAs?

Page 24: Sap Netweaver Faq1

FAQs

Q.1) If the application has been installed successfully, what are the conditions under which the deployed application link is not visible on the home page of SAP NetWeaver 7.1 Mobile Client?

(Or)

We have developed a PDA application and done the server deployment. The application is visible on the emulator but not on the physical device. What could be the cause of this?

A.1)

Reason 1. If the role SAP_DOE_ALL_APP_VISIBLE is missing for the user on the DOE system, then the application link is not visible on the home page.

Solution 1. Add the role via agents in the NWM portal. You should also perform a delta download for the following data objects in the SAP BASIS 7.10 software component version (SWCV):

1. USERDETAILS

2. USER_AUTHORIZATION

Reason 2. The application link is not visible because of the user authorization issue. Check whether the SAP BASIS 7.10 software component version is assigned to the device or not.

If the SAP BASIS 7.10 software component version is not assigned to the device, then follow either of the steps specified below (2a or 2b):

Solution 2a. Disable the authorization check on the mobile client

(For PDAs)

This can be done by creating a configuration.properties file in the \MI\Settings\ folder with the entry com.sap.tc.mobile.cfs.deploy.check_authorizations=false. Stop and start the client. The file is consumed, the authorization check is disabled, and then the application is visible in the application launcher.

(For laptops)

Add the parameter com.sap.tc.mobile.cfs.deploy.check_authorizations=false to the default.properties file in the \MI\Settings\ folder. Stop and start the client. The file is consumed, the authorization check is disabled, and then the application is visible in the application launcher.

Solution 2b. Assign the authorization-related SWCV to the device (in the NWM portal)

In the NWM portal, go to the DMSWCV tab in Device Management. Manually assign the SWCV containing the authorization data objects (SAP BASIS 7.10). Trigger an extract. Synchronize the device. The authorization objects are now available on the device. The application appears in the application launcher.

Reason 3. If the installed client version and the NWMCLIENT.SCA version uploaded in the DOE are different, even then the application link is not visible on the home page.

Solution 3. Upload the NWMCLIENT.SCA (same version of the client) to the DOE using transaction SDOE_UPLOAD_ARCHIVE.

Q.2) When MI_RUNNING is set to False in Install.XML (both laptop and PDA), the error message Connection aborted is displayed even after successful deployment. Why does this happen?

A.2) The GUI and the server part of the SAP NetWeaver Mobile 7.1 client communicate using an HTTP-based connection. As a result, the GUI can only receive information after it has sent a request to the SAP NetWeaver Mobile 7.1 client. Unfortunately, the SAP NetWeaver Mobile

Page 25: Sap Netweaver Faq1

FAQs

7.1 client shuts down the service when the communication model is not using it and thus the client is not able to notify the GUI, resulting in an error message.

Q.3) How can we enable synchronization logs on the SAP NetWeaver Mobile 7.1 client (both laptop and PDA)?

A.3) You can enable synchronization logs for the SAP NetWeaver Mobile 7.1 client by adding the parameters below to the default.properties file present in the Settings folder (NW Mobile Home Folder → Settings → Default.properties)

• com.sap.tc.mobile.sync.dumpInboundInFile=true

• com.sap.tc.mobile.sync.dumpOutboundInFile=true

Note: The synchronization logs should not be enabled the whole time because they occupy an increasing amount of space and affect the performance of the mobile client. The synchronization logs should be enabled only when required. They should be enabled only when there are errors (synchronization logs are required only for analysis of the problem).

For more information about configuration parameters, see the link below:

SAP Note number: 1312866

http://help.sap.com/saphelp_nwmobile71/helpdata/en/45/2605c71fdb4c2ce10000000a1553f6/frameset.htm

Q.4) How can we transfer documents or pictures from the front end to an SAP R/3 system in SAP NetWeaver Mobile 7.1 (both laptop and PDA)?

A.4) This can be achieved by creating a field (type: binary or text memo) in the data object (DO). This allows the storage of unstructured data, such as PDFs, BMPs, or any attachments in this single field of a DO node.

For more information, see the link below:

https://www.sdn.sap.com/irj/scn/wiki?path=/display/mobile/Create+applications+using+Binary+Memo+and+Text+Memo+in+NetWeaver+Mobile+7.1

Q.5) How can we check for registered devices in SAP NetWeaver Mobile Client folder (both laptop and PDA)? A.5) To check for the registered device name, go to the SAP NetWeaver Mobile Client folder (NW Mobile 7.1 home folder) → Settings folder → open the MobileEngine.config file. In the MobileEngine.config file, check for the configuration parameters detailed below: Name = Device Name com.sap.tc.mobile.cfs.conf.spi.deviceid = (Device ID generated for the device) com.sap.tc.mobile.cfs.registry.already_registered = True/false If the parameters mentioned above are present in the MobileEngine.config file, then the device is registered. Q.6) Where do we maintain the registration parameters required for the mobile client (both laptop and PDA) to set up the connection with the DOE?

A.6) To maintain the registration parameters, such as the device name, proceed as follows:

1. In the DOE, go to transaction SDOE_DEV_REGISTER.

Page 26: Sap Netweaver Faq1

FAQs

2. Choose Change Configuration.

3. Now check for the NAME field, which is STANDARD, and select the For Register and Mandatory checkboxes. You can also select other fields, such as device type, depending on your requirements and make sure that you select these two checkboxes.

4. Choose Save and then choose Freeze Configuration.

Q.7) We are using SAP NetWeaver Mobile 7.1 for laptops and MaxDB. We are checking our application but unfortunately we cannot see any data from the client side. How can we check that the data from the middleware was added to the MaxDB on the client? How can we identify why it is not displayed?

A.7) You can install SQL Studio and check the table for entries starting with an M followed by a number with your root node name; the same applies for the child node as well. If you see that the data is present, check whether the BIND method is written for the table in either the INIT or the supply function.

If all the table bindings and supply functions are in place as mentioned above, then check if the application that is being used is working with the correct version of the data object. It often happens that you change the data object in the DOE, regenerate it, but forget to reimport the new version to the IDE. Q.8) Is it possible to deploy two different applications within a single synchronization?

A.8) Yes, you can deploy two different applications within a single synchronization.

Q.9) After the application has been uninstalled on the mobile client, is there a message to inform the mobile client that there is an application pending for installation?

A.9) No message is displayed on the mobile client to state that the application is pending for installation.

The status Application Pending can be seen in the NWM portal on the Mobile Components Tab (the deployment status is installation pending on the device).

Note:

(For laptops) You can check the status of installed applications (status displayed as Installed) on the mobile client .To check the status on the mobile client, go to Information view → Installed Applications tab.

(For PDAs) You can check the status of the installed applications by choosing the following path: Menu → Manage Device → Information → Installed Applications

Q.10) Is it possible to deploy different versions of the same application during a single synchronization?

A.10) You can deploy two different versions of an application. Both versions are downloaded to the client and the older version of the application is installed first. However, when the client finds out that there is another version of the same application, it uninstalls the older version and installs the newer version in one single synchronization.

Note: The application installed acknowledgement goes to the DOE only during the second synchronization because deployment of the application happens only after the synchronization.

Page 27: Sap Netweaver Faq1

FAQs

Q.11) In SAP NetWeaver Mobile 7.1 (on PDA), the screen automatically goes to the application launcher after completion of the synchronization. We want to return to the original screen. How can we do this? For example: The user enters the data on the screen, chooses Save, and then selects Synchronize. After clicking Done on the Synchronization screen, the screen should return to the data entry screen instead of the application launcher screen. A.11) This feature, returning to data entry instead of the application launcher screen, is not entirely possible. Before navigating to the Synchronization UI, the system closes the application. It cannot go back to the same view from which the user triggered the synchronization. This is because the user has navigated to the view according to the application logic. In addition, the data bound to the UI is created after executing some custom code. Q.12) We want to make a table element invisible while another operation happens and then make it visible again, once that operation has been completed. This logic is not executing as expected. The table is still displayed during the operation and then disappears when the operation is completed. What do we need to change?

A.12) The mobile UI component design is such that all the events get executed just before rendering the UI and the UI is not rendered after each event. Therefore, if you set the visibility to NONE and then to VISIBLE in the same method, the system cannot see any difference even though those actions are being executed. So the flickering functionality that you expect may not work. One possibility could be to display a status message once the reset has been done.

Q.13) How should we model our views using the OCA layout?

A.13) You need to heed the following points when modeling a view using the OCA layouts:

1. The flow layout is calculated based on the fixed width for each UI element.

2. In the grid layout, each grid column has a fixed width depending on the number of columns.

3. We do not recommend using separate transparent containers for labels and texts.

Q.14) How can we log on to the system without going through the dialog box that prompts the user to enter a user name and password every time an administrator screen is launched?

Page 28: Sap Netweaver Faq1

FAQs

A.14) You can eliminate the need to log on to the system every time by configuring the Single Sign-On (SSO) feature. See the links below that explain how to configure SSO for SAP NetWeaver Mobile 7.1:

http://help.sap.com/saphelp_nwmobile71/helpdata/en/96/61b177267f4e87878794dca984b3d6/frameset.htm

http://help.sap.com/saphelp_nwmobile71/helpdata/en/4d/3f1a998b464036b8c52c073f38e12b/frameset.htm

http://help.sap.com/saphelp_nwmobile71/helpdata/en/ca/cd45019a2f4ee78749c8bbe0b72269/frameset.htm

Q.15) How can we configure Single Sign-On on the SAP NetWeaver Mobile PDA client? A.15) The SAP NetWeaver Mobile 7.11 PDA client supports a new feature: Single Sign-On integration based on SAP logon tickets. This feature is a pure online functionality; it is only available in cases where the mobile client is connected to a SAP logon ticket issuing system and to the DOE. The SAP logon ticket is used for the following actions:

1. Online user authentication 2. Synchronization

System landscape prerequisites:

1. Mobile client version: 7.11 2. DOE version: 7.11 3. Ticket issuing system: SAP NetWeaver Portal (for example)

• The user must have a user account on the portal server with the same user

ID as in the DOE. • The DOE has to be configured to trust SAP logon tickets that are issued by

the portal server. • The portal has to be configured to issue SAP logon tickets. • The portal has to be configured to support authentication mechanism via

user ID and password. In addition, the SAP NetWeaver Mobile 7.1 client's Web server on the mobile device has to belong to the same domain or sub-domain as the portal server.

The following properties have to be maintained accordingly before the Mobile client is started. To do this, create a file named configuration.properties and add the parameters listed below. Once the file is created, place this file in the Settings directory of the client. Connection properties:

• com.sap.tc.mobile.sync.http.url=<URL> SAP logon ticket support properties:

• com.sap.tc.mobile.cfs.sso.SAPLogonTicketSupportEnabled = true/false • com.sap.tc.mobile.cfs.sso.SAPLogonTicketRequestURL = <URL for ticket-issuing

system>

Q.16) Is the Time-Controlled Synchronization feature supported for both laptops and PDAs in SAP NetWeaver Mobile 7.1?

A.16) The Time-Controlled Synchronization feature does not support PDAs and only supports laptops in SAP Netweaver Mobile 7.1.

Page 29: Sap Netweaver Faq1

FAQs

Q.17) If an enhanced version of a client application exists in a production landscape, is it necessary to install the enhanced version on all existing productive devices?

A.17) If an enhanced version of a client application exists in a production landscape, it does not have to be installed on all existing production devices. The devices can continue to use the older version of the application.

Q.18) What happens when you try to create and assign a newer version of an application to existing devices?

A.18) If you make changes to the data model that involves adding new data objects or nodes, you must reimport the model to the SAP NetWeaver Developer Studio. This means that a newer version of the application must be created and assigned to existing devices without affecting the existing production devices.

In addition, when new nodes or node attributes are added to the model, doing a delta download to get data for these attributes in the DOE will not send any data to devices running the older version of the application. If a new version of an application is assigned to a device, only the ‘delta’ data is sent to the device.

CAUTION:

It is the responsibility of the application developer to ensure that a different version of the application is created and deployed to the DOE. If the application is changed without changing the version number, then existing devices stop receiving the data from the DOE. This is because data is sent to devices based on the version of the data object and the version of the application. Devices that work on the old version of the data objects will not receive any data.

Q.19) When users choose the Synchronize button, is it possible to automatically trigger GPRS connection? A.19) Currently, this feature is not supported by SAP NetWeaver Mobile 7.1. Q.20) When an application is launched from the desktop SAP NetWeaver Mobile client icon, a socket exception is shown and the application is not displayed at all. Why does this happen?

A.20) This exception usually occurs when the SAP NetWeaver Mobile Client icon on the desktop is accidentally clicked more than once. In such cases, more than one instance of the client tries to bind to a port and the exception is generated.

Solution:

1. Make sure that the client shortcut cannot be invoked twice.

2. Alternatively, close all the duplicate running instances of the client.

Q.21) What happens when multiple devices run multiple versions of an application?

A.21) In the event of multiple devices running multiple versions of an application, the data object message structures are generated according to the version used by each device. This ensures that each device gets only the data relevant for the application version that it is running.

Page 30: Sap Netweaver Faq1

FAQs

Q.22) Is it necessary to define a new version of the application if the application only requires additional distribution patterns to be defined on the new node attributes?

A.22) If the application only requires additional distribution patterns to be defined on the new node attributes, then you have to define a new rule in the distribution model (DM). In this case, a new version of the application is NOT absolutely necessary because this is only a change in distribution logic and not in the model.

Q.23) When a new version of a client application is available, what kind of approach should customers follow to roll out the application? A.23) When a new version of a client application is available, customers can follow a phased approach to roll out the application. This can include first assigning the new version of the application to some existing devices or to a set of new devices. The other devices continue to run the older version. In order to achieve a phased roll-out of the application, the new version of the application has to be assigned to the device without removing the assignment of the existing version.

Caution: When assigning a new version of the application, do not remove the assignment of the older version. This result in the system sending deletes to the device for all existing data. You must assign the newer version of the application in addition to the older version. Unless there is a change in the DM SWCV, you should not remove the assignment of the DM SWCV for the devices. If this approach is followed, the existing devices continue to run the older version of the application and they can be upgraded to the new version of application depending on the business requirements. If the new version of the application is assigned to the device profile for the existing devices, then all the devices are upgraded to the new version. In this case of following a Big Bang approach, we recommend that the application is first tested as a test application before assigning it to the devices because all devices will be upgraded at once when it is assigned.

When there is an older version on the handheld device, to upgrade the application to new version, proceed as follows:

1. Use transaction SDOE_UPLOAD_ARCHIVE to upload the new application version MCD to the DOE.

2. In the NWM Admin and Monitoring Portal, go to device administration, select the required device, and assign the new MCD to the device (The MCDs there have the status “Install pending”.

3. When the end user synchronizes the device with the DOE, the “older application version” receives a delete request from the DOE and it is uninstalled from the device. When the user synchronizes for the second time, the “new application version” is installed on the device.

Q.24) Currently the device has status "Registered". We return it to the "Initial" status and then try to register it with the same physical client that it was registered with before. When we perform the synchronization with the client, we receive the error message "Logon failed. Device ID or physical ID invalid". After this happens, the only thing we can do is completely uninstall the client and then install it from the beginning again. What is causing this?

A.24). The problem is that the client has not set the device registered parameter to “FALSE” after the synchronization. It is still referring to the device ID that was registered but cannot find it because the device is already set to the “initial” status.

Page 31: Sap Netweaver Faq1

FAQs

Q.25) When applying any patch to a PDA client, automatic shutdown and restart of client is not happening. What could be the issue?

A.25) This is resolved with SPS 06 Patch 03. Make sure that the following configurations are maintained:

1. The patch being applied should be set as "Silent" in the Install.XML file.

2. Parameter com.sap.tc.mobile.cfs.ci.dosoftreset should be set to true in the configuration.properties file in the settings folder of the SAP NetWeaver Mobile 7.1 client.

For more information, see SAP Note 1225246 (SAP NetWeaver Mobile Client 7.1 SPS 06 Patches).

Q.26) What new parameters are being introduced for hiding menu options, buttons, and links on a laptop client?

A.26) The following new parameters are being introduced for hiding menu options, buttons, and links on a LAPTOP client. These UI elements can be made visible or invisible by setting the parameters mentioned below to true or false respectively. These parameters should be added to the defaults.properties file in the settings folder of the SAP NetWeaver Mobile Client folder:

• com.sap.tc.mobile.cfs.LoginPage.DisplayNewUserButton

• com.sap.tc.mobile.cfs.HomePage.DisplayManagePasswordsLink

• com.sap.tc.mobile.cfs.SettingsPage.DisplayTraceMenu

• com.sap.tc.mobile.cfs.HomePage.DisplaySettingsLink

• com.sap.tc.mobile.cfs.HomePage.DisplaySynchronizeButton

Q.27) How does the data reset work in the SAP NetWeaver Mobile 7.1 Client?

A.27) Data reset can be done in device management screen. It is called device recovery.

Once the Device Recovery process has been triggered, the 'Z' message for all objects can be seen in the outbound queue.

Once the process has been triggered, the DOE automatically starts processing the distribution of data again. Therefore, it could happen that in a single synchronization your device is reset and refilled with data.

Note: 'Z' messages are Zap messages used to reset the data table of a particular object on the client.

Q.28) When attempting to import data from the storage device in interactive mode, the system cannot upload the files from the data carrier to the mobile client. The following error message is displayed Invalid source location: Disk meta file not present at C:\Program Files\SAP\SAP NetWeaver Mobile Client\DISC_SYNC. What is causing this and how can we solve it?

A.28) In the case of interactive mode, you specify the path up to the disk required, that is, the number of the disk inside the Disk Sync home folder.)

For example, to process disk 1, you specify the following path:

C:\Program Files\SAP\SAP NetWeaver Mobile Client\DISC_SYNC\1

Page 32: Sap Netweaver Faq1

FAQs

Q.29) I followed the instructions in the migration guide and imported the data objects. The mi_meta.xml file is created and the merepmeta.xml is changed. We uploaded the generated .SDA file and installed it on the SAP NetWeaver Mobile 7.1 client. When we clicked the application link, nothing happened. We restarted the client (using shutdown.bat and startserver.bat) and clicked the same link. A Java error occurred: ServletException with rootcause NoClassDefFoundError. What is causing this error?

A.29) The error occurs because the JSP application has not been precompiled. The SAP NetWeaver Mobile client framework starts with JRE and not JDK. So for compilation of JSP, either precompile it or change the JAVA_HOME in the startserver.bat file to point to the JDK.

Q.30) In which file should we add the configuration parameters for laptops and PDAs?

A.30)

For the laptop client: The configuration parameters for the laptop mobile client should be added to the default.properties file.

Note: The configuration parameters in default.properties have higher priority than the configuration parameters in the Mobileengine.config file.

For the PDA client: The configuration parameters for the PDA mobile client should be added to the Configuration.properties file.

Note: The configuration parameters in configuration.properties have higher priority than the configuration parameters in the Mobileengine.config file.

Page 33: Sap Netweaver Faq1

FAQs

4. Data Orchestration Engine (DOE)

1. When trying to activate the back-end adapter for a data object in SDOE_WB, the system displays the following message: No backend key fields defined for node. What is causing this and how can we solve it?

2. While trying to activate the standard data object USERDETAILS, the following message is displayed: You do not have authorization. What is causing this and how can we solve it?

3. Can we remove an MCD from the DOE? 4. Is it correct that untested MCDs should be assigned only to test devices? Does the

data synchronization work correctly if the MCDs have the status Untested MCD?

5. What are the criteria to determine that we can change the status of the mobile components to "Tested Successfully"?

6. The synchronization between the DOE and the back-end system works well, all the relevant information was downloaded to the DOE but when we view the application on the client, no data is displayed.

a. How can we check if the data was downloaded to the client database?

b. What could be the reason why the data is not displayed?

7. What is the purpose of SMQ2? What is this transaction usually used for? What does status Stop mean? What should we do with queues with status Sysfail? Can we delete queues shown in SMQ2?

8. How is the data distributed? What are the steps to perform the initial download?

9. How can we Control the time zone values from the middleware?

10. What is the purpose of transaction SDOE_CLEANUP?

11. What steps do we need to be taking in the scenario where the back-end system is changed and no upgrade is done?

12. How does the initial rule works?

13. How does rule evaluation work? What happens during MCD deployment?

14. Pictorial view: Rule wizard.

15. How do we set the HTTP timeout parameters?

16. How do we perform a delta download and how does it work?

17. How can we enable back-end triggering of data using the instance push?

18. Under which conditions “XSLT_ROOT_ERROR” might occur? How can we fix this error?

19. When we create setup package (with data), is data lost?

20. Device Registration Criteria: Scenario: A user is trying to synchronize the client for first time and enters a specific device name in the settings. After successful synchronization, the client has another device name on the Settings page and in the DOE it has synchronized using this device name. The new device name is the oldest available in the DOE, it is not a random one. What could be causing this?

21. While trying to assign or unassign a DMSWCV to a device that is created in device administration, the system terminates with the following message: The current ABAP

Page 34: Sap Netweaver Faq1

FAQs

program "SAPLSMMW_STRWRAPPER_APIS" had to be interrupted because it contains a statement that cannot be executed

22. How can we delete a distribution model, data object and distribution rule that is no longer required?

23. How can we transport an SWCV and all its components from one server to another server of SAP NetWeaver Mobile 7.1?

24. Why is the order of importing data objects important? What is the correct order for importing objects from a source system to a target system?

25. Is transporting the same object from more than one system a valid scenario? Does the DOE support this scenario?

26. What happens during an upgrade? What are compatible and incompatible changes? What is the modification concept?

27. What is version-conflict detection and resolution?

28. Is it possible to delete an SWCV in the DOE?

29. How should we handle the mobile application attribute if the application is migrated from SAP MI 7.0?

30. What are the implications of editing an SWCV to define a uses relationship?

31. What are the implications of performing the following operations on data objects?

1) Adding a node

2) Adding a node attribute at the end of the node

3) Editing a node attribute (changing the data type, length, or properties such as back-end field or back-end key field)

4) Deleting a node

5) Deleting a node attribute

6) Adding an association

7) Deleting an association

32. What are the implications of performing following operations on Distribution Model :

1) Add new rule

2) Add new dependency

3) Edit a rule

4) Delete a rule

5) Delete a dependency

33. What are the implications of performing following operations on Back-end Adapters -

1) Adjust adapter and Data object

2) Add a new backend mapping

3) Remove backend mapping

34. How to add own BAdi exits/enhancement spots to the backend adapter?

35. I am creating a new row in my JSP app. All work fines, I record the header and the child in the local BD. But when sync, appear an error in the queue (smq2): "Exception condition "INVALID_MBO_TRANS" raised." Why?

Page 35: Sap Netweaver Faq1

FAQs

36. There is a role SAP_DOE_DEVELOPER and a user can delete regenerate etc the various objects of Software component version, as we have big team of developers working on the system we want to categorize them in two groups, developers who have complete access to his and developers who have display only access. How to give display permission only?

37. When trying to activate a data object, the following error appears in SMQ2 - "Unable to activate structure”?

38. It is possible to check the flag on a data object to keep an instance locally after it has been uploaded to the middleware. But what is the concept behind it concerning removing unnecessary data instances? What is the concept about implementing logic to remove locally stored data (due to business logic)?

39. After importing the model from the DOE, the generated MEREPMETA.XML is wrong?

40. BAPI wrappers not getting imported as Data Objects?

41. There is a short dump in the DOE - exception condition "INVALID_RECEIVER_STORE" raised, what might have gone wrong?

42. After transporting Backend adapters, the generation of the imported adapters at the target system fails with a SYSFAIL in the queue. The error is displayed as 'Unable to uniquely determine data object’?

Page 36: Sap Netweaver Faq1

FAQs

Q.1) When trying to activate the back-end adapter for a data object in SDOE_WB, the system displays the following message: No backend key fields defined for node. What is causing this and how can we solve it?

A.1) If the back-end key fields are not maintained on the Node Attributes tab, then the following message is displayed: No back-end key fields defined for node.

To maintain the back-end key fields, proceed as follows:

1. In the data object, navigate to the node structure.

2. Select that node structure and navigate to the Node Attributes tab. Select the checkbox BE Key Field for the required field name.

Activate the back-end adapter again; this time it should be activated successfully.

Q.2) While trying to activate the standard data object USERDETAILS, the following message is displayed: You do not have authorization. What is causing this and how can we solve it?

A.2) This problem is caused by missing authorizations. Assign the required roles to the user and then try downloading the data to the user details.

For more information about which roles have to be assigned, see the document below: http://help.sap.com/saphelp_nwmobile71/helpdata/en/45/60eff9404b6628e10000000a1553f6/frameset.htm

Q.3) Can we remove an MCD from the DOE? A.3) Currently, the DOE does not allow removal of any MCDs.

Q.4) Is it correct that untested MCDs should be assigned only to test devices? Does the data synchronization work correctly if the MCDs have the status Untested MCD?

A.4) Yes, untested MCDs can only be assigned to test devices and not to any other devices. Data synchronization works correctly for MCDs with the status Untested MCD, but only for test devices.

Q.5) What are the criteria to determine that we can change the status of mobile components to Tested Successfully?

A.5) The administrator can test an untested MCD by assigning it to a test device. Once the MCD has been deployed on the client and if the application is working correctly, then the administrator has to manually change it to the status Tested Successfully.

Q.6) The synchronization between the DOE and the back-end system works well, all the relevant information was downloaded to the DOE but when we view the application on the client, no data is displayed.

6a. How can we check if the data was downloaded to the client database?

6b. What could be the reason why the data is not displayed?

A.6) 6a)

1. For MaxDb: Using MaxDB SQL Studio software, the data can be checked.

2. For Db2e: Using Hex Editor, the data can be checked.

3. For Mindb: Using Database visualiser, the data can be checked.

Page 37: Sap Netweaver Faq1

FAQs

6b)

1. If the data is present in the data folder (present in the SAP NetWeaver Mobile Client home folder), then you should check the application.

2. If the data has not been downloaded from the DOE to the device, proceed as follows:

1. Check whether or not a distribution model has been created for the data objects.

2. Check if the data objects are active and were generated without any errors.

3. Check if all the relevant data is first downloaded to the CDS or not.

4. Then check on the Rule Administration screen in the NWM portal if the rules are active or not. If they are not, activate them.

5. If the rules are active and even then the data is not downloaded, then check whether or not the DMSWCV is assigned to your device in Device Administration. In addition, check that the DMSCV is operational (in the NWM portal).

6. If it has not been assigned, then assign it and make sure that the DMSCV is in operational mode. Then only your data is downloaded.

7. If the DMSWCV is assigned and in operational mode and the data is still not downloaded to the device, go to the NWM portal Device Administration → Select the device → Pending Extracts.

On the Pending Extracts screen, make sure that no instances are present. If there are any pending extracts, choose Trigger Pending Extracts. After triggering the extract, the data should be downloaded to the device.

3. In the NWM portal, on the Device Administration screen, enter the device name and see if the outbound queue is filled with data. If the table only contains elements of 53 bytes or is empty, there are issues in the configuration steps mentioned in answer 6b) step 2. Either there is no bulk rule to send items to the table or the rules are not active in the NWM portal.

Q.7) What is the purpose of SMQ2? What is this transaction usually used for? What does status Stop mean? What should we do with queues with status Sysfail? Can we delete queues shown in SMQ2?

A.7) SMQ2 is the standard SAP transaction to view the qRFC queues and also to view the queues that have become stuck for some reason.

In SMQ2, you can unlock the queues that have the status Stop or Sysfail.

Stop simply stops the processing of the queue. After the Stop status, the latest LUW can be picked up for debugging by setting the queue status to Unregistered.

Sysfail happens if the processing of the flow cannot happen because an error has occurred during processing of the code lines or the configuration is missing.

Note: The queues that have the status Sysfail should never be deleted until the cause of the failure has been found. If the queue is deleted without identification of the problem, there may be data loss. In this case, the entire data has to be reprocessed.

Q.8) How is the data distributed? What are the steps to perform the initial download?

A.8) The distribution of data to the devices is done as follows:

Back-End System → Consolidated Data Store (CDS) of the DOE → Distribution Model Evaluation → Mobile Devices

Page 38: Sap Netweaver Faq1

FAQs

(When an initial load is performed [back-end system → CDS], the data is persisted in the CDS. After the data has been downloaded to the CDS, the rules should be activated. Once the rules are active, the DM evaluation event is triggered; this in turn triggers the data to be sent to the device [distribution model evaluation → mobile devices]).

Note: If no data is present in the CDS or if the rules are not active, the data is not distributed to the mobile devices.

For more information about the distribution model, see the link below:

http://help.sap.com/saphelp_nwmobile71/helpdata/en/1b/0e3d52492a45b79b9701bd5ced9799/frameset.htm

To perform the initial download, you need to proceed as follows:

1. Go to transaction SDOE_LOAD in the DOE.

2. Fill your SWCV and trigger it for all the data objects.

3. Run transaction SDOE_WB and check if the data has arrived in the CDS of the DOE.

Q.9) How can we control the time zone values from the middleware?

A.9) By assigning the time agent parameters to the device, you can control the value of the time zone from the middleware.

Note: If time zone parameters are assigned to a device, the device is in synchronization with the time zone that the middleware is located in.

Steps to be followed:

In the NWM portal:

1. Create a device.

2. Assign the TIME mobile component to the device.

3. Assign the Agent.dll (AGENT_DLL) mobile component to the device.

4. Add the time agent parameters on the Agents tab:

a. AGENT_HISTORY_INTERVAL=1

b. AGENT_MODE=ON

c. AGENT_HISTORY=TRUE

For more information about the parameters, see the following link:

http://help.sap.com/saphelp_nwmobile71/helpdata/en/46/4a71c1bf2751e7e10000000a114a6b/frameset.htm

After following all the steps mentioned above, follow the steps below on the mobile client:

1. Register the device (created in step one) with the mobile client.

2. Synchronize from the client.

3. The agent sub-folder is created in the NW Mobile 7.1 Home folder.

4. In Agent → Config → Time.properties, the parameters assigned in step three should be present.

Once the synchronization is complete, the device synchronized with the time zone that the middleware is located in.

Page 39: Sap Netweaver Faq1

FAQs

Q.10) What is the purpose of transaction SDOE_CLEANUP?

A.10) Transaction SDOE_CLEANUP is used to clean up the entire SWCV runtime data. This resets the SWCV so that the data can be re-downloaded and used from scratch.

Note:

1. We recommend using this transaction only in development or test systems because you keep changing the model during development or testing which may cause the runtime data to become inconsistent.

2. We do not recommend using this transaction after the model has gone live in your production system.

Q.11) What steps do we need to take in the scenario where the back-end system is changed and no upgrade is done?

A.11) In the case of changing your back-end system, all that is required is a delta download of the affected data objects. To make sure that too many delete messages are not sent to the devices as a part of the delta load, unassign the DMSWCVs from the devices first (unassigning a DMSWCV from a device sends zap messages for each data object associated with that DMSWCV, however, it does not clean up the outbound queue if it already contains messages). When the delta load is finished, assign the DMSWCVs to the devices again.

This is equivalent to reinitializing and recovering the devices. To summarize, you have to perform the following steps if your back-end system is changing and most of the data on the middleware is no longer relevant:

Unassign DMSWCVs from the devices.

Perform delta downloads for all the affected data objects.

Assign DMSWCVs to the devices again.

Q.12) How does the initial rule work? A.12) Initial rules work as follows: Let us suppose that the rule has two criteria fields (CF), in which one of the criteria fields is mapped to a constant value and the other is mapped to a device attribute. CF1 equals 123 CF2 equals MOBILE.CATEGORY.ATTR1 and three devices subscribe to this rule. The subscriptions are as follows: -------------------------------- Device CF1 CF2 -------------------------------- D1 | 123 | BLORE D2 | 123 | D3 | 123 | HYD -------------------------------- In this case, the data object instance values are checked for both the criteria fields for devices D1 and D3. Only those instances where CF1 equals 123 and CF2 equals BLORE are sent to device D1 and only those instances where CF1 equals 123 and CF2 equals HYD are sent to device D3.

Page 40: Sap Netweaver Faq1

FAQs

But for D2, only criteria field CF1 is checked against data object values because this device is subscribed only to CF1. So all the instances where CF1 equals 123 are sent to device D2 without considering a value for CF2.

Q.13) How does rule evaluation work? What happens during MCD deployment? A.13) Rule evaluation works as follows: Whenever the rule gets evaluated:

1. First it collects the set of devices to which the DMSWCV is assigned. Note: The rules are defined in the assigned DMSWCV. 2. Then it calculates the subscriptions for each device. Subscription calculation is

based on the rule definition. Example: For device attribute rules, subscription is device attribute values that are mapped to criteria fields. During MCD deployment, the attributes of the device are changed; this action is responsible for triggering the rule evaluation for the device. The rule evaluation does not happen completely, it just identifies whether or not there are any new instances that need to be sent to the devices. Note: If the data object contains a lot of data, the calculation itself takes a long time.

Q.14) Pictorial view: Rule Wizard A.14)

Q.15) How do we set the HTTP timeout parameters? A.15) To set the HTTP timeout parameters, follow the steps described below:

1. Go to transaction SMICM and choose Shift+F1. 2. Select HTTP and choose Service → Change from the menu. 3. Set the parameters Keep Alive (in Sec.) and Max. Processing Time.

Page 41: Sap Netweaver Faq1

FAQs

Q.16) How do we perform a delta download and how does it work? A.16) Delta download from the back-end system:

1. Go to transaction SDOE_LOAD and select the SWCV. 2. Select the data object.

Note: If you want to download all the data objects in the SWCV, you do not need to select the data object .It can be left blank.

3. Select the load type as Delta download. 4. You can leave the configuration in the default setting. (Only if you want to trigger the download of back-end-triggered data objects via the DOE should you deselect the DOE Triggered Adapters only checkbox.) 5. Choose Execute at the top of the screen.

This triggers the download of data asynchronously to the queue. For more information about back-end adapters and loads, see: http://help.sap.com/saphelp_nwmobile71/helpdata/en/88/9e21142beb442b9eae5085e34e813c/content.htm The delta download works as follows:

1. The getList BAPI wrapper is invoked to obtain all the headers. 2. For each of these headers, getDetails is invoked.

Q.17) How can we enable back-end triggering of data using the instance push? A.17)

1. Enter a function module name in the Instance Push Function field. The code for this function module is generated in the middleware system when the back-end adapter is activated.

2. In the back-end code, whenever an instance changes, you can call this RFC-enabled function module to push instances (one by one). (After activation, you can double-click the function module name to navigate to it). You have to fill in the task as either I (insert), U (update), or D (delete) and fill in the data in the tables parameter of the function module.

Q.18) Under which conditions might XSLT_ROOT_ERROR appear? How can we fix this error? A.18) The most likely reason for XSLT_ROOT_ERROR is because the PDA or laptop is sending more data than the middleware can hold for an attribute.

For example: In the middleware and back end, there is a CHAR32 data type attribute and the PDA or laptop is sending more than 32 characters. This results in this error.

1. The only way out is to enter the data again in the client and synchronize with the server. Once the UI validation on the application is done correctly, the error does not occur.

2. You have to delete the queue entry and there is no alternative way to fix the problem.

Q.19) When we create a setup package (with data), is data lost?

A.19) There is no data loss when creating a setup package with data. Even if one record does not reaches the PDA or laptop, the record is still in queue and does not get deleted because it has not received confirmation from client (the client sends a confirmation to the

Page 42: Sap Netweaver Faq1

FAQs

DOE stating that it has received the record, only then does the DOE delete the record from the queue). When the device is synchronized again, the data is sent to the PDA or laptop.

Q.20) Device Registration Criteria Scenario: A user is trying to synchronize the client for first time and enters a specific device name in the settings. After successful synchronization, the client has another device name on the Settings page and in the DOE it has synchronized using this device name. The new device name is the oldest available in the DOE, it is not a random one. What could be causing this? A.20) In the device registration criteria, if the DeviceName (or Name) is not set to mandatory for registration, during synchronization the client picks up the device name (which has the same user) at random and is registered with the DOE. In addition, it does not prompt the user to enter the device name.

To check whether or not the device registration criteria are met, proceed as follows: 1. Go to transaction SDOE_DEV_REGISTER. 2. Set the DeviceName or Name option to mandatory for registration.

Q.21) While trying to assign or unassign a DMSWCV to a device that is created in device administration, the system terminates with the following message: The current ABAP program "SAPLSMMW_STRWRAPPER_APIS" had to be interrupted because it contains a statement that cannot be executed.

A.21) In order to avoid this issue, proceed as follows:

1. Go to transaction SDOE_WB.

2. Select the relevant SWCV.

3. Go to Utilities.

4. Choose Generate Structure Wrapper.

Use this option to generate the structure and then do a syntax check for the data object for which the problem occurs.

Q.22) How can we delete a distribution model, data object, and distribution rule that are no longer required?

A.22) You can delete data objects and DMs only if they are in a consistent state. Before deleting a DM, make sure that the corresponding data object and DM are completely generated. Note:

• We recommend deleting data objects, DMs, and BEAs in the source system and then transporting these changes to other systems. (This is the correct procedure).

• We do not recommend deleting data objects, DMs, and BEAs in target systems.

Q.23) How can we transport an SWCV and all its components from one server to another server of SAP NetWeaver Mobile 7.1?

A.23) Before you transport an SWCV and all its components to another server, make sure that all the components have status Active.

Scenario 1: Proceed as follows:

1. Create a package using transaction SE80.

2. Create a transport request using transaction SE01.

Page 43: Sap Netweaver Faq1

FAQs

3. Select the Workbench Requests request type and specify the appropriate target system and client.

4. Create the data models and assign them to the package created in step 1 and the

transport request created in step 2.

5. Activate all the components.

6. Release the task and release the transport request.

Note: Before releasing the transport request, we recommend performing the complete check using the menu bar option.

Scenario 2:

If the SWCV is saved in a local package and that SWCV has to be transported, the SWCV can be moved to a transport package and can be transported to another server. Proceed as described below to move the SWCV and all its components from a local package to a transport package:

1. Select the SWCV, DOs, BEAs, and DMs that you want to move to a transport package.

2. In the menu option, choose Go To and navigate to Object Directory Entry. On the Display Object Directory Entry screen, go to change mode, change the package name, and assign it to the transport request you created.

Note: The SWCV and all its components should be assigned separately to the package and the transport request.

3. If the components are not active, activate all the components.

4. Release the task and release the transport request.

Caution:

Re-transport of previously-transported versions of DOE objects should be avoided unless specifically recommended by SAP. If an object is to be transported, only the last active version of the object should be included in the transport request. Q.24) Why is the order of importing data objects important? What is the correct order for importing objects from a source system to a target system? A.24) In the target system, the order in which the objects are imported is crucial in determining the consistency of the objects. It is mandatory that when an object is imported, all its dependent objects are already imported and are consistent. Note: The terms source system and target system are used in the example to denote two landscapes. In a scenario where the customer is using an SAP application, the source

Page 44: Sap Netweaver Faq1

FAQs

system would be the SAP system and the target system would mean the customer’s development system. In a scenario involving new development by the customer, the source system denotes the development system and the target system denotes the test/production system. Example If a back-end adapter for a data object is imported before the data object itself, the back-end adapter is inconsistent. This can be corrected by locking the data object in a new request and transporting it again, after which both the data object and back-end adapter would become consistent again. In order to avoid any inconsistencies that arise exclusively due to imports in the incorrect order, it is important that the SWCV and data objects are released first, before the back-end adapters and distribution models are released. Note: There can be other inconsistencies that are not caused by transports in the incorrect order. You must correct these errors in the source system and transport the object again. We recommend that when objects are manually added to a request and released, the following order must be maintained:

1. The data objects are added to a request and released. 2. Separate requests containing the back-end adapters and distribution models are

released. This ensures that the data is consistent in the target system. This also ensures that there are no errors due to the generation of runtime objects.

Q.25) Is transporting the same object from more than one system a valid scenario? Does the DOE support this scenario?

A.25) Transporting the same object from two different source systems is not a valid scenario and leads to inconsistencies in the object in the target system.

The DOE does not support a scenario where there are two or more development landscapes and a single production landscape. If an inconsistency arises due to such a transport, it cannot be resolved from the Workbench.

Q.26) What happens during an upgrade? What are compatible and incompatible changes? What is the modification concept?

A.26) Changes made to objects in an SWCV shipped by SAP are affected if an upgrade for the application is available from SAP.

The changes can be compatible or incompatible. A compatible change to an SWCV is one that does not result in data loss to the existing application. A change is considered compatible if new objects are added and no existing objects are modified. Adding a new data object, creating a new distribution model, modifying an existing data object, and adding new fields to an existing data object are also compatible changes. In addition, there is no loss of data if there is an upgrade shipped by SAP. Any changes made to existing objects that result in data loss are incompatible changes. Examples include removing a node from a data object or changing the data type of a node attribute.

Page 45: Sap Netweaver Faq1

FAQs

The modification concept is also valid for some changes that are compatible with respect to an application. Operations such as adding a node to a data object or adding a new rule or dependency are all compatible and do not result in data loss. However, these operations still represent modifications to the distribution model or data object, and if SAP ships an upgrade for the same object, a conflict would arise.

Note: The data orchestration workbench does not allow changes that affect the application or result in data loss. So operations such as editing a data object node attribute or editing a rule are not allowed because the SWCV that is shipped by SAP is flagged as Released for shipment.

Q.27) What is version-conflict detection and resolution? A.27) When the upgrade is shipped, in the event of object level changes in the customer system, the customer has to choose between the source and target versions of the objects if a conflict is detected. This is because SAP and the customer have modified the same object. If the customer chooses to keep the source (SAP) version, the custom changes are lost. If the target (customer) version is chosen instead, changes shipped by SAP are not available to the customer. Therefore, a “merge option” is also provided. This allows you to retain all changes from the source and all changes from the target in the object, provided the changes are mutually exclusive. Example The example shows the version changes that an object is subject to when custom enhancements are done to the object and SAP ships an upgrade. In this case, the term object refers to data objects, distribution models, and back-end adapters.

Operation System Version Content shipped by SAP SAP SAP0001 Edit a design time object in customer landscape CUS CUS0002 SAP edits the same object SAP SAP0002 Conflict resolution - keep source CUS SAP0002 Keep target CUS CUS0002 Merge CUS CUS0003

At the time of the upgrade, there are two active versions of the same object, SAP0002 and CUS0002, which results in a conflict.

So conflict resolution either retains one of these versions or results in a newer version if the merge option is chosen.

Q.28) Is it possible to delete an SWCV in the DOE? A.28) Yes, it is possible. You can delete an SWCV directly in transaction SDOE_WB. After deleting the underlying objects of the SWCV such as data objects, DMs, and back-end adapters, select the SWCV and right-click it to display the context menu. This menu contains an option to delete the SWCV. Note: SWCV deletion is only possible in the system in which it was created originally; you should not delete the SWCV directly in test and production systems.

Page 46: Sap Netweaver Faq1

FAQs

Q.29) How should we handle the mobile application attribute if the application is migrated from SAP MI 7.0? A.29) When a new data object is created in an SWCV that is backwards-compatible, the mobile application attributes have to be captured separately in the data orchestration workbench. For more information about handling mobile application attributes, see the link below: http://help.sap.com/saphelp_nwmobile71/helpdata/en/cf/091a632525429f85744dc1d6149dd4/frameset.htm Note: If the text file (data object definition file) is imported, you do not have to maintain the mobile application attribute. Q.30) What are the implications of editing an SWCV to define a uses relationship? A.30) The objects in the inherited SWCV are visible in the inheriting SWCV. You can define new distribution rules for these objects. Incompatible: If a uses relationship does not exist in the source system (SAP) and it is defined in the target system (Customer), it is deleted when the next transport is done from the source system and the inheritance information is lost. Q.31) What are the implications of performing the following operations on data objects?

1. Adding a node

2. Adding a node attribute at the end of the node

3. Editing a node attribute (changing the data type, length, or properties such as back-end field or back-end key field)

4. Deleting a node

5. Deleting a node attribute

6. Adding an association

7. Deleting an association

A.31)

1 & 2) After adding the node or node attribute, you have to define the back-end mapping for the back-end fields in the back-end adapter. You have to perform a delta download for the data object to obtain the data from the back-end system and have it in the DOE. If you add only middleware fields, you have to use custom services to populate the data appropriately.

The application developer has to import the model again.

Compatible: The addition of data object nodes or node attributes does not result in data loss for existing devices. On upgrading to the newer version of the application, only the delta data is sent to the devices.

3) Any changes to node attributes that are used in the existing application are incompatible changes. The DOE workbench does not allow such changes.

4 & 5) Deleting a data object node or node attribute results in data loss in the application.

Incompatible change: (DOE workbench does not allow this after the SWCV has been flagged as released.)

6) For existing entries in the CDS, calculation of associated instances is not triggered automatically. We do not support this calculation in SAP NetWeaver Mobile 7.10, therefore this change is incompatible.

7) This change is incompatible.

Page 47: Sap Netweaver Faq1

FAQs

Q.32) What are the implications of performing the following operations on distribution models?

1. Adding a new rule

2. Adding a new dependency

3. Editing a rule

4. Deleting a rule

5. Deleting a dependency

A.32)

1) New rules or dependencies are added if the application requires them to enhance the distribution logic, for example, if newly-added objects are to be distributed.

2) You do not have to import the model again if there are no changes to the data object. If the data object has also changed, you must import the model again. This is a compatible change. You have to activate the new rule in the NWM portal.

3) You cannot edit the criteria fields of a rule. If new criteria fields are required, you must define a new rule. This is the normal behavior of the DOE workbench.

Furthermore, you cannot edit the device binding of a rule if the SWCV is flagged as released. This is an incompatible change and the DOE workbench does not allow it.

4 & 5) These are incompatible changes that result in data loss for existing devices. The DOE workbench does not allow them. Q.33) What are the implications of performing the following operations on back-end adapters?

1. Adjusting adapters and data objects

2. Adding a new back-end mapping

3. Removing back-end mapping

A.33)

1) This operation is required if the back-end interface has changed and the change is to be reflected in the DOE objects. This operation is possible only if the data object and back-end adapter have been created by importing BAPI wrappers from the back-end system.

Incompatible and not allowed by the workbench: The only alternative is to make the changes manually in the DOE workbench. If a new back-end field or back-end structure has been added, you have to add it as a node attribute or node manually in the data object and after activating the data object, manually add the back-end mapping for the new attributes to the back-end adapter. Then you have to perform a delta download to obtain the back-end data for the new fields.

2) Compatible change: You should perform a delta download for the data object to obtain the data for the newly-mapped attributes in the CDS.

3) You cannot remove the mapping for a node attribute that is flagged as a back-end key field, but you can change it to map to a different back-end field that is compatible in type and length. This is a compatible change. Q.34) How can we add our own BAdi exits/enhancement spots to the back-end adapter?

A.34) The enhancement points are clearly defined in the code of the BAPIs. At these enhancements points, the enhancement (implementation) can be done, but you cannot define any new enhancement points.

Page 48: Sap Netweaver Faq1

FAQs

On the back-end adapter screen, enter the name of the enhancement spot. The BADI name, interface name, and the generation framework create a prefined interface definition in line with the structure of the BAPIs used in the adapter. The interface consists of the six methods that can be used for the implementation according to your requirements. The interface methods are classified as Pre and Post mapping methods – wherein you can override the mapping between the data object structure and the BAPI structure defined in the mapping tool. With the BAdi implementation, users can change the mapping patterns for getDetail, Create, and Modify. Q.35) We are creating a new row in our JSP application. Everything works fine, we record the header and the child in the local DB. But when we synchronize, an error appears in the queue in transaction SMQ2: Exception condition "INVALID_MBO_TRANS" raised. What could be causing this to happen?

A.35) The application is referring to the old data object. If the data object was created again or changed, the model import has to be done for this, so that the application gets the latest mbo trans id. You must import the model from the IDE. Therefore, each time the data object is changed, you have to import it from the IDE and the client application should refer to the new version of the data object. Q.36) There is a role called SAP_DOE_DEVELOPER, which contains authorization to delete, regenerate, and so on the various objects in a software component version. We have a large team of developers working on the system, therefore we want to place them in two groups, developers who have complete access to this and developers who have display-only access. How can we assign display authorization only?

A.36) Proceed as follows:

1. Go to transaction PFCG.

2. Copy the SAP_DOE_DEVELOPER role to a custom role.

3. Change the custom role and choose the Authorization tab and choose Change Authorization Data.

4. Open the tree for Mobile Middleware objects.

5. Change all the objects below it so that they contain only display permission in the activities.

6. Save and generate the role.

7. Go back and choose the User tab and perform a User Comparison.

8. Go to transaction SU01, enter the user name, and choose Change.

9. Go to the Roles tab and remove all existing roles.

10. Now add your custom role.

11. Save the user. Log off and log on again.

After assigning display permissions, the system does not allow the users in question to create SWCVs or activate any data object type operations. Q.37) When trying to activate a data object, the following error appears in transaction SMQ2: Unable to activate structure. What could be causing this to happen?

Page 49: Sap Netweaver Faq1

FAQs

A.37) The error Unable to activate structure appears because the data type of some fields has been changed. This is an incompatible change at the DDIC level and leads to loss of data. (If the delta load of the object has already been performed and there is already data, the DDIC displays the information message to the user stating the changes at the structure level. In addition, DDIC provides information in the activation log on how to fix the structure level changes.)

Solution:

1. Go to transaction SE14.

2. Adjust and activate the table.

3. Trigger generation of the data object again. Q.38) It is possible to select a checkbox for a data object to keep an instance locally after it has been uploaded to the middleware. What is the concept behind the removal of unnecessary data instances? What is the concept for implementing logic to remove locally-stored data (due to business logic)?

A.38) When a model is imported into the IDE, many APIs are generated for that data object. One such API, the remove method, can be used to delete the instances.

There is no function on the middleware to delete the instances that have been stored locally. It is up to the customer to delete them. Q.39) After importing the model from the DOE, the generated merepmeta.xml is incorrect. What could be causing this to happen?

A.39) In SAP NetWeaver Mobile 7.1, mi_meta.xml is used instead of merepmeta.xml. So you can ignore the generated merepmeta.xml. Q.40) BAPI wrappers are not being imported as data objects. What could be causing this to happen?

A.40) All the necessary BAPI grammar checks are incorporated and the fix is available in SAP Note 1109252.

You can find a procedure below that provides an overview of the types of BAPI wrappers and guidelines for your reference. BAPI Wrapper Development A BAPI wrapper is a function module more or less like a BAPI and has to follow certain rules to be a BAPI wrapper. Conceptually, a BAPI wrapper has the role of a private method of a business object and resides in a back-end system. That is, a back-end adapter of the data object calls the BAPI wrapper based on the request from a mobile device. Therefore, it is important that each BAPI wrapper contains the expected parameters and behaves as expected. For each business object, you can create and use up to five BAPI wrappers:

a. GetList: Returns a list of business object header data based on the selection criteria specified in the import parameters.

b. GetDetail: Returns one header data from the header data list as the export parameter based on the object key(s) specified in the import parameters. It also returns one or more list item entries associated with the header data.

c. Create: Creates a single business object and returns object key(s). d. Change: Modifies the header and/or items of the specified business object.

The function needs to replace the entire item data with the entries of table parameters.

e. Delete: Deletes the specified business object (including the items).

Page 50: Sap Netweaver Faq1

FAQs

All types of the BAPI wrappers must comply with the following rules: • Processing type of a function module must be remote-enabled module. • Parameter named RETURN needs to be defined as either an export or a tables

parameter if the parameter type is BAPIRET2 structure. • Parameters can only refer to either a structure or a field of a structure (<structure>-

<field>). • Changing parameter cannot be used. • Exceptions cannot be used. • Parameters cannot refer to structures that include other structures: The reference

structure must be a flat structure and fields in the structure cannot refer to types. • Consistency within the business object must be ensured by defining

export/import/table parameters of the five types of BAPI wrappers appropriately. • Commit Work and Wait needs to be executed in the update BAPI wrappers

(Create/Change/Delete). The following diagram describes the interface requirements for each type of BAPI wrapper.

Q.41) There is a short dump in the DOE with the following information: Exception condition INVALID_RECEIVER_STORE raised. What could be causing this to happen?

A.41) The device has been re-initialized on the middleware and the client has not been re-installed. Therefore, the client has a device ID that does not exist on the middleware. You need to re-install the client and start from the beginning again. Q.42) After transporting back-end adapters, generation of the imported adapters in the target system is unsuccessful, there is a Sysfail in the queue. The error is displayed as Unable to uniquely determine data object. What could be causing this to happen?

Page 51: Sap Netweaver Faq1

FAQs

A.42) This problem is resolved in SAP Note 1114730.

Page 52: Sap Netweaver Faq1

FAQs

5. SAP NetWeaver Mobile Administrator

1. The SAP Basis DMSWCV is not operational in the SAP NetWeaver Mobile Administrator. Why?

2. How can we undeploy a Web Dynpro mobile application installed on the SAP NetWeaver Mobile 7.1?

3. What damage is caused if we have done a lot of work with the DOE and have deleted a registered device from the DOE?

4. Do I need to create a device first in the DOE before I can register a mobile client on my laptop or handheld device?

5. Is a support package available that covers the scenario specified below automatically?

Scenario: If an application is modified, the application should be uploaded to the DOE using transaction SDOE_UPLOAD_ARCHIVE, the MCD status set to Tested Successfully and the application assigned to the device.

6. How can we track the queues?

7. The Days not synced option in the System Status Configuration in the SAP NetWeaver Mobile Administrator does not work. We do not receive the expected result. We configured this option to set the system status to Yellow if a device has not synchronized for more than one day, however, the system status does not contain the corresponding warning. What could be causing this to happen?

8. The help documentation describes how to configure parameters in general, but does not detail the function of each parameter. Where can we find the description of the parameters in the system status configuration?

9. No logs and traces were being sent to the DOE server from the PDA eSWT client with MinDB database in spite of the prerequisites below being fulfilled. What could be causing this to happen?

a. Trace is enabled.

b. We explicitly sent the trace from the client by choosing Send Trace.

c. We explicitly sent the trace via the TRACE agent from the SAP NetWeaver Mobile Administrator.

10. How are messages exchanged between the client and the middleware in SAP NetWeaver Mobile 7.1?

11. Is bulk download possible for data objects that are enabled for synchronous extraction?

12. Is there another way to set more device attributes such as CLIENT_FRAMEWORK_VERSION apart from using receiver generation data objects?

13. Are all the subscriptions calculated again for a device during re-assignment of the device to another profile or does this happen only if the application is changed (front-end changes only) in the MCD?

14. There is no troubleshooting guide or SAP note describing how we can ensure that userDetailsRoot and the user authorizations are sent to the client successfully. What steps do we need to take?

Page 53: Sap Netweaver Faq1

FAQs

Q.1) The SAP Basis DMSWCV is not operational in the SAP NetWeaver Mobile Administrator. Why?

A.1) The DMSWCV is not operational because the NWMCLIENT.sca file installed on the DOE has a different version to that installed on the client.

Every time a new client patch is installed, you must upload the NWMCLIENT.sca for that patch to the DOE before starting the client on the local machine or PDA. As of SPS 03, it is mandatory for the DOE and the mobile client. You must perform this step irrespective of whether the device in question is a laptop or a PDA.

Q.2) How can we undeploy a Web Dynpro mobile application installed on the SAP NetWeaver Mobile 7.1?

A.2) To uninstall an application from the client (SAP NetWeaver Mobile7.1), proceed as follows: In the SAP NetWeaver Mobile Administrator:

1. Go to Device Administration.

2. Select the logical device.

3. Go to the Mobile Components tab and choose Manage Components.

4. Unassign the MCD components from the device and choose Save.

On the mobile client:

When the device synchronizes with the DOE server, the application is uninstalled from the client.

Q.3) What damage is caused if we have done a lot of work with the DOE and have deleted a registered device from the DOE?

A.3) If the registered device is deleted from the DOE, the application and associated data is lost from the mobile client.

In order to obtain the application and the application data again, proceed as follows:

1. Re-install the mobile client.

2. Create a new device.

3. Register it again and perform synchronization from mobile client.

Q.4) Do I need to create a device first in the DOE before I can register a mobile client on my laptop or handheld device?

A.4) You need to first create a device (logical device) in the DOE and register it (register your physical device with the logical device created) by choosing SAP NetWeaver Mobile Administrator → Device Administration.

Q.5) Is a support package available that covers the scenario specified below automatically?

Scenario: If an application is modified, the application should be uploaded to the DOE using transaction SDOE_UPLOAD_ARCHIVE, the MCD status set to Tested Successfully and the application assigned to the device.

A.5) There are no support packages available that enable this scenario.

After making the necessary changes to the application, proceed as follows:

Page 54: Sap Netweaver Faq1

FAQs

1. Upload the changed MCD to the DOE.

2. Set the MCD status to Tested Successfully and assign it to the device manually by choosing Manage Components.

Q.6) How can we track the queues?

A.6) You can track the number of messages in the queue using the Queue Tracking function.

Q.7) The Days not synced option in the System Status Configuration in the SAP NetWeaver Mobile Administrator does not work. We do not receive the expected result. We configured this option to set the system status to Yellow if a device has not synchronized for more than one day, however, the system status does not contain the corresponding warning. What could be causing this to happen?

A.7) You do not see the devices because the Threshold for no. of days not synced is set in the Statistics Configuration and not in the System Status Configuration.

For more information about configuring parameters in the Statistics Configuration, see the link below:–

http://help.sap.com/saphelp_nwmobile71/helpdata/en/21/a56aed2107466db6e9a87fc32c450d/frameset.htm

For more information about configuring parameters in the System Status configuration, see the link below:

http://help.sap.com/saphelp_nwmobile71/helpdata/en/d1/7d34c431c243c594228a946b5aed75/frameset.htm

Q.8) The help documentation describes how to configure parameters in general, but does not detail the function of each parameter. Where can we find the description of the parameters in the system status configuration?

A.8) See SAP Note 1259673, which contains descriptions of the system status parameters in SAP NetWeaver Mobile 7.1.

Q.9) No logs and traces were being sent to the DOE server from the PDA eSWT client with MinDB database in spite of the prerequisites below being fulfilled. What could be causing this to happen?

Page 55: Sap Netweaver Faq1

FAQs

1. Trace is enabled.

2. We explicitly sent the trace from the client by choosing Send Trace.

3. We explicitly sent the trace via the TRACE agent from the SAP NetWeaver Mobile Administrator.

A.9) This problem is resolved with SPS 06 Patch 02. For more information, see SAP Note 1225246 (NetWeaver Mobile Client 7.1 SP06 Patches).

In addition, we recommend implementing SAP Note 1257393 to make sure that the client logs and traces are visible in device logs monitoring.

Q.10) How are messages exchanged between the client and the middleware in SAP NetWeaver Mobile 7.1?

A.10) In SAP NetWeaver Mobile 7.1, the client session monitoring has the information about the number of messages exchanged between the client and the middleware. It displays the number of messages exchanged, the data objects, and the content. You can use DEVICE NAME as a filter criterion for searches to check this.

Message monitoring also has an entry for each message that flows through the DOE.

Alternatively, you can switch on the synchronization logs and see the message information exchanged between the client and the DOE.

Note: Client session monitoring can be found at the path specified below:

SAP NetWeaver Mobile Administrator → Monitoring → Client Session Monitoring

For more information about client session monitoring, see the link below:

http://help.sap.com/saphelp_nwmobile71/helpdata/en/6e/3a373448a54423966d47ab902e1712/frameset.htm

For more information about monitoring, see the link below:

http://help.sap.com/saphelp_nwmobile71/helpdata/en/43/174d79176b576ee10000000a1553f6/frameset.htm

Q.11) Is bulk download possible for data objects that are enabled for synchronous extraction?

A.11) If the data objects are enabled for synchronous extraction, bulk download is not possible for those data objects.

Q.12) Is there another way to set more device attributes such as CLIENT_FRAMEWORK_VERSION apart from using receiver generation data objects?

A.12) You can use the device profiles function to set more device attributes. Proceed as follows:

1. Create a device profiles with the values set.

2. Assign this profile to many devices simultaneously. All the properties set in the device profile are applied to all the devices added to that profile.

Create and maintain device profiles from the administration screen.

For more information about creating device profiles, see the link below:

http://help.sap.com/saphelp_nwmobile71/helpdata/en/13/3d7f190a9e46e7bc6a4bf9859f6e1b/frameset.htm

For more information about assigning devices to a device profile, see the link below:

Page 56: Sap Netweaver Faq1

FAQs

http://help.sap.com/saphelp_nwmobile71/helpdata/en/24/fbd92a870b4f5d8c5d764e4e608f5f/frameset.htm

Q.13) Are all the subscriptions calculated again for a device during re-assignment of the device to another profile or does this happen only if the application is changed (front-end changes only) in the MCD?

A.13) The system re-calculates the subscriptions each time that a new profile is assigned to the device.

Q.14) There is no troubleshooting guide or SAP note describing how we can ensure that userDetailsRoot and the user authorizations are sent to the client successfully. What steps do we need to take?

A.14) Make sure that you have already downloaded the USER_DETAILS and USER_AUTHORIZATION data objects required to view the application.

For more information, see the link below:

http://help.sap.com/saphelp_nwmobile71/helpdata/en/45/63388014d73bdbe10000000a1553f7/frameset.htm

Page 57: Sap Netweaver Faq1

FAQs

Page 58: Sap Netweaver Faq1

FAQs

6. IDoc

1. Is there a feature planned that allows us to use IDocs as the interface to the back-end system? If so, when it will become available?

2. Are there any plans to convert DOE-triggered back-end adapters to IDoc rather than BAPI wrappers (RFCs)?

Page 59: Sap Netweaver Faq1

FAQs

Q.1) Is there a feature planned that allows us to use IDocs as the interface to the back-end system? If so, when it will become available?

A.1) IDocs are supported only for back-end-triggered scenarios. However, we have two scenarios with the DOE:

1. Back-end-triggered: The back end pushes the data object instance to the DOE whenever a change occurs in the back-end business object.

2. DOE-triggered: The DOE pulls the data from the back end.

While creating a back-end adapter, specify the trigger option that you require. In addition, you should specify the back-end business object name (if it is back-end-triggered) when creating this adapter.

When you activate the adapter, the instance function module is automatically created. For more information, see the link below:

http://help.sap.com/saphelp_nwmobile71/helpdata/en/88/9e21142beb442b9eae5085e34e813c/frameset.htm

To exchange data between the back end and the DOE if you are using IDocs, configure ALE between the two systems. For more information, see the link below:

http://help.sap.com/saphelp_erp2005vp/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm

Note: You must assign message type MEREP_DELTABO to the IDoc type.

Q.2) Are there any plans to convert DOE-triggered back-end adapters to IDoc rather than BAPI wrappers (RFCs)?

A.2) We do not have any plans to convert DOE-triggered back-end adapter to IDocs. IDocs are used for notification in back-end-triggered back-end adapters and provide keys for the records that are added, modified, or deleted in the back end. In response to this, the DOE pushes those records by executing the getList and getDetail BAPI wrappers.