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. You cannot run the "Void Check" function for a payment in Microsoft Dynamics NAV 2009

You cannot run the "Void Check" function for a payment in Microsoft Dynamics NAV 2009

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

Assume that you unapply a payment against a purchase invoice and then reapply it against the same invoice in Microsoft Dynamics NAV 2009. When you run the Void Check function for the payment by using the Unapply and void check void type, you receive the following error message:

In the Classic client in Microsoft Dynamics NAV 2009:
Unapplied must be No in Detailed Vendor Ledg. Entry Entry No. = '[EntryNumber]'.
In the RoleTailored client (RTC) in Microsoft Dynamics NAV 2009:
Unapplied must be equal to 'No' in Detailed Vendor Ledg. Entry: Entry No. = [EntryNumber]. Current value is 'Yes'.
This problem occurs in the following products:
  • Microsoft Dynamics NAV 2009 R2
  • Microsoft Dynamics NAV 2009 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. However, 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 Dynamics NAV client users are logged off the system. This includes Microsoft Dynamics NAV Application Server (NAS) services. 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 UnApplyVendInvoices function in the CheckManagement Codeunit (367) as follows:

Existing code

...
AppliesID := CheckLedgEntry."Document No.";

PaymentDetVendLedgEntry.SETCURRENTKEY("Vendor Ledger Entry No.","Entry Type","Posting Date");
PaymentDetVendLedgEntry.SETRANGE("Vendor Ledger Entry No.",OrigPaymentVendLedgEntry."Entry No.");

// Delete the following lines.
PaymentDetVendLedgEntry.SETRANGE("Entry Type",PaymentDetVendLedgEntry."Entry Type"::Application);
IF PaymentDetVendLedgEntry.FINDFIRST THEN BEGIN
GenJnlLine3."Document No." := OrigPaymentVendLedgEntry."Document No.";
GenJnlLine3."Posting Date" := VoidDate;
GenJnlLine3."Account Type" := GenJnlLine3."Account Type"::Vendor;
GenJnlLine3."Account No." := OrigPaymentVendLedgEntry."Vendor No.";
GenJnlLine3.Correction := TRUE;
GenJnlLine3.Description := STRSUBSTNO(Text001,CheckLedgEntry."Check No.");;
GenJnlLine3."Shortcut Dimension 1 Code" := OrigPaymentVendLedgEntry."Global Dimension 1 Code";
GenJnlLine3."Shortcut Dimension 2 Code" := OrigPaymentVendLedgEntry."Global Dimension 2 Code";
GenJnlLine3."Posting Group" := OrigPaymentVendLedgEntry."Vendor Posting Group";
GenJnlLine3."Source Type" := GenJnlLine3."Source Type"::Vendor;
GenJnlLine3."Source No." := OrigPaymentVendLedgEntry."Vendor No.";
GenJnlLine3."Source Code" := SourceCodeSetup."Financially Voided Check";
GenJnlLine3."Source Currency Code" := OrigPaymentVendLedgEntry."Currency Code";
GenJnlLine3."System-Created Entry" := TRUE;
GenJnlLine3."Financial Void" := TRUE;
GenJnlPostLine.UnapplyVendLedgEntry(GenJnlLine3,PaymentDetVendLedgEntry);
END;
// End of the deleted lines.

WITH OrigPaymentVendLedgEntry DO BEGIN
FINDSET(TRUE,FALSE); // re-get the now-modified payment entry.
REPEAT // set up to be applied by upcoming voiding entry.
MakeAppliesID(AppliesID,CheckLedgEntry."Document No.");
"Applies-to ID" := AppliesID;
...

Replacement code

...
AppliesID := CheckLedgEntry."Document No.";

PaymentDetVendLedgEntry.SETCURRENTKEY("Vendor Ledger Entry No.","Entry Type","Posting Date");
PaymentDetVendLedgEntry.SETRANGE("Vendor Ledger Entry No.",OrigPaymentVendLedgEntry."Entry No.");

// Add the following lines.
PaymentDetVendLedgEntry.SETRANGE(Unapplied,FALSE);
PaymentDetVendLedgEntry.SETFILTER("Applied Vend. Ledger Entry No.",'<>%1',0);
PaymentDetVendLedgEntry.SETRANGE("Entry Type",PaymentDetVendLedgEntry."Entry Type"::Application);
PaymentDetVendLedgEntry.FINDFIRST;
GenJnlLine3."Document No." := OrigPaymentVendLedgEntry."Document No.";
GenJnlLine3."Posting Date" := VoidDate;
GenJnlLine3."Account Type" := GenJnlLine3."Account Type"::Vendor;
GenJnlLine3."Account No." := OrigPaymentVendLedgEntry."Vendor No.";
GenJnlLine3.Correction := TRUE;
GenJnlLine3.Description := STRSUBSTNO(Text001,CheckLedgEntry."Check No.");;
GenJnlLine3."Shortcut Dimension 1 Code" := OrigPaymentVendLedgEntry."Global Dimension 1 Code";
GenJnlLine3."Shortcut Dimension 2 Code" := OrigPaymentVendLedgEntry."Global Dimension 2 Code";
GenJnlLine3."Posting Group" := OrigPaymentVendLedgEntry."Vendor Posting Group";
GenJnlLine3."Source Type" := GenJnlLine3."Source Type"::Vendor;
GenJnlLine3."Source No." := OrigPaymentVendLedgEntry."Vendor No.";
GenJnlLine3."Source Code" := SourceCodeSetup."Financially Voided Check";
GenJnlLine3."Source Currency Code" := OrigPaymentVendLedgEntry."Currency Code";
GenJnlLine3."System-Created Entry" := TRUE;
GenJnlLine3."Financial Void" := TRUE;
GenJnlPostLine.UnapplyVendLedgEntry(GenJnlLine3,PaymentDetVendLedgEntry);
// End of the added lines.

WITH OrigPaymentVendLedgEntry DO BEGIN
FINDSET(TRUE,FALSE); // re-get the now-modified payment entry.
REPEAT // set up to be applied by upcoming voiding entry.
MakeAppliesID(AppliesID,CheckLedgEntry."Document No.");
"Applies-to ID" := AppliesID;
...

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.

↑ 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 Usefor other considerations.

↑ Back to the top

Keywords: kberrmsg, kbmbscodefix, kbnoloc, kbsurveynew, kbmbspartner, kbmbsmigrate, kb, kbqfe, kbmbsquickpub

↑ Back to the top

Article Info
Article ID : 2788026
Revision : 1
Created on : 1/7/2017
Published on : 3/13/2013
Exists online : False
Views : 242