<?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: call a transaction code in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415221#M820263</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;CALL TRANSACTION &amp;lt;transaction name&amp;gt;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 08 Feb 2008 11:04:08 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-02-08T11:04:08Z</dc:date>
    <item>
      <title>call a transaction code</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415217#M820259</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;how to call a transaction code from within a abap program&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2008 11:01:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415217#M820259</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-08T11:01:55Z</dc:date>
    </item>
    <item>
      <title>Re: call a transaction code</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415218#M820260</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;ex:&lt;/P&gt;&lt;P&gt;CALL TRANSACTION 'SE38'  USING BDCDATA  MODE 'N' &lt;/P&gt;&lt;P&gt;                         MESSAGES INTO ITAB.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2008 11:03:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415218#M820260</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-08T11:03:35Z</dc:date>
    </item>
    <item>
      <title>Re: call a transaction code</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415219#M820261</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;Hope it will help you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Pls reward if help.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WT IS CALL TRANSACTION METHOD? WT IS SYNTAX/PROCEDURE?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL TRANSACTION :&lt;/P&gt;&lt;P&gt;1. It is compatible for small amount of data only. &lt;/P&gt;&lt;P&gt;2. It process the data Synchronously. i.e., The data is updated&lt;/P&gt;&lt;P&gt;at the time of execution. &lt;/P&gt;&lt;P&gt;3. It updates data both Synchronously and Asynchronously. When&lt;/P&gt;&lt;P&gt;we use Synchronous mode, it always verify all the data updated&lt;/P&gt;&lt;P&gt;successfully in the database. &lt;/P&gt;&lt;P&gt;When we use Asynchronous mode, the system can not wait till &lt;/P&gt;&lt;P&gt;all the data updated in the database. &lt;/P&gt;&lt;P&gt;4. It can handle only one application at a time. &lt;/P&gt;&lt;P&gt;5. It does not have Log file, we need to design logfile explicitly&lt;/P&gt;&lt;P&gt;using BDCMSGCOLL stucture. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Syntax :&lt;/P&gt;&lt;P&gt;CALL TRANSACTION &amp;lt;T.Code&amp;gt; USING &amp;lt;BDCTAB&amp;gt; MODE &amp;lt;A/N/E&amp;gt; UPDATE &amp;lt;S/A&amp;gt;&lt;/P&gt;&lt;P&gt;MESSAGES INTO &amp;lt;BDCMSGCOLL Int.Table&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Parameter 1 : Transaction Code&lt;/P&gt;&lt;P&gt;Parameter 2 : It is name of BDCDATA table.&lt;/P&gt;&lt;P&gt;Parameter 3 : Specifying Mode in which you execute transaction. &lt;/P&gt;&lt;P&gt;A - All screen mode. All the screen of transaction&lt;/P&gt;&lt;P&gt;are displayed. &lt;/P&gt;&lt;P&gt;N - No screen mode. No screen is displayed when you &lt;/P&gt;&lt;P&gt;execute the transaction. &lt;/P&gt;&lt;P&gt;E - Error screen. Only those screens are displayed &lt;/P&gt;&lt;P&gt;where you have error record. &lt;/P&gt;&lt;P&gt;Parameter 4 : Specifying Update type by which data base table is &lt;/P&gt;&lt;P&gt;updated.&lt;/P&gt;&lt;P&gt;S - It is for Synchronous update in which if you &lt;/P&gt;&lt;P&gt;change data for one table then all the relacted &lt;/P&gt;&lt;P&gt;tables gets updated. And then sy-subrc is returned&lt;/P&gt;&lt;P&gt;i.e., sy-subrc is returned for once and all. &lt;/P&gt;&lt;P&gt;A - It is for Asynchronous update, when you change &lt;/P&gt;&lt;P&gt;data of one table, the sy-subrc is returned. And&lt;/P&gt;&lt;P&gt;then updation of other affected tables takes place&lt;/P&gt;&lt;P&gt;If system fails to update other tables still&lt;/P&gt;&lt;P&gt;sy-subrc returned is 0.&lt;/P&gt;&lt;P&gt;Parameter 5 : When you update database table, operation is either&lt;/P&gt;&lt;P&gt;successful or unsuccessful or operation is successful&lt;/P&gt;&lt;P&gt;with some warning. These messages are stored in &lt;/P&gt;&lt;P&gt;internal table which you specify along with MESSAGE&lt;/P&gt;&lt;P&gt;statement. This internal table should be declared like&lt;/P&gt;&lt;P&gt;BDCMSGCOLL structure. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steps for CALL TRANSACTION Method :&lt;/P&gt;&lt;P&gt;1. Interanal table for the data (structure similler to local file)&lt;/P&gt;&lt;P&gt;2. BDCTAB like BDCDATA.&lt;/P&gt;&lt;P&gt;3. Use UPLOAD/WS_UPLOAD/GUI_UPLOAD or DATASETS for upload data from&lt;/P&gt;&lt;P&gt;local file to internal table (i.e. ITAB). &lt;/P&gt;&lt;P&gt;4. LOOP at Itab. &lt;/P&gt;&lt;P&gt;Populate BDCTAB table. &lt;/P&gt;&lt;P&gt;CALL TRANSACTION &amp;lt;T.Code&amp;gt; USING &amp;lt;BDCTAB&amp;gt; MODE &amp;lt;A/N/E&amp;gt;&lt;/P&gt;&lt;P&gt;UPDATE &amp;lt;S/A&amp;gt; MESSAGES INTO &amp;lt;BDCMSGCOLL Int.Table&amp;gt;&lt;/P&gt;&lt;P&gt;Refresh BDCTAB.&lt;/P&gt;&lt;P&gt;ENDLOOP.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2008 11:03:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415219#M820261</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-08T11:03:59Z</dc:date>
    </item>
    <item>
      <title>Re: call a transaction code</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415220#M820262</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;call transaction 'tcode name'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ex.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;call transaction 'SE38'.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2008 11:04:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415220#M820262</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-08T11:04:05Z</dc:date>
    </item>
    <item>
      <title>Re: call a transaction code</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415221#M820263</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;CALL TRANSACTION &amp;lt;transaction name&amp;gt;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2008 11:04:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415221#M820263</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-08T11:04:08Z</dc:date>
    </item>
    <item>
      <title>Re: call a transaction code</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415222#M820264</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;  Use 'CALL TRANSACTION' followed by the TCODE.&lt;/P&gt;&lt;P&gt;Eg. Call Transaction mm01.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards&lt;/P&gt;&lt;P&gt;Haritha.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2008 11:04:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415222#M820264</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-08T11:04:09Z</dc:date>
    </item>
    <item>
      <title>Re: call a transaction code</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415223#M820265</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;When you use the LEAVE TO TRANSACTION '&amp;lt;T_CODE&amp;gt;' statement, the system terminates the current&lt;/P&gt;&lt;P&gt;program and starts the transaction with transaction code &amp;lt;T_CODE&amp;gt;. The statement is the equivalent of&lt;/P&gt;&lt;P&gt;entering /n&amp;lt;T_CODE&amp;gt; in the command field.&lt;/P&gt;&lt;P&gt;CALL TRANSACTION '&amp;lt;T_CODE&amp;gt;' allows you to insert an ABAP program with a transaction code into the&lt;/P&gt;&lt;P&gt;call chain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To terminate an ABAP program, use the LEAVE PROGRAM statement. If the statement occurs in a&lt;/P&gt;&lt;P&gt;program that you called using CALL TRANSACTION '&amp;lt;T_CODE&amp;gt;' or SUBMIT &amp;lt;prog_name&amp;gt; AND&lt;/P&gt;&lt;P&gt;RETURN, the system resumes processing at the next statement after the call in the calling program. In all&lt;/P&gt;&lt;P&gt;other cases, the user returns to the application menu from which he or she started the program.&lt;/P&gt;&lt;P&gt;If you use the &amp;#133;AND SKIP FIRST SCREEN addition, the system does not display the screen contents of&lt;/P&gt;&lt;P&gt;the first screen in the transaction. However, it does process the flow logic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you started a transaction using CALL TRANSACTION that uses update techniques, you can use the&lt;/P&gt;&lt;P&gt;UPDATE&amp;#133; addition to specify the update technique (asynchronous (default), synchronous, or local) that&lt;/P&gt;&lt;P&gt;the program should use.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you call a transaction using the statement CALL TRANSACTION '&amp;lt;T_CODE&amp;gt;' USING &amp;lt;bi_itab&amp;gt;&amp;#133;&lt;/P&gt;&lt;P&gt;you can run the transaction &amp;lt;T_CODE&amp;gt; using the values from &amp;lt;bi_itab&amp;gt; in the screen fields. The&lt;/P&gt;&lt;P&gt;internal table must have the structure bdcdata.&lt;/P&gt;&lt;P&gt;The MODE addition allows you to specify whether the screen contents should all be displayed ('A' - the&lt;/P&gt;&lt;P&gt;default setting), only when an error occurs ('E'), or not at all ('N'). You can use the MESSAGE INTO&lt;/P&gt;&lt;P&gt;&amp;lt;mess_itab&amp;gt; to specify an internal table into which any system messages should be written. The&lt;/P&gt;&lt;P&gt;internal table must have the structure bdcmsgcoll.&lt;/P&gt;&lt;P&gt;You can find out if the transaction was executed successfully from the system field&lt;/P&gt;&lt;P&gt;sy-subrc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You might use this technique if&lt;/P&gt;&lt;P&gt;You are processing in the foreground, but the input fields have not been filled using GET parameters,&lt;/P&gt;&lt;P&gt;You want to process the transaction invisibly. In this case, you normally have to pass the function codes&lt;/P&gt;&lt;P&gt;in the table as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps, Do reward.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2008 11:04:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415223#M820265</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-08T11:04:09Z</dc:date>
    </item>
    <item>
      <title>Re: call a transaction code</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415224#M820266</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;hope it will work for u.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;reward if help.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL TRANSACTION 'MB1B' USING BDCDATA MODE W_MODE UPDATE 'S'&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2008 11:05:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415224#M820266</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-08T11:05:03Z</dc:date>
    </item>
    <item>
      <title>Re: call a transaction code</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415225#M820267</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;use this syntex to call transaction&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL TRANSACTION  &amp;lt;TCODE&amp;gt; &lt;/P&gt;&lt;P&gt;          USING &amp;lt;BDCDATANAME&amp;gt;&lt;/P&gt;&lt;P&gt;          MODE &amp;lt;N/A/E&amp;gt;&lt;/P&gt;&lt;P&gt;          UPDATE &amp;lt;S/A&amp;gt;&lt;/P&gt;&lt;P&gt;          MESSAGE &amp;lt;BDCMSGCOLL&amp;gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in the above syntax provide transaction code and ur internal table BDCDATA structure&lt;/P&gt;&lt;P&gt;MODE is N - no screen mode i.e, noscreen is displayed when u excute the transaction&lt;/P&gt;&lt;P&gt;              A - is all screen mode i.e, all the screens of the transaction are displayed&lt;/P&gt;&lt;P&gt;              E - is error screen i.e, only those screens are displayed  where in u have occured error&lt;/P&gt;&lt;P&gt;UPDATE S- synchronous update&lt;/P&gt;&lt;P&gt;              A- asynchronous update&lt;/P&gt;&lt;P&gt;MESSAGE  is used to catch the errors i.e, log display&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward if it is useful&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;S.Gangi Reddy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2008 11:15:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415225#M820267</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-08T11:15:10Z</dc:date>
    </item>
    <item>
      <title>Re: call a transaction code</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415226#M820268</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;Type CALL into your ABAP editor. &lt;/P&gt;&lt;P&gt;Place your cursor on the word CALL and press F1. &lt;/P&gt;&lt;P&gt;Select the CALL TRANSACTION documentation&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Chaitanya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 16 Feb 2008 12:19:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-a-transaction-code/m-p/3415226#M820268</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-16T12:19:50Z</dc:date>
    </item>
  </channel>
</rss>

