2007 Feb 13 6:41 AM
Hi,
1. Suppose i need to upload 5000 transaction records, of which 50 might turn error, Which method should i adopt ? Why ?
2. In Call transaction method, if an error record comes in the middle of 5000 records, like 51st record is giving UPDATE error, Will it go to the next transaction OR will it stop there ?
3. In session method, it is said that: only after database update of previos transaction it goes to the next one, ie syncronous database update. Does it mean that if an error record comes in session, it will not go to the next without update..?
4. Suppose we got the result as 50 records -error. How will we upload these error records after correction ? Will we have to upload only this 50 records ?
What will happen if we RUN the upload with all 5000 records again after the 50 records are corrected in the input file ?
5. What is special about BDC, that no other upload method is having ?
2007 Feb 13 6:54 AM
Hi Huzefa
To answer some of your questions
1. It is good practise to break your transactions up into chunks of 500 using a counter this way you can better process errors, it does not put such a load on the system etc
2. It will contiunue to the next transaction and you will get the error messages in your internal message table which you should make part of call transaction statement
3. Answered in point 2.
4. You can create a BDC session with the Error records and thereafter request the user to process the BDC as display errors only and fix them online
5. The major advantage of creating a BDC session is it gives the user the ability to process the records online, display errors only or in background. The reprocessing of error transactions is the best feature as if you follow point 4. you don't need to worry about re-processing transactions that have been successful.
Hope this helps.
Ciao.
Hi,
1. Suppose i need to upload 5000 transaction records, of which 50 might turn error, Which method should i adopt ? Why ?
2. In Call transaction method, if an error record comes in the middle of 5000 records, like 51st record is giving UPDATE error, Will it go to the next transaction OR will it stop there ?
3. In session method, it is said that: only after database update of previos transaction it goes to the next one, ie syncronous database update. Does it mean that if an error record comes in session, it will not go to the next without update..?
4. Suppose we got the result as 50 records -error. How will we upload these error records after correction ? Will we have to upload only this 50 records ?
What will happen if we RUN the upload with all 5000 records again after the 50 records are corrected in the input file ?
5. What is special about BDC, that no other upload method is having ?
2007 Feb 13 6:47 AM
Hi Huzefa ,
Following are some points of diffrence between session and call transaction method based on How databse is updated and how errors are handled
1.How database is updated:-
In Batch Input session , sap databse is updated during processing of the bach input session , while in Call transaction/Dialog method , the databse is updated as per execution of the of the batch input program.
2. How errors are handled:- In session method arrors are handled automatically by the system during the processing odf the session.These erros are kept there and if u run this session again then only erros are processed.
While in Call transcation method , erros are not handled by system , they must be handled manually.If u run proagram for this case, process starts from scratch.
Refer to this Link :
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-
in-bdc.htm
Regards.
Note: Reward if useful.
2007 Feb 13 6:54 AM
Hi Huzefa
To answer some of your questions
1. It is good practise to break your transactions up into chunks of 500 using a counter this way you can better process errors, it does not put such a load on the system etc
2. It will contiunue to the next transaction and you will get the error messages in your internal message table which you should make part of call transaction statement
3. Answered in point 2.
4. You can create a BDC session with the Error records and thereafter request the user to process the BDC as display errors only and fix them online
5. The major advantage of creating a BDC session is it gives the user the ability to process the records online, display errors only or in background. The reprocessing of error transactions is the best feature as if you follow point 4. you don't need to worry about re-processing transactions that have been successful.
Hope this helps.
Ciao.
2007 Feb 13 7:34 AM
Hi Ciao,
Gr8..!!! Thanks for the tips. Would like to get a detailed info on Point No. 4. As you said: To ask the user to create a session and to run in Display Error mode.
Is it in Session method OR CTU method ? I mean processing of Error records..
Also how to run session method in Display error screens Mode ?
Also what is the real diff. in running Synch OR Asynch MODE in CALL Transaction method ? Which method is the best ?
2007 Feb 14 5:32 AM
Hi,
I have a question regarding the error transaction records. You said in response to my question, in point no. 4 as --
"4. you don't need to worry about re-processing transactions that have been successful."
What does it imply ? Is it like even if we re process the whole session with the 5000 records once again.. only those error records which are going to be corrected online mode will be uploaded..
Is it like the corrrect transactions that were loaded previously, can be run again.. Or is it that we have to seperate only error transaction records and vreate another session with that and RUN it in Display error MODE..?
Can you please clarify..
2007 Feb 14 6:51 AM
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |