Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The depreciation is wrongly calculated for a fixed asset when you use the "Declining-Balance 1" depreciation method and post additional acquisitions in Microsoft Dynamics NAV


View products that this article applies to.

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION THAT IS CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED TO SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

↑ Back to the top


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

↑ Back to the top


Symptoms

Consider the following scenario. You set the depreciation method to "Declining-Balance 1" for a fixed asset in Microsoft Dynamics NAV. Then, you post additional acquisitions for the fixed asset. In this scenario, the depreciation is wrongly calculated. However, you may not notice this issue because there is no warning message. After you apply the codefix that is described in this article, you will be notified to manually check the postings and correct them if it is necessary.

↑ Back to the top


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.


↑ Back to the top



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, but 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 Navision client users are logged off the system. This includes Microsoft Navision Application Services (NAS) client users. 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 install this hotfix, change the code in the Gen. Jnl.-Post codeunit (231) as follows.

  1. Add a new global text constant:
    • Name: Text005
    • ConstValue: Using %1 for Declining Balance may result in misleading numbers for subsequent years. You should manually check the postings and correct if necessary.
  2. In the Code function, change the code as follows:
    1. Add a new local variable:
      • Name: FALedgEntry
      • DataType: Record
      • Subtype: FA Ledger Entry
    2. Change the code as follows.

      Existing code

      IF NOT CONFIRM(Text001,FALSE) THEN
      EXIT;
      TempJnlBatchName := "Journal Batch Name";
      GenJnlPostBatch.RUN(GenJnlLine);
      Replacement code

      IF NOT CONFIRM(Text001,FALSE) THEN
      EXIT;
      IF "Account Type" = "Account Type"::"Fixed Asset" THEN BEGIN
      FALedgEntry.SETRANGE("FA No.","Account No.");
      FALedgEntry.SETRANGE("FA Posting Type","FA Posting Type"::"Acquisition Cost");
      IF FALedgEntry.FINDFIRST AND "Depr. Acquisition Cost" THEN
      IF NOT CONFIRM(Text005,FALSE,FIELDCAPTION("Depr. Acquisition Cost")) THEN
      EXIT;
      END;
      TempJnlBatchName := "Journal Batch Name";
      GenJnlPostBatch.RUN(GenJnlLine);

Prerequisites

To install this codefix, you must have one of the following products installed:
  • Microsoft Dynamics NAV 5.0
  • Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1)
  • Microsoft Dynamics NAV 2009
  • Microsoft Dynamics NAV 2009 SP1

Restart information

You do not have to restart the computer after you apply this codefix.

↑ Back to the top


Status

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

↑ Back to the top


More Information

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED IN THE DOCUMENTS AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALS”) FOR ANY PURPOSE.

THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

↑ Back to the top


Keywords: kb, kbmbsfixedassets, kbnotautohotfix, kbsurveynew, kbmbspartner, kbmbsmigrate, kbqfe, kbmbscodefix, kbnoloc, kbmbsquickpub

↑ Back to the top

Article Info
Article ID : 980559
Revision : 2
Created on : 9/25/2018
Published on : 9/25/2018
Exists online : False
Views : 313