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.
This article applies to Microsoft Dynamics NAV 2009 for all countries and all language locales.
Symptoms
Consider the following scenario in Microsoft Dynamics NAV 2009:
-
A production bill of material (BOM) item that uses the FIFO costing method is set up.
-
An output is posted in two or three postings.
-
A reverse output is then posted and applied to the original output.
-
The consumption is posted.
-
The status of the released production order is changed to Finished.
-
The Adjust Cost Item process runs or the Automatic Cost Adjustment setting is set to Always to automatically adjust the cost.
In this scenario, an incorrect entry that uses the Rounding type is generated. Therefore, when the inventory is zeroed out for the item and you run the "Inventory Valuation" report, the remaining value of the item is displayed as zero.
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, change the code in the PostOutput procedure in the "Inventory Adjustment" codeunit (5895) as follows:Existing code
...
WITH OrigValueEntry DO BEGIN ItemJnlLine.INIT; ItemJnlLine."Value Entry Type" := CostElementBuf.Type; ItemJnlLine."Variance Type" := CostElementBuf."Variance Type"; ItemJnlLine."Invoiced Quantity" := OutputQtyBase; ItemJnlLine."Invoiced Qty. (Base)" := OutputQtyBase; ItemJnlLine."Qty. per Unit of Measure" := 1; ItemJnlLine."Source Type" := ItemJnlLine."Source Type"::Item; ItemJnlLine."Source No." := "Item No."; ItemJnlLine.Description := Description; // Delete the following lines. IF OutputQtyBase < 0 THEN BEGIN ItemApplnEntry.SETCURRENTKEY("Item Ledger Entry No."); ItemApplnEntry.SETRANGE("Item Ledger Entry No.","Item Ledger Entry No."); ItemApplnEntry.FINDFIRST; RndgResidualBuf.AddAdjustedCost( ItemApplnEntry."Inbound Item Entry No.",NewAdjustedCost,NewAdjustedCostACY, ItemApplnEntry."Output Completely Invd. Date" <> 0D); END; // End of the deleted lines. PostItemJnlLine(ItemJnlLine,OrigValueEntry,NewAdjustedCost,NewAdjustedCostACY); END; ...
Replacement code
...
WITH OrigValueEntry DO BEGIN ItemJnlLine.INIT; ItemJnlLine."Value Entry Type" := CostElementBuf.Type; ItemJnlLine."Variance Type" := CostElementBuf."Variance Type"; ItemJnlLine."Invoiced Quantity" := OutputQtyBase; ItemJnlLine."Invoiced Qty. (Base)" := OutputQtyBase; ItemJnlLine."Qty. per Unit of Measure" := 1; ItemJnlLine."Source Type" := ItemJnlLine."Source Type"::Item; ItemJnlLine."Source No." := "Item No."; ItemJnlLine.Description := Description; PostItemJnlLine(ItemJnlLine,OrigValueEntry,NewAdjustedCost,NewAdjustedCostACY); END; ...
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
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.
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.