Error message when you try to void a check that is applied to both a currency invoice and a non- currency invoice in Microsoft Dynamics NAV 4.0: "Currency code '' does not exist"

Article ID: 976238 - View products that this article applies to.
Rapidly Published articles provide information directly from within the Microsoft support organization. The information that is contained herein is created in response to emerging or unique topics, or is intended to supplement other Knowledge Base information.
Microsoft Business Solutions-Navision 4.0 and Microsoft Navision 4.0 are now part of Microsoft Dynamics NAV 4.0. All references to Microsoft Business Solutions-Navision or to Microsoft Navision 4.0 relate to Microsoft Dynamics NAV.
This article applies to Microsoft Dynamics NAV for all countries and all language locales.
Expand all | Collapse all

On This Page

SYMPTOMS

When you try to void a check that is applied to both a currency invoice and a non-currency invoice in Microsoft Dynamics NAV 4.0, you receive the following error message:
Currency code '' does not exist.

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 4.0 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. Change the code in the PrintSettledLoop - OnAfterGetRecord procedure of the DataItem 4 object in the Check report (1401) as follows:
    Existing code 1
    ...
                      CustLedgEntry.SETRANGE("Document Type",GenJnlLine2."Applies-to Doc. Type");
                      CustLedgEntry.SETRANGE("Document No.",GenJnlLine2."Applies-to Doc. No.");
                      CustLedgEntry.SETRANGE("Customer No.",BalancingNo);
                      CustLedgEntry.FIND('-');
                      CustUpdateAmounts(CustLedgEntry,CurrentLineAmount);
                      LineAmount := CurrentLineAmount;
    ...
    
    Replacement code 1
    ...
                      CustLedgEntry.SETRANGE("Document Type",GenJnlLine2."Applies-to Doc. Type");
                      CustLedgEntry.SETRANGE("Document No.",GenJnlLine2."Applies-to Doc. No.");
                      CustLedgEntry.SETRANGE("Customer No.",BalancingNo);
    
                      // Add the following line.
                      CustLedgEntry.SETRANGE("Amount (LCY)",-GenJnlLine2."Amount (LCY)");		
    
                      CustLedgEntry.FIND('-');
                      CustUpdateAmounts(CustLedgEntry,CurrentLineAmount);
                      LineAmount := CurrentLineAmount;
    ...
    
    Existing code 2
    ...
                      VendLedgEntry.SETRANGE("Document Type",GenJnlLine2."Applies-to Doc. Type");
                      VendLedgEntry.SETRANGE("Document No.",GenJnlLine2."Applies-to Doc. No.");
                      VendLedgEntry.SETRANGE("Vendor No.",BalancingNo);
                      VendLedgEntry.FIND('-');
                      VendUpdateAmounts(VendLedgEntry,CurrentLineAmount);
                      LineAmount := CurrentLineAmount;
    ...
    
    Replacement code 2
    ...
                      VendLedgEntry.SETRANGE("Document Type",GenJnlLine2."Applies-to Doc. Type");
                      VendLedgEntry.SETRANGE("Document No.",GenJnlLine2."Applies-to Doc. No.");
                      VendLedgEntry.SETRANGE("Vendor No.",BalancingNo);
    
                      // Add the following line.
    	                 VendLedgEntry.SETRANGE("Amount (LCY)",-GenJnlLine2."Amount (LCY)");		
    
                      VendLedgEntry.FIND('-');
                      VendUpdateAmounts(VendLedgEntry,CurrentLineAmount);
                      LineAmount := CurrentLineAmount;
    ...
    
  2. Change the code in the FinancialVoidCheck procedure in the CheckManagement codeunit (367) as follows:
    Existing code 1
    ...
          WITH CustLedgEntry DO BEGIN
            SETCURRENTKEY("Transaction No.");
            SETRANGE("Transaction No.",BankAccLedgEntry2."Transaction No.");
            SETRANGE("Document No.",BankAccLedgEntry2."Document No.");
            SETRANGE("Posting Date",BankAccLedgEntry2."Posting Date");
            IF FIND('-') THEN BEGIN
              REPEAT
                CALCFIELDS("Original Amount");
                GenJnlLine2.VALIDATE(Amount,-"Original Amount");
                BalanceAmountLCY := BalanceAmountLCY + GenJnlLine2."Amount (LCY)";
                MakeAppliesID(GenJnlLine2."Applies-to ID",CheckLedgEntry."Document No.");
                GenJnlLine2."Shortcut Dimension 1 Code" := "Global Dimension 1 Code";
                GenJnlLine2."Shortcut Dimension 2 Code" := "Global Dimension 2 Code";
    ...
    
    Replacement code 1
    ...
          WITH CustLedgEntry DO BEGIN
            SETCURRENTKEY("Transaction No.");
            SETRANGE("Transaction No.",BankAccLedgEntry2."Transaction No.");
            SETRANGE("Document No.",BankAccLedgEntry2."Document No.");
            SETRANGE("Posting Date",BankAccLedgEntry2."Posting Date");
            IF FIND('-') THEN BEGIN
              REPEAT
                CALCFIELDS("Original Amount");
                GenJnlLine2.VALIDATE(Amount,-"Original Amount");
    
                // Add the following line.
                GenJnlLine2.VALIDATE("Currency Code","Currency Code");			
    
                BalanceAmountLCY := BalanceAmountLCY + GenJnlLine2."Amount (LCY)";
                MakeAppliesID(GenJnlLine2."Applies-to ID",CheckLedgEntry."Document No.");
                GenJnlLine2."Shortcut Dimension 1 Code" := "Global Dimension 1 Code";
                GenJnlLine2."Shortcut Dimension 2 Code" := "Global Dimension 2 Code";
    ...
    
    Existing code 2
    ...
          WITH VendorLedgEntry DO BEGIN
            SETCURRENTKEY("Transaction No.");
            SETRANGE("Transaction No.",BankAccLedgEntry2."Transaction No.");
            SETRANGE("Document No.",BankAccLedgEntry2."Document No.");
            SETRANGE("Posting Date",BankAccLedgEntry2."Posting Date");
            IF FIND('-') THEN BEGIN
              REPEAT
                CALCFIELDS("Original Amount");
                GenJnlLine2.VALIDATE(Amount,-"Original Amount");
                BalanceAmountLCY := BalanceAmountLCY + GenJnlLine2."Amount (LCY)";
                MakeAppliesID(GenJnlLine2."Applies-to ID",CheckLedgEntry."Document No.");
                GenJnlLine2."Shortcut Dimension 1 Code" := "Global Dimension 1 Code";
                GenJnlLine2."Shortcut Dimension 2 Code" := "Global Dimension 2 Code";
    ...
    
    Replacement code 2
    ...
          WITH VendorLedgEntry DO BEGIN
            SETCURRENTKEY("Transaction No.");
            SETRANGE("Transaction No.",BankAccLedgEntry2."Transaction No.");
            SETRANGE("Document No.",BankAccLedgEntry2."Document No.");
            SETRANGE("Posting Date",BankAccLedgEntry2."Posting Date");
            IF FIND('-') THEN BEGIN
              REPEAT
                CALCFIELDS("Original Amount");
                GenJnlLine2.VALIDATE(Amount,-"Original Amount");
    
                // Add the following line.
                GenJnlLine2.VALIDATE("Currency Code","Currency Code");			
    
                BalanceAmountLCY := BalanceAmountLCY + GenJnlLine2."Amount (LCY)";
                MakeAppliesID(GenJnlLine2."Applies-to ID",CheckLedgEntry."Document No.");
                GenJnlLine2."Shortcut Dimension 1 Code" := "Global Dimension 1 Code";
                GenJnlLine2."Shortcut Dimension 2 Code" := "Global Dimension 2 Code";
    ...
    
If you use the North American version of Microsoft Dynamics NAV 4.0, make additional code changes in the PmtTolGenJnl procedure in the "Payment Tolerance Management" codeunit (426). To do this, follow these steps:
  1. Add the following local variable:
    SourceCodeSetup@1020000 : Record 242;
  2. Change the code as follows:
    Existing code 2
    ...
    MaxPmtTolAmount := 0;
    PmtDiscAmount := 0;
    AppliedAmount := 0;
    ApplyingAmount := 0;
    AmounttoApply := 0;
    GenJnlLine := NewGenJnlline;
    
    IF GenJnlLine."Check Printed" = TRUE THEN
      EXIT(TRUE);
    ...
    
    Replacement code 2
    ...
    MaxPmtTolAmount := 0;
    PmtDiscAmount := 0;
    AppliedAmount := 0;
    ApplyingAmount := 0;
    AmounttoApply := 0;
    GenJnlLine := NewGenJnlline;
    
    // Add the following lines.
    SourceCodeSetup.GET;									 
    IF (GenJnlLine."Source Code" = SourceCodeSetup."Financially Voided Check") THEN	 
      EXIT(TRUE);										 
    // End of the added lines.
    
    IF GenJnlLine."Check Printed" = TRUE THEN
      EXIT(TRUE);
    ...
    

Prerequisites

You must have Service Pack 3 for Microsoft Dynamics NAV 4.0 installed to apply this hotfix.

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.
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED IN THE DOCUMENTS AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALS”) FOR ANY PURPOSE.

THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Properties

Article ID: 976238 - Last Review: August 4, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft Dynamics NAV 4.0
Keywords: 
kbmbsbankaccountmanagement kberrmsg kbsurveynew kbmbsmigrate kbqfe kbmbscodefix KB976238

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com