07-14-2007 4:25 AM
hi all,
Can anyone explain the significance of batch input and direct input method and let me know there difference with an real time scenario.
thanxs in advance
hari
07-14-2007 4:38 AM
Call Transaction:
Speed.
Synchronous process.
SYnc. and Async both update possible.
Error handling thro Message structure BDCMSGCOLL.
Single Transaction.
Batch Input Session:
Slow.
Asynchronous process.
SYnc. update possible.
Error log is created in the SM35.
Multiple Transaction possible.
Direct Input.
Without calling the screens but all the validations should be done and only for master datas upload.
Direct Input method:
1. Only for error free datas and also master data
updation.
2. It will directly updates the database table. No
screens involved.
3. Transaction BMVO or Program RBMVSHOW has been
used.
BDC(Batch Input Session):
1. Screens will be called programmatically.
2. First sessions will be created then we'll run the seesions in SM35 transaction.
3.Synchronous database update. After the processing the session only database update will occur.
Thanks
Seshu
07-14-2007 7:33 AM
Hi
BDC:
Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a
non-SAP system to SAP System.
Features :
BDC is an automatic procedure.
This method is used to transfer large amount of data that is available in electronic medium.
BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external
system).
BDC uses normal transaction codes to transfer data.
Types of BDC :
CLASSICAL BATCH INPUT (Session Method)
CALL TRANSACTION
BATCH INPUT METHOD:
This method is also called as CLASSICAL METHOD.
Features:
Asynchronous processing.
Synchronous Processing in database update.
Transfer data for more than one transaction.
Batch input processing log will be generated.
During processing, no transaction is started until the previous transaction has been written to the database.
CALL TRANSACTION METHOD :
This is another method to transfer data from the legacy system.
Features:
Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING
statement.
Updating the database can be either synchronous or asynchronous. The program specifies the update type.
Transfer data for a single transaction.
Transfers data for a sequence of dialog screens.
No batch input processing log is generated.
Differences between Call Transaction and Sessions Method:
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
6) generally used for back ground jobs.
7) at atime we can update to more than one screens.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
6) for background n fore ground jobs.
7) at atime we can update to a single screen.
Direct Input method:
Without calling the screens but all the validations should be done and only for master datas upload.
1. Only for error free datas and also master data updation.
2. It will directly updates the database table. No screens involved.
3. Transaction BMVO or Program RBMVSHOW has been used.
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&;
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
<b>Reward points for useful Answers</b>
Regards
Anji
07-14-2007 7:35 AM
07-14-2007 3:18 PM
Hi,
Check these Links out
BDC does a CALL TRANSACTION. So each and every case (document, master data,...) is committed to the database on commit. The commit occurs after completion of the transaction.
Direct input will commit the data to the database when the commit is requested explicitly.
During BDC and direct input relevant DB tables are locked, they can not be updated by other processes. After commit they are unlocked.
Thus a program using direct input must care for intermittent commits to avoid an overflow of the lock tables. For master data, a lock table overflow may occur for more than (roughly) 2000 cases.
Although direct input does not do any screen input, the same routines are passed as BDC with (simulated) screen input
some more...
Call Transaction:
Speed.
Synchronous process.
SYnc. and Async both update possible.
Error handling thro Message structure BDCMSGCOLL.
Single Transaction.
Batch Input Session:
Slow.
Asynchronous process.
SYnc. update possible.
Error log is created in the SM35.
Multiple Transaction possible.
Direct Input.
Without calling the screens but all the validations should be done and only for master datas upload.
<b>Reward points</b>
Regards