topic Re: BDC Errors in Application Development and Automation Discussions

BDC Errors

Former Member — Sat, 10 May 2008 10:58:19 GMT

Hi Rocks,

Scenario 1: I am uploading 1000 records using session method. I have an error in 950th record. What will happen and howmany records will upload?

Scenario 2: I am uploading 1000 records using Call Transaction method. I have an error in 950th record. What will happen and howmany records will upload?

Re: BDC Errors

Former Member — Sat, 10 May 2008 10:59:49 GMT

999 records gets created in both the cases.

Re: BDC Errors

Former Member — Sat, 10 May 2008 11:14:13 GMT

Hi ,

Session is synchronus and call transaction is asynchrnous. As u told If both are same what is the use of syn and asyn?

Re: BDC Errors

Former Member — Sat, 10 May 2008 11:21:38 GMT

It is like this.

In a session, your progarm will create a session and you can process the created session whenever you like.

In a call transaction method, the upload of the records happen as and when you run the program.

Regards,

Ravi Kanth Talagana

Re: BDC Errors

Former Member — Sat, 10 May 2008 11:33:29 GMT

I think you are not aware of that syn and asyn? There is difference in updating in syn and asyn. Pls conform your answer.

Re: BDC Errors

Former Member — Sat, 10 May 2008 11:43:04 GMT

[Asynch vs Synch|http://help.sap.com/saphelp_nw70/helpdata/en/41/7af4cba79e11d1950f0000e82de14a/frameset.htm] ... it's just a question of waiting for the answer...

Jonathan

Re: BDC Errors

Former Member — Sat, 10 May 2008 12:26:15 GMT

thanks to all,

But I didnt get proper answer.

Re: BDC Errors

vinod_vemuru2 — Sat, 10 May 2008 12:39:16 GMT

Hi Buddula,

In both cases it will upload 999 records. But the difference is like this.

In call transaction method when error occurs at 950th record u have to process ur error record explicitely by capturing the messages. Check the messages into addition in call transaction. After call transaction statement u have to read this messages table with message type as error(E), abort(A) and dump(X). If u have any then u have to display this record information in report output so that user knows which record failed. Mean while all other records will be uploaded to the data base.

In session method once u execute ur program ur data base will not be executed unless u process the session. When u process the session system will automatically creates the error log. U can directly go the log and process the error records in fore ground by entering the correct values.

Difference between synchronous and Asynchronous

When u call the transaction a commit work module will be called by the system. In case of synchronous update system will not process the second record till the control comes back from the commit work module. In case of asynchronous mode once the transaction is finished it will come and process second record irrespective of first record is commited or not. Commit work will be done as a seperate process and not related to ur program execution.

Hope this is clear now.

Thanks,

Vinod.

Edited by: Vinod Kumar Vemuru on May 10, 2008 6:10 PM

Re: BDC Errors

Former Member — Sat, 10 May 2008 13:02:08 GMT

hi check this..

session it is always synchronous means if any record fails then it will not process the other reocrds so it will process 949 records..

call transaction it may be synchronous or asynchrous. if the process is synchronous the result is same means there will only 949 records will processed. if it is asynchronous then 999 records will processed if there is no error records found .

regards,

venakt

Re: BDC Errors

Former Member — Sat, 10 May 2008 14:44:26 GMT

Hi Vinod,

In both cases if all the records updates then why should we go for sync and asyn.

Re: BDC Errors

vinod_vemuru2 — Sat, 10 May 2008 16:21:29 GMT

Hi Buddula,

Let me explain with some practical example.

As i already told in case of synchronous update 2nd record will be processed only if the first record is updated to data base. Till this update happens control waits to process 2nd record.

If any error in 1st record then control will start processing 2nd record.

Assume power went exactly at the time of updating the first record to data base. In this case when u switch on the system for next time this particular record(1st) will be updated to data base.

So the summary is there will be no chance is losing data if transaction is successfull. At any point of time all the successful records will be updated to database.

Now consider the case of asynchronous for the same scenario.

Ur first record was successfully processed,Assume Data base update was delayed because of heavy load. Now ur control will not wait till data base is updated for first record and therefore it will start processing second record. Assume power went in this case also. When u switch on the system for next time this record will not be updated to database. So u will be losing data even ur transaction was success.

So if u want safety then go for Synchronous mode. But process will be slow because control has to wait till control comes back from commit work module.

If u want fastness in performance then go for asynchronous mode. But danger of losing data.

Hope this will be clear now.

Thanks,

Vinod.