<?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/3251407#M776397</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sandeep,&lt;/P&gt;&lt;P&gt;The following may be helpful regarding BDC and give u a fair idea of what is happening with SHDB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;What is BDC&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;BDC ( Batch Data Communication ) is used for uploading mass data into SAP system. In SAP system BDC also referred to batch input or data tranfer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Typical Uses&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Typical uses of batch input include the one-time import of data from a legacy system into a newly installed R/3 System. Another typical use is for periodic transfers of data from external systems or legacy systems that are still in use into SAP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Background of BDC&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;To ensure data consistency in SAP system, we must not update SAP data directly from ABAP program. We must upload data through similar program flow compared to manual input by user. SAP provide this by BDC. BDC works by simulating the user input from transactional screen via an ABAP program. This means that you do not bypass any of the standard SAP consistency checks, authorisations, update conjunction tables, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;How it works&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Data input entered by user simulated in BDC by data packet. The transaction then started using this internal table as the input and executed in the background.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data packet is an internal table has a structure of BDCDATA, it has fields:&lt;/P&gt;&lt;P&gt;1. PROGRAM (program name)&lt;/P&gt;&lt;P&gt;2. DYNPRO (screen number)&lt;/P&gt;&lt;P&gt;3. DYNBEGIN (New screen start) X=new screen&lt;/P&gt;&lt;P&gt;4. FNAM (Field name)&lt;/P&gt;&lt;P&gt;5. FVAL (Field value)&lt;/P&gt;&lt;P&gt;Data packet contain of screen by screen packets. One screen packet contain:&lt;/P&gt;&lt;P&gt;1. Screen no&lt;/P&gt;&lt;P&gt;2. Cursor position&lt;/P&gt;&lt;P&gt;3. User command&lt;/P&gt;&lt;P&gt;4. Input fields&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;To accomodate you to build data packet, SAP provide BDC recording in tcode SHDB.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Do following action:&lt;/P&gt;&lt;P&gt;1. Go to tcode SHDB&lt;/P&gt;&lt;P&gt;2. click "New recording", enter recording name to identified your record, and TCode to be recorded.&lt;/P&gt;&lt;P&gt;3. You will enter recording mode of the transaction, simulate action you want to perform in this transaction&lt;/P&gt;&lt;P&gt;4. At the end it will result internal table ready to upload to data transfer methods (Call transaction or BDC sessions).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After internal table created then we pass this to data transfer methods. There are two alternatives of data transfer methods, using Call Transaction or BDC session.&lt;/P&gt;&lt;P&gt;Call transaction performed by calling command &amp;#145;Call Transaction&amp;#146;. ABAP program must do the error handling based on returning table from call transaction command. It is used for real-time interfaces and custom error handling &amp;amp; logging features. This is suitable when processing sequential update, it means, next data will depend on previous data.&lt;/P&gt;&lt;P&gt;In BDC Sessions, the ABAP program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Reward if helpful.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thankyou,&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 08 Jan 2008 05:35:22 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-01-08T05:35:22Z</dc:date>
    <item>
      <title>BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/3251405#M776395</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When we upload data using upload function module then i am not getting why to put code created by SHDB in that report programm???........plz tell me exact relation betn SHDB and report program which uploads data.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Jan 2008 05:30:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/3251405#M776395</guid>
      <dc:creator>former_member530652</dc:creator>
      <dc:date>2008-01-08T05:30:09Z</dc:date>
    </item>
    <item>
      <title>Re: BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/3251406#M776396</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;SHDB for recording....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And SM35 is to process a session in case u use BDC Session method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check out these links for more details&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html" target="test_blank"&gt;http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap-img.com/abap/learning-bdc-programming.htm" target="test_blank"&gt;http://www.sap-img.com/abap/learning-bdc-programming.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap-img.com/bdc.htm" target="test_blank"&gt;http://www.sap-img.com/bdc.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.sap.com/www.sappoint.com/abap/bdcconcept.pdf" target="test_blank"&gt;www.sappoint.com/abap/bdcconcept.pdf&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap-img.com/abap/learning-bdc-programming.htm" target="test_blank"&gt;http://www.sap-img.com/abap/learning-bdc-programming.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapdevelopment.co.uk/bdc/bdchome.htm" target="test_blank"&gt;http://www.sapdevelopment.co.uk/bdc/bdchome.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.planetsap.com/bdc_main_page.htm" target="test_blank"&gt;http://www.planetsap.com/bdc_main_page.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;even LSMW is other option.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*****************&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bdc uses shdb for recording the first transaction .Give your session name &lt;/P&gt;&lt;P&gt;Then press new recording.&lt;/P&gt;&lt;P&gt;Give name and the transaction .&lt;/P&gt;&lt;P&gt;Start recording .&lt;/P&gt;&lt;P&gt;Give all the required fields .You will get a tabular content .&lt;/P&gt;&lt;P&gt;Use this to program bdc in se38 .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After programming goto sm35 .&lt;/P&gt;&lt;P&gt;Give the session name .&lt;/P&gt;&lt;P&gt;select the session and click on process .&lt;/P&gt;&lt;P&gt;Select the type of process , Backgroun , foreground or display error only .&lt;/P&gt;&lt;P&gt;Select extended log ,Expert mode .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example program :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TYPES : BEGIN OF STRUCT ,&lt;/P&gt;&lt;P&gt;MATNR TYPE RMMG1-MATNR ,&lt;/P&gt;&lt;P&gt;END OF STRUCT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA :W_GRPID TYPE APQI-GROUPID .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA :IT_MARA TYPE TABLE OF STRUCT WITH HEADER LINE,&lt;/P&gt;&lt;P&gt;IT_BDCDATA TYPE TABLE OF BDCDATA WITH HEADER LINE,&lt;/P&gt;&lt;P&gt;GT_CNT TYPE MARA-BISMT .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;initialization.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT MATNR&lt;/P&gt;&lt;P&gt;FROM MARA&lt;/P&gt;&lt;P&gt;INTO CORRESPONDING FIELDS OF TABLE IT_MARA&lt;/P&gt;&lt;P&gt;up to 10 rows&lt;/P&gt;&lt;P&gt;WHERE MTART = 'HAWA'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;W_GRPID = 'SESSION-ID'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;START-OF-SELECTION.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL FUNCTION 'BDC_OPEN_GROUP'&lt;/P&gt;&lt;P&gt;EXPORTING&lt;/P&gt;&lt;P&gt;CLIENT = SY-MANDT&lt;/P&gt;&lt;P&gt;GROUP = W_GRPID&lt;/P&gt;&lt;P&gt;KEEP = 'X'&lt;/P&gt;&lt;P&gt;USER = SY-UNAME.&lt;/P&gt;&lt;P&gt;IF SY-SUBRC 0.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO &lt;/P&gt;&lt;P&gt;WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. &lt;/P&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOOP AT IT_MARA.&lt;/P&gt;&lt;P&gt;GT_CNT = GT_CNT + 1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PERFORM : F001-BDC_A USING 'SAPLMGMM' '0060' 'X',&lt;/P&gt;&lt;P&gt;F002-BDC_B USING 'RMMG1-MATNR' IT_MARA-MATNR ,&lt;/P&gt;&lt;P&gt;F002-BDC_B USING 'BDC_OKCODE' '/00',&lt;/P&gt;&lt;P&gt;F001-BDC_A USING 'SAPLMGMM' '0070' 'X',&lt;/P&gt;&lt;P&gt;F002-BDC_B USING 'MSICHTAUSW-KZSEL(01)' 'X' ,&lt;/P&gt;&lt;P&gt;F002-BDC_B USING 'MSICHTAUSW-KZSEL(02)' 'X' ,&lt;/P&gt;&lt;P&gt;F002-BDC_B USING 'BDC_OKCODE' '=ENTR',&lt;/P&gt;&lt;P&gt;F001-BDC_A USING 'SAPLMGMM' '4004' 'X',&lt;/P&gt;&lt;P&gt;F002-BDC_B USING 'MARA-BISMT' GT_CNT ,&lt;/P&gt;&lt;P&gt;F002-BDC_B USING 'BDC_OKCODE' '=BU',&lt;/P&gt;&lt;P&gt;F003-BDC_C USING 'MM02'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ENDLOOP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL FUNCTION 'BDC_CLOSE_GROUP' .&lt;/P&gt;&lt;P&gt;IF SY-SUBRC 0.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO &lt;/P&gt;&lt;P&gt;WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. &lt;/P&gt;&lt;P&gt;ENDIF..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;amp;----&lt;/P&gt;&lt;HR originaltext="---------------------------------------------------------------" /&gt;&lt;P&gt;*&amp;amp; Form F001-BDC_A&lt;/P&gt;&lt;P&gt;&amp;amp;----&lt;/P&gt;&lt;HR originaltext="---------------------------------------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;text &lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="--------------------------------------------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&amp;gt;PROGRAM text &lt;/P&gt;&lt;P&gt;--&amp;gt;DYNPRO text &lt;/P&gt;&lt;P&gt;--&amp;gt;DYNBEG text &lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="--------------------------------------------------------------------" /&gt;&lt;P&gt;FORM F001-BDC_A USING program dynpro dynbeg.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IT_BDCDATA-PROGRAM = PROGRAM.&lt;/P&gt;&lt;P&gt;IT_BDCDATA-dynpro = DYNPRO.&lt;/P&gt;&lt;P&gt;IT_BDCDATA-dynbegin = DYNBEG.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;APPEND IT_BDCDATA .&lt;/P&gt;&lt;P&gt;CLEAR IT_BDCDATA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ENDFORM. "F001-BDC_A&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;amp;----&lt;/P&gt;&lt;HR originaltext="---------------------------------------------------------------" /&gt;&lt;P&gt;*&amp;amp; Form F002-BDC_B&lt;/P&gt;&lt;P&gt;&amp;amp;----&lt;/P&gt;&lt;HR originaltext="---------------------------------------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;text &lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="--------------------------------------------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&amp;gt;FNAM text &lt;/P&gt;&lt;P&gt;--&amp;gt;FVAL text &lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="--------------------------------------------------------------------" /&gt;&lt;P&gt;FORM F002-BDC_B USING FNAM FVAL .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IT_BDCDATA-FNAM = FNAM .&lt;/P&gt;&lt;P&gt;IT_BDCDATA-FVAL = FVAL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;APPEND IT_BDCDATA .&lt;/P&gt;&lt;P&gt;CLEAR IT_BDCDATA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ENDFORM. "F002-BDC_B&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;amp;----&lt;/P&gt;&lt;HR originaltext="----------------------------------------------------------------" /&gt;&lt;P&gt;*&amp;amp; Form F003-BDC_C&lt;/P&gt;&lt;P&gt;&amp;amp;----&lt;/P&gt;&lt;HR originaltext="----------------------------------------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;text &lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="---------------------------------------------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&amp;gt;P_0124 text &lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="---------------------------------------------------------------------" /&gt;&lt;P&gt;FORM F003-BDC_C USING TRCODE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL FUNCTION 'BDC_INSERT'&lt;/P&gt;&lt;P&gt;EXPORTING&lt;/P&gt;&lt;P&gt;TCODE = TRCODE&lt;/P&gt;&lt;P&gt;TABLES&lt;/P&gt;&lt;P&gt;DYNPROTAB = IT_BDCDATA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REFRESH IT_BDCDATA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;***************************&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Jan 2008 05:33:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/3251406#M776396</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-08T05:33:34Z</dc:date>
    </item>
    <item>
      <title>Re: BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/3251407#M776397</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sandeep,&lt;/P&gt;&lt;P&gt;The following may be helpful regarding BDC and give u a fair idea of what is happening with SHDB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;What is BDC&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;BDC ( Batch Data Communication ) is used for uploading mass data into SAP system. In SAP system BDC also referred to batch input or data tranfer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Typical Uses&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Typical uses of batch input include the one-time import of data from a legacy system into a newly installed R/3 System. Another typical use is for periodic transfers of data from external systems or legacy systems that are still in use into SAP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Background of BDC&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;To ensure data consistency in SAP system, we must not update SAP data directly from ABAP program. We must upload data through similar program flow compared to manual input by user. SAP provide this by BDC. BDC works by simulating the user input from transactional screen via an ABAP program. This means that you do not bypass any of the standard SAP consistency checks, authorisations, update conjunction tables, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;How it works&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Data input entered by user simulated in BDC by data packet. The transaction then started using this internal table as the input and executed in the background.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data packet is an internal table has a structure of BDCDATA, it has fields:&lt;/P&gt;&lt;P&gt;1. PROGRAM (program name)&lt;/P&gt;&lt;P&gt;2. DYNPRO (screen number)&lt;/P&gt;&lt;P&gt;3. DYNBEGIN (New screen start) X=new screen&lt;/P&gt;&lt;P&gt;4. FNAM (Field name)&lt;/P&gt;&lt;P&gt;5. FVAL (Field value)&lt;/P&gt;&lt;P&gt;Data packet contain of screen by screen packets. One screen packet contain:&lt;/P&gt;&lt;P&gt;1. Screen no&lt;/P&gt;&lt;P&gt;2. Cursor position&lt;/P&gt;&lt;P&gt;3. User command&lt;/P&gt;&lt;P&gt;4. Input fields&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;To accomodate you to build data packet, SAP provide BDC recording in tcode SHDB.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Do following action:&lt;/P&gt;&lt;P&gt;1. Go to tcode SHDB&lt;/P&gt;&lt;P&gt;2. click "New recording", enter recording name to identified your record, and TCode to be recorded.&lt;/P&gt;&lt;P&gt;3. You will enter recording mode of the transaction, simulate action you want to perform in this transaction&lt;/P&gt;&lt;P&gt;4. At the end it will result internal table ready to upload to data transfer methods (Call transaction or BDC sessions).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After internal table created then we pass this to data transfer methods. There are two alternatives of data transfer methods, using Call Transaction or BDC session.&lt;/P&gt;&lt;P&gt;Call transaction performed by calling command &amp;#145;Call Transaction&amp;#146;. ABAP program must do the error handling based on returning table from call transaction command. It is used for real-time interfaces and custom error handling &amp;amp; logging features. This is suitable when processing sequential update, it means, next data will depend on previous data.&lt;/P&gt;&lt;P&gt;In BDC Sessions, the ABAP program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Reward if helpful.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thankyou,&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Jan 2008 05:35:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/3251407#M776397</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-08T05:35:22Z</dc:date>
    </item>
  </channel>
</rss>

