阅读文章

BAPI vs Call transaction

[日期:2006-10-20] 来源:sap-img  作者:sapsky [字体: ]

 -----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-----



阅读:
录入:sapsky

评论 】 【 推荐 】 【 打印
上一篇:Difference and/or similarities between BAPI and IDOC's
下一篇:COMMIT WORK and BAPI_TRANSACTION_COMMIT
相关文章      
本文评论       全部评论
发表评论


点评: 字数
姓名:

  • 尊重网上道德,遵守中华人民共和国的各项有关法律法规
  • 承担一切因您的行为而直接或间接导致的民事或刑事法律责任
  • 本站管理人员有权保留或删除其管辖留言中的任意内容
  • 本站有权在网站内转载或引用您的评论
  • 参与本评论即表明您已经阅读并接受上述条款