I would like to be able to issue a manual commit

BobK

I would like to be able to issue a manual commit, or maybe some one could suggest a work around.

Here is the problem.
I have several scheduled processes that update BOs. On rare occasions, one of these processes encounters some invalid data which causes an internal error, the process stops and all changes made up to that point are rolled back. The next time the process runs, it tries to process the same BO, hits the error, stops, rolls back and no valid BOs are being processed until I notice the problem.

My BO has a status field and the process updates only BOs with a status of 'Ready'. The first thing the process does is set the status to 'InProcess', but this change is part of the transaction and gets rolled back when the error is hit. If I could commit that change right after making it, that BO would stay in 'InProcess' when the roll back is executed and the next time the process runs, it would not try to update that BO but would continue with the valid BOs.

Any and all suggestions welcome

tford

I wonder if IN BATCHES OF 1 would help commit the changes before the error occurs.

BobK

Thanks Tom, but I am already doing IN BATCHES OF 1 and the error is occurring before the commit.

aware_support

You need to use failure rules for this. I believe almost exactly the same scenario is described in the User Guide when it talks about failure rules

BobK

It is my understanding the failure rules only execute when a REPORT ERROR is executed.

From the Users Guide (italics mine)

The recommended solution to the above problem is to define process failure rules.
These rules may be attached to a process and they will be executed whenever the
process fails as a result of the execution of the REPORT ERROR action anywhere during
the course of the process.

I am not talking about a situation where a REPORT ERROR is executed but when a system error occurs such as, for example, a divide by 0 (which I would never do :lol: )

When ever something like this happens, I create code to check for these situations and code around it, but I keep getting surprised (usually in the middle of the night) with new ways for the system to fail. I would just like a way to keep the system running until I come in in the morning and fix the problem.