Lessons Learned from MTT Implementations
A SAP Mobile Time and Travel Implementation is straight forward - but there are some things that you learn over time, some things that are done wrong by many people who do it the first time. Here are some lessons learned from our experience with MTT:
- Adapt the Workflow: The guided procedures are a great support for casual users, but they do not meet the requirement of power users who enter trips and working time on a daily basis. Here we recommend changing the workflow of the application. For example, replace the guided procedures with tabs to allow a faster business process.
- Take advantage of user exits: The performance of the application decreases with a high amount of trips and time entries. To alleviate unfavorable performance, we recommend employing the existing user exits (i.e. MYCATXX) on the back end to limit the downloaded data. This task speeds up the UI and improves the speed of the synchronization process.
- Roll out slowly: If you have a large organization, instead of a big-bang approach in which all users go live at the same time, roll out the mobile project department by department, group by group, and so on.
- Use transaction PR01 for SAP MTR customizing: Even though SAP MTR uses transaction PR05 (Travel Expense Manager) to create the trips in the back end during synchronization, SAP MTR uses the customizing settings, such as field selection, of transaction PR01. You must customize the field selection in transaction PR01. All other customizing settings (e.g., expense types and trip schemas) affect both PR01 and PR05, so you only need to set them once. This is especially important to remember when applying the customizing settings for the offline application, which you can perform by following IMG menu path Financial Accounting > Travel Management > Travel Expenses.