BAPI vs Call transaction

-----Original Message-----
Subject: BAPI vs Call transaction

Hi all! 

Could you explain me why a BAPI is faster than a call transaction?. 

E.g. If i have the BAPI: create_sales_document and I could also do a call transaction to
va01. Wich one is better?. Why?. 

Thanks in advance...

-----Reply Message-----
Subject: RE: BAPI vs Call transaction

Hi, As of I know BAPI's R internally they RFC functions and they were implemented
with Objects...  ..May be because of this reason they R faqster..if it is wrong ..please
don't mind...Regards...

-----Reply Message-----
Subject: RE: BAPI vs Call transaction

A BAPI is faster because it is updating the DB "directly" through ABAP code. A BDC with call
transaction goes through the whole screen sequence like any user would do, simply put, it
is filling screens. 

Use BAPIs whenever possible.

-----Reply Message-----
Subject: RE: BAPI vs Call transaction

you use a special BAPI, cause this one uses CALL TRANSACTION to create a sales order. 
A lot of BAPIS and IDOC - input FM use DIRECT INPUT instead of CALL TA. Much faster. And
you can do a lot with them, you can't do as easy in CALL TA. 
But the best reason for BAPIs is, that they are farely safe on release change or support
package change. 

Bye

-----Reply Message-----
Subject: RE: BAPI vs Call transaction

Thanks for your answers... They have been very useful...

-----End of Message-----

Read Also
Simple Program that Create Internal Table Dynamically

ABAP Books
ABAP Certification, BAPI, Java, Web Programming, Smart Forms, Sapscripts Reference Books

More ABAP Tips

Main Index
SAP ERP Modules, Basis, ABAP and Other IMG Stuff

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG. 
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk. 
 The content on this site may not be reproduced or redistributed without the express written permission of 
www.erpgreat.com or the content authors.