Dynamics Blogger

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. ...

  Recently I had encountered an issue while depreciating fixed assets in Dynamics GP 2010. The system hangs for a while and only option was to kill the dynamics.exe from the task manager. I found that there is an issue with assets for which depreciation is less than 0.01. What I did was to run the following statement first in SQL server to get rid of the current depreciation run after taking a backup of data. DELETE FA01500 DELETE FA41900 DELETE FA40203 DELETE FAINDEX Then, I set those penny assets depreciation method to None from straight line original life method. Now, ran the depreciation routine and it worked like a charm.

Consider this scenario. You are implementing Dynamics GP Fixed Assets in your company. None of the Fixed Assets have been imported yet. You have ensured you did all your setups just perfect. Now, It’s turn to import your assets into Asset General window using Integration Manager. It can be handled using Integration Manager eConnect destination adapter for Fixed Assets.  You have made sure you set your source files, relationships as well as mappings are all proper. Now, It’s time to run your integration so you hit your Run Integration button. For no mistake of yours, the integration fails returning this error below. Microsoft.Dynamics.GP.eConnect: Number = 6625 Stored procedure taCreateAssetID : Description = unable to obtain the next FAINDEX. What’s wrong with the integration? There is nothing wrong that you did during this  process except resorting to this workaround for getting away with this error. Go to your Fixed Assets General window. Enter one Asset...