‎2007 May 14 7:58 AM
hi,
for less volume of data we use call transaction and where as for large volume of data we use session method.but in one interview i faced one q like how u will decide whether it is small volume of data r large data like that.........can any one ans plz.......
‎2007 May 14 8:31 AM
Hi Srinu,
Depending on the flat file structure and the transaction which u r processing you can decide which method to go for. Actually it is decided by the Team lead or more high level members of the project itself.
Just you need to develop the program...
Regards
‎2007 May 14 9:27 AM
hi
good
the fact is it all depends on your requirement and the decision taken by your client as well as the functional consultant,you r not the decesion maker bcz you dont know what is the amout of data you r going to get to upload,after they people taken the decision you only work accordingly.
thanks
mrutyun^
‎2007 May 14 10:21 AM
Yes you are not the person(as a developer) who will decide the size/volume of the data. It will be done by Functional experts / SMEs.
If required you can give an option on the selection screen that will allow user to execute the program, and choose from batch session or call transaction.
Vishal
‎2007 May 14 11:15 AM
hi srinu,
As like naga said,its a work from a team lead or a project manager.u have to work according to their concern.he will decide by seeing the structure and flat file sizes.
thanks and regards
vijay
‎2007 May 15 3:06 AM
Actually the conversion is to transfer data from a non-SAP system(legacy system) to SAP system.There r two types of BDC
1.Call Transaction
2.Session
In call transaction the session is automatically released whereas in session we need to externally release the session .
Call Transaction is for small amount of data and Session is for huge data.
The volume of data depends on the data that u need to transfer.
‎2007 May 15 4:05 AM
hi.it depends on the data that will be there in the flat file(notepad,excel).and based on that you can decide whether to use call transaction or session.