Fixed Asset Projection numbers for the current month do not match the previous month. No retirements, transfers, or additions were done for the current month. All assets are straight-line depreciation. Pre-projection numbers especially seem to be overstated or understated. Fixed Asset projections may also error or time out.

Symptoms

The Fixed Assets Projection master file may have become corrupt.

Cause

Note Before you follow the instructions in this article, make sure that you have a complete backup copy of the database that you can restore if a problem occurs.

To resolve this problem, follow these steps:

  1. Have all users exit Microsoft Dynamics GP.

  2. Open SQL Server Management Studio using the appropriate method below:

    • If you use Microsoft SQL Server 2008, start SQL Server Management Studio. To do this, click Start , point to All Programs , point to Microsoft SQL Server 2008, and then click SQL Server Management Studio.

    • If you use Microsoft SQL Server 2005, start SQL Server Management Studio. To do this, click Start , point to All Programs, point to Microsoft SQL Server 2005 , and then click SQL Server Management Studio.

    • If you use Microsoft SQL Server 2000, start SQL Query Analyzer. To do this, click Start, point to All Programs, point to Microsoft SQL Server, and then click Query Analyzer.

  3. If you know the specific asset causing the issue, run a select statement against the Asset General Information Master table (FA00100) in the Company database to find the asset index (ASSETINDEX):

    Select * from FA00100 where ASSETID = 'XX'

    (where XX = the Asset Id)

  4. Run a delete statement to remove the asset from the Projections Report Master table (FA41900) in the company database.

    To have us remove the projections for all assets from the FA41900 table for you, go to the "Fix it for me" section. To run a delete statement to remove the specific asset from the FA41900 table yourself, go to the "Let me fix it myself" section.

    Fix it for meTo automatically remove the projections for all the assets from the FA41900 table, click the Fix this problem button or link. Click Run in the File Download dialog box, and then follow the steps in the Fix it wizard.


    Note This wizard may be in English only; however, the automatic fix also works for other language versions of Windows.

    Note If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.

    Let me fix it myself

    Remove the projection for the asset from the FA41900 table using the appropriate method below.

    Method 1:

    Step 1:If you know the specific asset causing the issue, run a select statement against the Asset General Information Master table (FA00100) in the Company database to find the asset index (ASSETINDEX):

    Select * from FA00100 where ASSETID = 'XX'

    (where XX = the Asset Id)

    Step 2: Execute the following delete statement yourself in SQL Server Management Studio to remove the specific asset projection from the FA41900 table:

    Delete FA41900 where ASSETINDEX = 'XXX'

    (where XXX = the asset index number found in Step 2)

    Method 2:
    There is an Automated Solution available to clear the projections for all assets from the FA41900 table to stop projections from erring or timing out. For more information visit the Automated Solutions Page at the following link:

    https://mbs.microsoft.com/customersource/support/selfsupport/automatedsolutions

  5. Rerun the Fixed Asset projections using the appropriate method below:

    • For a single asset, click on Microsoft Dynamics GP, point to Tools, point to Routines, point to Fixed Assets and click on Depreciate One Asset. (Make sure to mark the Project Only checkbox.)

    • For all assets or an asset group, click on Microsoft Dynamics GP, point to Tools, point to Routines, point to Fixed Assets and click on Projection.

    Note In running the projection, you will want to take into consideration the Depreciated To Date of your assets. The system will only project the amounts on the periods where the assets have not been depreciated yet. For example, if the assets have been depreciated on the first 3 months and you run projections up to the 12th month, the projection amounts will only be populated from the 4th month to the 12th month. You will not see any projections for the first 3 months since they have already been depreciated.

Resolution

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×