Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

BDC

Former Member
0 Likes
431

Hi

Q:=> what are the different types of BDC. and the difference between them.

Q:=> what is synchronize and Asynchronize concept in BDC.

Q:=> what msgcol ?

plz explain.

Thanx u ppl.

1 ACCEPTED SOLUTION
3 REPLIES 3
Read only

Former Member
0 Likes
401

hi check this...

bdc is of 3 types..

1. direct method

2. session method

3. call transaction method..

synchronous is like series processing if one record failed the records may not be processed..asynchronous is like parallel processing...enen one record fails the process will be completed.

msgcoll is used in the call transaction method for capturing the error/success messages, by the function module..

format_message

regards,

venkat

Read only

Former Member
0 Likes
401

Hi sujit,

Please check this link

http://help.sap.com/erp2005_ehp_03/helpdata/EN/fa/097015543b11d1898e0000e8322d00/content.htm

Data Transfer Methods

You can use the following methods to transfer data:

---> Direct input: With direct input, the SAP function modules execute the consistency checks. However with batch input, these consistency checks are executed with the help of the screens. This means that direct input has considerable performance advantages.

---> CALL TRANSACTION: Data consistency check with the help of screen logic.

---> Batch input with batch input sessions: Data consistency check with the help of screen logic.

Difference between Batch Input and CALL TRANSACTION

If the direct input cannot be used for your task, this makes creating a data transfer program easier since the underlying transactions ensure that the data consistency checks are executed.

Batch input methods

With the batch input method, an ABAP program reads the external data that is to be entered in the SAP system and stores the data in a u201Cbatch input sessionu201D. The session records the actions that are required to transfer data into the system using normal SAP transactions.

When the program has generated the session, you can run the session to execute the SAP transactions in it. You can explicitly start and monitor a session with the batch input management function (by choosing System ® Services ® Batch input), or have the session run in the background processing system.

CALL TRANSACTION methods

In the second method, your program uses the ABAP statement CALL TRANSACTION USING to run an SAP transaction. External data does not have to be deposited in a session for later processing. Instead, the entire batch input process takes place inline in your program.

Asynchronous updating.

In this mode, the called transaction does not wait for any updates it produces to be completed. It simply passes the updates to the SAP update service.Asynchronous processing therefore usually results in faster execution of your batch input program.

Asynchronous processing is NOT recommended for processing any larger amount of data. This is because the called transaction receives no completion message from the update module in asynchronous updating. The calling batch input program, in turn, cannot determine whether a called transaction ended with a successful update of the database or not.

If you use asynchronous updating, then you will need to use the update management facility (transaction SM12) to check whether updates have been terminated abnormally during session processing. Error analysis and recovery is less convenient than with synchronous updating.

Synchronous updating.

In this mode, the called transaction waits for any updates that it produces to be completed. Execution is slower than with asynchronous updating because called transactions wait for updating to be completed. However, the called transaction is able to return any update error message that occurs to your program. It's much easier for you to analyze and recover from errors.

We handle errors in CALL TRANSACTION BDC method using BDCMSGCOLL Structure

Using CALL TRANSACTION USING for Data Transfer

http://help.sap.com/erp2005_ehp_03/helpdata/EN/fa/09715a543b11d1898e0000e8322d00/content.htm

Creating Batch Input Sessions

http://help.sap.com/erp2005_ehp_03/helpdata/EN/fa/097119543b11d1898e0000e8322d00/content.htm

http://help.sap.com/erp2005_ehp_03/helpdata/EN/fa/097126543b11d1898e0000e8322d00/content.htm

http://help.sap.com/erp2005_ehp_03/helpdata/EN/fa/097133543b11d1898e0000e8322d00/content.htm

http://help.sap.com/erp2005_ehp_03/helpdata/EN/fa/097140543b11d1898e0000e8322d00/content.htm

http://help.sap.com/erp2005_ehp_03/helpdata/EN/fa/09714d543b11d1898e0000e8322d00/content.htm

Best regards,

raam