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 payment journal that is suggested for a mix of LCY invoices and foreign currency invoices can be paid by using a check from a LCY Bank unexpectedly in the North American version of Microsoft Dynamics NAV 2009

A payment journal that is suggested for a mix of LCY invoices and foreign currency invoices can be paid by using a check from a LCY Bank unexpectedly in the North American version of Microsoft Dynamics NAV 2009

View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the following countries and language locales.
  • English–Canada (en-ca)
  • English–U.S. (en-us)
  • Spanish–Mexico (es-mx)
  • French-Canada (fr-ca)

↑ Back to the top

Symptoms

Assume that you have a payment journal that is suggested for a mix of LCY invoices and foreign currency invoices in the North American version of Microsoft Dynamics NAV 2009. You set a same Document No. value for LCY invoices and foreign currency invoices and the first line of the payment journal is a LCY invoice. In this situation, when you run the Print Check function on the payment journal, the system does not generate an error as expected. Additionally, after you post the payment journal for the printed check, there is an imbalance between the check ledger and the bank account ledger.

Note If the first line of the payment journal is a foreign currency invoice, when you run the Print Check function on the payment journal, the system generates the following error message:
The Bank Account and General Journal Line must have the same currency.
However, this behavior is correct.

This problem occurs in the following products:
  • The North American version of Microsoft Dynamics NAV 2009 R2
  • The North American version of 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 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:
  1. Change the code in the CheckPages - OnPostDataItem trigger in the Check report (1401) as follows:
    Existing code
    ...
    END ELSE BEGIN
    "TotalLineAmount$" := 0;
    IF GenJnlLine2.FIND('-') THEN BEGIN
    HighestLineNo := GenJnlLine2."Line No.";
    REPEAT
    IF GenJnlLine2."Line No." > HighestLineNo THEN
    HighestLineNo := GenJnlLine2."Line No.";
    GenJnlLine3 := GenJnlLine2;
    GenJnlLine3.TESTFIELD("Posting No. Series",'');
    GenJnlLine3."Bal. Account No." := '';
    ...
    Replacement code
    ...
    END ELSE BEGIN
    "TotalLineAmount$" := 0;
    IF GenJnlLine2.FIND('-') THEN BEGIN
    HighestLineNo := GenJnlLine2."Line No.";
    REPEAT

    // Add the following lines.
    IF BankAcc2."Currency Code" <> GenJnlLine2."Currency Code" THEN
    ERROR(Text005);
    // End of the added lines.

    IF GenJnlLine2."Line No." > HighestLineNo THEN
    HighestLineNo := GenJnlLine2."Line No.";
    GenJnlLine3 := GenJnlLine2;
    GenJnlLine3.TESTFIELD("Posting No. Series",'');
    GenJnlLine3."Bal. Account No." := '';
    ...
  2. Change the code in the CheckPages - OnPostDataItem trigger in the Check report (10401) as follows:
    Existing code 
    ...
    END ELSE BEGIN
    "TotalLineAmount$" := 0;
    IF GenJnlLine2.FIND('-') THEN BEGIN
    HighestLineNo := GenJnlLine2."Line No.";
    REPEAT
    IF GenJnlLine2."Line No." > HighestLineNo THEN
    HighestLineNo := GenJnlLine2."Line No.";
    GenJnlLine3 := GenJnlLine2;
    GenJnlLine3.TESTFIELD("Posting No. Series",'');
    GenJnlLine3."Bal. Account No." := '';
    GenJnlLine3."Bank Payment Type" := GenJnlLine3."Bank Payment Type"::" ";
    GenJnlLine3."Document No." := UseCheckNo;
    GenJnlLine3."Check Printed" := TRUE;
    GenJnlLine3.VALIDATE(Amount);
    "TotalLineAmount$" := "TotalLineAmount$" + GenJnlLine3."Amount (LCY)";
    GenJnlLine3.MODIFY;
    UNTIL GenJnlLine2.NEXT = 0;
    END;
    ...
    Replacement code 
    ...
    END ELSE BEGIN
    "TotalLineAmount$" := 0;
    IF GenJnlLine2.FIND('-') THEN BEGIN
    HighestLineNo := GenJnlLine2."Line No.";
    REPEAT

    // Add the following lines.
    IF BankAcc2."Currency Code" <> GenJnlLine2."Currency Code" THEN
    ERROR(Text005);
    // End of the added lines.

    IF GenJnlLine2."Line No." > HighestLineNo THEN
    HighestLineNo := GenJnlLine2."Line No.";
    GenJnlLine3 := GenJnlLine2;
    GenJnlLine3.TESTFIELD("Posting No. Series",'');
    GenJnlLine3."Bal. Account No." := '';
    GenJnlLine3."Bank Payment Type" := GenJnlLine3."Bank Payment Type"::" ";
    GenJnlLine3."Document No." := UseCheckNo;
    GenJnlLine3."Check Printed" := TRUE;
    GenJnlLine3.VALIDATE(Amount);
    "TotalLineAmount$" := "TotalLineAmount$" + GenJnlLine3."Amount (LCY)";
    GenJnlLine3.MODIFY;
    UNTIL GenJnlLine2.NEXT = 0;
    END;
    ...
  3. Change the code in the CheckPages - OnPostDataItem trigger in the Check report (10411) as follows:
    Existing code 
    ...
    END ELSE BEGIN
    "TotalLineAmount$" := 0;
    IF GenJnlLine2.FIND('-') THEN BEGIN
    HighestLineNo := GenJnlLine2."Line No.";
    REPEAT
    IF GenJnlLine2."Line No." > HighestLineNo THEN
    HighestLineNo := GenJnlLine2."Line No.";
    GenJnlLine3 := GenJnlLine2;
    GenJnlLine3.TESTFIELD("Posting No. Series",'');
    GenJnlLine3."Bal. Account No." := '';
    GenJnlLine3."Bank Payment Type" := GenJnlLine3."Bank Payment Type"::" ";
    GenJnlLine3."Document No." := UseCheckNo;
    GenJnlLine3."Check Printed" := TRUE;
    GenJnlLine3.VALIDATE(Amount);
    "TotalLineAmount$" := "TotalLineAmount$" + GenJnlLine3."Amount (LCY)";
    GenJnlLine3.MODIFY;
    UNTIL GenJnlLine2.NEXT = 0;
    END;
    ...
    Replacement code 
    ...
    END ELSE BEGIN
    "TotalLineAmount$" := 0;
    IF GenJnlLine2.FIND('-') THEN BEGIN
    HighestLineNo := GenJnlLine2."Line No.";
    REPEAT

    // Add the following lines.
    IF BankAcc2."Currency Code" <> GenJnlLine2."Currency Code" THEN
    ERROR(Text005);
    // End of the added lines.

    IF GenJnlLine2."Line No." > HighestLineNo THEN
    HighestLineNo := GenJnlLine2."Line No.";
    GenJnlLine3 := GenJnlLine2;
    GenJnlLine3.TESTFIELD("Posting No. Series",'');
    GenJnlLine3."Bal. Account No." := '';
    GenJnlLine3."Bank Payment Type" := GenJnlLine3."Bank Payment Type"::" ";
    GenJnlLine3."Document No." := UseCheckNo;
    GenJnlLine3."Check Printed" := TRUE;
    GenJnlLine3.VALIDATE(Amount);
    "TotalLineAmount$" := "TotalLineAmount$" + GenJnlLine3."Amount (LCY)";
    GenJnlLine3.MODIFY;
    UNTIL GenJnlLine2.NEXT = 0;
    END;
    ...

Prerequisites

You must have one of the following products installed to apply this hotfix:
  • The North American version of Microsoft Dynamics NAV 2009 R2
  • The North American version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)

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

↑ Back to the top

Article Info
Article ID : 2683010
Revision : 1
Created on : 1/7/2017
Published on : 4/5/2012
Exists online : False
Views : 151