topic Re: Commit Work problem in Application Development and Automation Discussions

Commit Work problem

Former Member — Wed, 11 Jul 2007 13:43:01 GMT

Hi experts,

A strange problem. I use a FM for DB updating of table EANL an EANLH, after the FM, data is updated to the table, but when the commit work is executed, the changes to table EANL is gone. Does any1 have any idea about this weird problem?

Points will be rewarded.

Thx in advance.

Vincent.

Re: Commit Work problem

RaymondGiuseppi — Wed, 11 Jul 2007 13:51:29 GMT

Sounds like the COMMIT WORK starts updates (Update V1, V2) which erase those of the module function used.

Which FM do you use?

Regards

Re: Commit Work problem

Former Member — Wed, 11 Jul 2007 14:00:23 GMT

Hi Vincent,

Use COMMIT WORK only if you're using the new updated values in the program immediately. Otherwise, the statement is not needed as the data will be automaticallly commited.

If you're using BAPI to update use FM BAPI_TRANSACTION_COMMIT to commit the work.

Reward helpful answers.

Regards,

Siddhesh Sanghvi.

Re: Commit Work problem

Former Member — Wed, 11 Jul 2007 14:05:34 GMT

ISU_DB_EANL_UPDATE

Re: Commit Work problem

RaymondGiuseppi — Wed, 11 Jul 2007 14:11:00 GMT

Be sure there is no OSS note to apply in your system for this object (look at 946002)

Regards

Re: Commit Work problem

Former Member — Wed, 11 Jul 2007 14:12:08 GMT

there is no need of using the commit statement in your program.