topic Re: REFRESH BDCDATA in Application Development and Automation Discussions

REFRESH BDCDATA

Former Member — Wed, 23 Jun 2010 05:02:42 GMT

Hi Gurus ,

Could anyone guide me for the folowing scenario : -BDC Call transaction

A custom report was created to extend payee vendors for every principal vendors in two company codes : xxxx and yyyy.

But when ever tested : the payee vendors were getting created for one company code and later when the same payee vendor details were being passed as Reference Vendor information : it was not creating vendors in the other company code : yyyy.

using FK01 : creating vendors .

1st Step : provide company code (xxxx) and Account groupdetails in FK01 : vendor created through custom interface.

2nd Step : created vendor details : Vendor Number (created in step1), Company Code (yyyy), Account group(grp1) and Reference Vendor details : Vendor number (created in step1) , Company Code (xxxx) were suppose to be passed through

the BDC process.

While testing the BDC the first step was executing fine no issues but while executing the second step the reference field details were not populating automatically (it was blank) although the Recording was correct , all the neccessary BDC code were available .

Now between the first and second creation there was a BDC table which was being populated with DYNNAME , FNAME FVAL detatils: all the BDC details were in that table. I have used a REFRESH BDCDATA between 1st and 2 nd step (as mentioned above) and then it started creating the vendors with reference details also.

Could you please tell me the importance of REFRESH BDCDATA ?

My question is : what is the importance of REFRESH BDCDATA : since after adding that i could check that all the neccessary details were being populated to the screen fields of FK01 (first screen) through BDC ?

Thanks

Kylietisha

Edited by: kylietisha on Jun 23, 2010 7:03 AM

Re: REFRESH BDCDATA

Former Member — Wed, 23 Jun 2010 05:14:24 GMT

BDCDATA is the structure in which all the information related to the recording, i,e the screen no, fields names, ok_codes, etc will be populated based on which the recording will run. Its important to refresh this particular internal table whenever there are two instances of recording being run on the same set of screens, fields so that the system will consider the second instance as a fresh recording without manipulating with that of the previous recording.

Vikranth

Re: REFRESH BDCDATA

Former Member — Wed, 23 Jun 2010 05:31:55 GMT

Heyy..

REFRESH BDCDATA is very simple to understand . Look , BDCDATA is a table with header line (you must be using the BDC code that system proposes in recording) , so when you refresh BDCDATA it clears all the contents from this table BDCDATA. in your case as you were not refreshing it , older values were getting into consideration and might be thatz the reason it was not working.

In so many programs not just BDC , because you miss clear or refresh of variables , work ares , temporary tables , it causes very abnormal reasonable behavior.

Hope this is helpful.

Regards,

Uma Dave

Re: REFRESH BDCDATA

Former Member — Wed, 23 Jun 2010 05:56:33 GMT

Hi Kylietisha,

A transaction can contain many screens, in ur case FK01 u r updating in 2 screens.

For eg. if u have to uplaod 10 vendor creation ie (10 records in flat file) using BDC in ur case each record will go to 2 screens then BDCDATA internal table will populate first record i.e data for two screens.

After completing 1st record(i.e for 2 screens) before going to 2nd record u have to refresh table BDCDATA the reason is if u don't REFRESH the 1st record will also be there so when transaction is called 1st record data will go.

Plz check wheter data for whole cycle of the transaction is present in BDCDATA and ur refreshing when ur going for 2nd record.

Hope this might help u............