<?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: problem in BDC for  CA01 in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-bdc-for-ca01/m-p/5347921#M1231535</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi gurus , still my question is not answerd , &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; i am writing a bdc for this  ca01 , in CA01  transaction when group name is not given the system automatically  takes the group..  it can take  existing group or  create new group.  now when new group the group counter is 1 the screen sequence is for eg .  1  , 2 ,  3,   4,  and when group counter is more than  1 for that  group  screen  sequence is  1  , 2a,  2 , 3  ,4.    since  the group is internally  taken by  system we dont know  what  will be group no .... &lt;/P&gt;&lt;P&gt;                                              pls help how to  do this bdc  .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 16 Mar 2009 12:10:24 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-03-16T12:10:24Z</dc:date>
    <item>
      <title>problem in BDC for  CA01</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-bdc-for-ca01/m-p/5347918#M1231532</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi gurus , i am writing a bdc for ca01. here the screen sequence  changes when we create routing first time and second or subsequent time. how know that which screen  will be next when we are not passing the  group, as if  counter can  be  1  or more than 1 since  group is taken automatically.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;&amp;lt;text often considered offensive, removed&amp;gt;&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards &lt;/P&gt;&lt;P&gt;Aditya.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Matt on Mar 9, 2009 12:20 PM - "Urgently" read the Rules of Engagement&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Mar 2009 10:14:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-bdc-for-ca01/m-p/5347918#M1231532</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-03-09T10:14:34Z</dc:date>
    </item>
    <item>
      <title>Re: problem in BDC for  CA01</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-bdc-for-ca01/m-p/5347919#M1231533</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;Have a look at [this|&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="1962203"&gt;&lt;/A&gt;;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pushpraj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Mar 2009 10:18:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-bdc-for-ca01/m-p/5347919#M1231533</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-03-09T10:18:30Z</dc:date>
    </item>
    <item>
      <title>Re: problem in BDC for  CA01</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-bdc-for-ca01/m-p/5347920#M1231534</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Aditya,&lt;/P&gt;&lt;P&gt;  Try using a couner variable so that after every sequence you can increment it and also try capturing the messages using &lt;STRONG&gt;bdcmsgcoll&lt;/STRONG&gt; may be you can get some useful messages that might direct you.&lt;/P&gt;&lt;P&gt;And try to observe your recoding and the screen numbers coz only for the first screen if its differenet and for the other screen its the same you can split ypur code in to 2 parts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Much Regards,&lt;/P&gt;&lt;P&gt;Amuktha.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Mar 2009 10:20:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-bdc-for-ca01/m-p/5347920#M1231534</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-03-09T10:20:30Z</dc:date>
    </item>
    <item>
      <title>Re: problem in BDC for  CA01</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-bdc-for-ca01/m-p/5347921#M1231535</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi gurus , still my question is not answerd , &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; i am writing a bdc for this  ca01 , in CA01  transaction when group name is not given the system automatically  takes the group..  it can take  existing group or  create new group.  now when new group the group counter is 1 the screen sequence is for eg .  1  , 2 ,  3,   4,  and when group counter is more than  1 for that  group  screen  sequence is  1  , 2a,  2 , 3  ,4.    since  the group is internally  taken by  system we dont know  what  will be group no .... &lt;/P&gt;&lt;P&gt;                                              pls help how to  do this bdc  .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Mar 2009 12:10:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-bdc-for-ca01/m-p/5347921#M1231535</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-03-16T12:10:24Z</dc:date>
    </item>
    <item>
      <title>Re: problem in BDC for  CA01</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-bdc-for-ca01/m-p/5347922#M1231536</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can remove group from your BDC recording. if you do so evry time new group will be created when you create a routing for the material.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Mar 2009 12:14:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-bdc-for-ca01/m-p/5347922#M1231536</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-03-16T12:14:25Z</dc:date>
    </item>
    <item>
      <title>Re: problem in BDC for  CA01</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-bdc-for-ca01/m-p/5347923#M1231537</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;this will keep your screen sequence uniform each time&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Mar 2009 12:14:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-bdc-for-ca01/m-p/5347923#M1231537</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-03-16T12:14:58Z</dc:date>
    </item>
    <item>
      <title>Re: problem in BDC for  CA01</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-bdc-for-ca01/m-p/5347924#M1231538</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;closing thread&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Feb 2010 12:06:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/problem-in-bdc-for-ca01/m-p/5347924#M1231538</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-02-05T12:06:33Z</dc:date>
    </item>
  </channel>
</rss>

