Page tree
Skip to end of metadata
Go to start of metadata

xApp Mobile Time and Travel Frequently Asked Questions

When synchronizing Mobile Travel, I get the following message in my sync protocol Due to a communications error method XXX could not be executed.

This type of error occurs for one of the following reasons:

  1. The middleware or the backend system is not running
  2. The middleware or the backend system cannot be reached due to connection problems
  3. The connection was lost during the synchronization process

To fix the problem, try the following:

  1. Try logging in the middleware or backend system. If you're not able to, the system might be down. Contact your system administrator.
  2. Re-synchronize. The problem might be due to a loss of connectivity.
  3. Check the mapping in table BWAFMAPP on the middleware. Refer to the Business Configuration Guide for Mobile Time and Travel 1.6 for Laptop or the SAP xApp Mobile Time and Travel 2.0 Configuration and Operations Guides for details.
  4. If applicable, check the RFC destination in table MEMAPPDEST on the middleware. Refer to the Business Configuration Guide for Mobile Time and Travel 1.6 for Laptop or the SAP xApp Mobile Time and Travel 2.0 Configuration and Operations Guides for details.
  5. Make sure the Function Modules listed for the BWAFMAPP table are all remote-enabled.

back to top

We have successfully deployed the Mobile Time and Travel Expenses components and can run the applications from the client. However, the first synchronization results in customization errors. How can we troubleshoot this problem?

Please make sure all the required back-end customization settings for Mobile Time and Travel have been completed. You can find the latest information in the Mobile Time and Travel Business Scenario Configuration Guide or the SAP xApp Mobile Time and Travel 2.0 Configuration and Operations Guides available at For trouble shooting steps:

  1. If applicable, check that your RFC connections from the middleware to the back-end system (and vice-versa) work properly. You can do this by executing the transaction SM59, navigating to your RFD destination, and clicking on the 'Remote logon'. If you receive any error messages, please refer the RFC Connection documentation available at for further troubleshooting in this area.
  2. For Mobile Travel Expenses, there is a debugging tool built-in the back-end system. Refer to the Mobile Time and Travel Business Scenario Configuration Guide for details on this feature and how to activate it if you are working with in an Enterprise system. You can execute this tool via transaction SE38. Enter the program name, RPR_WAF_DEBUGGING and click on execute. Enter the user id you would like to test. If you are working with an Enterprise system, enter the application name, PR05. Click on execute. If you don't have any entries here and the report is activated, you may have RFC connection problems. If you have entries here, then you can debug your FM calls from this report (the standard ABAP Debugger will be launched) and determine what could be causing the synchronization problem.

back to top

When trying to synchronize/download the Mobile Time and Travel applications to the mobile client, the error message "Conversation ID could not be generated INTERNAL_ERROR, conversation ID, INTERNAL ERROR" is displayed on the mobile and no applications are downloaded to the device. What causes this error message?

Valid For: xMTT 1.6

In the Mobile Server/WebAS, run the transaction MEREP_PD. This necessary initialization steps for each client are then executed. Smart Sync applications require specific configuration settings via this transaction whereas Mobile Time and Travel, generic sync applications, only require the initialization steps that are performed by simply running this transaction. Please refer to note 592284.

back to top

Is it possible to setup one Mobile Infrastructure Server and have it communicate to several backend servers?

Valid For: xMTT 1.6

Mobile Time and Travel is a Generic Sync application and its Mobile Engine related configuration is client dependent. This means you can configure clients to point to different backends. For example: on your MI Server, client 100 can point to your development environment and client 200 can point to your quality assurance environment. However, we highly recommend a dedicated MI Server for your production environment. If both Time and Travel are to be deployed, certain Master data is shared by the two applications requiring that for any specific user both applications should be directed at the same R/3 server.

back to top

Should I install NW Mobile middleware (J2EE component) on a separate hardware instead of sharing the same instance with the backend system (e.g. NW2004s and ERP2005 on the same server)??

We recommend the NW Mobile middleware (J2EE component) to be installed on a separate server when ERP2005 is used as backend system.

back to top

We got synchronization error within CATS_MY_GET_ADMIN_PERNR function module. And we already have this function entry in tables MEMAPPDEST and BWAFMAPP.

You may have the function module entered in the backend server instead of the middleware server. In this case, make sure you do the following:
1- In table BWAFMAPP of the middleware system, make an entry for
CATS_MY_GET_ADMIN_PERNR (left column). This method must be associated
with CATS_MY_WAF_ADMIN_PERNR (right column).
2- Save your entries.
3- In table MEMAPPDEST of the middleware system, copy an existing entry
(e.g.: CATS_MY_GET_MASTER_DATA) and change the method name to
4- Save your entries.

back to top

  • No labels