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 Calculate Inventory function suggests incorrect lines for locations that use bins in the "Phys. Inventory Journal" dialog box after you delete a location in Microsoft Dynamics NAV 2009

The Calculate Inventory function suggests incorrect lines for locations that use bins in the "Phys. Inventory Journal" dialog box after you delete a location 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

Assume that you have an item with item ledger entries available on multiple locations in Microsoft Dynamics NAV 2009. You can delete one of the locations without receiving a prompt. In this situation, when you run the Calculate Inventory function on the item in the Phys. Inventory Journal dialog box, you may receive incorrect lines suggested for the existing locations that use bins.
However, you should be unable to delete a location card that has item ledger entries created for.
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, 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 Global Variables in the Location table (Table 14) as follows:
    Existing code
    ...
    Text010@1015 : TextConst 'ENU=Checking item ledger entries for open entries...';
    Text011@1016 : TextConst 'ENU=You cannot change the %1 to %2 until the inventory stored in this bin is 0.';
    Text012@1017 : TextConst 'ENU=Before you can use Online Map, you must fill in the Online Map Setup window.\See Setting Up Online Map in Help.';
    PROCEDURE RequireShipment@5(LocationCode@1000 : Code[10]) : Boolean;
    BEGIN
    ...
    Replacement code
    ...
    Text010@1015 : TextConst 'ENU=Checking item ledger entries for open entries...';
    Text011@1016 : TextConst 'ENU=You cannot change the %1 to %2 until the inventory stored in this bin is 0.';
    Text012@1017 : TextConst 'ENU=Before you can use Online Map, you must fill in the Online Map Setup window.\See Setting Up Online Map in Help.';

    // Add the following line.
    Text013@1018 : TextConst 'ENU=You cannot delete %1 because there are one or more ledger entries on this location.';

    PROCEDURE RequireShipment@5(LocationCode@1000 : Code[10]) : Boolean;
    BEGIN
    ...
  2. Change the code in the WMSCheckWarehouse function in the Location table (table 14) as follows:
    Existing code 1
    ...
    WarehouseEntry@1002 : Record 7312;
    WarehouseEntry2@1001 : Record 7312;
    WhseJnlLine@1000 : Record 7311;
    BEGIN
    WarehouseEntry.SETCURRENTKEY("Location Code");
    WarehouseEntry.SETRANGE("Location Code",Code);
    ...
    Replacement code 1
    ...
    WarehouseEntry@1002 : Record 7312;
    WarehouseEntry2@1001 : Record 7312;
    WhseJnlLine@1000 : Record 7311;

    // Add the following lines.
    ItemLedgerEntry@1007 : Record 32;
    PositiveFilter@1008 : Boolean;
    // End of the lines.

    BEGIN
    WarehouseEntry.SETCURRENTKEY("Location Code");
    WarehouseEntry.SETRANGE("Location Code",Code);
    ...
    Existing code 2
    ...
    IF WhseJnlLine.FINDFIRST THEN
    ERROR(Text001,TABLECAPTION,Code);
    Zone.SETRANGE("Location Code",Code);
    Zone.DELETEALL;
    Bin.SETRANGE("Location Code",Code);
    ...
    Replacement code 2
    ...
    IF WhseJnlLine.FINDFIRST THEN
    ERROR(Text001,TABLECAPTION,Code);

    // Add the following lines.
    ItemLedgerEntry.SETCURRENTKEY("Item No.",Positive,"Location Code","Variant Code");
    IF ItemLedgerEntry.FINDFIRST THEN
    REPEAT
    ItemLedgerEntry.SETRANGE("Item No.",ItemLedgerEntry."Item No.");
    ItemLedgerEntry.SETRANGE("Location Code",Code);
    FOR PositiveFilter := FALSE TO TRUE DO BEGIN
    ItemLedgerEntry.SETRANGE(Positive,PositiveFilter);
    IF ItemLedgerEntry.FINDLAST THEN
    ERROR(Text013,Code);
    END;
    ItemLedgerEntry.SETRANGE(Positive);
    ItemLedgerEntry.SETRANGE("Location Code");
    ItemLedgerEntry.FINDLAST;
    ItemLedgerEntry.SETRANGE("Item No.");
    UNTIL ItemLedgerEntry.NEXT = 0;
    // End of the lines.

    Zone.SETRANGE("Location Code",Code);
    Zone.DELETEALL;
    Bin.SETRANGE("Location Code",Code);
    ...

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

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

↑ Back to the top

Article Info
Article ID : 2701896
Revision : 1
Created on : 1/7/2017
Published on : 7/13/2012
Exists online : False
Views : 238