Commit work

[Former Member]

hi to all experts,

why commit work is not prefer to write withih BAPI function module.

if i write commit work in bapi.what type of problem is occure.

thanks in advance and reward also.

Regard:

Deepsama

[Former Member]

SAP has provided commit work with in it...

u no need to use commit work Statement in Report

it reduces the performance of the program.....

if it is usefull Plz reward

Regards

Anbu

[Former Member]

if i create custom bapi, in this case what heppened.

[Former Member]

it is very rare case to create a bapi...........

there u can use comit ststement if u need ......

FM : BAPI_TRANSACTION_COMMIT

u can try this also..........

if it is useful....Plz reward

Regards

Anbu

Edited by: anbu b on May 23, 2008 1:26 PM

[valter_oliveira]

Hello.

After calling a BAPI, if the return table shows no errors, you should call FM BAPI_TRANSACTION_COMMIT, with parameter WAIT = 'X' if needed.

Best regards.

Valter Oliveira.

[Former Member]

Hi,

Executes a database commit and thus closes a Logical Unit of Work ( LUW) (see also Transaction Processing). This means that

all database updates are made irrevocable and cannot be reversed with ROLLBACK WORK and

all database locks are released.

COMMIT WORK also

calls the subroutines specified by PERFORM ... ON COMMIT,

executes asynchronously any update requests (see CALL FUNCTION ... IN UPDATE TASK) specified in these subroutines or started just before,

processes the function modules specified in CALL FUNCTION ... IN BACKGROUND TASK,

closes all open database cursors (see OPEN CURSOR) and

resets the time slice counter to 0.

Never Use Commit work in a select... endselect .. program dumps..

Regards,

Raj.