Rollbacks
The posting of transactions may involve updating many of the database tables. To protect the database, the system records the progress of the transactions as they are posted.
If the system is unable to complete all the required postings, half completed actions are reversed (rolled back) by the system using these progress records.
A rollback occurring is not always an indication of corruption in the database.
There may be circumstances where, due to a Project or Cost Centre used on a transaction having a status of suspended, cancelled or completed, a rollback transaction will occur.
In this scenario, changing the status of the Project or Cost Centre back to Active will make it possible to complete the posting of the transaction successfully.
If a rollback has occurred and your machine is still running, a message will inform you of the rollback.
Transactions that were being processed live, but were rolled back, are put into a batch with the original User's ID.
Transactions that were being processed from a batch are returned to their original batch if a rollback occurs.
Transactions are flagged with 'R' to indicate partial rollback has occurred.
However if a rollback has occurred and your machine is no longer running (perhaps because of a crash or power failure) the message cannot be displayed. In this case, as soon as the system is running again, all Users should look at their batched transactions to see if there are any rolled back transactions.
All transactions that have been rolled back will need to be investigated to see if there is a reason why the transaction could not be posted.
If the transaction can been corrected, then it can be processed.
If the processing fails again, this may be an indication of database corruption.
If the indication is that your database has been corrupted, the only safe course is to restore the database from your last backup and re-enter all the work done since the backup was taken.