<?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: Screen in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/screen/m-p/1863048#M364181</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Solution 1) &lt;/P&gt;&lt;P&gt;Move the transport request that has added the screen field in the DEV envoronment to the QA and PROD system(If it is needed).&lt;/P&gt;&lt;P&gt;If it is not needed in the QA and PROD systems, delete the transport request that has made this change(Or atleast decativate the Badi as other have suggested).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Solution 2)&lt;/P&gt;&lt;P&gt;Look for a BAPI or a function module, which does the same thing as the PA30 transaction. BAPI/FM doesn't depend upon the screen flow logic and hence will not have any problem unlike the bdcs.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 05 Feb 2007 08:25:50 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-02-05T08:25:50Z</dc:date>
    <item>
      <title>Screen</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/screen/m-p/1863046#M364179</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Friends,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is difference in the screen for the T-code PA30 between Development, Quality and Production servers. The difference is that, the field Gender is available in Development but not in Quality and Production servers.  Due this, the BDC program written for updating the employee details are not working in quality and production servers.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kindly guide me as to how to correct the screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TIA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark K&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Feb 2007 07:04:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/screen/m-p/1863046#M364179</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-05T07:04:14Z</dc:date>
    </item>
    <item>
      <title>Re: Screen</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/screen/m-p/1863047#M364180</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i think this screen component is creating by some screen-exit or badi . If it is so just deactivate that implementation in development and do the recording again. w&lt;/P&gt;&lt;P&gt;which will give you the correct result.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;shiba dutta&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Feb 2007 08:16:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/screen/m-p/1863047#M364180</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-05T08:16:36Z</dc:date>
    </item>
    <item>
      <title>Re: Screen</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/screen/m-p/1863048#M364181</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Solution 1) &lt;/P&gt;&lt;P&gt;Move the transport request that has added the screen field in the DEV envoronment to the QA and PROD system(If it is needed).&lt;/P&gt;&lt;P&gt;If it is not needed in the QA and PROD systems, delete the transport request that has made this change(Or atleast decativate the Badi as other have suggested).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Solution 2)&lt;/P&gt;&lt;P&gt;Look for a BAPI or a function module, which does the same thing as the PA30 transaction. BAPI/FM doesn't depend upon the screen flow logic and hence will not have any problem unlike the bdcs.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Feb 2007 08:25:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/screen/m-p/1863048#M364181</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-05T08:25:50Z</dc:date>
    </item>
    <item>
      <title>Re: Screen</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/screen/m-p/1863049#M364182</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Mark,&lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;  There are 2 chances&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is problem with code sync.Means whatever the code in production &amp;amp; &lt;/P&gt;&lt;P&gt;    Development are not matching why because&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.Because of Development somebody might just done some code changes which is not required.Since they have not transported the code to production.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. If this code change is important one contact with Basis consultant explain them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3.Before you have to develop code you should make sure that production &amp;amp; development serv ers code are same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pls. mark if useful&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Feb 2007 08:34:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/screen/m-p/1863049#M364182</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-05T08:34:43Z</dc:date>
    </item>
  </channel>
</rss>

