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. Item charge cost and final invoiced component cost do not roll up into the COGS of an assembly BOM item when the item is sold in Microsoft Dynamics NAV 2013

Item charge cost and final invoiced component cost do not roll up into the COGS of an assembly BOM item when the item is sold in Microsoft Dynamics NAV 2013

View products that this article applies to.

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

↑ Back to the top

Symptoms

Assume that you create an assembly bill of material (BOM) item in Microsoft Dynamics NAV 2013. If an item charge cost is assigned to components of the assembled item later, the charge cost is part of the assembled output. However, when the item is sold by using Assembly to Order, the item charge cost does not roll up into the Cost of Goods Sold (COGS) of the assembly BOM item.

↑ 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 2013 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 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 Date Filter - OnAfterValidate trigger in the _Item Statistics form (9222). To do this, follow these steps:
  1. Change the code in the InsertValueEntry function in the Item Jnl.-Post Line codeunit (22) as follows:
    Existing code
    ...
             IF ValueEntry.Inventoriable THEN
               PostInventoryToGL(ValueEntry);
     
             ValueEntry.INSERT;

    // Delete the following line. 
             ItemApplnEntry.SetOutboundsNotUpdated(ItemLedgEntry,ValueEntry.Adjustment);
    ...
    Replacement code
    ...
             IF ValueEntry.Inventoriable THEN
               PostInventoryToGL(ValueEntry);
     
             ValueEntry.INSERT;
     
    // Add the following line.
             ItemApplnEntry.SetOutboundsNotUpdated(ItemLedgEntry);
    ...
  2. Change the code in the InsertCorrValueEntry function in the Item Jnl.-Post Line codeunit (22) as follows:
    Existing code
    ...
           IF NewValueEntry.Inventoriable THEN
             PostInventoryToGL(NewValueEntry);
     
           NewValueEntry.INSERT;

    // Delete the following line. 
           ItemApplnEntry.SetOutboundsNotUpdated(ItemLedgEntry,NewValueEntry.Adjustment);
    ...
    Replacement code
    ...
           IF NewValueEntry.Inventoriable THEN
             PostInventoryToGL(NewValueEntry);
     
           NewValueEntry.INSERT;
     
    // Add the following line.
           ItemApplnEntry.SetOutboundsNotUpdated(ItemLedgEntry);
    ...
  3. Change the code in the UpdateAdjmtBuf function in the Inventory Adjustment codeunit (5895) as follows:
    Existing code
    ...
    TempInvtAdjmtBuf.AddBalanceExpectedCostBuf(OrigValueEntry,NewAdjustedCost,NewAdjustedCostACY);
           END;
     
           IF OrigValueEntry."Item Ledger Entry Quantity" >= 0 THEN BEGIN
             ItemLedgEntry.GET(OrigValueEntry."Item Ledger Entry No.");

    // Delete the following line.
           ItemApplnEntry.SetOutboundsNotUpdated(ItemLedgEntry,OrigValueEntry.Adjustment);
    ...
    Replacement code
    ...
    TempInvtAdjmtBuf.AddBalanceExpectedCostBuf(OrigValueEntry,NewAdjustedCost,NewAdjustedCostACY);
           END;
     
           IF OrigValueEntry."Item Ledger Entry Quantity" >= 0 THEN BEGIN
             ItemLedgEntry.GET(OrigValueEntry."Item Ledger Entry No.");

    // Add the following line.
           ItemApplnEntry.SetOutboundsNotUpdated(ItemLedgEntry);
    ...
  4. Change the code in the SetOutboundsNotUpdated function in the Item Application Entry table (339) as follows:
    Existing code
    ...
    // Delete the following line.
        PROCEDURE SetOutboundsNotUpdated@110(ItemLedgEntry@1000 : Record 32;AdjustmentValueEntry@1002 : Boolean);

         ...
         VAR
           ItemApplnEntry@1001 : Record 339;
         BEGIN

    // Delete the following line.
          IF (ItemLedgEntry.Quantity < 0) OR AdjustmentValueEntry THEN
    ...
    Replacement code
    ...
    // Add the following line.
        PROCEDURE SetOutboundsNotUpdated@110(ItemLedgEntry@1000 : Record 32);

         ...
         VAR
           ItemApplnEntry@1001 : Record 339;
         BEGIN

    // Add the following line.
          IF ItemLedgEntry.Quantity < 0 THEN
    ...

Prerequisites

You must have Microsoft Dynamics NAV 2013 installed to apply this hotfix.

Removal information

You cannot remove this hotfix.

↑ Back to the top

More Information

To fix the data that is already posted, you must run additional steps. These steps are taken for FIFO costing.  These steps must be done in Object Designer in the Development Database:
  1. In table 32, on the Assembly Output that the sale is applied to, set the Applied Entry to Adjust value to Yes.
  2. In table 339, filter on the Outbound Item Entry No. field to the Item Ledger Entry number of the sale, and then set the Outbound Entry is Updated value to No.
  3. In table 5804, find the record for the item number, together with the valuation date, and the location/variant if applicable, and then set the Cost is Adjusted value to No.
  4. Run Adjust Cost.

↑ 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 Use for other considerations.

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2800697
Revision : 1
Created on : 1/7/2017
Published on : 10/17/2014
Exists online : False
Views : 256