Microsoft KB Archive Search

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.

  1. Home
  2. Payment tolerance does not work as expected after you apply hotfix 2799636 in the Italian version of Microsoft Dynamics NAV 2009

Payment tolerance does not work as expected after you apply hotfix 2799636 in the Italian version of Microsoft Dynamics NAV 2009

View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the Italian (it) language locale.

↑ Back to the top

Symptoms

Assume that you apply hotfix 2799636 in the Italian version of Microsoft Dynamics NAV 2009. You select the Payment Tolerance Warning check box on the Application tab in the General Ledger Setup form. Then you create a payment for a customer. Next, you select multiple entries in the Apply Customer Entries form. Then you change the Amount to apply values for the entries. In this situation, you experience one of the following problems:
  1. When you click Ok, the payment tolerance warning does not appear.
  2. When you click Ok, the payment tolerance warning appears. However, the system calculates incorrect payment amounts.
This problem also occurs in the Apply Vendor Entries form. This problem occurs in the following products:
  • The Italian version of Microsoft Dynamics NAV 2009 R2
  • The Italian version of Microsoft Dynamics NAV 2009 Service Pack 1
For more information about hotfix 2799636, click the following article number to view the article in the Microsoft Knowledge Base:
2799636 The system calculates incorrect payment tolerance amount when you post a payment for an installment in the Italian version of Microsoft Dynamics NAV 2009

↑ 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 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.

↑ 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 PutCustPmtTolAmount function in the Payment Tolerance Management codeunit (426) as follows:
    Existing code 1
    ...
    CustledgEntry."Posting Date");
    END ELSE
    AcceptedTolAmount := AcceptedTolAmount - AcceptedEntryTolAmount;

    // Delete the following line.
    AppliedCustLedgEntry."Accepted Payment Tolerance" := AcceptedTolAmountTemp;

    END ELSE BEGIN
    AcceptedEntryTolAmount := AcceptedTolAmount;
    IF CustledgEntry."Currency Code" <> AppliedCustLedgEntry."Currency Code" THEN
    AcceptedEntryTolAmount :=
    ...

    Replacement code 1
    ...
    CustledgEntry."Posting Date");
    END ELSE
    AcceptedTolAmount := AcceptedTolAmount - AcceptedEntryTolAmount;

    // Add the following lines.
    AppliedCustLedgEntry."Accepted Payment Tolerance" := RetAccPmtTol(CustledgEntry."Applies-to Doc. No.",
    Amount + AppliedAmount,AcceptedEntryTolAmount);
    // End of the lines.

    END ELSE BEGIN
    AcceptedEntryTolAmount := AcceptedTolAmount;
    IF CustledgEntry."Currency Code" <> AppliedCustLedgEntry."Currency Code" THEN
    AcceptedEntryTolAmount :=
    ...
    Existing code 2
    ...
    GenJnlPostLine.ExchAmount(
    AcceptedEntryTolAmount,CustledgEntry."Currency Code",AppliedCustLedgEntry."Currency Code",
    CustledgEntry."Posting Date");

    // Delete the following line.
    AppliedCustLedgEntry."Accepted Payment Tolerance" := AcceptedTolAmountTemp;

    END;
    AppliedCustLedgEntry."Max. Payment Tolerance" := AppliedCustLedgEntryTemp."Max. Payment Tolerance";
    AppliedCustLedgEntry."Amount to Apply" := AppliedCustLedgEntryTemp."Remaining Amount";
    AppliedCustLedgEntry.MODIFY;
    ...
    Replacement code 2
    ...
    GenJnlPostLine.ExchAmount(
    AcceptedEntryTolAmount,CustledgEntry."Currency Code",AppliedCustLedgEntry."Currency Code",
    CustledgEntry."Posting Date");

    // Add the following ines.
    AppliedCustLedgEntry."Accepted Payment Tolerance" := RetAccPmtTol(CustledgEntry."Applies-to Doc. No.",
    Amount + AppliedAmount,AcceptedEntryTolAmount);
    // End of the lines.

    END;
    AppliedCustLedgEntry."Max. Payment Tolerance" := AppliedCustLedgEntryTemp."Max. Payment Tolerance";
    AppliedCustLedgEntry."Amount to Apply" := AppliedCustLedgEntryTemp."Remaining Amount";
    AppliedCustLedgEntry.MODIFY;
    ...
  2. Change the code in the PutVendPmtTolAmount function in the Payment Tolerance Management codeunit (426) as follows:
    Existing code 1
    ...
    VendLedgEntry."Posting Date");
    END ELSE
    AcceptedTolAmount := AcceptedTolAmount - AcceptedEntryTolAmount;

    // Delete the following line.
    AppliedVendLedgEntry."Accepted Payment Tolerance" :=AcceptedTolAmountTemp;

    END ELSE BEGIN
    AcceptedEntryTolAmount := AcceptedTolAmount;
    IF VendLedgEntry."Currency Code" <> AppliedVendLedgEntry."Currency Code" THEN
    AcceptedEntryTolAmount :=
    ...
    Replacement code 1
    ...
    VendLedgEntry."Posting Date");
    END ELSE
    AcceptedTolAmount := AcceptedTolAmount - AcceptedEntryTolAmount;

    // Add the following lines. 
    AppliedVendLedgEntry."Accepted Payment Tolerance" := RetAccPmtTol(VendLedgEntry."Applies-to Doc. No.",
    Amount + AppliedAmount,AcceptedEntryTolAmount);
    // End of the lines.

    END ELSE BEGIN
    AcceptedEntryTolAmount := AcceptedTolAmount;
    IF VendLedgEntry."Currency Code" <> AppliedVendLedgEntry."Currency Code" THEN
    AcceptedEntryTolAmount :=
    ...
    Existing code 2
    ...
    GenJnlPostLine.ExchAmount(
    AcceptedEntryTolAmount,VendLedgEntry."Currency Code",AppliedVendLedgEntry."Currency Code",
    VendLedgEntry."Posting Date");

    // Delete the following line.
    AppliedVendLedgEntry."Accepted Payment Tolerance" := AcceptedTolAmountTemp;
     
    END;
    AppliedVendLedgEntry."Max. Payment Tolerance" := AppliedVendLedgEntryTemp."Max. Payment Tolerance";
    AppliedVendLedgEntry."Amount to Apply" := AppliedVendLedgEntryTemp."Remaining Amount";
    AppliedVendLedgEntry.MODIFY;
    ...
    Replacement code 2
    ...
    GenJnlPostLine.ExchAmount(
    AcceptedEntryTolAmount,VendLedgEntry."Currency Code",AppliedVendLedgEntry."Currency Code",
    VendLedgEntry."Posting Date");

    // Add the following lines.
    AppliedVendLedgEntry."Accepted Payment Tolerance" := RetAccPmtTol(VendLedgEntry."Applies-to Doc. No.",
    Amount + AppliedAmount,AcceptedEntryTolAmount);
    // End of the lines.

    END;
    AppliedVendLedgEntry."Max. Payment Tolerance" := AppliedVendLedgEntryTemp."Max. Payment Tolerance";
    AppliedVendLedgEntry."Amount to Apply" := AppliedVendLedgEntryTemp."Remaining Amount";
    AppliedVendLedgEntry.MODIFY;
    ...
  3. Change the code in the DelVendPmtTolAcc2 function in the Payment Tolerance Management codeunit (426) as follows:
    Existing code
    ...
    COMMIT;
    END;
    END;
    END;
    ...
    Replacement code
    ...
    COMMIT;
    END;
    END;
    END;

    // Add the following lines.
    PROCEDURE RetAccPmtTol@1130000(AppToDocNo@1130000 : Code[20];TotalTolAmt@1130001 : Decimal;EntryTolAmt@1130002 : Decimal) : Decimal;
    BEGIN
    IF AppToDocNo <> '' THEN
    EXIT(TotalTolAmt);
    EXIT(EntryTolAmt);
    END;
    // End of the lines.
    ...

Prerequisites

You must have one of the following products installed to apply this hotfix:
  • The Italian version of Microsoft Dynamics NAV 2009 R2
  • The Italian version of Microsoft Dynamics NAV 2009 Service Pack 1

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, kbmbscodefix, kbnoloc, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 2802042
Revision : 1
Created on : 1/7/2017
Published on : 3/22/2013
Exists online : False
Views : 228