Hi experts,
Is there a way to trigger a second save transaction from within a determination? We are facing a situation where, when saving to a BOPF table, another standard table has to be maintained.
In a normal situation we can control the two updates via the BOPF commit, but because of some unfortunate circumstances, the standard table has to be updated via an RFC call. This means that the update of the standard table is already committed before the BOPF commit has succeeded, leaving room for inconsistencies between the two tables. The user should receive an error message if any of the two updates failed.
The current idea is to work with a status variable in the BOPF node:
- transaction 1 = BOPF update + commit; status = update pending; for changed made by user
- transaction 2 = standard table update + commit; status = active; via determination after load, for all records where status = update pending.
I could trigger the second save via the transaction manager instance from the FPM application controller, but the BOPF model should also work from outside the FPM application.
I'm aware that this approach is not optimal. Any other strategies to tackle this problem are welcome 
Thanks in advance!
Kind regards,
Bjorn