If a posting journal file exists, this will prevent other processes that require the journals to be purged from running. This includes Year End Processing and editing Control Account Sets. Likely the scenario is that though you chose to print/purge the adjustment audit list, something on the computer/network was holding on to it and prevented it from setting the file size to zero.

To fix this, you need to manually rename or delete the file. In the data directory, look for files that start with 'ARPOST' - for example, the adjustment posting journal is 'ARPOSTA.dat'. Make sure no-one is in the data, and rename the extension to 'old' or something other than what you are using. If there are any other 'ARPOST' files that have a size greater than zero, follow the same process.

This should allow you to edit your control account set. Also, these renamed files will be recreated the next time you post a transaction.

Maybe there is an uncleared 'posting error journal ' file as well. Look for the 'ARPSTE' files, such as ARPSTEA.dat for the adjustment posting error journal.

Open batches (yet to be posted) do not affect the ability of editing control account sets.

This problem was the result of a ARGLOB file that was damaged or out of sysc with the Adjustment Batch Status report. This may have occurred as a result of "copying" AR backup data into the folder without first deleting the AR data that was in the folder.