Microsoft KB Archive Search

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.

  1. Home
  2. Dimensions are not pulled correctly when calculating depreciation in Microsoft Dynamics NAV 2009

Dimensions are not pulled correctly when calculating depreciation in Microsoft Dynamics NAV 2009

View products that this article applies to.

When calculating depreciation in the fixed asset module in Microsoft Dynamics NAV 2009, dimensions are not pulled correctly. Follow the steps in the code changes section to solve this issue. This problem occurs in the following products:
  • Microsoft Dynamics NAV 2009 R2
  • Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)

↑ 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. 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 InsertJnlLineDim function in the FA Insert G/L Account Codeunit (5601) as follows:

Existing code 1

...
FADimMgt@1003 : Codeunit 5674;
    BEGIN
      JnlLineDimTmp2.DELETEALL;
      IF FAGLPostBuf."FA Posting Group" <> '' THEN BEGIN
        FAAllocDim.SETRANGE(Code,FAGLPostBuf."FA Posting Group");
        FAAllocDim.SETRANGE("Allocation Type",FAGLPostBuf."FA Allocation Type");
...

Replacement code 1

...
FADimMgt@1003 : Codeunit 5674;
    BEGIN
      JnlLineDimTmp2.DELETEALL;

// Add the following lines.
     IF JnlLineDimTmp.FINDSET THEN
       REPEAT
         JnlLineDimTmp2.INIT;
         JnlLineDimTmp2."Dimension Code" := JnlLineDimTmp."Dimension Code";
         JnlLineDimTmp2."Dimension Value Code" := JnlLineDimTmp."Dimension Value Code";
         JnlLineDimTmp2.INSERT;
       UNTIL JnlLineDimTmp.NEXT = 0;
// End of the added lines.

      IF FAGLPostBuf."FA Posting Group" <> '' THEN BEGIN
        FAAllocDim.SETRANGE(Code,FAGLPostBuf."FA Posting Group");
        FAAllocDim.SETRANGE("Allocation Type",FAGLPostBuf."FA Allocation Type");
...

Existing code 2

...
FAAllocDim.SETRANGE("Line No.",FAGLPostBuf."FA Allocation Line No.");
        IF FAAllocDim.FIND('-') THEN
          REPEAT

// Delete the following lines.
           JnlLineDimTmp2."Dimension Code" := FAAllocDim."Dimension Code";
           JnlLineDimTmp2."Dimension Value Code" := FAAllocDim."Dimension Value Code";
           JnlLineDimTmp2.INSERT;
// End of the deleted lines.

          UNTIL FAAllocDim.NEXT = 0;
      END;
...

Replacement code 2

...
FAAllocDim.SETRANGE("Line No.",FAGLPostBuf."FA Allocation Line No.");
        IF FAAllocDim.FIND('-') THEN
          REPEAT

// Add the following lines.
           JnlLineDimTmp2.SETRANGE("Dimension Code",FAAllocDim."Dimension Code");
           IF JnlLineDimTmp2.FINDFIRST THEN BEGIN
             JnlLineDimTmp2."Dimension Value Code" := FAAllocDim."Dimension Value Code";
             JnlLineDimTmp2.MODIFY;
           END ELSE BEGIN
             JnlLineDimTmp2.INIT;
             JnlLineDimTmp2."Dimension Code" := FAAllocDim."Dimension Code";
            JnlLineDimTmp2."Dimension Value Code" := FAAllocDim."Dimension Value Code";
             JnlLineDimTmp2.INSERT;
           END;
           JnlLineDimTmp2.SETRANGE("Dimension Code");
// End of the added lines.

          UNTIL FAAllocDim.NEXT = 0;
      END;
...

Existing code 3

...
UNTIL FAAllocDim.NEXT = 0;
      END;

// Delete the following lines.
     IF JnlLineDimTmp.FINDSET THEN
       REPEAT
         JnlLineDimTmp2.SETRANGE("Dimension Code",JnlLineDimTmp."Dimension Code");
         IF JnlLineDimTmp2.FINDFIRST THEN BEGIN
           JnlLineDimTmp2."Dimension Value Code" := JnlLineDimTmp."Dimension Value Code";
           JnlLineDimTmp2.MODIFY;
         END ELSE BEGIN
           JnlLineDimTmp2.INIT;
           JnlLineDimTmp2."Dimension Code" := JnlLineDimTmp."Dimension Code";
           JnlLineDimTmp2."Dimension Value Code" := JnlLineDimTmp."Dimension Value Code";
           JnlLineDimTmp2.INSERT;
         END;
         JnlLineDimTmp2.SETRANGE("Dimension Code");
       UNTIL JnlLineDimTmp.NEXT = 0;
// End of the deleted lines.

      FADimMgt.InsertJnlLineDim(
        DATABASE::"Gen. Journal Line",
        GenJnlLine."Journal Template Name",
...

Replacement code 3

...
UNTIL FAAllocDim.NEXT = 0;
      END;

      FADimMgt.InsertJnlLineDim(
        DATABASE::"Gen. Journal Line",
        GenJnlLine."Journal Template Name",
...

Prerequisites

You must have one of the following products installed to apply this hotfix:
  • Microsoft Dynamics NAV 2009 R2
  • Microsoft Dynamics NAV 2009 SP1

Removal information

You cannot remove this hotfix.

↑ 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

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 Usefor other considerations.

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2976078
Revision : 1
Created on : 1/7/2017
Published on : 6/25/2014
Exists online : False
Views : 280