Year-End Closing: Backup And Backup Data

“Prevention is Better than Cure”

We came to the Year-End of 2010 and we would see the Year-end closing Routine in Dynamics GP in most clients in the months to come based on their Year-end Audit schedules. Year-End Closing in Dynamics GP is all that simple it looks. It can also be a night mare if not handled properly. In general, Clients  depend on their Microsoft partners with the year-end process. This is always a safe bet relying on the subject-matter experts on clients side. However some clients do not want to go for Partners support and instead perform the Year-End process. If they have an in house GP consultant, yes, it helps. If not, Be wary of it.

MAKE SURE YOU TAKE A VALID BACKUP OF ALL COMPANIES AND DYNAMICS DATABASES BEFORE RUNNING THE YEAR-END ROUTINE. There is no exception to this task. You MUST take the backup. I have seen several clients experience problems who failed to take sufficient data backups. A classical example of what I have seen is the client thought the Year-end process went well, didn’t have any backup pre and post year-end routine. Continued posting transactions for the current year and after a month or so, realized the balances still popping up in Summary Inquiry and Detail Inquiry instead of them sitting in History Inquiry and History Detail. Cause was Year-end wasn’t complete and the balances were still in Open (GL20000) tables instead of History (GL30000) tables. This is one such example and there can be several other examples and experiences encountered by fellow consultants. Most clients would want to ring their Microsoft Partner buddies only when they experience issue and do not want to ring them before that.

My suggestion would be to have your Microsoft Dynamics GP Partner assist you in the Year-End process, be it an extra charge for you. Their expertise can always help you close the year smoothly than to run into issues later on.

Popular posts from this blog

Dynamics GP Fixed Assets GL Posting Batch Missing After Depreciation Run

Image
I got a call from a user who was seemingly worried about her monthly depreciation batch went missing from GL posting routine in the Dynamics GP Fixed Assets. I quickly took her desktop on Teamviewer Quick support and understood the problem she is facing. Let me explain the issue in detail before I tell you the solution. Dynamics GP Fixed Assets GL Posting Issue Issue The user ran the depreciation routine in Dynamics GP for November month through Dynamics GP | Financial | Routines | Depreciate All Assets. Till here, all was good. She then proceeded to FA GL posting routine. Dynamics GP | Financial | Routines | GL Posting. She could not find the batch in GL posting lookup. In other words, the monthly depreciation batch is not accessible for posting. She then ran the depreciation process again and this time when she went to GL posting window and tried processing, the system threw an error message as below There are no transactions matching these restrictions. Modify yo
Read more

How to Enable and Disable Maintenance Mode in Dynamics 365 FO

Image
Maintenance mode in Dynamics 365 for Finance and Operations is required to be switched on for system administrators to make system changes that might affect system functionality. It is available for the safe use of the application. Only those users with Maintenance mode user role and system administrators roles can sign into the application till the time the mode is turned off. When the maintenance mode is switched off, there can't be changes made in certain areas of the system. Maintenance mode is required for activities such as activating financial dimensions, creating departments/cost centres, account structure activation and other system related functions. Enable and Disable Maintenance Mode  The easy way to enable and disable maintenance mode is using SQL query the D365 FO on premises is installed. Previously, Lifecycle services (LCS) used to have such an option for configuring the maintenance mode.  Maintenance mode can be changed from enabled to disabled and v
Read more