<?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 bdc in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/3234867#M771839</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what is the difference between&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BATCH INPUT METHOD,&lt;/P&gt;&lt;P&gt;RECORDING,&lt;/P&gt;&lt;P&gt;BAPI,&lt;/P&gt;&lt;P&gt;IDOC.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 31 Dec 2007 05:28:19 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-12-31T05:28:19Z</dc:date>
    <item>
      <title>bdc</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/3234867#M771839</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what is the difference between&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BATCH INPUT METHOD,&lt;/P&gt;&lt;P&gt;RECORDING,&lt;/P&gt;&lt;P&gt;BAPI,&lt;/P&gt;&lt;P&gt;IDOC.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Dec 2007 05:28:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/3234867#M771839</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-31T05:28:19Z</dc:date>
    </item>
    <item>
      <title>Re: bdc</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/3234868#M771840</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;Batch input method means passing the data between two systems through the internal table.in this we use session and call transaction method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;recording means we just record the values of any screen whatever the values to be stored and show it as a program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BAPI means it is aremote enabled function module.we can pass the data between two systems like sap and sap systems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;idoc is an intermediate document can be send between two systems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward points, if it useful.&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;satish.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Dec 2007 05:33:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/3234868#M771840</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-31T05:33:04Z</dc:date>
    </item>
    <item>
      <title>Re: bdc</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/3234869#M771841</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;BATCH INPUT METHOD (BDC &amp;amp; LSMW)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Batch 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;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;RECORDING,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;With recording, user can avoid manual search for fields and tables required in a program including screen numbers. SHDB is the transaction code.&lt;/P&gt;&lt;P&gt;&lt;A href="http://goldenink.com/abap/shdb.html" target="test_blank"&gt;http://goldenink.com/abap/shdb.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;BAPI&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BAPI (Business Application Programming Interface) is an API method of a business object which intern is a RFC enabled Function Module.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Business Objects are the Objects which has business sence associated to it. Ex. Sales Orders, Purchase Orders etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Properties of BAPI are:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Every BAPI name should start with letters 'BAPI'. &lt;/P&gt;&lt;P&gt;It is an API method of a Business Object. &lt;/P&gt;&lt;P&gt;it does not contain a internal COMMIT statement in the Function Module. &lt;/P&gt;&lt;P&gt;It does not contain "CALL TRANSACTION" statements. &lt;/P&gt;&lt;P&gt;BAPI do not raise 'EXCEPTIONS'. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a RETURN structure is defined as an interface parameter of a BAPI which is used to log all the errors, warnings and the successful processes tha are triggered in the course of execution of a BAPI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A successful execution of a BAPI requires the data to be commited and this process of performing a COMMIT is achieved by calling the BAPI_TRANSACTION_COMMIT' explicitly if there are no errors logged in the RETURN structure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are two types of BAPI's: Instance Dependent &amp;amp; Instance Independent.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BAPI provides an access to the SAP system for external applications to have the business data processed in the form of web services. When BAPI's are used to post the data in SAP system these are used as Function Modules.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;IDOC.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward Points if useful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Dec 2007 06:04:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/3234869#M771841</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-31T06:04:07Z</dc:date>
    </item>
  </channel>
</rss>

