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. The Adjust Cost Item Entry (ACIE) goes into a loop when you run the ACIE process in Microsoft Dynamics NAV 2009 SP1 or in Microsoft Dynamics NAV 2009 R2

The Adjust Cost Item Entry (ACIE) goes into a loop when you run the ACIE process in Microsoft Dynamics NAV 2009 SP1 or in Microsoft Dynamics NAV 2009 R2

View products that this article applies to.

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

↑ Back to the top

Symptoms

When you run the Adjust Cost Item Entry (ACIE) process in Microsoft Dynamics NAV 2009 SP1 or in Microsoft Dynamics NAV 2009 R2, the ACIE goes into a loop and never finishes.

↑ Back to the top

Cause

This problem occurs because of the incorrect "chain" of Valuation Date. The production order contains the same item as component but the Consumption was posted later than output. The algorithm did not check the Consumption and Output of one production order because there is no application between them (application entries are checked).

↑ 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 in the Item Jnl.-Post Line codeunit (22):
  1. Create the following local function: MaxConsumptionValuationDate@86(ProdOrderNo@1000 : Code[20]) : Date;
    Add two local variables for the local function as follows:
    • Name: ValueEntry; DataType: Record; 5802;
    • Name: ValuationDate; DataType: Date;

    Add the code as follows:
    ValueEntry.SETCURRENTKEY("Prod. Order No.");
    ValueEntry.SETRANGE("Prod. Order No.",ProdOrderNo);
    ValueEntry.SETRANGE("Item Ledger Entry Type",ValueEntry."Item Ledger Entry Type"::Consumption);
    IF ValueEntry.FIND('-') THEN
    REPEAT
    IF (ValueEntry."Valuation Date" > ValuationDate) AND
    (ValueEntry."Entry Type" <>ValueEntry."Entry Type"::Revaluation)
    THEN
    ValuationDate := ValueEntry."Valuation Date";
    UNTIL ValueEntry.NEXT = 0;
    EXIT(ValuationDate);
  2. Create the following local function: UpdateOutputEntryAndChain@87(VAR TempValueEntry@1000 : TEMPORARY Record 5802;ValuationDate@1001 : Date);
    Add two local variables for the local function as follows:
    • Name: ValueEntry; DataType: Record; 5802;
    • Name: ItemLedgerEntryNo; DataType: Integer;

    Add the code as follows:
    TempValueEntry.SETCURRENTKEY("Item Ledger Entry No.","Entry Type");
    IF TempValueEntry.FIND('-') THEN
    REPEAT
    ValueEntry.GET(TempValueEntry."Entry No.");
    IF ValueEntry."Valuation Date" <ValuationDate THEN BEGIN
    IF ItemLedgerEntryNo <>TempValueEntry."Item Ledger Entry No." THEN BEGIN
    ItemLedgerEntryNo := TempValueEntry."Item Ledger Entry No.";
    UpdateLinkedValuationDate(ValuationDate,ItemLedgerEntryNo,TRUE);
    END;


    ValueEntry."Valuation Date" := ValuationDate;
    ValueEntry.MODIFY;
    IF ValueEntry."Entry No." = DirCostValueEntry."Entry No." THEN
    DirCostValueEntry := ValueEntry;
    END;
    UNTIL TempValueEntry.NEXT = 0;
  3. Create the following local function: CorrectOutputValuationDate@85( @1000 : Record 32);
    Add two local variables for the local function as follows:
    • Name: ValueEntry; DataType: Record; 5802;
    • Name: TempValueEntry; DataType: TEMPORARY Record; 5802;
    • Name: ValuationDate; DataType: Date;

    Add the code as follows:
    IF NOT (ItemLedgerEntry."Entry Type" IN [ItemLedgerEntry."Entry Type"::Consumption,ItemLedgerEntry."Entry Type"::Output]) THEN
    EXIT;



    ValuationDate := MaxConsumptionValuationDate(ItemLedgerEntry."Prod. Order No.");



    ValueEntry.SETCURRENTKEY("Prod. Order No.");
    ValueEntry.SETRANGE("Prod. Order No.",ItemLedgerEntry."Prod. Order No.");
    ValueEntry.SETRANGE("Item Ledger Entry Type",ValueEntry."Item Ledger Entry Type"::Output);
    IF ValueEntry.FIND('-') THEN
    REPEAT
    TempValueEntry := ValueEntry;
    TempValueEntry.INSERT;
    UNTIL ValueEntry.NEXT = 0;



    UpdateOutputEntryAndChain(TempValueEntry,ValuationDate);
  4. Change the code in the RunWithCheck function as follows:
    Existing code
    ...
    ItemJnlLine2 := ItemJnlLine;
    RedoApplications;
    ...
    Replacement code
    ...
    ItemJnlLine2 := ItemJnlLine;

    // Add the following line.
    CorrectOutputValuationDate(GlobalItemLedgEntry); 
    // End of the added line.

    RedoApplications;
    ...
  5. Change the code in the PostItemk function as follows:
    Existing code
    ...
    IF "Value Entry Type" = "Value Entry Type"::"Direct Cost" THEN
    GlobalItemLedgEntry.GET("Item Shpt. Entry No.")
    ELSE
    GlobalItemLedgEntry.GET("Applies-to Entry");
    InitValueEntry(GlobalValueEntry,GlobalItemLedgEntry);
    END;
    ...
    Replacement code
    ...
    IF "Value Entry Type" = "Value Entry Type"::"Direct Cost" THEN
    GlobalItemLedgEntry.GET("Item Shpt. Entry No.")
    ELSE
    GlobalItemLedgEntry.GET("Applies-to Entry");

    // Add the following line.
    CorrectOutputValuationDate(GlobalItemLedgEntry); 
    // End of the added line.

    InitValueEntry(GlobalValueEntry,GlobalItemLedgEntry);
    END;
    ...
  6. Change the code in the UpdateValuationDate function as follows:
    Existing code
    ...
    ToValueEntry2.FIND('-');

    // Delete the following lines.
    IF FromInbound THEN 
    ToValueEntry2.MODIFYALL("Valuation Date",FromValuationDate) 
    ELSE 
    // End of the deleted lines.
    REPEAT
    ...
    Replacement code
    ...
    ToValueEntry2.FIND('-');

    // Add the following lines.
    IF FromInbound THEN BEGIN 
    IF ToValueEntry2."Valuation Date"<FromValuationDate THEN 
    ToValueEntry2.MODIFYALL("Valuation Date",FromValuationDate); 
    END ELSE 
    // End of the added lines.

    REPEAT
    ...
  7. Change the code in the CalcExpectedCost function as follows:
    Add the following parameter:
    CalcExpectedCost(VAR InvdValueEntry@1009 : Record 5802;ItemLedgEntryNo@1003 : Integer;InvoicedQty@1006 : Decimal;Quantity@1005 : Decimal;VAR ExpectedCost@1001 : Decimal;VAR ExpectedCostACY@1002 : Decimal;VAR ExpectedSalesAmt@1007 : Decimal;VAR ExpectedPurchAmt@1008 : Decimal;CalcReminder@1004 : Boolean);

    Existing code
    ...
    // Delete the following lines.
    END ELSE BEGIN
    REPEAT
    IF "Expected Cost" THEN BEGIN
    ExpectedCost := ExpectedCost + "Cost Amount (Expected)";
    ExpectedCostACY := ExpectedCostACY + "Cost Amount (Expected) (ACY)";
    IF NOT CalledFromAdjustment THEN BEGIN
    ExpectedSalesAmt := ExpectedSalesAmt + "Sales Amount (Expected)";
    ExpectedPurchAmt := ExpectedPurchAmt + "Purchase Amount (Expected)";

    END;

    END;
    UNTIL NEXT = 0;
    ExpectedCost :=
    CalcExpCostToBalance(ExpectedCost,InvoicedQty,Quantity,GLSetup."Amount Rounding Precision");
    ExpectedCostACY :=
    CalcExpCostToBalance(ExpectedCostACY,InvoicedQty,Quantity,Currency."Amount Rounding Precision");
    IF NOT CalledFromAdjustment THEN BEGIN
    ExpectedSalesAmt :=
    CalcExpCostToBalance(ExpectedSalesAmt,InvoicedQty,Quantity,GLSetup."Amount Rounding Precision");
    ExpectedPurchAmt :=
    CalcExpCostToBalance(ExpectedPurchAmt,InvoicedQty,Quantity,GLSetup."Amount Rounding Precision");
    END;
    END;
    // End of the deleted lines.
    ...
    Replacement code
    ...
    // Add the following lines.
    END ELSE
    IF InvdValueEntry.Adjustment AND
    (InvdValueEntry."Entry Type" = InvdValueEntry."Entry Type"::"Direct Cost")
    THEN BEGIN
    ExpectedCost := -InvdValueEntry."Cost Amount (Actual)";
    ExpectedCostACY := -InvdValueEntry."Cost Amount (Actual) (ACY)";
    IF NOT CalledFromAdjustment THEN BEGIN
    ExpectedSalesAmt := -InvdValueEntry."Sales Amount (Actual)";
    ExpectedPurchAmt := -InvdValueEntry."Purchase Amount (Actual)";
    END
    END ELSE BEGIN
    REPEAT
    IF "Expected Cost" THEN BEGIN
    ExpectedCost := ExpectedCost + "Cost Amount (Expected)";
    ExpectedCostACY := ExpectedCostACY + "Cost Amount (Expected) (ACY)";
    IF NOT CalledFromAdjustment THEN BEGIN
    ExpectedSalesAmt := ExpectedSalesAmt + "Sales Amount (Expected)";
    ExpectedPurchAmt := ExpectedPurchAmt + "Purchase Amount (Expected)";
    END;
    END;
    UNTIL NEXT = 0;
    ExpectedCost :=
    CalcExpCostToBalance(ExpectedCost,InvoicedQty,Quantity,GLSetup."Amount Rounding Precision");
    ExpectedCostACY :=
    CalcExpCostToBalance(ExpectedCostACY,InvoicedQty,Quantity,Currency."Amount Rounding Precision");
    IF NOT CalledFromAdjustment THEN BEGIN
    ExpectedSalesAmt :=
    CalcExpCostToBalance(ExpectedSalesAmt,InvoicedQty,Quantity,GLSetup."Amount Rounding Precision");
    ExpectedPurchAmt :=
    CalcExpCostToBalance(ExpectedPurchAmt,InvoicedQty,Quantity,GLSetup."Amount Rounding Precision");
    END;

    END;
    // End of the added lines.
    ...
  8. Change the code in the InsertValueEntry function as follows:
    Existing code
    ...
    CalcExpectedCost(

    ItemLedgEntry."Entry No.",
    InvoicedQty,
    ItemLedgEntry.Quantity,
    ValueEntry."Cost Amount (Expected)",
    ValueEntry."Cost Amount (Expected) (ACY)",
    ValueEntry."Sales Amount (Expected)",
    ValueEntry."Purchase Amount (Expected)",
    ItemLedgEntry.Quantity = ItemLedgEntry."Invoiced Quantity");


    // Delete the following lines.
    IF (InvdValueEntry."Cost Amount (Expected)" <> 0) AND (ValueEntry."Cost Amount (Expected)" <> 0) THEN
    ValueEntry."Cost Amount (Expected)" :=
    ValueEntry."Cost Amount (Expected)" - InvdValueEntry."Cost Amount (Expected)";
    IF (InvdValueEntry."Cost Amount (Expected) (ACY)" <> 0) AND (ValueEntry."Cost Amount (Expected) (ACY)" <> 0) THEN
    ValueEntry."Cost Amount (Expected) (ACY)" :=
    ValueEntry."Cost Amount (Expected) (ACY)" - InvdValueEntry."Cost Amount (Expected) (ACY)";
    // End of the deleted lines.

    END;
    ...
    Replacement code
    ...
    CalcExpectedCost(

    // Add the following line.
    ValueEntry, 
    // End of the added line.

    ItemLedgEntry."Entry No.",
    InvoicedQty,
    ItemLedgEntry.Quantity,
    ValueEntry."Cost Amount (Expected)",
    ValueEntry."Cost Amount (Expected) (ACY)",
    ValueEntry."Sales Amount (Expected)",
    ValueEntry."Purchase Amount (Expected)",
    ItemLedgEntry.Quantity = ItemLedgEntry."Invoiced Quantity");
    END;
    ...

Prerequisites

You must have one of the following products installed to apply this hotfix:
  • Microsoft Dynamics NAV 2009 SP1
  • Microsoft Dynamics NAV 2009 R2


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

References

VSTF DynamicsNAV SE: 207975

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

↑ Back to the top

Article Info
Article ID : 2533593
Revision : 2
Created on : 9/21/2018
Published on : 9/21/2018
Exists online : False
Views : 324