Doubt in LUW concept and commit work

Former Member — Fri, 08 Feb 2008 10:30:27 GMT

Hi All,

I have a main program and I want to write a separate piece of code inside that main program which is independent of commit or rollback of main program.

In my piece of code, I am using FM - BAL_DB_SAVE, and I am using Commit Work after it at the end of my part of code.

But this commit for my piece of code is also commiting the main program which I don't want.

I have tried with insert record in database table without commit in the main program. But as soon as I process the commit of the piece of code, record is inserted in the database table which is not needed.

How can I create a separate LUW for the piece of code which doesnot affect the LUW of the main program. This piece of code shouldnot commit or rollback the main program, and, this piece of code should not be commited or rollbacked for any of the commit or rollback statement in the main program.

I tried writing the piece of code in the separate report using SUBMIT <repname>, tried call transaction, tried my piece of code in a FM using as a background task, but nothing worked.

Please help, <REMOVED BY MODERATOR>

Edited by: Alvaro Tejada Galindo on Feb 8, 2008 10:09 AM

Re: Doubt in LUW concept and commit work

Former Member — Fri, 08 Feb 2008 15:17:14 GMT

Write ur FM BAl_----

commit work

and then write the other piece of code

basicaly u need 2 rte the FM get itinto 1 luw

and then process other

thnk

bhanu

topic Re: Doubt in LUW concept and commit work in Application Development and Automation Discussions

Doubt in LUW concept and commit work

Re: Doubt in LUW concept and commit work