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. Microsoft Dynamics NAV 2009 always uses the default dimension of an item when you run the Calculate Inventory Value function on a revaluation journal by using the Calculate Per Item Ledger Entry option

Microsoft Dynamics NAV 2009 always uses the default dimension of an item when you run the Calculate Inventory Value function on a revaluation journal by using the Calculate Per Item Ledger Entry option

View products that this article applies to.

Rapidly Published 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 2009 for all countries and all language locales.

↑ Back to the top

Symptoms

Consider the following scenario in Microsoft Dynamics NAV 2009. You run the Calculate Inventory Value function on a revaluation journal. When you do this, you click
Item Ledger Entry in the Calculate Per area in the Calculate Inventory Value dialog box. In this scenario, the Microsoft Dynamics NAV 2009 always uses the default dimension of an item. Therefore, if the item has no dimension specified and you post a purchase order that contains dimensions, the item ledger entry (ILE) dimension is ignored when you run the Calculate Inventory Value report. If the item has any dimension specified and the ILE has no dimension specified, Microsoft Dynamics NAV sets the dimension of the item for all lines.

↑ 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 resolve this problem, follow these steps:
  1. Change the code in the OnAfterGetRecord trigger in the Calculate Inventory Value report (5899) as follows:
    Existing code
    ...
    CalculatePer::Item:

    // Delete the following line.
    BEGIN 

    InsertValJnlBuffer(
    ItemLedgEntry."Item No.",ItemLedgEntry."Variant Code",
    ItemLedgEntry."Location Code",RemQty,
    CalculateRemInvValue(ItemLedgEntry."Entry No.",ItemLedgEntry.Quantity,RemQty,
    IncludeExpectedCost AND NOT ItemLedgEntry."Completely Invoiced"));

    // Delete the following line.
    END;

    END;
    ...
    Replacement code
    ...
    CalculatePer::Item:
    InsertValJnlBuffer(
    ItemLedgEntry."Item No.",ItemLedgEntry."Variant Code",
    ItemLedgEntry."Location Code",RemQty,
    CalculateRemInvValue(ItemLedgEntry."Entry No.",ItemLedgEntry.Quantity,RemQty,
    IncludeExpectedCost AND NOT ItemLedgEntry."Completely Invoiced"));
    END;
    ...
  2. Change the code in the InsertItemJnlLine function in the Calculate Inventory Value report (5899) as follows:
    Existing code
    ...
    // Delete the following line.
    IF CalculatePer = CalculatePer::"Item Ledger Entry" THEN 

    "Applies-to Entry" := ApplyToEntry2;
    VALIDATE(Quantity,Quantity2);
    ...
    Replacement code
    ...
    // Add the following line.
    IF CalculatePer = CalculatePer::"Item Ledger Entry" THEN BEGIN 

    "Applies-to Entry" := ApplyToEntry2;

    // Add the following lines.
    CreateDimFromILE;
    END;
    // End of the added lines.

    VALIDATE(Quantity,Quantity2);
    ...
  3. Create the CreateDimFromILE function in the Calculate Inventory Value report (5899). To do this, follow these steps:
    1. Set the Local property of the function to Yes.
    2. Add a local variable, and then specify the variable as follows:
      • Name:
        JnlLineDim
      • DataType:
        Record
      • Subtype: Journal Line Dimension
    3. Add a local variable, and then specify the variable as follows:
      • Name:
        LedgEntryDim
      • DataType:
        Record
      • Subtype: Ledger Entry Dimension
    4. Add a local variable, and then specify the variable as follows:
      • Name:DimMgt
      • DataType: Codeunit
      • Subtype:DimensionManagement
    5. Add the following code to the CreateDimFromILE function: 

      JnlLineDim.SETRANGE("Table ID",DATABASE::"Item Journal Line");
      JnlLineDim.SETRANGE("Journal Template Name",ItemJnlLine."Journal Template Name");
      JnlLineDim.SETRANGE("Journal Batch Name",ItemJnlLine."Journal Batch Name");
      JnlLineDim.SETRANGE("Journal Line No.",ItemJnlLine."Line No.");
      JnlLineDim.DELETEALL;
      LedgEntryDim.SETRANGE("Table ID",DATABASE::"Item Ledger Entry");
      LedgEntryDim.SETRANGE("Entry No.",ItemLedgEntry."Entry No.");
      DimMgt.MoveLedgEntryDimToJnlLineDim(LedgEntryDim,JnlLineDim,DATABASE::"Item Journal Line",
      ItemJnlLine."Journal Template Name",ItemJnlLine."Journal Batch Name",ItemJnlLine."Line No.",0);
      JnlLineDim.SETCURRENTKEY("Dimension Code","Dimension Value Code");
      JnlLineDim.SETRANGE("Dimension Code",GLSetup."Global Dimension 1 Code");
      IF JnlLineDim.FINDFIRST THEN
        ItemJnlLine."Shortcut Dimension 1 Code" := JnlLineDim."Dimension Value Code"
      ELSE
        ItemJnlLine."Shortcut Dimension 1 Code" := '';
      JnlLineDim.SETRANGE("Dimension Code",GLSetup."Global Dimension 2 Code");
      IF JnlLineDim.FINDFIRST THEN
        ItemJnlLine."Shortcut Dimension 2 Code" := JnlLineDim."Dimension Value Code"
      ELSE
        ItemJnlLine."Shortcut Dimension 2 Code" := '';

Prerequisites

You must have Microsoft Dynamics NAV 2009 Service Pack 1 or Microsoft Dynamics NAV 2009 installed to apply this hotfix.

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

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: kbmbsquickpub, kbnoloc, kbmbscodefix, kbqfe, kbnotautohotfix, kbmbspartner, kbsurveynew, kbmbsinventory, kb, kbmbsmigrate

↑ Back to the top

Article Info
Article ID : 979020
Revision : 2
Created on : 9/19/2018
Published on : 9/19/2018
Exists online : False
Views : 271