"There is no Cust Ledger Entry within the filter" error message when you try to post a journal line in Microsoft Dynamics NAV 2013

Applies to: Dynamics NAV 2013

This article applies to Microsoft Dynamics NAV for all countries and all language locales.

Symptoms


Assume that you enter an incorrect Applies-to document No. value in a journal line in Microsoft Dynamics NAV 2013. Then, you correct the Applies-to document No. value. In this situation, when you try to post the journal line, you receive the following error message:
There is no Cust Ledger Entry within the filter.

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 2013 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 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, use the following steps:
  1. Create two functions in the Gen. Journal Line table (81) as follows:
    LOCAL PROCEDURE CustVendAccountNosModified@32() : Boolean;
    BEGIN
    EXIT(
    (("Bal. Account No." <> xRec."Bal. Account No.") AND
    ("Bal. Account Type" IN ["Bal. Account Type"::Customer,"Bal. Account Type"::Vendor])) OR
    (("Account No." <> xRec."Account No.") AND
    ("Account Type" IN ["Account Type"::Customer,"Account Type"::Vendor])))
    END;

    LOCAL PROCEDURE CheckPaymentTolerance@34();
    BEGIN
    IF Amount <> 0 THEN
    IF ("Bal. Account No." <> xRec."Bal. Account No.") OR ("Account No." <> xRec."Account No.") THEN
    PaymentToleranceMgt.PmtTolGenJnl(Rec);
    END;
  2. Change the code in the Fields in the Gen. Journal Line table (81) as follows:
    Existing code 1
    ...
    END;
    VALIDATE("Payment Terms Code");
    END;
    "Account Type"::Vendor:
    ...
    Replacement code 1
    ...
    END;
    VALIDATE("Payment Terms Code");

    // Add the following line.
    CheckPaymentTolerance;
    // End of the added line.

    END;
    "Account Type"::Vendor:
    ...
    Existing code 2
    ...
    END;
    VALIDATE("Payment Terms Code");
    END;
    "Account Type"::"Bank Account":
    ...
    Replacement code 2
    ...
    END;
    VALIDATE("Payment Terms Code");

    // Add the following line.
    CheckPaymentTolerance;
    // End of the added line.

    END;
    "Account Type"::"Bank Account":
    ...
    Existing code 3
    ...
    END;
    VALIDATE("Payment Terms Code");
    END;
    "Bal. Account Type"::Vendor:
    ...
    Replacement code 3
    ...
    END;
    VALIDATE("Payment Terms Code");

    // Add the following line.
    CheckPaymentTolerance;
    // End of the added line.

    END;
    "Bal. Account Type"::Vendor:
    ...
    Existing code 4
    ...
    END;
    VALIDATE("Payment Terms Code");
    END;
    "Bal. Account Type"::"Bank Account":
    ...
    Replacement code 4
    ...
    END;
    VALIDATE("Payment Terms Code");

    // Add the following line.
    CheckPaymentTolerance;
    // End of the added line.

    END;
    "Bal. Account Type"::"Bank Account":
    ...
    Existing code 5
    ...
    "Currency Factor" := 0;
    VALIDATE("Currency Factor");

    // Delete the following lines.
    IF ("Currency Code" <> xRec."Currency Code") AND (Amount <> 0) THEN
    PaymentToleranceMgt.PmtTolGenJnl(Rec);
    // End of the deleted lines.

    END;
    }
    ...
    Replacement code 5
    ...
    "Currency Factor" := 0;
    VALIDATE("Currency Factor");

    // Add the following lines.
    IF NOT CustVendAccountNosModified THEN
    IF ("Currency Code" <> xRec."Currency Code") AND (Amount <> 0) THEN
    PaymentToleranceMgt.PmtTolGenJnl(Rec);
    // End of the added lines.

    END;
    }
    ...
    Existing code 6
    ...
    END;

    // Delete the following line.
    IF xRec.Amount <> 0 THEN
    // End of the deleted line.

    IF NOT PaymentToleranceMgt.PmtTolGenJnl(Rec) THEN
    EXIT;
    ...
    Replacement code 6
    ...
    END;

    // Add the following line.
    IF Amount <> 0 THEN
    // End of the added line.

    IF NOT PaymentToleranceMgt.PmtTolGenJnl(Rec) THEN
    EXIT;
    ...
  3. Change the code in the General Journal page (39) as follows:
    Existing code
    ...
    SourceExpr=IsApplied }

    { 26 ;2 ;Field ;
    SourceExpr="Applies-to Doc. No.";
    ...
    Replacement code
    ...
    SourceExpr=IsApplied }

    // Add the following lines.
    { 5 ;2 ;Field ;
    SourceExpr="Applies-to Doc. Type";
    Visible=FALSE }
    // End of the added lines.

    { 26 ;2 ;Field ;
    SourceExpr="Applies-to Doc. No.";
    ...

Prerequisites

You must have Microsoft Dynamics NAV 2013 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 Usefor other considerations.