End Of Month processing (EOM) ran by mistake

End Of Month processing (EOM) ran by mistake.  What are the steps to correct any Transactional records affected by this situation?

Please do not enter or post any batches until you have completed this fix.

1)  Check if the Fiscal Year and Fiscal Month were updated. If they have not been updated then you stopped the process before it got too far. You may continue entering and posting transactions.
2)  If there has been a change to the Fiscal Year or Fiscal Month, do not enter or post any batches. Submit a ticket on Case Central.
3)  If used, suspend the GLI process until all the transaction data issues are sorted out.

You may need to complete the following steps:

  • Go to Activity Type Code Entry to check each Start Date and correct if needed.  Also, check the Period dates and correct those (if you are using them).
  • Find any open batches that were created since End of Month Processing ran.  Correct the Fiscal Month on Batch Summary and this will automatically carry over to the Batch Detail items.
  • If you had to fix the Start Dates in Activity Type Code Entry, then you will probably need to fix some of the Benefit Start Dates in Batch_Detail manually. Start by checking a few benefits to new donors.
Due to the nature and complexity of this issue, Support recommends that MS-Tech handle the research and updates to the records.
  EOM Ran Twice.zip

Was this article helpful?