why bapi buffer isn't

[Former Member]

Hello experts!

in this document: http://wiki.sdn.sap.com/wiki/display/ABAP/BAPI_TRANSACTION_COMMIT+versus+COMMIT+WORK

it says " Now, as only CALL FUNCTION IN UPDATE TASK should be used, it makes obsolete this documentation and the need for storing data in memory. But buffer is still in use as I explained above."

it makes no sence because without the buffer it is not possible to use a sequence of bapis without commit because the data is not in the database and its needed to check data in the buffer ( for exemple BAPI_CHANGE changes field X to 1 and BAPI_CHANGE2 checks that field X equals 1 before update another field),, UPDATE TASK isn't relating data that hasn't been commited yet.. so why do they say BUFFER is not needed?

thanks!

[Former Member]

The article says buffer is needed.

It mentions 3 things:

1. BAPI and need to use BAPI commit or BAPI rollback.
2. Old way of doing Perform on Commit, for which global variables had to be maintained.
3. Call Function..Update Task

The last line says point 2 is obsolete, and hence global variables need not be maintained.

[Former Member]

The article says buffer is needed.

It mentions 3 things:

1. BAPI and need to use BAPI commit or BAPI rollback.
2. Old way of doing Perform on Commit, for which global variables had to be maintained.
3. Call Function..Update Task

The last line says point 2 is obsolete, and hence global variables need not be maintained.