This article applies to Microsoft Dynamics NAV for all regions.

Symptoms

Assume that you select the Require Pick and the Bin Mandatory check boxes for a location in the Location Card dialog box in Microsoft Dynamics NAV 2009. When you ship a sales order for a kit item that has the Automatic Build Kit BOM check box selected from the location, an incorrect quantity remains in the warehouse entry. However, the item ledger entry displays a correct quantity for the sales entry. Therefore, there is an imbalance between the warehouse entry and the item ledger entry.
This problem occurs in the following products:

  • Microsoft Dynamics NAV 2009 R2

  • Microsoft Dynamics NAV 2009 Service Pack 1


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.



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. Create a new global variable in the Item Jnl.-Post Line codeunit (22), and then specify the variable as follows:

    • Name: TempWhseJnlLine

    • DataType: Record

    • Subtype: Warehouse Journal Line

    • Temporary: Yes

  2. Change the code in the PostOutput function in the Item Jnl.-Post Line codeunit (22) as follows:
    Existing code

    ...
    "Invoiced Quantity" := 0;
    END;
    PostItem;
    IF NOT Kitting THEN
    UpdateProdOrderLine(ProdOrderLine,ReTrack);

    // Delete the following lines.
    IF Location."Bin Mandatory" AND (NOT CalledFromInvtPutawayPick) THEN
    WhseJnlPostLine.RUN(WhseJnlLine);
    // End of the lines.

    END;
    END;
    END;
    ...

    Replacement code

    ...
    "Invoiced Quantity" := 0;
    END;
    PostItem;
    IF NOT Kitting THEN
    UpdateProdOrderLine(ProdOrderLine,ReTrack);

    // Add the following lines.
    IF Location."Bin Mandatory" AND (NOT CalledFromInvtPutawayPick) THEN BEGIN
    TempWhseJnlLine := WhseJnlLine;
    WhseJnlPostLine.RUN(WhseJnlLine);
    END;
    // End of the lines.

    END;
    END;
    END;
    ...
  3. Create the GetOutputWhseJnlLine procedure in the Item Jnl.-Post Line codeunit (22) as follows:

    1. Create a parameter variable, and then specify the variable as follows:

      • Name: OutputWhseJnlLine

      • DataType: Record

      • Subtype: Warehouse Journal Line

      • Temporary: Yes

    2. Add the code as follows:

      PROCEDURE GetOutputWhseJnlLine(VAR OutputWhseJnlLine);
      OutputWhseJnlLine := TempWhseJnlLine;
      OutputWhseJnlLine.INSERT;
  4. Create a new local variabl in the Code function in the BOM Jnl.-Post Line codeunit (32), and then specify the variable as follows:

    • Name: TempOutputWhseJnlLine

    • DataType: Record

    • Subtype: Warehouse Journal Line

    • Temporary: Yes

  5. Change the code in the Code function in the BOM Jnl.-Post Line codeunit (32) as follows:
    Existing code 1

    ...
    TransferDimToItemJnlLine(ItemJnlLine,TempJnlLineDim2);
    ReserveBOMJnlLine.TransferBOMJnlToItemJnlLine(BOMJnlLine,ItemJnlLine,"Quantity (Base)");
    ItemJnlPostLine.RunWithCheck(ItemJnlLine,TempJnlLineDim2);
    IF "Entry Type" = "Entry Type"::Assembly THEN BEGIN
    ProdOrderLine.DELETE;
    ProdOrderLine.Status := ProdOrderLine.Status::Finished;
    ProdOrderLine.INSERT;
    ...

    Replacement code 1

    ...
    TransferDimToItemJnlLine(ItemJnlLine,TempJnlLineDim2);
    ReserveBOMJnlLine.TransferBOMJnlToItemJnlLine(BOMJnlLine,ItemJnlLine,"Quantity (Base)");
    ItemJnlPostLine.RunWithCheck(ItemJnlLine,TempJnlLineDim2);

    // Add the following line.
    ItemJnlPostLine.GetOutputWhseJnlLine(TempOutputWhseJnlLine);

    IF "Entry Type" = "Entry Type"::Assembly THEN BEGIN
    ProdOrderLine.DELETE;
    ProdOrderLine.Status := ProdOrderLine.Status::Finished;
    ProdOrderLine.INSERT;
    ...

    Existing code 2

    ...
    OutputItemLedgEntryNo := ItemJnlLine."Item Shpt. Entry No.";
    END;
    PostWhseJnlLine(ItemJnlLine,TempHandlingSpecification,OriginalQuantity,OriginalQuantityBase);
    PostTempJnlLines;
    IF BOMReg."No." = 0 THEN BEGIN
    BOMReg.LOCKTABLE;
    IF BOMReg.FIND('+') THEN
    BOMReg."No." := BOMReg."No." + 1
    ...

    Replacement code 2

    ...
    OutputItemLedgEntryNo := ItemJnlLine."Item Shpt. Entry No.";
    END;
    PostWhseJnlLine(ItemJnlLine,TempHandlingSpecification,OriginalQuantity,OriginalQuantityBase);
    PostTempJnlLines;

    // Add the following line.
    PostSalesWhseJnlLine(TempOutputWhseJnlLine);

    IF BOMReg."No." = 0 THEN BEGIN
    BOMReg.LOCKTABLE;
    IF BOMReg.FIND('+') THEN
    BOMReg."No." := BOMReg."No." + 1
    ...
  6. Create the PostSalesWhseJnlLine function in the BOM Jnl.-Post Line codeunit (32) as follows:

    1. Create a new parameter, and then specify the parameter as follows:

      • Name: TempOutputWhseJnlLine2

      • DataType: Record

      • Subtype: Warehouse Journal Line

      • Temporary: Yes



    2. Add the code as follows:

      LOCAL PROCEDURE PostSalesWhseJnlLine(VAR TempOutputWhseJnlLine);
      BEGIN
      WITH TempOutputWhseJnlLine2 DO BEGIN
      IF FINDFIRST THEN BEGIN
      Quantity := -Quantity;
      "From Bin Code" := "To Bin Code";
      "From Zone Code" := "To Zone Code";
      "To Bin Code" := '';
      "To Zone Code" := '';
      WhseJnlPostLine.RUN(TempOutputWhseJnlLine2);
      END;
      END;
      END;


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.

Status

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

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.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×