topic Re: Commit Work for just one function module in Application Development and Automation Discussions

Commit Work for just one function module

Former Member — Thu, 13 Mar 2014 19:53:48 GMT

Hi experts,

i have one question;

I need one solutions for commit work but just one function module. If i set commit work in function module then everything is taking the commit. But i dont like this. I need just for FM. This is impossible ?

Thak you, regards.

Re: Commit Work for just one function module

ThomasZloch — Thu, 13 Mar 2014 19:58:11 GMT

Commit work writes all changes within a LUW (logical unit of work) to the database. By singling out just the changes that one FM did, you are violating the fundamental principle behind it. What should happen to the other changes, should they be rolled back? Why are they done in the first place?

Please explain more about the context, maybe there is another way to do what's required.

Thomas

Re: Commit Work for just one function module

Former Member — Thu, 13 Mar 2014 20:49:55 GMT

Hi Thomas,

first thank you for answer. I have one enhancement. İt is for invoice grouping and i need before inv. grouping delete one document. If dont set commit then make to group all inv. ( so together should be deleted inv ).

Re: Commit Work for just one function module

Private_Member_7726 — Thu, 13 Mar 2014 22:58:35 GMT

Hi,

The only way I know involves creating a nested LUW - opening a new internal session by calling ABAP program using SUBMIT ... AND RETURN or a CALL transaction code.

Meaning, you'd have to code your logic in a report program/transaction, use the function module to merely call that report/transaction and, if necessary, use EXPORT/IMPORT or SHARED MEMORY to exchange data between the sessions. It's quite "ugly" solution IMO, and it involves session handling overhead, which can make it unsuitable for time-critical mass processing.

Cheers,

Janis