This is a trick which we have taught users for years, to quickly resolve what batches are incomplete in the module you are trying to do a period or yearend close. This is the message I am talking about:
What Solomon is trying to tell you is that you have started a batch but it was not completely processed. Solomon wants you to know that it is best to resolve what you want to do with this batch as soon as possible. It may be that you started a batch, but got interrupted and restarted second batch; or maybe you have a suspended batch which needs to be fixed.
The problem is how to quickly find which batches are causing the problem, since there are many times multiple places you might have to look, especially with modules like AR and AP which have multiple input screens. This trick allows you to look one place and see all batches, both released, balanced for release, and suspended batches. It is a one stop to see, and if you want you can also delete the batch.
This trick should be restricted to only your power users and most trusted employees, because we are going to turn on a seldom used access right called initialization for the Journal Transaction screen, 01.010.00. You will need to navigate to the access rights screen which is either located under the administration area for Solomon 7.x or under the Utilities menu. In this screen add this feature for the initialization option :
Close out of the access rights screen.
Next we need to start the Initialization mode option. In the Solomon 6.x version, you need to click on the menu choice called Application_options:
You have started initialization mode when you have a check box displayed as shown above.
Next open up the Journal Transaction screen and note you have the ability to change the module field, which normally is set to a GJ grey value. Change this value to the module you are trying to close, say the Accounts Receivable module.
You can next click on the batch number field, and then F3 to display all batches, likely your batches causing the closing warning message.
We have found this trick very useful to quickly find incomplete or problem batches which are causing the warning when you try to close a module.
I hope you find this trick useful
Regards,
Jeff
