<?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: regarding bdc in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bdc/m-p/1987918#M403249</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rajesh,&lt;/P&gt;&lt;P&gt;         This is used if you would like to do a commit work once call trnasaction is done. This has also got very important property, for example if your Screen resolution is different from others then the screen (Application) will be different that is you'll be having say 5 lines in your screen where as your friend will be having 8 or 10 so your program might fail in this case. If you set variable DEFSIZE as 'X' it will always use the default screen size and hence avoids error.&lt;/P&gt;&lt;P&gt;        &lt;/P&gt;&lt;P&gt;         Hope this would have helped you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Prashanth.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 16 Feb 2007 05:24:15 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-02-16T05:24:15Z</dc:date>
    <item>
      <title>regarding bdc</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bdc/m-p/1987915#M403246</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;for what purpose we are using CTU_PARAM  in BDC program&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what are the parameters which can have&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;plz explain clearly with code and comments&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Feb 2007 05:15:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bdc/m-p/1987915#M403246</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-16T05:15:23Z</dc:date>
    </item>
    <item>
      <title>Re: regarding bdc</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bdc/m-p/1987916#M403247</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;  To handle the Table Controls in BDC we use CTU_PARAM structure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;kumar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Feb 2007 05:16:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bdc/m-p/1987916#M403247</guid>
      <dc:creator>sreeramkumar_madisetty</dc:creator>
      <dc:date>2007-02-16T05:16:57Z</dc:date>
    </item>
    <item>
      <title>Re: regarding bdc</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bdc/m-p/1987917#M403248</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"CTU_PARMS will force the BDC to use the standard default screen size (rather than being dynamic based on the user's settings. I think I explained that right, but all I know is that it keeps the BDC from behaving differently between users and makes things more consistent for coding logic".&lt;/P&gt;&lt;P&gt;check these links&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="2919004"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="2247712"&gt;&lt;/A&gt;;&amp;amp;#56352;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Feb 2007 05:20:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bdc/m-p/1987917#M403248</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-16T05:20:24Z</dc:date>
    </item>
    <item>
      <title>Re: regarding bdc</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bdc/m-p/1987918#M403249</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rajesh,&lt;/P&gt;&lt;P&gt;         This is used if you would like to do a commit work once call trnasaction is done. This has also got very important property, for example if your Screen resolution is different from others then the screen (Application) will be different that is you'll be having say 5 lines in your screen where as your friend will be having 8 or 10 so your program might fail in this case. If you set variable DEFSIZE as 'X' it will always use the default screen size and hence avoids error.&lt;/P&gt;&lt;P&gt;        &lt;/P&gt;&lt;P&gt;         Hope this would have helped you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Prashanth.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Feb 2007 05:24:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bdc/m-p/1987918#M403249</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-16T05:24:15Z</dc:date>
    </item>
    <item>
      <title>Re: regarding bdc</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bdc/m-p/1987919#M403250</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks a lot&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Feb 2007 05:31:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bdc/m-p/1987919#M403250</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-16T05:31:05Z</dc:date>
    </item>
    <item>
      <title>Re: regarding bdc</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bdc/m-p/1987920#M403251</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Read below from sap help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL TRANSACTION tcod OPTIONS FROM opt. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Addition OPTIONS FROM opt gives you control using the values of the components of the structure opt, which must be of the Dictionary type CTU_PARAMS. The components have the following meaning: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DISMODE&lt;/P&gt;&lt;P&gt;Processing mode (comparable with the MODE addition) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;UPDMODE&lt;/P&gt;&lt;P&gt;Update mode (comparable with the UPDATE addition) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CATTMODE&lt;/P&gt;&lt;P&gt;CATT mode (controlling a CATT procedure) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The CATT mode can have the following values: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;' ' No CATT procedure active &lt;/P&gt;&lt;P&gt;'N' CATT procedure without single screen control &lt;/P&gt;&lt;P&gt;'A' CATT procedure with single screen control &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DEFSIZE&lt;/P&gt;&lt;P&gt;Use standard window size &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RACOMMIT&lt;/P&gt;&lt;P&gt;COMMIT WORK does not end CATT procedure &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NOBINPT&lt;/P&gt;&lt;P&gt;No batch input mode, that s SY-BINPT = SPACE. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NOBIEND&lt;/P&gt;&lt;P&gt;No batch input mode after BDC data has been read &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The components DEFSIZE , RACOMMIT, NOBINPT, NOBIEND always take the following values: &lt;/P&gt;&lt;P&gt;'X' Yes &lt;/P&gt;&lt;P&gt;' ' No &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the OPTIONS addition is omitted, the following settings are valid for the control parameters: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DISMODE from the MODE addition &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;UPDMODE&lt;/P&gt;&lt;P&gt;from the UPDATE addition &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CATTMODE&lt;/P&gt;&lt;P&gt;No CATT procedure active &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DEFSIZE&lt;/P&gt;&lt;P&gt;Do not use standard window size &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RACOMMIT&lt;/P&gt;&lt;P&gt;COMMIT WORK ends procedure successfully &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NOBINPT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Batch input mode, that is SY-BINPT =X. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NOBIEND&lt;/P&gt;&lt;P&gt;Batch input mode also active after BDC data has been read &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Vibha &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*Please mark all the helpful answers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Feb 2007 05:31:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-bdc/m-p/1987920#M403251</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-16T05:31:07Z</dc:date>
    </item>
  </channel>
</rss>

