Question:
If a non-SAP program access multiple (more than one) BAPIs to make updates to R/3, how can one make sure that data remains consistent in R/3? What if after 3 BAPI calls the connection between calling program and R/3 breaks? How can one resolve or take care of such situations to begin with?
Answer:
The BAPI transaction model offers the user explicit transaction control. Therefore, if several BAPIs are called together, the caller can decide him/herself when to execute a COMMIT WORK (or ROLLBACK WORK).
Meaning, that BAPIs themselves cannot (generally) execute a COMMIT WORK command.
Answer:
it's true that Bapis normally don't send a Transaction Commit on their own. However there are some old BAPIs which still do it. So if you're not sure about your BAPIs, have a look to SAP Note 131838