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. "A dimension used in Item Journal Line [line number] has caused an error" error message when you post more than one dimension line in a warehouse reclassification journal in Microsoft Dynamics NAV 2009 Service Pack 1

"A dimension used in Item Journal Line [line number] has caused an error" error message when you post more than one dimension line in a warehouse reclassification journal in Microsoft Dynamics NAV 2009 Service Pack 1

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

When you post more than one line that has the dimensions specified in a warehouse reclassification journal in Microsoft Dynamics NAV 2009 Service Pack 1 (SP1), you receive an error message that resembles the following:
A dimension used in Item Journal Line line number has caused an error. Select a Dimension Value Code for the Dimension Code AREA for Item item name.

↑ Back to the top

Cause

This problem occurs because the CreateItemJnlLine function uses the line number from one warehouse reclassification journal line, when you create the dimensions for another warehouse reclassification journal line. The line number is not updated until the end of the function. Because the dimensions refer to the old line number, the dimensions cannot be found later.

↑ 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 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 CreateItemJnlLine function in the Whse. Jnl.-Register Batch codeunit (7304) as follows:

Existing code
WhseItemTrkgLine.SETCURRENTKEY(
  "Source ID","Source Type","Source Subtype","Source Batch Name",
  "Source Prod. Order Line","Source Ref. No.","Location Code");
WhseItemTrkgLine.SETRANGE("Source Type",DATABASE::"Warehouse Journal Line");
WhseItemTrkgLine.SETRANGE("Source ID",WhseJnlLine2."Journal Batch Name");
WhseItemTrkgLine.SETRANGE("Source Batch Name",WhseJnlLine2."Journal Template Name");
WhseItemTrkgLine.SETRANGE("Source Ref. No.",WhseJnlLine2."Line No.");
WhseItemTrkgLine.SETRANGE("Location Code",WhseJnlLine2."Location Code");
IF WhseItemTrkgLine.FINDSET THEN BEGIN
  ItemJnlLine.INIT;
  ItemJnlLine.VALIDATE("Entry Type",ItemJnlLine."Entry Type"::Transfer);
  WITH WhseJnlLine2 DO BEGIN
    REPEAT
      IF ((WhseItemTrkgLine."New Serial No." <> WhseItemTrkgLine."Serial No.") OR
          (WhseItemTrkgLine."New Lot No." <> WhseItemTrkgLine."Lot No.") OR
          (WhseItemTrkgLine."New Expiration Date" <> WhseItemTrkgLine."Expiration Date")) THEN BEGIN
        CreateReservEntry.CreateReservEntryFor(
          DATABASE::"Item Journal Line",
          ItemJnlLine."Entry Type",
          '',
          '',
          0,
          "Line No.",
          WhseItemTrkgLine."Qty. per Unit of Measure",
          ABS(WhseItemTrkgLine."Qty. to Handle (Base)"),
          WhseItemTrkgLine."Serial No.",
          WhseItemTrkgLine."Lot No.");
        CreateReservEntry.SetNewSerialLotNo(WhseItemTrkgLine."New Serial No.",WhseItemTrkgLine."New Lot No.");
        CreateReservEntry.SetDates(WhseItemTrkgLine."Warranty Date",WhseItemTrkgLine."Expiration Date");
        CreateReservEntry.SetNewExpirationDate(WhseItemTrkgLine."New Expiration Date");
        CreateReservEntry.CreateEntry(
          "Item No.",
          "Variant Code",
          "Location Code",
          Description,
          0D,
          0D,
         0,
         ReservEntry."Reservation Status"::Prospect);
       QtyToHandleBase += ABS(WhseItemTrkgLine."Qty. to Handle (Base)");
      END;
    UNTIL WhseItemTrkgLine.NEXT = 0;
    IF QtyToHandleBase <> 0 THEN BEGIN
      ItemJnlLine."Document No." := "Whse. Document No.";
      ItemJnlLine.VALIDATE("Posting Date", "Registering Date");
      ItemJnlLine.VALIDATE("Item No.", "Item No.");
      ItemJnlLine.VALIDATE("Variant Code","Variant Code");
      ItemJnlLine.VALIDATE("Location Code","Location Code");
      ItemJnlLine.VALIDATE("Unit of Measure Code", "Unit of Measure Code");
      ItemJnlLine.VALIDATE("Quantity (Base)", QtyToHandleBase);
      ItemJnlLine.Description := Description;
      ItemJnlLine."Source Type" := ItemJnlLine."Source Type"::Item;
      ItemJnlLine."Source No." := "Item No.";
      ItemJnlLine."Source Code" := "Source Code";
      ItemJnlLine."Reason Code" := "Reason Code";

//Delete the following line.
      ItemJnlLine."Line No." := "Line No."; 

    END;
  END;
END;
Replacement code
WhseItemTrkgLine.SETCURRENTKEY(
  "Source ID","Source Type","Source Subtype","Source Batch Name",
  "Source Prod. Order Line","Source Ref. No.","Location Code");
WhseItemTrkgLine.SETRANGE("Source Type",DATABASE::"Warehouse Journal Line");
WhseItemTrkgLine.SETRANGE("Source ID",WhseJnlLine2."Journal Batch Name");
WhseItemTrkgLine.SETRANGE("Source Batch Name",WhseJnlLine2."Journal Template Name");
WhseItemTrkgLine.SETRANGE("Source Ref. No.",WhseJnlLine2."Line No.");
WhseItemTrkgLine.SETRANGE("Location Code",WhseJnlLine2."Location Code");
IF WhseItemTrkgLine.FINDSET THEN BEGIN
  ItemJnlLine.INIT;

//Add the following line.
  ItemJnlLine."Line No." := WhseJnlLine2."Line No.";      

  ItemJnlLine.VALIDATE("Entry Type",ItemJnlLine."Entry Type"::Transfer);
  WITH WhseJnlLine2 DO BEGIN
    REPEAT
      IF ((WhseItemTrkgLine."New Serial No." <> WhseItemTrkgLine."Serial No.") OR
          (WhseItemTrkgLine."New Lot No." <> WhseItemTrkgLine."Lot No.") OR
          (WhseItemTrkgLine."New Expiration Date" <> WhseItemTrkgLine."Expiration Date")) THEN BEGIN
        CreateReservEntry.CreateReservEntryFor(
          DATABASE::"Item Journal Line",
          ItemJnlLine."Entry Type",
          '',
          '',
          0,
          "Line No.",
          WhseItemTrkgLine."Qty. per Unit of Measure",
          ABS(WhseItemTrkgLine."Qty. to Handle (Base)"),
          WhseItemTrkgLine."Serial No.",
          WhseItemTrkgLine."Lot No.");
        CreateReservEntry.SetNewSerialLotNo(WhseItemTrkgLine."New Serial No.",WhseItemTrkgLine."New Lot No.");
        CreateReservEntry.SetDates(WhseItemTrkgLine."Warranty Date",WhseItemTrkgLine."Expiration Date");
        CreateReservEntry.SetNewExpirationDate(WhseItemTrkgLine."New Expiration Date");
        CreateReservEntry.CreateEntry(
          "Item No.",
          "Variant Code",
          "Location Code",
          Description,
          0D,
          0D,
         0,
         ReservEntry."Reservation Status"::Prospect);
       QtyToHandleBase += ABS(WhseItemTrkgLine."Qty. to Handle (Base)");
      END;
    UNTIL WhseItemTrkgLine.NEXT = 0;
    IF QtyToHandleBase <> 0 THEN BEGIN
      ItemJnlLine."Document No." := "Whse. Document No.";
      ItemJnlLine.VALIDATE("Posting Date", "Registering Date");
      ItemJnlLine.VALIDATE("Item No.", "Item No.");
      ItemJnlLine.VALIDATE("Variant Code","Variant Code");
      ItemJnlLine.VALIDATE("Location Code","Location Code");
      ItemJnlLine.VALIDATE("Unit of Measure Code", "Unit of Measure Code");
      ItemJnlLine.VALIDATE("Quantity (Base)", QtyToHandleBase);
      ItemJnlLine.Description := Description;
      ItemJnlLine."Source Type" := ItemJnlLine."Source Type"::Item;
      ItemJnlLine."Source No." := "Item No.";
      ItemJnlLine."Source Code" := "Source Code";
      ItemJnlLine."Reason Code" := "Reason Code";
    END;
  END;
END;


Prerequisites

You must have Microsoft Dynamics NAV 2009 Service Pack 1 installed to apply this hotfix.

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

↑ Back to the top

Article Info
Article ID : 976237
Revision : 2
Created on : 9/21/2018
Published on : 9/21/2018
Exists online : False
Views : 311