<?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 transaction in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction/m-p/2663993#M614697</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;Many SAP transactions behave differently in online mode and in Batch mode and this mode is determined by the SY-BINPT variable that can be controlled using the OPTIONS command in addition to the CALL TRANSACTION.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, the error message that usually comes in status bar while you are running the transaction online might appear in a popup window when you are running that in batch. This will make your fields disabled for input. This OPTIONS addition will remove this problem &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The way to use the OPTIONS addition.&lt;/P&gt;&lt;P&gt;Declare a work area of type CTU_PARAMS.&lt;/P&gt;&lt;P&gt;Fill the fields of CTU_PARAMS. The field NOBINPT should be set to &amp;#145;X&amp;#146;.&lt;/P&gt;&lt;P&gt;This will set the SY-BINPT to space. So now the transaction which you will be calling will run in online mode. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example.&lt;/P&gt;&lt;P&gt;clear X_OPTIONS.&lt;/P&gt;&lt;P&gt;X_OPTIONS-DISMODE = 'E'.&lt;/P&gt;&lt;P&gt;X_OPTIONS-UPDMODE = 'S'.&lt;/P&gt;&lt;P&gt;X_OPTIONS-CATTMODE = ' '.&lt;/P&gt;&lt;P&gt;X_OPTIONS-DEFSIZE = ' '.&lt;/P&gt;&lt;P&gt;X_OPTIONS-RACOMMIT = ' '.&lt;/P&gt;&lt;P&gt;X_OPTIONS-NOBINPT = 'X'.&lt;/P&gt;&lt;P&gt;X_OPTIONS-NOBIEND = ' '.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;call transaction 'BP' using T_BDCDATA[] options from X_OPTIONS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note:&lt;/P&gt;&lt;P&gt;Do not use the MODE &amp;amp; UPDATE additions when you are using OPTIONS. The mode &amp;amp; update values are passed in the CTU_PARAMS structure. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward if it helps..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Omkar.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 17 Aug 2007 10:20:35 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-08-17T10:20:35Z</dc:date>
    <item>
      <title>Call transaction</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction/m-p/2663992#M614696</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 i am using call trasaction for MB1B whileusing all screen i am able to post it, where as while using N screen I am getting error message.&lt;/P&gt;&lt;P&gt;can any one help inthis regard.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Aug 2007 10:17:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction/m-p/2663992#M614696</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-17T10:17:59Z</dc:date>
    </item>
    <item>
      <title>Re: Call transaction</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction/m-p/2663993#M614697</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;Many SAP transactions behave differently in online mode and in Batch mode and this mode is determined by the SY-BINPT variable that can be controlled using the OPTIONS command in addition to the CALL TRANSACTION.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, the error message that usually comes in status bar while you are running the transaction online might appear in a popup window when you are running that in batch. This will make your fields disabled for input. This OPTIONS addition will remove this problem &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The way to use the OPTIONS addition.&lt;/P&gt;&lt;P&gt;Declare a work area of type CTU_PARAMS.&lt;/P&gt;&lt;P&gt;Fill the fields of CTU_PARAMS. The field NOBINPT should be set to &amp;#145;X&amp;#146;.&lt;/P&gt;&lt;P&gt;This will set the SY-BINPT to space. So now the transaction which you will be calling will run in online mode. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example.&lt;/P&gt;&lt;P&gt;clear X_OPTIONS.&lt;/P&gt;&lt;P&gt;X_OPTIONS-DISMODE = 'E'.&lt;/P&gt;&lt;P&gt;X_OPTIONS-UPDMODE = 'S'.&lt;/P&gt;&lt;P&gt;X_OPTIONS-CATTMODE = ' '.&lt;/P&gt;&lt;P&gt;X_OPTIONS-DEFSIZE = ' '.&lt;/P&gt;&lt;P&gt;X_OPTIONS-RACOMMIT = ' '.&lt;/P&gt;&lt;P&gt;X_OPTIONS-NOBINPT = 'X'.&lt;/P&gt;&lt;P&gt;X_OPTIONS-NOBIEND = ' '.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;call transaction 'BP' using T_BDCDATA[] options from X_OPTIONS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note:&lt;/P&gt;&lt;P&gt;Do not use the MODE &amp;amp; UPDATE additions when you are using OPTIONS. The mode &amp;amp; update values are passed in the CTU_PARAMS structure. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward if it helps..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Omkar.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Aug 2007 10:20:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction/m-p/2663993#M614697</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-17T10:20:35Z</dc:date>
    </item>
  </channel>
</rss>

