<?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: BDC in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2045001#M420985</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hai basheer&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Background scheduling&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;SM36 	-	Create background job&lt;/P&gt;&lt;P&gt;SM37 	-	Background job monitor, Select background jobs&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;2)error handling is automatic&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;In call transaction use structure BDCMSGCOLL and for session method go to sm35&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;3)syncronus&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;During the processing no transaction is stored until the previous transaction has been written to the Database. This is called Synchronous Database update.&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4)RSBDCSUB&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Ready made program for Release batch-input sessions automatically&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5) Huge amount of DATA ( it seems it is not a genuine answer)&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;More than 10000 records&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;**&lt;STRONG&gt;Please reward suitable points&lt;/STRONG&gt;***&lt;/P&gt;&lt;P&gt;With Regards&lt;/P&gt;&lt;P&gt;Navin Khedikar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 28 Mar 2007 04:19:47 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-03-28T04:19:47Z</dc:date>
    <item>
      <title>BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2044997#M420981</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ALL&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  When do we go for SESHEN METORD in BDC &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what i know is :-&lt;/P&gt;&lt;P&gt;1) Background scheduling&lt;/P&gt;&lt;P&gt;2)error handling is automatic&lt;/P&gt;&lt;P&gt;3)syncronus&lt;/P&gt;&lt;P&gt;4)RSBDCSUB&lt;/P&gt;&lt;P&gt;5) Huge amount of DATA  ( it seems it is not a genuine answer)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  Hope you know what i need.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;basheer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Mar 2007 04:10:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2044997#M420981</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-28T04:10:56Z</dc:date>
    </item>
    <item>
      <title>Re: BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2044998#M420982</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;one time process and Immediate Update.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Mar 2007 04:14:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2044998#M420982</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-28T04:14:50Z</dc:date>
    </item>
    <item>
      <title>Re: BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2044999#M420983</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mohammed Ahmed,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this documentation about Session method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this method you transfer data from internal table to database table through sessions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unless session is processed, the data is not transferred to database table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BDC_OPEN_GROUP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You create the session through program by BDC_OPEN_GROUP function. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Parameters to this function are: &lt;/P&gt;&lt;P&gt;&amp;#149; User Name: User name &lt;/P&gt;&lt;P&gt;&amp;#149; Group: Name of the session&lt;/P&gt;&lt;P&gt;&amp;#149; Lock Date: The date on which you want to process the session.&lt;/P&gt;&lt;P&gt;&amp;#149; Keep: This parameter is passed as &amp;#145;X&amp;#146; when you want to retain session after&lt;/P&gt;&lt;P&gt;processing it or &amp;#145; &amp;#145; to delete it after processing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BDC_INSERT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This function creates the session &amp;amp; data is transferred to Session.&lt;/P&gt;&lt;P&gt;Parameters to this function are:&lt;/P&gt;&lt;P&gt;&amp;#149; Tcode: Transaction Name &lt;/P&gt;&lt;P&gt;&amp;#149; Dynprotab: BDC Data&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BDC_CLOSE_GROUP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This function closes the BDC Group. No Parameters.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some additional information for session processing&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this resolves your query.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward all the helpful answers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Mar 2007 04:15:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2044999#M420983</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-28T04:15:28Z</dc:date>
    </item>
    <item>
      <title>Re: BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2045000#M420984</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mohammed , &lt;/P&gt;&lt;P&gt;  Most of the reasons you haev mentioned are correct .&lt;/P&gt;&lt;P&gt; When volume of data is large : In call transaction the transaction is run only for one set of data , for the next set another call has to be made . So session is used when volume of data is large i.e. the transaction is to be called a number of times.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For this very reason that you can call the transaction a number of times so session is also used when we want to schedule the job in background.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is easier to handle errors in session as we can handle all the errors at a go but in call transaction for each call we need to handle errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Arun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Mar 2007 04:16:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2045000#M420984</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-28T04:16:46Z</dc:date>
    </item>
    <item>
      <title>Re: BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2045001#M420985</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hai basheer&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Background scheduling&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;SM36 	-	Create background job&lt;/P&gt;&lt;P&gt;SM37 	-	Background job monitor, Select background jobs&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;2)error handling is automatic&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;In call transaction use structure BDCMSGCOLL and for session method go to sm35&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;3)syncronus&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;During the processing no transaction is stored until the previous transaction has been written to the Database. This is called Synchronous Database update.&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4)RSBDCSUB&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Ready made program for Release batch-input sessions automatically&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5) Huge amount of DATA ( it seems it is not a genuine answer)&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;More than 10000 records&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;**&lt;STRONG&gt;Please reward suitable points&lt;/STRONG&gt;***&lt;/P&gt;&lt;P&gt;With Regards&lt;/P&gt;&lt;P&gt;Navin Khedikar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Mar 2007 04:19:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2045001#M420985</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-28T04:19:47Z</dc:date>
    </item>
    <item>
      <title>Re: BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2045002#M420986</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Batch Input Session: In this method data consistency is checked with the help of screen logic.&lt;/P&gt;&lt;P&gt;As soon as the program generates the  session, you will be able to run the session in order to execute the SAP transactions in it. Moreover, you can start the session, and at the same time, can monitor a session with the help of batch input management function. For this you have to choose:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;System à Services à Batch input. Moreover, you can have the session run in the background processing.&lt;/P&gt;&lt;P&gt;Batch input method is a type of data transfer method. It is used for bulk data transfer; it is one of the primary ways by which data can transferred into the R/3 System. This method is not for near real-time data transfers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are various typical uses of batch input. One of the ways includes the one-time import of data. This import of data is from a legacy system into a newly installed R/3 System. In addition to it, another typical use is for periodic (i.e. hourly, daily..., and so on) transfers of data. These transfers are from external systems or legacy systems which are still in use into R/3 system where all enterprise data is consolidated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The R/3 applications deliver different programs for batch input, which are ready to be used. However, in some cases a customer has to write his or her own batch input program. This is required in order to convert the concerned data from a legacy System or from a proprietary format into an R/3 data format.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;keerthi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Mar 2007 04:27:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2045002#M420986</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-28T04:27:42Z</dc:date>
    </item>
    <item>
      <title>Re: BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2045003#M420987</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Arun&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  Thanks for the answer it was exactly what i ws looking for can you put some more light onthsi  please.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When volume of data is large : In call transaction the transaction is run only for one set of data , for the next set another call has to be made . So session is used when volume of data is large i.e. the transaction is to be called a number of times.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;Query:&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) One set of data means? suppose i have a flat file with 1lakhs records i gave the path and it starts to update both CALL TRANS AND SESHEN . But what is one set of DATA? will we hav to take flat files dynamcally&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thansk  a lot&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Mar 2007 06:33:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2045003#M420987</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-28T06:33:14Z</dc:date>
    </item>
    <item>
      <title>Re: BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2045004#M420988</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mohammed,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For such huge amount of data , it is better to go for the Bapi Method .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As asked by you , in Arun's post, the one set of data means that in Session method we can create a session for each set of data individually for the same program and release them at a later time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For more info check my post which I have posted or revert back.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this resolves your query.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward all the helpful answers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Mar 2007 06:37:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2045004#M420988</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-28T06:37:30Z</dc:date>
    </item>
    <item>
      <title>Re: BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2045005#M420989</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi , &lt;/P&gt;&lt;P&gt;  What i ment by one set of data is all the data you need to execute the transaction once.&lt;/P&gt;&lt;P&gt;Consider this scenario you want to upload 10 materials into your system using BDC , if you use call transaction you will have to call the transaction 10 times , once for each material , but in case of Session all this is done at one go , tough internally when you execute the session , the process might be the same , but for you as a user the process is done only once.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One more advantage of using the session mehod is in case there is some sort of system error when you execute the session you also have the option to execute it again , but in case of call transaction , you will have to execute the entire program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regadrs&lt;/P&gt;&lt;P&gt;Arun&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Please assign points if reply is useful&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Mar 2007 06:39:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2045005#M420989</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-28T06:39:47Z</dc:date>
    </item>
    <item>
      <title>Re: BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2045006#M420990</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dar Kiran &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Can you put som more light on thsi satements &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;System à Services à Batch input. Moreover, you can have the session run in the background processing.&lt;/P&gt;&lt;P&gt;Batch input method is a type of data transfer method. It is used for bulk data transfer; it is one of the primary ways by which data can transferred into the R/3 System. &lt;U&gt;&lt;B&gt;This method is not for near real-time data transfers.&lt;/B&gt;&lt;/U&gt;&lt;BR /&gt;&lt;BR /&gt;There are various typical uses of batch input. One of the ways includes the one-time import of data. This import of data is from a legacy system into a newly installed R/3 System. &lt;U&gt;&lt;B&gt;In addition to it, another typical use is for periodic (i.e. hourly, daily..., and so on) transfers of data.&lt;/B&gt;&lt;/U&gt; These transfers are from external systems or legacy systems which are still in use into R/3 system where all enterprise data is consolidated.&lt;BR /&gt;&lt;BR /&gt;&lt;U&gt;Query :&lt;/U&gt;&lt;BR /&gt;1) so we dont use &lt;B&gt;&lt;/B&gt;&lt;/P&gt;&lt;P&gt;Batch input&lt;/P&gt; methord in real time ? if so what is the other one used?&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) If i have to run BDC every day night 1am &lt;/P&gt;&lt;P&gt;   to upload a file from my desk top  then? what is to process...... SHOULD I        CREATE FLAT FILE WITH SAME DLETING TH OLD FILE EVERY DAY?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Mar 2007 06:49:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2045006#M420990</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-28T06:49:21Z</dc:date>
    </item>
  </channel>
</rss>

