The warehouse entry and the item ledger entry are inconsistent when you disassemble a kit and one of the components has more than one lot number entered in the item tracking lines

Article ID: 946219 - View products that this article applies to.
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION THAT IS CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED TO SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
This article applies to Microsoft Dynamics NAV for the North America (na) language locale.
Expand all | Collapse all

On This Page

SYMPTOMS

When you disassemble a kit and the kit line has more than one lot number entered in the item tracking lines in the North American version of Microsoft Dynamics NAV 5.0, the warehouse entry and the item ledger entry are inconsistent.

For example, consider the following scenario:
  • The component quantity per is set to 1 on the kit line.
  • There are two separated item tracking lines entered by using two separated lot number.
  • Each lot number has a quantity of 1.
In this example, if you assemble a kit, two separated item ledger entries that have positive adjustment are created for a quantity of one and each item ledger entry has its own lot number. However, if you disassemble the kit, only one warehouse entry is created for a quantity of one. Therefore, the warehouse entry and the item ledger entry are out of sync.

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 5.0 service pack or the next 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 install this hotfix, change the code in the BOM Jnl.-Post Line codeunit (32) as follows.
Existing code 1
...
        ResReg@1001 : Record 240;
        GLReg@1480000 : Record 45;
        TempHandlingSpecification@1002 : Record 336;
      BEGIN
        IF TempItemJnlLine.FIND('-') THEN
          REPEAT
...
Replacement code 1
...
        ResReg@1001 : Record 240;
        GLReg@1480000 : Record 45;
        TempHandlingSpecification@1002 : Record 336;
        OriginalQuantity@1462000 : Decimal; // Add this new line.
        OriginalQuantityBase@1462001 : Decimal; // Add this new line.
      BEGIN
        IF TempItemJnlLine.FIND('-') THEN
          REPEAT
...
Existing code 2
...
        IF TempItemJnlLine.FIND('-') THEN
          REPEAT
            TransferDimToItemJnlLine(TempItemJnlLine,TempJnlLineDim2);
            ItemJnlPostLine.RunWithCheck(TempItemJnlLine,TempJnlLineDim2);
            PostWhseJnlLine(TempItemJnlLine,TempHandlingSpecification,TempItemJnlLine.Quantity,TempItemJnlLine."Quantity (Base)"); // Delete this line.
            BOMLedgEntry."Entry No." += 1;
            BOMLedgEntry."Entry Type" := BOMLedgEntry."Entry Type"::Component;
            BOMLedgEntry."Reference Type" := BOMLedgEntry."Reference Type"::Item;
...
Replacement code 2
...
        IF TempItemJnlLine.FIND('-') THEN
          REPEAT
            TransferDimToItemJnlLine(TempItemJnlLine,TempJnlLineDim2);
            OriginalQuantity := TempItemJnlLine.Quantity; // Add this new line.
            OriginalQuantityBase := TempItemJnlLine."Quantity (Base)"; // Add this new line.
            ItemJnlPostLine.RunWithCheck(TempItemJnlLine,TempJnlLineDim2);
            PostWhseJnlLine(TempItemJnlLine,TempHandlingSpecification,OriginalQuantity,OriginalQuantityBase); // Add this new line.
            BOMLedgEntry."Entry No." += 1;
            BOMLedgEntry."Entry Type" := BOMLedgEntry."Entry Type"::Component;
            BOMLedgEntry."Reference Type" := BOMLedgEntry."Reference Type"::Item;
...

Prerequisites

You must have the North American version of Microsoft Dynamics NAV 5.0 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED IN THE DOCUMENTS AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALS”) FOR ANY PURPOSE.

THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Properties

Article ID: 946219 - Last Review: August 2, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft Dynamics NAV 5.0
Keywords: 
kbmbsinventory kbnav50presp1fix kbqfe kbmbsmigrate KB946219

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com