<?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: Disabling screens. in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/disabling-screens/m-p/7031018#M1499390</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you may use transaction and screen variants (SHD0 transaction). See SAP library or forum for more information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Screen variants allow you to act on GUI elements (and user commands).&lt;/P&gt;&lt;P&gt;Transaction variant makes the connections between a transaction and screen variants.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you call the transaction, you need to indicate the transaction variant to be used, by calling RS_HDSYS_CALL_TC_VARIANT (note: you may not create a Z transaction of type "transaction variant" because you use skip first screen, as explained in Note 318448 - Call and skip first screen).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 25 Jun 2010 18:44:26 GMT</pubDate>
    <dc:creator>Sandra_Rossi</dc:creator>
    <dc:date>2010-06-25T18:44:26Z</dc:date>
    <item>
      <title>Disabling screens.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/disabling-screens/m-p/7031017#M1499389</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;I am calling transaction VL31N from my custom program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;set PARAMETER ID 'LIF' FIELD '114390'.&lt;/P&gt;&lt;P&gt;set PARAMETER ID 'BES' FIELD '45077732322'.&lt;/P&gt;&lt;P&gt;CALL TRANSACTION 'VL31N' AND SKIP FIRST SCREEN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is there a way to capture events (user clicks) somehow from my custom program and cancel it?&lt;/P&gt;&lt;P&gt;I want user to not be able to press some key combinations that will popup search screen for example.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Jun 2010 15:20:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/disabling-screens/m-p/7031017#M1499389</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-06-25T15:20:36Z</dc:date>
    </item>
    <item>
      <title>Re: Disabling screens.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/disabling-screens/m-p/7031018#M1499390</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you may use transaction and screen variants (SHD0 transaction). See SAP library or forum for more information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Screen variants allow you to act on GUI elements (and user commands).&lt;/P&gt;&lt;P&gt;Transaction variant makes the connections between a transaction and screen variants.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you call the transaction, you need to indicate the transaction variant to be used, by calling RS_HDSYS_CALL_TC_VARIANT (note: you may not create a Z transaction of type "transaction variant" because you use skip first screen, as explained in Note 318448 - Call and skip first screen).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Jun 2010 18:44:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/disabling-screens/m-p/7031018#M1499390</guid>
      <dc:creator>Sandra_Rossi</dc:creator>
      <dc:date>2010-06-25T18:44:26Z</dc:date>
    </item>
  </channel>
</rss>

