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)

Symptoms

In the North American version of Microsoft Dynamics NAV 2009, if a bank account is set up for an electronic funds transfer (EFT) and if you specify the Export Format setting to CA (Canada) on the Transfer tab of the bank account card, the Input Qualifier field is available. If you do not specify the Input Qualifier number, you receive the following error message when you send out a file:

You must specify Input Qualifier in Bank Account No. = 'Bank_Account_Number'.

Microsoft Dynamics NAV 2009 does not let you process a payment transaction if the Input Qualifier field is blank. However, if you specify the Input Qualifier number, the Royal Bank of Canada will reject the file.
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

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.


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 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 StartExportFile function in the Export Payments (RB) codeunit (10091) as follows:

Existing code 1

...
TESTFIELD("Last E-Pay Export File Name");
TESTFIELD("Bank Acc. Posting Group");
TESTFIELD(Blocked,FALSE);
TESTFIELD("Client No.");
TESTFIELD("Client Name");

// Delete the following line.
TESTFIELD("Input Qualifier");

// NA0007.begin
GenJnlLine.TESTFIELD("Transaction Code");
GenJnlLine.TESTFIELD("Company Entry Description");
// NA0007.end
...

Replacement code 1

...
TESTFIELD("Last E-Pay Export File Name");
TESTFIELD("Bank Acc. Posting Group");
TESTFIELD(Blocked,FALSE);
TESTFIELD("Client No.");
TESTFIELD("Client Name");
// NA0007.begin
GenJnlLine.TESTFIELD("Transaction Code");
GenJnlLine.TESTFIELD("Company Entry Description");
// NA0007.end
...

Existing code 2

...
FileIsInProcess := TRUE;
FileDate := TODAY;
FileTime := TIME;
NoOfRec := 0;
TotalFileDebit := 0;
TotalFileCredit := 0;
RecordLength := 152;
// NA0007.begin
Transactions := 0;
// NA0007.end
FileHeaderRec := '';

// Delete the following line.
AddToPrnString(FileHeaderRec,"Input Qualifier",1,23,Justification::Left,' ');

ExportPrnString(FileHeaderRec);
...

Replacement code 2

...
FileIsInProcess := TRUE;
FileDate := TODAY;
FileTime := TIME;
NoOfRec := 0;
TotalFileDebit := 0;
TotalFileCredit := 0;
RecordLength := 152;
// NA0007.begin
Transactions := 0;
// NA0007.end
FileHeaderRec := '';
ExportPrnString(FileHeaderRec);
...

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

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.

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.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×