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.

You cannot close the inventory period if you have items that are unadjusted in Microsoft Dynamics NAV 2009


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

If you have items that are unadjusted after the ending date of the inventory period in Microsoft Dynamics NAV 2009, you cannot close the inventory period. This problem occurs in the following products:
  • Microsoft Dynamics NAV 2009 R2
  • Microsoft Dynamics NAV 2009 Service Pack 1

↑ 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. 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, follow these steps:
  1. Change the code in Data Item Number 4 in the Close Inventory Period - Test report (1004) as follows:
    Existing code 1
    ...
    {
    DataItemIndent=2;
    DataItemTable=Table27;
    DataItemTableView=SORTING(No.);
    PrintOnlyIfDetail=Yes;

    // Delete the following line.
    OnAfterGetRecord=BEGIN

    IF NOT "Inventory Period".Closed THEN BEGIN
    ...
    Replacement code 1
    ...
    {
    DataItemIndent=2;
    DataItemTable=Table27;
    DataItemTableView=SORTING(No.);
    PrintOnlyIfDetail=Yes;

    // Add the following lines.
    OnAfterGetRecord=VAR
    AvgCostEntryPoint@1004 : Record 5804;
    BEGIN
    // End of the lines.

    IF NOT "Inventory Period".Closed THEN BEGIN
    ...
    Existing code 2
    ...
    IF NOT "Inventory Period".Closed THEN BEGIN

    // Delete the following line.
    IF NOT "Cost is Adjusted" THEN

    AddError(
    STRSUBSTNO(
    Text002,FIELDCAPTION("Cost is Adjusted"),TRUE,TABLECAPTION,"No."));
    END;
    END;
    ...
    Replacement code 2
    ...
    IF NOT "Inventory Period".Closed THEN BEGIN

    // Add the following lines.
    AvgCostEntryPoint.RESET;
    AvgCostEntryPoint.SETCURRENTKEY("Item No.","Cost Is Adjusted","Valuation Date");
    AvgCostEntryPoint.SETRANGE("Item No.","No.");
    AvgCostEntryPoint.SETRANGE("Cost Is Adjusted",FALSE);
    AvgCostEntryPoint.SETRANGE("Valuation Date",0D,"Inventory Period"."Ending Date");
    IF NOT AvgCostEntryPoint.ISEMPTY THEN
    // End of the lines.

    AddError(
    STRSUBSTNO(
    Text002,FIELDCAPTION("Cost is Adjusted"),TRUE,TABLECAPTION,"No."));
    END;
    END;
    ...
  2. Change the code in Properties in the Close Inventory Period codeunit (5820) as follows:
    Existing code
    ...
    EXIT;

    TESTFIELD(Closed,ReOpen);
    IF NOT ReOpen THEN BEGIN
    TESTFIELD("Ending Date");

    // Delete the following line.
    CheckCostIsAdjusted;

    CheckOpenOutboundEntryExist("Ending Date");
    END ELSE
    IF NOT HideDialog AND AccPeriodIsClosed("Ending Date") THEN
    IF NOT CONFIRM(Text008,FALSE,TABLECAPTION,"Ending Date") THEN
    EXIT;
    ...
    Replacement code
    ...
    EXIT;

    TESTFIELD(Closed,ReOpen);
    IF NOT ReOpen THEN BEGIN
    TESTFIELD("Ending Date");

    // Add the following line.
    CheckCostIsAdjusted("Ending Date");

    CheckOpenOutboundEntryExist("Ending Date");
    END ELSE
    IF NOT HideDialog AND AccPeriodIsClosed("Ending Date") THEN
    IF NOT CONFIRM(Text008,FALSE,TABLECAPTION,"Ending Date") THEN
    EXIT;
    ...
  3. Change the code in the CheckCostIsAdjusted function in the Close Inventory Period codeunit (5820) as follows:
    Existing code 1
    ...

    // Delete the following line.
    LOCAL PROCEDURE CheckCostIsAdjusted@4();

    VAR
    Item@1002 : Record 27;
    ProdOrderLine@1000 : Record 5406;
    InvtPeriod@1001 : Record 5814;
    ...
    Replacement code 1
    ...

    // Add the following line.
    LOCAL PROCEDURE CheckCostIsAdjusted@4(EndingDate@1004 : Date);

    VAR
    Item@1002 : Record 27;
    ProdOrderLine@1000 : Record 5406;
    InvtPeriod@1001 : Record 5814;
    ...
    Existing code 2
    ...
    VAR
    Item@1002 : Record 27;
    ProdOrderLine@1000 : Record 5406;
    InvtPeriod@1001 : Record 5814;
    BEGIN
    ...
    Replacement code 2
    ...
    VAR
    Item@1002 : Record 27;
    ProdOrderLine@1000 : Record 5406;
    InvtPeriod@1001 : Record 5814;

    // Add the following lines.
    AvgCostEntryPoint@1003 : Record 5804;
    ValueEntry@1010 : Record 5802;
    // End of the lines.

    BEGIN
    ...
    Existing code 3
    ...
    BEGIN

    // Delete the following lines.
    Item.SETCURRENTKEY("Cost is Adjusted");
    Item.SETRANGE("Cost is Adjusted",FALSE);
    IF NOT Item.ISEMPTY THEN
    // End of the lines.

    ERROR(Text000,InvtPeriod.TABLECAPTION,Item.TABLECAPTION);

    ProdOrderLine.SETCURRENTKEY(Status,"Cost is Adjusted");
    ...
    Replacement code 3
    ...
    BEGIN

    // Add the following lines.
    AvgCostEntryPoint.RESET;
    AvgCostEntryPoint.SETCURRENTKEY("Item No.","Cost Is Adjusted","Valuation Date");
    AvgCostEntryPoint.SETRANGE("Cost Is Adjusted",FALSE);
    AvgCostEntryPoint.SETRANGE("Valuation Date",0D,EndingDate);
    IF NOT AvgCostEntryPoint.ISEMPTY THEN
    // End of the lines.

    ERROR(Text000,InvtPeriod.TABLECAPTION,Item.TABLECAPTION);

    ProdOrderLine.SETCURRENTKEY(Status,"Cost is Adjusted");
    ...
    Existing code 4
    ...
    ERROR(Text000,InvtPeriod.TABLECAPTION,Item.TABLECAPTION);

    ProdOrderLine.SETCURRENTKEY(Status,"Cost is Adjusted");

    // Delete the following line.
    ProdOrderLine.SETRANGE(Status,ProdOrderLine.Status::Finished);

    ProdOrderLine.SETRANGE("Cost is Adjusted",FALSE);
    ...
    Replacement code 4
    ...
    ERROR(Text000,InvtPeriod.TABLECAPTION,Item.TABLECAPTION);

    ProdOrderLine.SETCURRENTKEY(Status,"Cost is Adjusted");

    // Add the following line.
    ProdOrderLine.SETRANGE(Status,ProdOrderLine.Status::Released,ProdOrderLine.Status::Finished);

    ProdOrderLine.SETRANGE("Cost is Adjusted",FALSE);
    ...
    Existing code 5
    ...
    ProdOrderLine.SETRANGE("Cost is Adjusted",FALSE);

    // Delete the following lines.
    IF NOT ProdOrderLine.ISEMPTY THEN
    ERROR(Text000,InvtPeriod.TABLECAPTION,ProdOrderLine.TABLECAPTION);
    // End of the lines.

    END;

    LOCAL PROCEDURE CheckOpenOutboundEntryExist@5(EndingDate@1001 : Date);
    VAR
    ItemLedgEntry@1000 : Record 32;
    ...
    Replacement code 5
    ...
    ProdOrderLine.SETRANGE("Cost is Adjusted",FALSE);

    // Add the following lines.
    IF ProdOrderLine.FINDSET THEN
    REPEAT
    ValueEntry.SETCURRENTKEY("Prod. Order No.");
    ValueEntry.SETRANGE("Prod. Order No.",ProdOrderLine."Prod. Order No.");
    ValueEntry.SETRANGE("Prod. Order Line No.",ProdOrderLine."Line No.");
    ValueEntry.SETRANGE("Item Ledger Entry Type",ValueEntry."Item Ledger Entry Type"::Output);
    ValueEntry.SETRANGE("Valuation Date",0D,EndingDate);
    IF NOT ValueEntry.ISEMPTY THEN
    ERROR(Text000,InvtPeriod.TABLECAPTION,ProdOrderLine.TABLECAPTION);
    UNTIL ProdOrderLine.NEXT = 0;
    // End of the lines.

    END;

    LOCAL PROCEDURE CheckOpenOutboundEntryExist@5(EndingDate@1001 : Date);
    VAR
    ItemLedgEntry@1000 : Record 32;

    ...

Prerequisites

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

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


More Information

The condition for closing inventory period is as follows now:
  • All outgoing ILEs in the period must be closed.
  • All items in the period must be adjusted.
  • All finished and released productions must be adjusted.
The validation is now based on the Avg. Cost Adjmt. Entry Point table instead of the Item table.

↑ 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, kbmbscodefix, kbqfe, kbmbspartner, kbfix, kb, kbmbsmigrate

↑ Back to the top

Article Info
Article ID : 2675771
Revision : 1
Created on : 1/7/2017
Published on : 5/22/2013
Exists online : False
Views : 149