topic Re: Difference between BDC and IDOC in Application Development and Automation Discussions

Difference between BDC and IDOC

Former Member — Mon, 16 Apr 2007 08:52:29 GMT

Hi,

Plz tell me the difference between BDC and IDOC

Thanks,

Vamsi

Re: Difference between BDC and IDOC

Former Member — Mon, 16 Apr 2007 08:55:16 GMT

HI,

Check this out to know the difference

Regrds,

Santosh

Re: Difference between BDC and IDOC

Former Member — Mon, 16 Apr 2007 08:57:59 GMT

Hi Vamsi,

<b>IDoc</b> is a intermediate document to exchange data between two SAP Systems.

*IDocs are structured ASCII files (or a virtual equivalent).

*Electronic Interchange Document

*They are the file format used by SAP R/3 to exchange data with foreign systems.

*Data Is transmitted in ASCII format, i.e. human readable form

*IDocs exchange messages

*IDocs are used like classical interface files

IDOC types are templates for specific message types depending on what is the business document, you want to exchange.

WE30 - you can create a IDOC type.

An IDOC with data, will have to be triggered by the application that is trying to send out the data.

FOr testing you can use WE19.

How to create idoc?

*WE30 - you can create a IDOC type

For more information in details on the same along with the examples can be viewed on:

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm

<b>BATCH DATA COMMUNICATION</b>

About Data Transfer In R/3 System

When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.

In the process of replacing current applications and transferring application data, two situations might occur:

• The first is when application data to be replaced is transferred at once, and only once.

• The second situation is to transfer data periodically from external systems to SAP and vice versa.

• There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.

The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called “batch input” or “batch data communication”.

1. SESSION METHOD

2. CALL TRANSACTION

3. DIRECT INPUT

Advantages offered by BATCH INPUT method:

1. Can process large data volumes in batch.

2. Can be planned and submitted in the background.

3. No manual interaction is required when data is transferred.

4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.

To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a “data transfer” program must map the data from the external system into the data structure required by the SAP batch input program.

The batch input program must build all of the input to execute the SAP transaction.

Hope this resolves your query.

Reward all the helpful answers.

Regards

Re: Difference between BDC and IDOC

Former Member — Mon, 16 Apr 2007 09:00:52 GMT

BDC means Batch data communication which does download or upload data from various systems like

upload data from windows GUI to SAP system and vice-versa

and download SAP data to windows flat file(text format)

BDC is mostly useful in update the huge amount of data in SAP(from flat file)

and IDOC means intermediate document

it is a container(which holds data) it does nothing

and while u attach this idoc to ALE that data transfer from one client to another client

IDOC only container

rewards if it helps u

JVS

Re: Difference between BDC and IDOC

Former Member — Mon, 16 Apr 2007 09:36:47 GMT

Hi Vamsi,

Plz gothrough this info,

IDoc:

IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system

Idocs are processed asynchronously and no information whatsoever is returned to the client,

Idocs – by using tRFC – support guaranteed delivery

With asynchronous links the sub- process on the client can be finished even if the communication line or the server is not available. In this case the message is stored in the database and the communication can be done later

The disadvantage of asynchronous links is that the sub-process on the server can not return information

the calling sub-process on the client. A special way for sending information back to the client is required. In addition, a special error handling mechanism is required

handle errors on the receiving side.

IDOCs may be more changable from release

release.

IDOCs are poorly documented

BDC:

Call Transaction:

In this method, the ABAP/4 program uses the call transaction <T-code > using <bdc_tab> mode <mode> update <update > method.

In ‘ Call Transaction ’ , the transactions are triggered at the time of processing itself and so the

ABAP program must do the error handling.

Synchronous Processing

We can update the database both synchronously and asynchronously. We can specify the mode in the program.

No batch input processing log

While execution it starts from the first.

Faster than session method

Session Method:

In this method, ABAP/4 program read the external data that is to be entered to the SAP system and stores the data in the batch input session. When the prgm has finished creating the session, we can run the session thro the TC SM35. This method involves FM like BDC_OPEN,BDC_INSERT,BDC_CLOSE

Whereas in Batch Input 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.

Asynchronous Processing

Synchronous Database update. During processing, no transaction is started until the previous transaction has been written to the database.

Detailed Log will be generated for all the sessions

While executing it wont start from the first.

will start from the place where it ends with error.

Not as fast as call transaction method

Rewords points.

Rgds,

P.Nag