<?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 Multiple transaction codes for a SAP program in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/multiple-transaction-codes-for-a-sap-program/m-p/5963030#M1337970</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For some SAP programs , there are multiple tcodes in SE80. &lt;/P&gt;&lt;P&gt;As program is same with selection screen same as , for example 1000, how the functionality differes with different tcodes?&lt;/P&gt;&lt;P&gt;how is the code written to handle different tcodes in the same program?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for help in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Yogita&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 11 Aug 2009 21:28:35 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-08-11T21:28:35Z</dc:date>
    <item>
      <title>Multiple transaction codes for a SAP program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/multiple-transaction-codes-for-a-sap-program/m-p/5963030#M1337970</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For some SAP programs , there are multiple tcodes in SE80. &lt;/P&gt;&lt;P&gt;As program is same with selection screen same as , for example 1000, how the functionality differes with different tcodes?&lt;/P&gt;&lt;P&gt;how is the code written to handle different tcodes in the same program?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for help in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Yogita&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Aug 2009 21:28:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/multiple-transaction-codes-for-a-sap-program/m-p/5963030#M1337970</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-11T21:28:35Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple transaction codes for a SAP program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/multiple-transaction-codes-for-a-sap-program/m-p/5963031#M1337971</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no uniform way to do this. Different application areas use various methods to differentiate between create / change / display mode while processing the same screen in different transaction codes.&lt;/P&gt;&lt;P&gt;For instance, in SD (and some other application areas) the Screen Sequence Control tables are queried at the beginning of a transaction, and in table T180 there is a field (TRTYP) that will determine what mode is the transaction for, so based on that the module pool will decide what functionality is available. But this is not a method that's used everywhere - as said, there are many ways to accomplish this.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Aug 2009 22:20:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/multiple-transaction-codes-for-a-sap-program/m-p/5963031#M1337971</guid>
      <dc:creator>Tamas_Hoznek</dc:creator>
      <dc:date>2009-08-11T22:20:22Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple transaction codes for a SAP program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/multiple-transaction-codes-for-a-sap-program/m-p/5963032#M1337972</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;  We have Different types of Programs such as Executable, Modulepool and Functionpools.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We can design different selection-screens, Normal Screens through all of the above program types with different transactions.&lt;/P&gt;&lt;P&gt;Based on transaction we can write its own functionality. &lt;/P&gt;&lt;P&gt;Ex: ZZ01 for change   =&amp;gt; all fields in editable mode &lt;/P&gt;&lt;P&gt;      ZZ02 is for Display  =&amp;gt; all fields in display mode.  &lt;/P&gt;&lt;P&gt;      (Module Pool, Normal Screen.)&lt;/P&gt;&lt;P&gt;declare one Module under PBO.  Module FIELD_ATTRIBUTES.&lt;/P&gt;&lt;P&gt;Write code like this:&lt;/P&gt;&lt;P&gt;   loop at screen.&lt;/P&gt;&lt;P&gt;      If sy-tcode = 'ZZ01'.&lt;/P&gt;&lt;P&gt;        screen-input = 1.&lt;/P&gt;&lt;P&gt;      elseif sy-tcode = 'ZZ02'.&lt;/P&gt;&lt;P&gt;        screen-input = 0.&lt;/P&gt;&lt;P&gt;      endif.&lt;/P&gt;&lt;P&gt;      modify screen.&lt;/P&gt;&lt;P&gt;   endloop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  This is very small example. If you compare F-02 and FBS1 transactions, you can observe this method. We can observe more input fields in FBS1. This is based Configuration also.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Balaji Peethani,&lt;/P&gt;&lt;P&gt;Tanuku.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Aug 2009 23:51:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/multiple-transaction-codes-for-a-sap-program/m-p/5963032#M1337972</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-11T23:51:05Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple transaction codes for a SAP program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/multiple-transaction-codes-for-a-sap-program/m-p/5963033#M1337973</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;adding to what said about...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if sy-tcode = 'ONE'.&lt;/P&gt;&lt;P&gt;do this and this..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;elseif sy-tcode = 'TWO'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;do this and this..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;endif.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the same thing can be done based on called program and the flag values... like if flag = 'V' sales so do this if flag = 'K'  purchasing so do this...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Aug 2009 23:58:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/multiple-transaction-codes-for-a-sap-program/m-p/5963033#M1337973</guid>
      <dc:creator>former_member156446</dc:creator>
      <dc:date>2009-08-11T23:58:52Z</dc:date>
    </item>
  </channel>
</rss>

