<?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/3183715#M758012</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;atch Data Communication or BDC is a batch interfacing&lt;/P&gt;&lt;P&gt;technique that SAP developed.  It is mainly used for&lt;/P&gt;&lt;P&gt;uploading data into the SAP R/3 system.   BDC works by&lt;/P&gt;&lt;P&gt;simulating the user input from transactional screen via an&lt;/P&gt;&lt;P&gt;ABAP program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The data input data file will come in the form of a flat&lt;/P&gt;&lt;P&gt;file which the user save as file type txt file or prn file&lt;/P&gt;&lt;P&gt;from the Microsoft Excel program.  An Abaper will create a&lt;/P&gt;&lt;P&gt;program to read the text file and upload into the SAP system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Normally, the tcode SHDB will be used to record the&lt;/P&gt;&lt;P&gt;transaction code the user used.  After, the simulation, the&lt;/P&gt;&lt;P&gt;Abaper can generate a sample program and modify from there.&lt;/P&gt;&lt;P&gt; It makes the programming easier and faster.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 28 Dec 2007 08:32:23 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-12-28T08:32:23Z</dc:date>
    <item>
      <title>bdc</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/3183714#M758011</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;whwt is BDC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Dec 2007 07:14:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/3183714#M758011</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-28T07:14:28Z</dc:date>
    </item>
    <item>
      <title>Re: bdc</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/3183715#M758012</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;atch Data Communication or BDC is a batch interfacing&lt;/P&gt;&lt;P&gt;technique that SAP developed.  It is mainly used for&lt;/P&gt;&lt;P&gt;uploading data into the SAP R/3 system.   BDC works by&lt;/P&gt;&lt;P&gt;simulating the user input from transactional screen via an&lt;/P&gt;&lt;P&gt;ABAP program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The data input data file will come in the form of a flat&lt;/P&gt;&lt;P&gt;file which the user save as file type txt file or prn file&lt;/P&gt;&lt;P&gt;from the Microsoft Excel program.  An Abaper will create a&lt;/P&gt;&lt;P&gt;program to read the text file and upload into the SAP system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Normally, the tcode SHDB will be used to record the&lt;/P&gt;&lt;P&gt;transaction code the user used.  After, the simulation, the&lt;/P&gt;&lt;P&gt;Abaper can generate a sample program and modify from there.&lt;/P&gt;&lt;P&gt; It makes the programming easier and faster.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Dec 2007 08:32:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/3183715#M758012</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-28T08:32:23Z</dc:date>
    </item>
    <item>
      <title>Re: bdc</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/3183716#M758013</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;This is in Breif abt BDC.... I guess this would be helpful...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BDC - BATCH DATA COMMUNICATIONS&lt;/P&gt;&lt;P&gt;BDC allows you to perform database updates in the background using standard SAP transactions. The resultant entries will be as if the user had manually entered the data via SAP. This means that you do not bypass any of the standard SAP consistency checks, authorisations etc. There are two main methods of ABAP BDC, these are Call Transaction and Batch Input. Other methods of update include Direct update, Idoc and BAPI&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data transfer program, an effective and efficient way of transferring large amount of data into your new system (SAP)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Two steps involved in data transfer are "&lt;STRONG&gt;C&lt;/STRONG&gt;onverting data from your legacy system into the required flat file format" &lt;STRONG&gt;and&lt;/STRONG&gt; "&lt;STRONG&gt;A&lt;/STRONG&gt;utomatically entering data into the SAP system.  A SAP data transfer program reads the prepared data from the flat file and moves it into R/3".&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Dec 2007 08:34:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/3183716#M758013</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-28T08:34:15Z</dc:date>
    </item>
  </channel>
</rss>

