You receive an error message when you try to post the payment journal after you import a Bank Giro file in the Swedish version of Microsoft Dynamics NAV 2009 SP1

Applies to: Microsoft Dynamics NAV 2009 Service Pack 1

This article applies to Microsoft Dynamics NAV for the Sweden (se) language locale.

Symptoms


Assume that you import a Bank Giro file as a vendor payment journal in the Swedish version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1). When you try to post the payment journal, you receive the following error message:
There is no Vendor Ledger Entry within the filter. Filters: Document No.: Document_No., Open: Yes, Vendor No.: Vendor_No., Document Type: ' ', On Hold: '' It is not possible to post without adding information.

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, 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 OnPostReport trigger in the Report back from Bank Giro report (11210) as follows:
    Exsiting code
    ...
    IF LineType = '14' THEN BEGIN
    IF InvioceExists(DocumentNo) THEN BEGIN
    GenJournalLine.VALIDATE("Account No.",VendorLedgerEntry."Vendor No.");
    GenJournalLine.VALIDATE("Applies-to Doc. No.",VendorLedgerEntry."Document No.");
    END ELSE
    GenJournalLine.VALIDATE("Applies-to Doc. No.", '');
    GenJournalLine.VALIDATE(Amount,Txt2Dec(TxtLine,38,12));
    GenJournalLine.VALIDATE(Description,GenJournalLine."Applies-to Doc. No." + ' ' + BA002);
    END ELSE BEGIN
    IF CreditMemoExists(DocumentNo) THEN BEGIN
    GenJournalLine.VALIDATE("Account No.",VendorLedgerEntry."Vendor No.");
    GenJournalLine.VALIDATE("Applies-to Doc. No.",VendorLedgerEntry."Document No.");
    END ELSE
    GenJournalLine.VALIDATE("Applies-to Doc. No.", '');
    GenJournalLine.VALIDATE(Amount,-Txt2Dec(TxtLine,38,12));
    GenJournalLine.VALIDATE(Description,GenJournalLine."Applies-to Doc. No." + ' ' + BA003);
    END;
    IF GenJournalLine."Applies-to Doc. No." = '' THEN
    GenJournalLine.VALIDATE(Description, BA004 + ' ' + DocumentNo);
    GenJournalLine.INSERT;
    ...
    Replacement code
    ...
    IF LineType = '14' THEN BEGIN
    IF InvioceExists(DocumentNo) THEN BEGIN
    GenJournalLine.VALIDATE("Account No.",VendorLedgerEntry."Vendor No.");

    // Add the following line.
    GenJournalLine.VALIDATE("Applies-to Doc. Type",VendorLedgerEntry."Document Type");
    // End of the added line.

    GenJournalLine.VALIDATE("Applies-to Doc. No.",VendorLedgerEntry."Document No.");
    END ELSE
    GenJournalLine.VALIDATE("Applies-to Doc. No.", '');
    GenJournalLine.VALIDATE(Amount,Txt2Dec(TxtLine,38,12));
    GenJournalLine.VALIDATE(Description,GenJournalLine."Applies-to Doc. No." + ' ' + BA002);
    END ELSE BEGIN
    IF CreditMemoExists(DocumentNo) THEN BEGIN
    GenJournalLine.VALIDATE("Account No.",VendorLedgerEntry."Vendor No.");

    // Add the following line.
    GenJournalLine.VALIDATE("Applies-to Doc. Type",VendorLedgerEntry."Document Type");
    // End of the added line.

    GenJournalLine.VALIDATE("Applies-to Doc. No.",VendorLedgerEntry."Document No.");
    END ELSE
    GenJournalLine.VALIDATE("Applies-to Doc. No.", '');
    GenJournalLine.VALIDATE(Amount,-Txt2Dec(TxtLine,38,12));
    GenJournalLine.VALIDATE(Description,GenJournalLine."Applies-to Doc. No." + ' ' + BA003);
    END;
    IF GenJournalLine."Applies-to Doc. No." = '' THEN
    GenJournalLine.VALIDATE(Description, BA004 + ' ' + DocumentNo);
    // Add the following line.
    GenJournalLine."External Document No." := VendorLedgerEntry."External Document No.";
    // End of the added line.
    GenJournalLine.INSERT;
    ...
  2. Change the code in the InvioceExists function in the Report back from Bank Giro report (11210) as follows:
    Exsiting code
    ...
    VendorLedgerEntry.SETCURRENTKEY("Document No.");
    VendorLedgerEntry.SETRANGE(Open,TRUE);
    VendorLedgerEntry.SETRANGE("Document No.",InDocumentNo);
    EXIT(VendorLedgerEntry.FIND('-'))
    ...
    Replacement code
    ...
    VendorLedgerEntry.SETCURRENTKEY("Document No.");
    VendorLedgerEntry.SETRANGE(Open,TRUE);

    // Add the following line.
    VendorLedgerEntry.SETRANGE("Document Type",VendorLedgerEntry."Document Type"::Invoice);
    // End of the added line.

    VendorLedgerEntry.SETRANGE("Document No.",InDocumentNo);
    EXIT(VendorLedgerEntry.FIND('-'));
    ...
  3. Change the code in the CreditMemoExists function in the Report back from Bank Giro report (11210) as follows:
    Exsiting code
    ...
    VendorLedgerEntry.SETCURRENTKEY("Document No.");
    VendorLedgerEntry.SETRANGE(Open,TRUE);
    VendorLedgerEntry.SETRANGE("Document No.",InDocumentNo);
    EXIT(VendorLedgerEntry.FIND('-'));
    ...
    Replacement code
    ...
    VendorLedgerEntry.SETCURRENTKEY("Document No.");
    VendorLedgerEntry.SETRANGE(Open,TRUE);

    // Add the following line.
    VendorLedgerEntry.SETRANGE("Document Type",VendorLedgerEntry."Document Type"::"Credit Memo");
    // End of the added line.

    VendorLedgerEntry.SETRANGE("Document No.",InDocumentNo);
    EXIT(VendorLedgerEntry.FIND('-'));
    ...

Prerequisites

You must have the Swedish version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1) 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.
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.