<?xml version="1.0"?>
<rss version="2.0">
<channel>
  <title>msc mobile blog - mtt tag</title>
  <link>http://blog.msc-mobile.com:80/tags/mtt/</link>
  <description>About the daily work in a IT nuthouse</description>
  <language>en</language>
  <copyright>msc mobile</copyright>
  <lastBuildDate>Wed, 18 May 2011 00:10:00 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>SAP Mobile Timesheet sucks??? </title>
    <link>http://blog.msc-mobile.com:80/2009/03/05/1236263820000.html</link>
    
      
      
        <description>
          One anonymous person wrote a comment on my blog post about MTS (&lt;a href=&#034;http://blog.msc-mobile.com/2008/10/17/1224239460000.html&#034;&gt;A look at the SAP MTS Functionality&lt;/a&gt;).&lt;p&gt;&lt;a href=&#034;http://blog.msc-mobile.com:80/2009/03/05/1236263820000.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
    
    
    <comments>http://blog.msc-mobile.com:80/2009/03/05/1236263820000.html#comments</comments>
    <guid isPermaLink="true">http://blog.msc-mobile.com:80/2009/03/05/1236263820000.html</guid>
    <pubDate>Thu, 05 Mar 2009 14:37:00 GMT</pubDate>
  </item>
  
  <item>
    <title>Lessons Learned from MTT Implementations</title>
    <link>http://blog.msc-mobile.com:80/2008/10/21/1224579360000.html</link>
    
      
      
        <description>
          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.&lt;p&gt;&lt;a href=&#034;http://blog.msc-mobile.com:80/2008/10/21/1224579360000.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
    
    
    <comments>http://blog.msc-mobile.com:80/2008/10/21/1224579360000.html#comments</comments>
    <guid isPermaLink="true">http://blog.msc-mobile.com:80/2008/10/21/1224579360000.html</guid>
    <pubDate>Tue, 21 Oct 2008 08:56:00 GMT</pubDate>
  </item>
  
  <item>
    <title>A look at the SAP MTS Functionality</title>
    <link>http://blog.msc-mobile.com:80/2008/10/17/1224239460000.html</link>
    
      
      
        <description>
          SAP MTS enables employees in an organization
to record their working times on
laptops, anywhere at any time. A network
connection is not required for time
recording. This option primarily benefits
employees who must travel frequently and
don’t always have a connection to their
corporate network.&lt;p&gt;&lt;a href=&#034;http://blog.msc-mobile.com:80/2008/10/17/1224239460000.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
    
    
    <comments>http://blog.msc-mobile.com:80/2008/10/17/1224239460000.html#comments</comments>
    <guid isPermaLink="true">http://blog.msc-mobile.com:80/2008/10/17/1224239460000.html</guid>
    <pubDate>Fri, 17 Oct 2008 10:31:00 GMT</pubDate>
  </item>
  
  <item>
    <title>A look at the SAP MTR Functionality</title>
    <link>http://blog.msc-mobile.com:80/2008/02/01/1201865580000.html</link>
    
      
      
        <description>
          SAP MTR allows
employees to capture their travel expenses
in a disconnected mode and send the data to the back-end system once a connection is
established, also known as synchronization.
In both SAP MTS and MTR, the back-end
application logic is mirrored with the offline
application because the business logic from
the back end was recoded for the mobile
device. You can access recorded SAP MTR
data in the back end as soon as the synchronization
is over. Depending on the amount
of data you are loading, the synchronization
takes between 30 seconds and five minutes
to complete. SAP MTR allows users to
choose which trips should be synchronized,
which is useful if some incomplete expense
reports were created offline and are not
ready to be sent to the backend yet.&lt;p&gt;&lt;a href=&#034;http://blog.msc-mobile.com:80/2008/02/01/1201865580000.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
    
    
    <comments>http://blog.msc-mobile.com:80/2008/02/01/1201865580000.html#comments</comments>
    <guid isPermaLink="true">http://blog.msc-mobile.com:80/2008/02/01/1201865580000.html</guid>
    <pubDate>Fri, 01 Feb 2008 11:33:00 GMT</pubDate>
  </item>
  
  <item>
    <title>Mobile Business Solutions - Ready for the big Market?</title>
    <link>http://blog.msc-mobile.com:80/2006/10/16/1160985660000.html</link>
    
      
      
        <description>
          The development of mobile applications based on SAP technology (Mobile Infrastructure, Mobile Web DynPro) is not rocket science. If you are a skilled Java or ABAP developer you can do it! In general an Mobile Infrastructure development project is no different from any other development project you have worked on in the past! But with every new technology there are new things you have to think about, new snares and new challenges. There is less experience and not many people you can ask for help. But because of this we have the SDN, the great forums and now another blog dealing with the development of mobile applications.&lt;p&gt;&lt;a href=&#034;http://blog.msc-mobile.com:80/2006/10/16/1160985660000.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
    
    
    <comments>http://blog.msc-mobile.com:80/2006/10/16/1160985660000.html#comments</comments>
    <guid isPermaLink="true">http://blog.msc-mobile.com:80/2006/10/16/1160985660000.html</guid>
    <pubDate>Mon, 16 Oct 2006 08:01:00 GMT</pubDate>
  </item>
  
  </channel>
</rss>

