The lot quantity in the Item Ledger Entry does not match the quantity in the Warehouse Entry after you post a Whse. Reclass. Journal for a lot specific tracked item to establish correct lot numbers in Microsoft Dynamics NAV

View products that this article applies to.

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

Symptoms

Assume that you post a Whse. Reclass. Journal for a lot specific tracked item to establish correct lot numbers in a directed pick and put-away location in Microsoft Dynamics NAV. Then, when you check the Item Ledger Entry for the item, you notice that the lot quantity in the Item Ledger Entry does not match the quantity in the Warehouse Entry.
This problem occurs in the following products:

Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
Microsoft Dynamics NAV 2009 R2
Microsoft Dynamics NAV 2009
Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1)

↑ 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, change the code in the SumUpItemTracking function in the Item Tracking Management codeunit (6500) as follows:
Existing code

...
     IF T337.FINDSET THEN REPEAT
        IF (T337."Lot No." <> '') OR (T337."Serial No." <>'') THEN BEGIN
         IF SumPerLine THEN            TempHandlingSpecification.SETRANGE("Source Ref. No.",T337."Source Ref. No."); // Sum up line per line
          IF SumPerLotSN THEN BEGIN
            TempHandlingSpecification.SETRANGE("Serial No.",T337."Serial No.");
            TempHandlingSpecification.SETRANGE("Lot No.",T337."Lot No."); 
         END; 
         IF TempHandlingSpecification.FINDFIRST THEN BEGIN
...

Replacement code

...
      IF T337.FINDSET THEN REPEAT
        IF (T337."Lot No." <>'') OR (T337."Serial No." <> '') THEN BEGIN
          IF SumPerLine THEN
            TempHandlingSpecification.SETRANGE("Source Ref. No.",T337."Source Ref. No."); // Sum up line per line 
         IF SumPerLotSN THEN BEGIN

// Add the following lines.
           IF T337."New Serial No."<>'' THEN
            TempHandlingSpecification.SETRANGE("Serial No.",T337."New Serial No." )
           ELSE
// End of the added lines.

            TempHandlingSpecification.SETRANGE("Serial No.",T337."Serial No.");

// Add the following lines.
           IF T337."New Lot No."<>'' THEN
            TempHandlingSpecification.SETRANGE("Lot No.",T337."New Lot No.")
           ELSE
// End of the added lines.

            TempHandlingSpecification.SETRANGE("Lot No.",T337."Lot No."); 
         END;
          IF TempHandlingSpecification.FINDFIRST THEN BEGIN
...

Prerequisites

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

Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
Microsoft Dynamics NAV 2009 R2
Microsoft Dynamics NAV 2009
Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1)

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: 275462

↑ 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