‎2008 Mar 12 4:14 AM
‎2008 Mar 12 4:19 AM
hi,
The BAPI executes a COMMIT WORK command. It is required for transactions developed externally to the R/3 System that change data in the R/3 System via BAPI calls.
When you call BAPIs in your program that change data in the R/3 System, afterwards you must call this method to write the changes to the database.
Regads,
Santosh
‎2008 Mar 12 4:20 AM
Yes, after Commit work only the changes are permanent to the database.
‎2008 Mar 12 4:22 AM
Hi,
It is not necessary for a BAPI to execute 'Commit work' commands.
Please look at the below reference for more information on the same:
http://help.sap.com/saphelp_nw04/helpdata/en/a5/3ec8654ac011d1894e0000e829fbbd/frameset.htm
<REMOVED BY MODERATOR - REQUEST OR OFFER POINTS ARE FORBIDDEN>
Regards,
Esha Raj
Edited by: Alvaro Tejada Galindo on Jan 8, 2009 2:37 PM
‎2008 Mar 12 5:05 AM
Unless you do COMMIT WORK the changes wont get updated in the database.
Example: If you are creating a purchase orderusing BAPI, the PO will get created but if you come out without COMMIT you cant find the PO number.
Check for the Errors in return[] table if no errors then do a COMMIT.
You can use
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = 'X'.After BAPI...
Hope this clears.
‎2009 Jan 08 12:16 PM
Yes, after Commit work only the changes are permanent to the database.