<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Mobile Data Entry Enhancements in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/mobile-data-entry-enhancements/m-p/7315370#M1536129</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Only workaround possible is to CASE SY-TCODE for all these developments.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Dec 2010 13:35:00 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2010-12-15T13:35:00Z</dc:date>
    <item>
      <title>Mobile Data Entry Enhancements</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/mobile-data-entry-enhancements/m-p/7315369#M1536128</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I used SAP standard enhancement technique to override the standard physical screen of transaction LM06. But now I find out that this physical screen (SAPLLMOB:2100) is shared by 11 transactions LM02, LM03, LM05, LM06, LM08, LM09, LM26, LM27, LM56, LM66 and LM76. Now that I've implemented the new physical screen in SPRO 'Define Screen Management', all the other transactions look exactly like LM06 and have the same functionality. We're on 4.7 and cannot use enhancement spots, which would have been an easy way out. There are no workarounds in config, user-exits or BADIs. The only alternative is to change SAP standard or to dynamically change the labels and display of the fields and buttons from the user exit subscreen. But this would mean that I have to simulate all the PAI and PBO functionality of screen SAPLLMOB:2100 in user exit subscreen SAPLXLRF:1100. If anyone has found an easier solution/workaround in SAP 4.7, please assist. Thank you, Adrian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Sep 2010 14:05:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/mobile-data-entry-enhancements/m-p/7315369#M1536128</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-09-09T14:05:09Z</dc:date>
    </item>
    <item>
      <title>Re: Mobile Data Entry Enhancements</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/mobile-data-entry-enhancements/m-p/7315370#M1536129</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Only workaround possible is to CASE SY-TCODE for all these developments.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Dec 2010 13:35:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/mobile-data-entry-enhancements/m-p/7315370#M1536129</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-12-15T13:35:00Z</dc:date>
    </item>
  </channel>
</rss>

