Inconsistent data is created when you run the Application Worksheet form for an item in Microsoft Dynamics NAV

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 in Microsoft Dynamics NAV. When you run the Application Worksheet form for the item, inconsistent data is created. The inconsistent data may cause a loop when you run the Adjust Cost-Item Entries batch job. 
Fox example, if you create a fixed application between an inbound item ledger entry and an outbound item ledger entry in the Application Worksheet form, the value entries that are attached to the outbound item ledger entry state Yes incorrectly in the Valued by Average Cost field.
If you remove an fixed application in the Application Worksheet form, the value in the Cost Application field in the corresponding item application entry is still Yes incorrectly.
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)

  • Microsoft Dynamics NAV 5.0


Cause

This problem occurs because the system creates an incorrect value in the Valued by Average Cost field in the Value Entry table after you run the Apply function or the Remove Application function in the Application Worksheet form.

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 UnApply function in the Item Jnl.-Post Line codeunit (22) as follow:
    Existing code

    ...
    //Delete the following lines.
    IF Item."Costing Method" = Item."Costing Method"::Average THEN BEGIN
    IF Application.Fixed THEN BEGIN
    ValueEntry.SETCURRENTKEY("Item Ledger Entry No.");
    ValueEntry.SETRANGE("Item Ledger Entry No.",CostItemLedgEntry."Entry No.");
    ValueEntry.SETRANGE("Valued By Average Cost",FALSE);
    ValueEntry.MODIFYALL("Valued By Average Cost",TRUE);
    END;
    END;
    //End of the lines.

    Replacement code

    //Add the following lines.
    IF Item."Costing Method" = Item."Costing Method"::Average THEN
    IF Application.Fixed THEN
    UpdateValuedByAverageCost(CostItemLedgEntry."Entry No.",TRUE);
    //End of the lines.

    ...
  2. Change the code in the ReApply function in the Item Jnl.-Post Line codeunit (22) to the following:

    ...
    TotalAppliedQty := 0;
    CostApplication := FALSE;
    IF ApplyWith <> 0 THEN BEGIN
    ItemLedgEntry2.GET(ApplyWith);
    ...
    UpdateLinkedValuationDate(ValueEntry."Valuation Date",GlobalItemLedgEntry."Entry No.",GlobalItemLedgEntry.Positive);
    END;

    //Add the following lines.
    IF ItemApplnEntry.Fixed AND (ItemApplnEntry.CostReceiver <> 0) THEN
    IF Item.GET(ItemLedgEntry."Item No.") THEN
    IF Item."Costing Method" = Item."Costing Method"::Average THEN
    UpdateValuedByAverageCost(ItemApplnEntry.CostReceiver,FALSE);
    //End of the lines.

    END ELSE
    BEGIN // ApplyWith is 0
    ...
  3. Create a new UpdateValuedByAverageCost function in the Item Jnl.-Post Line codeunit (22). To create this function, follow these steps:

    1. Create the new function as follow:

      UpdateValuedByAverageCost(CostItemLedgEntryNo : Integer;ValuedByAverage : Boolean);
    2. Add a new local variable, and then specify the variable as follows:

      • Name: ValueEntry

      • DataTypeRecord

      • Subtype: Value Entry (5802)

    3. Add the code as follows:

          BEGIN
      IF CostItemLedgEntryNo = 0 THEN
      EXIT;

      ValueEntry.SETCURRENTKEY("Item Ledger Entry No.");
      ValueEntry.SETRANGE("Item Ledger Entry No.",CostItemLedgEntryNo);
      ValueEntry.SETRANGE("Valued By Average Cost",NOT ValuedByAverage);
      ValueEntry.MODIFYALL("Valued By Average Cost",ValuedByAverage);
      END;
      ...
  4. Change the code in the CreateItemJNLLinefromEntry function in the Item Jnl.-Post Line codeunit (22) as follow:
    Existing code

    ...
    //Delete the following line.
    Quantity := NewQuantity;
    ...

    Replacement code

    ...
    //Add the following line.
    Quantity := Signed(NewQuantity);

    ...

Prerequisites

You must have one of the following products installed to apply this hotfix:

  • Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)

  • Microsoft Dynamics NAV 2009

  • Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1)

  • Microsoft Dynamics NAV 5.0


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.

Нуждаете се от още помощ?

Разширете уменията си
Преглед на обучението
Получавайте първи новите функции
Присъединете се към Microsoft приобщени

Беше ли полезна тази информация?

Благодарим ви за обратната връзка!

Благодарим ви за вашата обратна връзка. Изглежда, че ще бъде полезно да ви свържем с един от нашите агенти по поддръжката на Office.

×