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.

"Item No. [Item_No.] does not exist" error message when you try to reverse register in the Vendor Ledger Entries form in the Russian version of Microsoft Dynamics NAV 2009 R2 with Feature Pack 1


View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the Russian (ru) language locale.

↑ Back to the top


Symptoms

In the Russian version of Microsoft Dynamics NAV 2009 R2 with Feature Pack 1, if the VAT Entry table (254) has the VAT allocation changes operations, when you try to reverse register in the Vendor Ledger Entries form, you receive the following error message:
Item No.Item_No. does not exist.

↑ 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:
Note To create the field (12490), use the following .fob file.
File nameFile versionFile sizeDateTimePlatform
Vstf260227.fobNot applicable169,34003-Jun-201110:08Not applicable
The following file is available for download from the Microsoft Dynamics File Exchange Server:

Release Date: April 2, 2014

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
  1. Change the code in the Reversal Entry table (179) as follows:
    1. Add the following field: { 12490; ;VAT Allocation ;Boolean }
    2. Change the code in the InsertReversalEntry function as follows:
      Existing code
      ...
      ReversalEntry."Bal. Account Type" := GLEntry."Bal. Account Type";

      ReversalEntry."Bal. Account No." := GLEntry."Bal. Account No.";

      ReversalEntry."Line No." := NextLineNo;

      NextLineNo := NextLineNo + 1;

      ReversalEntry.INSERT;



      IF GLEntry.Amount > 0 THEN BEGIN

      GLItemLedgRelation.RESET;

      GLItemLedgRelation.SETRANGE("G/L Entry No.",GLEntry."Entry No.");
      ...
      Replacement code
      ...
      ReversalEntry."Bal. Account Type" := GLEntry."Bal. Account Type";

      ReversalEntry."Bal. Account No." := GLEntry."Bal. Account No.";

      ReversalEntry."Line No." := NextLineNo;

      // Add the following line.
      ReversalEntry."VAT Allocation" := VATAllocOnCost;
      // End of the added line.

      NextLineNo := NextLineNo + 1;

      ReversalEntry.INSERT;



      IF GLEntry.Amount >0 THEN BEGIN

      GLItemLedgRelation.RESET;

      GLItemLedgRelation.SETRANGE("G/L Entry No.",GLEntry."Entry No.");
      ...
    3. Change the code in the CheckEntries function as follows:
      Existing code 1
      ...
      PROCEDURE CheckEntries@14();
      ...
      Replacement code 1
      ...
      PROCEDURE CheckEntries@14(IsVATAllocOnCost@1000000000 : Boolean);
      ...
      Existing code 2
      ...
      MaxPostingDate := 0D;

      IF NOT GLEntry.FIND('-') THEN

      ERROR(Text009,GLEntry.TABLECAPTION,GLAcc.TABLECAPTION);

      // Delete the following line.
      VATAllocOnCost := VATAllocationExist(VATEntry);
      // End of the deleted line.

      IF GLEntry.FIND('-') THEN BEGIN

      // Delete the following line.
      IF (GLEntry."Journal Batch Name" = '') AND NOT VATAllocOnCost THEN
      // End of the deleted line.

      TestFieldError;

      REPEAT

      CheckGLAcc(GLEntry,BalanceCheckAmount,BalanceCheckAddCurrAmount);

      UNTIL GLEntry.NEXT = 0;

      END;
      ...
      Replacement code 2
      ...
      MaxPostingDate := 0D;

      IF NOT GLEntry.FIND('-') THEN

      ERROR(Text009,GLEntry.TABLECAPTION,GLAcc.TABLECAPTION);

      IF GLEntry.FIND('-') THEN BEGIN

      // Add the following line.
      IF (GLEntry."Journal Batch Name" = '') AND NOT IsVATAllocOnCost THEN
      // End of the added line.

      TestFieldError;

      REPEAT

      CheckGLAcc(GLEntry,BalanceCheckAmount,BalanceCheckAddCurrAmount);

      UNTIL GLEntry.NEXT = 0;

      END;
      ...
      Existing code 3
      ...
      IF VATEntry.FIND('-') THEN

      REPEAT

      CheckVAT(VATEntry);

      UNTIL VATEntry.NEXT = 0;

      // Delete the following line.
      IF VATAllocOnCost THEN
      // End of the deleted line.

      IF ValueEntry.FIND('-') THEN

      REPEAT

      CheckItem(ValueEntry);

      UNTIL ValueEntry.NEXT = 0;
      ...
      Replacement code 3
      ...
      IF VATEntry.FIND('-') THEN

      REPEAT

      CheckVAT(VATEntry);

      UNTIL VATEntry.NEXT = 0;

      // Add the following line.
      IF IsVATAllocOnCost THEN
      // End of the added line.

      IF ValueEntry.FIND('-') THEN

      REPEAT

      CheckItem(ValueEntry);

      UNTIL ValueEntry.NEXT = 0;
      ...
    4. Change the code in the SetReverseFilter function as follows:
      Existing code 1
      ...
      TaxDiffEntry.SETRANGE("Transaction No.",Number);

      END ELSE BEGIN

      GLReg.GET(Number);
      ...
      Replacement code 1
      ...
      TaxDiffEntry.SETRANGE("Transaction No.",Number);

      // Add the following line.
      ValueEntry.SETRANGE("Entry No.",0);
      // End of the added line.

      END ELSE BEGIN

      GLReg.GET(Number);
      ...
      Existing code 2
      ...
      VATEntry.SETRANGE("Entry No.",GLReg."From VAT Entry No.",GLReg."To VAT Entry No.");

      GLItemLedgRelation.SETCURRENTKEY(GLItemLedgRelation."G/L Register No.");

      GLItemLedgRelation.SETRANGE("G/L Register No.",GLReg."No.");

      IF GLItemLedgRelation.FINDFIRST THEN

      FromValueEntryNo := GLItemLedgRelation."Value Entry No.";

      IF GLItemLedgRelation.FINDLAST THEN

      ToValueEntryNo := GLItemLedgRelation."Value Entry No.";

      ValueEntry.SETRANGE("Entry No.",FromValueEntryNo,ToValueEntryNo);
      ...
      Replacement code 2
      ...
      VATEntry.SETRANGE("Entry No.",GLReg."From VAT Entry No.",GLReg."To VAT Entry No.");

      // Add the following lines.
      FromValueEntryNo := 0;

      ToValueEntryNo := 0;

      IF VATAllocOnCost THEN BEGIN
      // End of the added lines.

      GLItemLedgRelation.SETCURRENTKEY(GLItemLedgRelation."G/L Register No.");

      GLItemLedgRelation.SETRANGE("G/L Register No.",GLReg."No.");

      IF GLItemLedgRelation.FINDFIRST THEN

      FromValueEntryNo := GLItemLedgRelation."Value Entry No.";

      IF GLItemLedgRelation.FINDLAST THEN

      ToValueEntryNo := GLItemLedgRelation."Value Entry No.";
      // Add the following line.
      END;
      // End of the added line.

      ValueEntry.SETRANGE("Entry No.",FromValueEntryNo,ToValueEntryNo);
      ...
    5. Change the code in the VATAllocationExist function as follows:
      Existing code
      ...
      // Delete the following line.
      VATEntry2.COPYFILTERS(VATEntry2);
      // End of the deleted line.

      VATEntry2.SETRANGE("VAT Allocation Type",VATEntry2."VAT Allocation Type"::Charge);

      EXIT(NOT VATEntry2.ISEMPTY);
      ...
      Replacement code
      ...
      // Add the following line.
      VATEntry2.COPYFILTERS(VATEntry);
      // End of the added line.

      VATEntry2.SETRANGE("VAT Allocation Type",VATEntry2."VAT Allocation Type"::Charge);

      EXIT(NOT VATEntry2.ISEMPTY);
      ...
  2. Change the code in the Post function in the Reverse Entries form (179) as follows:
    Add the following local variable:
    • Name: VATAllocOnCost
    • DataType: Boolean
    Existing code 1
    ...
    IF TempGLReg.FINDSET THEN

    REPEAT

    ReversalEntry2.SetReverseFilter(TempGLReg."No.","Reversal Type");

    // Delete the following line.
    ReversalEntry2.CheckEntries;
    // End of the deleted line.

    GET(1);

    IF "Reversal Type" = "Reversal Type"::Register THEN

    Number := TempGLReg."No."

    ELSE

    Number := "Transaction No.";
    ...
    Replacement code 1
    ...
    IF TempGLReg.FINDSET THEN

    REPEAT

    // Add the following lines.
    SETRANGE("G/L Register No.",TempGLReg."No.");

    SETRANGE("VAT Allocation",TRUE);

    VATAllocOnCost := NOT ISEMPTY;
    // End of the added lines.

    ReversalEntry2.SetReverseFilter(TempGLReg."No.","Reversal Type");

    // Add the following line.
    ReversalEntry2.CheckEntries(VATAllocOnCost);
    // End of the added line.

    GET(1);

    IF "Reversal Type" = "Reversal Type"::Register THEN

    Number := TempGLReg."No."

    ELSE

    Number := "Transaction No.";
    ...
    Existing code 2
    ...
    UNTIL TempGLReg.NEXT = 0;

    END ELSE BEGIN

    ReversalEntry2.SetReverseFilter("Transaction No.","Reversal Type");

    // Delete the following line.
    ReversalEntry2.CheckEntries;
    // End of the deleted line.

    GET(1);

    IF "Reversal Type" = "Reversal Type"::Register THEN

    Number := "G/L Register No."
    ...
    Replacement code 2
    ...
    UNTIL TempGLReg.NEXT = 0;

    END ELSE BEGIN

    // Add the following lines.
    SETRANGE("G/L Register No.",TempGLReg."No.");

    SETRANGE("VAT Allocation",TRUE);

    VATAllocOnCost := NOT ISEMPTY;
    // End of the added lines.

    ReversalEntry2.SetReverseFilter("Transaction No.","Reversal Type");

    // Add the following line.
    ReversalEntry2.CheckEntries(VATAllocOnCost);
    // End of the added line.

    GET(1);

    IF "Reversal Type" = "Reversal Type"::Register THEN

    Number := "G/L Register No."
    ...

Prerequisites

You must have the Russian version of Microsoft Dynamics NAV 2009 R2 with Feature 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


References

VSTF DynamicsNAV SE: 260227

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

↑ Back to the top

Article Info
Article ID : 2562552
Revision : 3
Created on : 1/31/2017
Published on : 1/31/2017
Exists online : False
Views : 182