I have read several questions about BAPIS on this great site. There is still one thing I do not understand:
How can it be acceptable for a BAPI to commit data to the database (and therefore terminate the LUW) since at that point in time, the middleware will not have been informed of any database changes?
Is this not 'bad' from a transactional integrity point of view?
The middleware knows nothing about the SAP LUWs, nor - in my view - should it. Your client program controls the beginning and end of its session with SAP and issues Commits whenever appropriate. This is all prefectly okay.
Dig Deeper on SAP ABAP
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.