Hi Tilmann,
Again thank you for your response! Using an after successful save (after commit) determination was also my first idea. But when I use the factory class to obtain the transaction manager, the framework detects my BO instance is still in state after successful save, and only the interaction state is allowed as next state:
lo_txn_mngr = /bobf/cl_tra_trans_mgr_factory=>get_transaction_manager( ).
lo_txn_mngr->save( ).
A similar check occurs in the after load case, when obtaining a new transaction manager instance. (method callstack restriction)
Would you happen to know if there is another way to access the existing transaction and service manager from within an after load determination? I tried with io_modify-->do_action( "save" ) but I suspect this is only possible for custom actions, having an action class.
At the moment I'm looking at the option to obtain the transaction manager from a new process, via a 'starting new task' function module.
Please let me know if you see other options
Thanks!
Kind regards,
Bjorn