Q

BAPIs committing data to database

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?

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.


This was first published in October 2001

Dig deeper on SAP ABAP

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchManufacturingERP

SearchOracle

SearchDataManagement

SearchAWS

SearchBusinessAnalytics

SearchCRM

SearchContentManagement

SearchFinancialApplications

Close