Tom,
Then what is the value of running the consistency check in the background? It doesn't fix anything, nor does it end with a return code so the schedule process knows that there are inconsistencies that need to be fixed.
The advantage is that you don't have to wait for the system to perform the analysis; you can go directly to the results and then take whatever steps necessary.
At some convenient time after the background job has completed, execute transaction //OM17 interactively. Select "Evaluate any background job" > select the job of interest. You are presented with the results of the /SAPAPO/OM_SYNC_LC_DB run, and the option to correct the items in whatever manner suits you.
I agree with expert Ada; automatically correcting all results is a short-sighted approach. This transaction should be coupled with an intelligent analysis of root cause, and the root cause should be addressed periodically.
By the way, if you decide to run /SAPAPO/OM_SYNC_LC_DB in batch, make sure you also run /SAPAPO/OM_SYNC_LC_DB_DELETE periodically to clean out the old results logs.
Best Regards,
DB49