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. The "Suggest Vendor Payments" batch job unexpectedly rounds the amount of the suggested payment line in the payment journal in the Hungarian version of Microsoft Dynamics NAV 2009 R2

The "Suggest Vendor Payments" batch job unexpectedly rounds the amount of the suggested payment line in the payment journal in the Hungarian version of Microsoft Dynamics NAV 2009 R2

View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the Hungarian (hu) language locale.

↑ Back to the top

Symptoms

Consider the following scenario in the Hungarian version of Microsoft Dynamics NAV 2009 R2: 
  • You apply hotfix 2664500.
  • The amount rounding precision in the General Ledger Setup dialog box is set to one.
  • You post a purchase invoice in a foreign currency. Vendor ledger entries are created.
  • You run the "Suggest Vendor Payments" batch job in a payment journal to create a suggested payment line for the invoice based on the vendor ledger entries processing.
  • You review the suggested payment line in the payment journal.
In this scenario, the system unexpectedly rounds the amount of the suggested payment line.

For more information about hotfix 2664500, click the following article number to view the article in the Microsoft Knowledge Base:
2664500 Incorrect exchange rate is used when you post a general ledger journal that has several lines that use the additional reporting currency in the Hungarian version of Microsoft Dynamics NAV 2009 R2

↑ 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 Fields section in the "Gen. Journal Line" table (81) as follows:
    Existing code 
    ...
    "VAT Prod. Posting Group" := '';

    // Delete the following line.
    IF (Vend."Pay-to Vendor No." <> '') AND (Vend."Pay-to Vendor No." <> "Account No.") THEN BEGIN

    OK := CONFIRM(Text014,FALSE,Vend.TABLECAPTION,Vend."No.",Vend.FIELDCAPTION("Pay-to Vendor No."),
    ...
    Replacement code
    ...
    "VAT Prod. Posting Group" := '';

    // Add the following lines.
    IF (Vend."Pay-to Vendor No." <> '') AND (Vend."Pay-to Vendor No." <> "Account No.") AND
    NOT HideValidationDialog
    THEN BEGIN
    // End of the lines.

    OK := CONFIRM(Text014,FALSE,Vend.TABLECAPTION,Vend."No.",Vend.FIELDCAPTION("Pay-to Vendor No."),
    ...
  2. Change the code in the Global Variables section in the "Gen. Journal Line" table (81) as follows:
    Existing code
    ...
    WarningMessageShown@1064 : Boolean;
    ...
    Replacement code 
    ...
    WarningMessageShown@1064 : Boolean;

    // Add the following line.
    HideValidationDialog@1074 : Boolean;
    ...
  3. Add the new SetHideValidation function in the "Gen. Journal Line" table (81) as follows:
    PROCEDURE SetHideValidation@52(NewHideValidationDialog@1000 : Boolean);
    BEGIN
    HideValidationDialog := NewHideValidationDialog;
    END;
  4. Change the code in the SaveAmount function in the Suggest Vendor Payments report (393) as follows:
    Existing code 1
    ...
    "VAT Prod. Posting Group" := '';
    VALIDATE("Payment Terms Code");
    ...
    Replacement code 1
    ...
    "VAT Prod. Posting Group" := '';

    // Add the following line.
    VALIDATE("Currency Code",VendLedgEntry."Currency Code");

    VALIDATE("Payment Terms Code");
    ...
    Existing code 2
    ...
    Amount := -VendLedgEntry."Remaining Amount";

    // Delete the following line.
    VALIDATE("Account No.",Vend2."No.");

    VALIDATE(Amount);
    ...
    Replacement code 2
    ...
    Amount := -VendLedgEntry."Remaining Amount";
    VALIDATE(Amount);
    ...
  5. Change the code in the MakeGenJnlLines function in the Suggest Vendor Payments report (393) as follows:
    Existing code 1
    ...
    GLSetup@1005 : Record 98;
    DimBufMgt@1003 : Codeunit 411;
    ...
    Replacement code 1
    ...
    GLSetup@1005 : Record 98;

    // Add the following line.
    Vendor@1007 : Record 23;

    DimBufMgt@1003 : Codeunit 411;
    ...
    Existing code 2
    ...
    "Account Type" := "Account Type"::Vendor;
    VALIDATE("Account No.",TempPaymentBuffer."Vendor No.");
    ...
    Replacement code 2
    ...
    "Account Type" := "Account Type"::Vendor;

    // Add the following line.
    SetHideValidation(TRUE);

    VALIDATE("Account No.",TempPaymentBuffer."Vendor No.");
    ...
    Existing code 3
    ...
    VALIDATE("Account No.",TempPaymentBuffer."Vendor No.");
    "Bal. Account Type" := BalAccType;
    ...
    Replacement code 3
    ...
    VALIDATE("Account No.",TempPaymentBuffer."Vendor No.");

    // Add the following lines.
    Vendor.GET(TempPaymentBuffer."Vendor No.");
    IF (Vendor."Pay-to Vendor No." <> '') THEN
    Vendor.TESTFIELD("Pay-to Vendor No.","Account No.");
    // End of the lines.

    "Bal. Account Type" := BalAccType;
    ...

Prerequisites

You must have the Hungarian 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, kbmbscodefix, kbnoloc, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 2806365
Revision : 1
Created on : 1/7/2017
Published on : 3/7/2013
Exists online : False
Views : 146