topic aboutbdc in Application Development and Automation Discussions

aboutbdc

Former Member — Sat, 30 Sep 2006 13:32:20 GMT

higurus,

while iam processing BDC session system is crashed iwant toknow howmanyrecords have successfully uploaded. how about doing it.how to resehedule the failed ones.

does call transaction methos returns SY-subrc orsession method returns explain.

regards.

Due points will begiven.

Re: aboutbdc

Former Member — Sun, 01 Oct 2006 08:33:52 GMT

Hi,

Whenever you are using BDC's. You can use two methods Call transaction or session method.

When you use call transaction you write statement as follows:

Call transaction 'VA01' messages in messtab.

This table messtab contains all the messages encountered during the processing of this particular transaction.

If you use session method then in SM35 tcode, you can see the log for each and every session.

That way you can keep a track of ur BDC.

Re: aboutbdc

Former Member — Sun, 01 Oct 2006 13:06:53 GMT

Hi,

In session method you can track the

processed records by seeing the log in sm35.

Regards,

amole

Re: aboutbdc

Former Member — Sun, 01 Oct 2006 13:17:49 GMT

Hi,

call transaction method returns sy-subrc value

but session will not return subrc value.

error records can

be again reprocessed in session method using

session name.

Using call transaction If any error occurs you

can store the recorss in internal table and

send this records to BDC session by

calling BDC_open_group,BDC_insert,BDC_close_group

Error Analysis and Restart Capability

Unlike batch input methods using sessions, CALL TRANSACTION USING processing does not provide any special handling for incorrect transactions. There is no restart capability for transactions that contain errors or produce update failures.

You can handle incorrect transactions by using update mode S (synchronous updating) and checking the return code from CALL TRANSACTION USING. If the return code is anything other than 0, then you should do the following:

write out or save the message table

use the BDCDATA table that you generated for the CALL TRANSACTION USING to generate a batch input session for the faulty transaction. You can then analyze the faulty transaction and correct the error using the tools provided in the batch input management facility.

also check link

http://help.sap.com/saphelp_nw2004s/helpdata/en/69/c2501a4ba111d189750000e8322d00/frameset.htm

regards

amole