Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


This article applies to Microsoft Dynamics NAV for all countries and all language locales.

Symptoms

Assume that you apply hotfix 2523968 in Microsoft Dynamics NAV. You post an appreciation entry for a fixed asset. In this situation, when you calculate the depreciation, the system returns incorrect amounts.
For more information about hotfix 2523968, click the following article number to view the article in the Microsoft Knowledge Base:

2523968 The calculation of the Fixed Asset Depreciation is incorrect after you process a Write-Down posting for a Fixed Asset G/L Journal in Microsoft Dynamics NAV This problem occurs in the following products:

  • Microsoft Dynamics NAV 2009 R2

  • Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)

  • Microsoft Dynamics NAV 5.0 SP1

Resolution

Hotfix information

A supported hotfix is now available from Microsoft. However, it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics NAV 2009 service pack or the next Microsoft Dynamics NAV version that contains this hotfix.

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.



Installation information

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure. However, they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

Note Before you install this hotfix, verify that all Microsoft Dynamics NAV client users are logged off the system. This includes Microsoft Dynamics NAV Application Server (NAS) services. You should be the only client user who is logged on when you implement this hotfix.

To implement this hotfix, you must have a developer license.

We recommend that the user account in the Windows Logins window or in the Database Logins window be assigned the "SUPER" role ID. If the user account cannot be assigned the "SUPER" role ID, you must verify that the user account has the following permissions:

  • The Modify permission for the object that you will be changing.

  • The Execute permission for the System Object ID 5210 object and for the System Object ID 9015 object.



Note You do not have to have rights to the data stores unless you have to perform data repair.

Code changes

Note Always test code fixes in a controlled environment before you apply the fixes to your production computers.
To resolve this problem, change the code in the Depreciation Calculation codeunit (5616). To do this, follow these steps:

  1. Change the code in the GetLastEntryDates function as follows:
    Exiting code

    IF GetPartOfCalculation(0,i - 1,DeprBookCode) THEN BEGIN
    IF FIND('-') THEN
    REPEAT
    IF "Part of Book Value" OR "Part of Depreciable Basis" THEN
    IF "FA Posting Date" > EntryDates[i] THEN

    // Delete the following line.
    EntryDates[i] := "FA Posting Date";

    UNTIL NEXT = 0;
    END;
    END;
    END;
    END;

    Replacement code

    IF GetPartOfCalculation(0,i - 1,DeprBookCode) THEN BEGIN
    IF FIND('-') THEN
    REPEAT
    IF "Part of Book Value" OR "Part of Depreciable Basis" THEN
    IF "FA Posting Date" > EntryDates[i] THEN

    // Add the following line.
    EntryDates[i] := CheckEntryDate(FALedgEntry);

    UNTIL NEXT = 0;
    END;
    END;
    END;
    END;


  2. Change the code in the in the GetFirstDeprDate function as follows:
    Existing code

    IF FIND('+') THEN
    IF ToMorrow("FA Posting Date",Year365Days) > LocalDate THEN
    LocalDate := ToMorrow("FA Posting Date",Year365Days);
    GetLastEntryDates(FANo,DeprBookCode,EntryDates);
    FOR i := 1 TO 4 DO

    // Delete the following lines.
    IF EntryDates[i] <> 0D THEN
    IF ToMorrow(EntryDates[i],Year365Days) > LocalDate THEN
    LocalDate := ToMorrow(EntryDates[i],Year365Days);
    // End of the deleted lines.

    END;
    EXIT(LocalDate);
    END;

    PROCEDURE GetMinusBookValue@17(FANo@1000 : Code[20];DeprBookCode@1001 : Code[10];StartingDate@1002 : Date;EndingDate@1003 : Date) : Decimal;

    Replacement code

    IF FIND('+') THEN
    IF ToMorrow("FA Posting Date",Year365Days) > LocalDate THEN
    LocalDate := ToMorrow("FA Posting Date",Year365Days);
    GetLastEntryDates(FANo,DeprBookCode,EntryDates);
    FOR i := 1 TO 4 DO

    // Add the following lines.
    IF EntryDates[i] > LocalDate THEN
    LocalDate := EntryDates[i];
    // End of the added lines.

    END;
    EXIT(LocalDate);
    END;

    PROCEDURE GetMinusBookValue@17(FANo@1000 : Code[20];DeprBookCode@1001 : Code[10];StartingDate@1002 : Date;EndingDate@1003 : Date) : Decimal;
  3. Change the code in the CheckEntryDate function as follows:
    Exiting code

    ThisDate := ThisDate - 1;
    ThisDate := ThisDate - 1;
    EXIT(ThisDate);
    END;

    BEGIN
    END.
    }
    }

    Replacement code

    ThisDate := ThisDate - 1;
    ThisDate := ThisDate - 1;
    EXIT(ThisDate);
    END;

    // Add the following lines.
    LOCAL PROCEDURE CheckEntryDate@1001(FALedgerEntry@1002 : Record 5601) : Date;
    BEGIN
    WITH FALedgerEntry DO BEGIN
    IF (FALedgerEntry."FA Posting Type" = FALedgerEntry."FA Posting Type"::"Write-Down") AND ("FA Posting Date" <> 0D)THEN
    IF (DATE2DMY("FA Posting Date",2) = 2) AND (DATE2DMY("FA Posting Date",2) <> DATE2DMY("FA Posting Date" + 1,2)) THEN
    EXIT("FA Posting Date" + 1);
    EXIT("FA Posting Date");
    END;
    END;

    // End of the added lines.

    BEGIN
    END.
    }
    }

Prerequisites

You must have one of the following products installed to apply this hotfix:

  • Microsoft Dynamics NAV 2009 R2

  • Microsoft Dynamics NAV 2009 SP1

  • Microsoft Dynamics NAV 5.0 SP1

Removal information

You cannot remove this hotfix.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×