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.

The payment tolerance is not posted as expected in the Cash Management module in the East European version of Microsoft Dynamics NAV 2009 R2


View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the Eastern Europe (EE) region.

↑ Back to the top


Symptoms

Assume that you enabled the payment tolerance in the East European version of Microsoft Dynamics NAV 2009 R2. When you post a payment by using a cash receipt in the Cash Management module, the payment tolerance is not applied. Additionally, the corresponding invoice remains open.

↑ 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 Amount - OnValidate trigger in the Cash Order Line table (26541) as follows:
    Existing code
    ...
    TestStatusOpen;
    IF Amount <> 0 THEN
    TESTFIELD("Account Type");

    UpdateBalance(0);
    ...
    Replacement code
    ...
    TestStatusOpen;
    IF Amount <> 0 THEN
    TESTFIELD("Account Type");

    UpdateBalance(0);

    // Add the following lines.
    IF ((Rec.Amount <> xRec.Amount)) THEN BEGIN
    IF ("Applies-To Doc. No." <> '') OR ("Applies-to ID" <> '') THEN
    SetApplyToAmount;
    PmtTolCashOrder();
    END;
    //End of the lines.
    ...
  2. Add a new global variable in the Cash Order Line table (26541), and then specify the variable as follows:
    • Name: PaymentToleranceMgt
    • DataType: Codeunit
    • Subtype: Payment Tolerance Management (426)
  3. Create a new global function in the Cash Order Line table (26541) as follows:
    PROCEDURE SetApplyToAmount@20();
    VAR
    CustLedgEntry@1000 : Record 21;
    VendLedgEntry@1001 : Record 25;
    BEGIN
    IF "Account Type" = "Account Type"::Customer THEN BEGIN
    CustLedgEntry.SETCURRENTKEY("Document No.");
    CustLedgEntry.SETRANGE("Document No.",Rec."Applies-To Doc. No.");
    CustLedgEntry.SETRANGE("Customer No.","Account No.");
    CustLedgEntry.SETRANGE(Open,TRUE);
    IF CustLedgEntry.FIND('-') THEN BEGIN
    CustLedgEntry.CALCFIELDS("Remaining Amount");
    CustLedgEntry."Amount to Apply" := CustLedgEntry."Remaining Amount";
    CODEUNIT.RUN(CODEUNIT::"Cust. Entry-Edit",CustLedgEntry);
    END;
    END ELSE IF "Account Type" = "Account Type"::Vendor THEN BEGIN
    VendLedgEntry.SETCURRENTKEY("Document No.");
    VendLedgEntry.SETRANGE("Document No.",Rec."Applies-To Doc. No.");
    VendLedgEntry.SETRANGE("Vendor No.","Account No.");
    VendLedgEntry.SETRANGE(Open,TRUE);
    IF VendLedgEntry.FIND('-') THEN BEGIN
    VendLedgEntry.CALCFIELDS("Remaining Amount");
    VendLedgEntry."Amount to Apply" := VendLedgEntry."Remaining Amount";
    CODEUNIT.RUN(CODEUNIT::"Vend. Entry-Edit",VendLedgEntry);
    END;
    END;
    END;
  4. Create a new global function in the Cash Order Line table (26541) as follows:
    PROCEDURE PmtTolCashOrder@21();
    VAR
    GenJnlLine@1000 : Record 81;
    MaxPmtTolAmount@1001 : Decimal;
    PmtDiscAmount@1002 : Decimal;
    AppliedAmount@1003 : Decimal;
    ApplyingAmount@1004 : Decimal;
    AmounttoApply@1005 : Decimal;
    CashOrderHeader@1006 : Record 26540;
    BEGIN
    MaxPmtTolAmount := 0;
    PmtDiscAmount := 0;
    AppliedAmount := 0;
    ApplyingAmount := 0;
    AmounttoApply := 0;

    CashOrderHeader.GET("Cash Desk No.",
    "Order Type",
    "Cash Order No.");

    GenJnlLine.INIT;
    GenJnlLine."Line No." := 10000;
    IF "Account Type" = "Account Type"::Customer THEN BEGIN
    GenJnlLine."Account Type" := GenJnlLine."Account Type"::Customer;
    GenJnlLine.Amount := -Amount;
    END ELSE
    IF "Account Type" = "Account Type"::Vendor THEN BEGIN
    GenJnlLine."Account Type" := GenJnlLine."Account Type"::Vendor;
    GenJnlLine.Amount := Amount;
    END;
    GenJnlLine."Account No." := "Account No.";
    GenJnlLine."Applies-to Doc. Type" := "Applies-To Doc. Type";
    GenJnlLine."Applies-to Doc. No." := "Applies-To Doc. No.";
    GenJnlLine."Posting Date" := CashOrderHeader."Posting Date";
    GenJnlLine."Document Type" := "Document Type";
    GenJnlLine."Document No." := "Cash Order No.";
    GenJnlLine."Currency Code" := CashOrderHeader."Currency Code";
    PaymentToleranceMgt.PmtTolGenJnl(GenJnlLine);
    END;

Prerequisites

You must have the Eastern European version of Microsoft Dynamics NAV 2009 R2 installed to apply this hotfix.

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

↑ Back to the top

Article Info
Article ID : 2599283
Revision : 2
Created on : 9/19/2018
Published on : 9/19/2018
Exists online : False
Views : 173