Need a function module for commit

[Former Member]

Hi Experts,

I have a requirement of displaying a PO report in alv and when the user clicks the po it showed navigate to ME23N to display the PO.

Here the user can go in change mode to change some details in po, and when he returns back, the report should show the changes in the PO.

I am able to update the report once the user return back to the report from ME23N.

But only thing is there is a lag(5 Secs) of updating the database table when the user saves the PO.

So we need to commit once the user return to the report and then fetch the data from database.

I tried to use the " Commit work Statement" but it does't update as early.

can some one please telll me some commit Fucntion module which can update the ME23N related tables qiuckly.?

Regards,

Venkatesh.

[Former Member]

http://help.sap.com/saphelp_nw2004s/helpdata/EN/c5/e4af4a453d11d189430000e829fbbd/content.htm

Check this site which will help you

[Sm1tje]

what about COMMIT WORK AND WAIT or

BAPI_TRANSACTION_COMMIT

[Former Member]

u can use wait uptp 5 seconds to compensate tht lag

[Former Member]

Use FM : DB_COMMIT.

[ThomasZloch]

The commit is already done inside ME23N (change mode). A possibility would be to call the transaction in synchronous mode (UPDATE = 'S'), but for this you would need to also use the USING addition and some BDC-data for the initial screen.

Thomas

[Former Member]

This message was moderated.

[Former Member]

since the same answer is already given above there's no need to post again.

[JozsefSzikszai]

>

> since the same answer is already given above there's no need to post again.

Especially when that answer is wrong...

As we talk about a standard transaction here, the COMMIT is included in the standard transaction, so it does not make any sense to do it once more in an FM, or directly in the ABAP program (not mentioning that the LUW is closed already, so there is nothing to commit...)

On the other hand, the replies with WAIT UP TO ... are very strange, because now the time is 5 seconds, but next time it could be 7 seconds, who knows... this is not a stabile solution.

The only reply is worth considering is the one from Thomas!

[Former Member]

Hi Experts,

Thanks for the clarification.

But is it advisable to use commit statement in a custom program.

Regards,

Venkatesh

[Former Member]

hi..

you can use WAIT UPTO 5 SEC or bapi_transaction_commit so as to cover the lagtime.In the past have faced a similar problem and i had used wait upto 5 secs so as to compensate for the lag.

[ThomasZloch]

and what if the "lag" (i.e. update task) takes 6 seconds due to high system load?

I would always prefer a synchronous call transaction to cater for any delay in the update task.

Thomas

[Former Member]

Normally

COMMIT WORK AND WAIT.

should add the required delay.

Edited by: vivek amrute on Dec 11, 2008 1:00 PM