COMMIT WORK AND WAIT; Flag WAIT in BAPI_TRANSACTION_COMMIT BAPI?

[former_member202077]

Hello

1) Some times we use COMMIT WORK AND WAIT and some times we pass 'X' falg for WAIT param in BAPI_TRANSACTION_COMMIT, so the standars SAP How many micro seoconds / seconds will be passes for this WAIT command?

2) Instead can i sue COMMIT WORK and checking the system DB for update in question, if its successful, EXITting the block, Can i implement this alternative in performence perspective is it useful?

Thank you

Moderator message: please do not cross-post the same question in multiple spaces.

Message was edited by: Thomas Zloch

[Former Member]

Read this wiki.It shows about commitwork versus BAPI_TRANSACTION_COMMIT

SAP Community Network Wiki - ABAP Development - BAPI_TRANSACTION_COMMIT versus COMMIT WORK

[former_member202077]

Thank you.

By chance, do you know How much time(seconds) standard SAP uses for this WAIT stetement either in COMMIT WORK AND WAIT and passing flag to WAIT in BAPI_TRANSACTION_COMIT?

[Former Member]

Use WAIT UPTO XXXX Seconds .. after bapi commit.

[kesavadas_thekkillath]

COMMIT WORK AND WAIT - The wait statement indicates synchronous( one after another ) update and not the time waited.

Better read the SAP documentation on this. Its very well explained there.