Persistent Object Services and Commit Work

Former Member — Mon, 11 Jan 2010 22:41:12 GMT

I have two table A and B with Persistent Object Services which are wrapped around a OO transaction service.

I have a program which calls a SQL update to a table C. I do not do a commit work.

Right after the update statement to C I make a call to the transaction service.

Basically the code in the transaction service is as follows:

cl_os_system=>init_and_set_modes( i_external_commit = oscon_false

i_update_mode = oscon_dmode_direct ).

tx_manager = cl_os_system=>get_transaction_manager( ).

tx = tx_manager->create_transaction( ).

tx->start( ).

Set the data in the persistent object services for tables A and B.

tx->end( ).

Now my understanding was that only the data in A and B should get updated on the tx->end( ) call.

However the data in table C, which is not part of the object services is also getting updated at the same time. I do not want this to happen. Is there a way to prevent this update to table C?

Thanks a lot in advance.

Re: Persistent Object Services and Commit Work

mvoros — Tue, 12 Jan 2010 00:00:54 GMT

Hi,

I've never done this but have you tried to set up different modes? It looks like it's well described [here|http://help.sap.com/saphelp_nw04/helpdata/en/f5/a3682bbc6911d4b2e80050dadfb92b/frameset.htm]. Especially, the section Nesting and Concatenation looks related to your issue.

Cheers

topic Re: Persistent Object Services and Commit Work in Application Development and Automation Discussions

Persistent Object Services and Commit Work

Re: Persistent Object Services and Commit Work