The unit cost of items becomes negative after you run the revaluation on items that use the Average costing method in Microsoft Dynamics NAV

Applies to: Dynamics NAV 2009 Service Pack 1Dynamics NAV 2009Microsoft Dynamics NAV 5.0 Service Pack 1

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

Symptoms


Assume that you have an item that uses the Average costing method. When you run the revaluation on the item, the unit cost of the item becomes negative unexpectedly. Additionally, you experience slow performance when you perform the Adjust Cost batch job for the item.
This problem occurs in the following products:
  • Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
  • Microsoft Dynamics NAV 2009
  • Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1) with hotfix 975251 applied
Note For more information about hotfix 975251, click the following article number to view the article in the Microsoft Knowledge Base:
975251 You experience slow performance when you perform the Adjust Cost batch job for the average cost in Microsoft Dynamics NAV 5.0

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, 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 AvgValueEntriesToAdjustExist function in the Inventory Adjustment codeunit (5895) to the following:
    ...
    IF FindNextRange THEN BEGIN
    AvgCostAdjmtEntryPoint."Valuation Date" := GetNextDate(AvgCostAdjmtEntryPoint."Valuation Date");
    AvgValueEntriesToAdjustExist(OutbndValueEntry,ExcludedValueEntry,AvgCostAdjmtEntryPoint);
    END;

    // Add the following line.
    OutbndValueEntry.SETCURRENTKEY("Item Ledger Entry No.");

    ...
  2. Change the code in the IsExcludeEntryFromAvgCostCalc function in the Inventory Adjustment codeunit (5895) to the following:
    ...
    IF NOT "Valued By Average Cost" THEN
    EXIT(FALSE);
    ItemLedgEntry.GET("Item Ledger Entry No.");
    IF ItemLedgEntry.Positive THEN
    EXIT(FALSE);

    // Delete the following line.
    EXIT(TRUE);

    // Add the following line.
    EXIT("Item Ledger Entry No." > OutbndValueEntry."Item Ledger Entry No.");
    ...

    ...
    // Delete the following lines.
    LOCAL PROCEDURE GetEntryNoToStartAt@78
    BEGIN
    StartAt := 0;
    WITH ExcludedValueEntry DO BEGIN
    RESET;
    IF FINDFIRST THEN
    REPEAT
    IF "Partial Revaluation" AND
    (OutbndValueEntry."Entry No." > "Entry No.")
    THEN
    StartAt := "Entry No.";
    UNTIL NEXT = 0;
    END;
    EXIT(StartAt + 1);
    END;
    // End of the lines.
    ...
  3. Change the code in the AdjustItemAvgCost function in the Inventory Adjustment codeunit (5895) to the following:
    ...
    WHILE NOT Restart AND AvgValueEntriesToAdjustExist(
    TempOutbndValueEntry,TempExcludedValueEntry,AvgCostAdjmtEntryPoint)
    DO BEGIN
    REPEAT

    // Delete the following lines.
    TempExcludedValueEntry.SETFILTER("Entry No.",'>=%1',
    GetEntryNoToStartAt(TempOutbndValueEntry,TempExcludedValueEntry));
    // End of the lines.

    AdjustOutbndAvgEntry(TempOutbndValueEntry,TempExcludedValueEntry);
    UpdateConsumpAvgEntry(TempOutbndValueEntry);
    UNTIL TempOutbndValueEntry.NEXT = 0;
    ...
  4. Change the code in the IsExcludeEntryFromAvgCostCalc function in the Inventory Adjustment codeunit (5895) to the following:
    ...
    BEGIN
    WITH ValueEntry DO BEGIN
    IF "Partial Revaluation" THEN

    // Delete the following line.
    EXIT(TRUE);

    // Add the following lines.
    EXIT(
    ("Entry No." > OutbndValueEntry."Entry No.") OR
    (("Entry No." < OutbndValueEntry."Entry No.") AND NOT
    IncludedInCostCalculation(ValueEntry,OutbndValueEntry."Item Ledger Entry No.")));
    // End of the lines.

    IF "Item Ledger Entry No." = OutbndValueEntry."Item Ledger Entry No." THEN
    EXIT(TRUE);
    ...

Prerequisites

You must have one of the following products installed to apply this hotfix:
  • Microsoft Dynamics NAV 2009 Service Pack 1
  • Microsoft Dynamics NAV 2009
  • Microsoft Dynamics NAV 5.0 Service Pack 1 with hotfix 975251 applied

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.