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. An incorrect liquidity date is suggested when you run the Fill function on a liquidity journal for an invoice that has no discount included in the German version of Microsoft Dynamics NAV 2009

An incorrect liquidity date is suggested when you run the Fill function on a liquidity journal for an invoice that has no discount included in the German version of Microsoft Dynamics NAV 2009

View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the German (de) language locale.

↑ Back to the top

Symptoms

Consider the following scenario in the German version of Microsoft Dynamics NAV:
  • You enable the Consider Discount setting in a liquidity card.
  • ou run the Fill function on a liquidity journal for an invoice that has no discount included.
In this scenario, an incorrect liquidity date is suggested in the liquidity journal. The liquidity date is equal to the posting date of the invoice instead of the due date of the invoice.
This problem occurs in the following products:
  • The German version of Microsoft Dynamics NAV 2009 R2
  • The German version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)

↑ 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 Cust. Ledger Entry - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250) as follows:
    Existing code
    ...
          "Payment Discount" := "Cust. Ledger Entry"."Original Pmt. Disc. Possible";
        Amount := "Cust. Ledger Entry"."Remaining Amt. (LCY)" - "Payment Discount";
        "Amount (Currency)" := "Cust. Ledger Entry"."Remaining Amount" - "Cust. Ledger Entry"."Original Pmt. Disc. Possible";

        // Delete the following line.
        IF "Cust. Ledger Entry"."Pmt. Discount Date" <> 0D THEN BEGIN

          "Liquidity Date" := "Cust. Ledger Entry"."Pmt. Discount Date";
        IF Liquidity."Consider Pmt. Disc. Tol. Date" THEN
          "Liquidity Date" := "Cust. Ledger Entry"."Pmt. Disc. Tolerance Date";
        END;
    ...
    Replacement code
    ...
          "Payment Discount" := "Cust. Ledger Entry"."Original Pmt. Disc. Possible";
        Amount := "Cust. Ledger Entry"."Remaining Amt. (LCY)" - "Payment Discount";
        "Amount (Currency)" := "Cust. Ledger Entry"."Remaining Amount" - "Cust. Ledger Entry"."Original Pmt. Disc. Possible";

        // Add the following line.
        IF ("Cust. Ledger Entry"."Pmt. Discount Date" <> 0D) AND ("Payment Discount" <> 0) THEN BEGIN

          "Liquidity Date" := "Cust. Ledger Entry"."Pmt. Discount Date";
        IF Liquidity."Consider Pmt. Disc. Tol. Date" THEN
          "Liquidity Date" := "Cust. Ledger Entry"."Pmt. Disc. Tolerance Date";
        END;
    ...
  2. Change the code in the Vendor Ledger Entry - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250) as follows:
    Existing code
    ...
          "Payment Discount" := "Vendor Ledger Entry"."Original Pmt. Disc. Possible";
        Amount := "Vendor Ledger Entry"."Remaining Amt. (LCY)" - "Payment Discount";
        "Amount (Currency)" := "Vendor Ledger Entry"."Remaining Amount" - "Vendor Ledger Entry"."Original Pmt. Disc. Possible";

        // Delete the following line.
        IF "Vendor Ledger Entry"."Pmt. Discount Date" <> 0D THEN BEGIN

          "Liquidity Date" := "Vendor Ledger Entry"."Pmt. Discount Date";
        IF Liquidity."Consider Pmt. Disc. Tol. Date" THEN
          "Liquidity Date" := "Vendor Ledger Entry"."Pmt. Disc. Tolerance Date";
        END;
    ...
    Replacement code
    ...
          "Payment Discount" := "Vendor Ledger Entry"."Original Pmt. Disc. Possible";
        Amount := "Vendor Ledger Entry"."Remaining Amt. (LCY)" - "Payment Discount";
        "Amount (Currency)" := "Vendor Ledger Entry"."Remaining Amount" - "Vendor Ledger Entry"."Original Pmt. Disc. Possible";

        // Add the following line.
        IF ("Vendor Ledger Entry"."Pmt. Discount Date" <> 0D) AND ("Payment Discount" <> 0) THEN BEGIN

          "Liquidity Date" := "Vendor Ledger Entry"."Pmt. Discount Date";
        IF Liquidity."Consider Pmt. Disc. Tol. Date" THEN
          "Liquidity Date" := "Vendor Ledger Entry"."Pmt. Disc. Tolerance Date";
        END;
    ...
  3. Change the code in the Purchase Line - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250) as follows:
    Existing code
    ...
      "Due Date" := PurchHeader."Due Date";
      "Document No." := "Purchase Line"."Document No.";

      // Delete the following lines.
      IF (PurchHeader."Pmt. Discount Date" <> 0D) AND (Liquidity."Consider Discount") THEN BEGIN
        "Liquidity Date" := PurchHeader."Pmt. Discount Date";
      // End of the lines.

        IF Liquidity."Consider Pmt. Disc. Tol. Date" THEN
          "Liquidity Date" := CALCDATE(GLSetup."Payment Discount Grace Period","Liquidity Date");
      END ELSE
        "Liquidity Date" := PurchHeader."Due Date";
    ...
    Replacement code
    ...
      "Due Date" := PurchHeader."Due Date";
      "Document No." := "Purchase Line"."Document No.";

      // Add the following lines.
      IF (PurchHeader."Pmt. Discount Date" <> 0D) AND
        (Liquidity."Consider Discount") AND
        (PurchHeader."Payment Discount %" <> 0)
      THEN BEGIN
        "Liquidity Date" := PurchHeader."Pmt. Discount Date";
      // End of the lines.

        IF Liquidity."Consider Pmt. Disc. Tol. Date" THEN
          "Liquidity Date" := CALCDATE(GLSetup."Payment Discount Grace Period","Liquidity Date");
      END ELSE
        "Liquidity Date" := PurchHeader."Due Date";
    ...
  4. Change the code in the Sales Line - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250) as follows:
    Existing code
    ...
      "Due Date" := SalesHeader."Due Date";
      "Document No." := "Sales Line"."Document No.";

      // Delete the following lines.
      IF (SalesHeader."Pmt. Discount Date" <> 0D) AND (Liquidity."Consider Discount") THEN BEGIN
        "Liquidity Date" := SalesHeader."Pmt. Discount Date";
      // End of the lines.

        IF Liquidity."Consider Pmt. Disc. Tol. Date" THEN
          "Liquidity Date" := CALCDATE(GLSetup."Payment Discount Grace Period","Liquidity Date");
      END ELSE
        "Liquidity Date" := SalesHeader."Due Date";
    ...
    Replacement code
    ...
      "Due Date" := SalesHeader."Due Date";
      "Document No." := "Sales Line"."Document No.";

      // Add the following lines.
      IF (SalesHeader."Pmt. Discount Date" <> 0D) AND
        (Liquidity."Consider Discount") AND
        (SalesHeader."Payment Discount %" <> 0)
      THEN BEGIN
        "Liquidity Date" := SalesHeader."Pmt. Discount Date";
      // End of the lines.

        IF Liquidity."Consider Pmt. Disc. Tol. Date" THEN
          "Liquidity Date" := CALCDATE(GLSetup."Payment Discount Grace Period","Liquidity Date");
      END ELSE
        "Liquidity Date" := SalesHeader."Due Date";
    ...
  5. Change the code in the Service Line - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250) as follows:
    Existing code
    ...
        Customer.GET(ServiceHeader."Bill-to Customer No.");
        IF Customer."Payment Terms Code" <> '' THEN BEGIN
          PaymentTerms.GET(Customer."Payment Terms Code");

          // Delete the following line.
          IF Liquidity."Consider Discount" THEN BEGIN

            "Liquidity Date" := CALCDATE(PaymentTerms."Discount Date Calculation",ServiceHeader."Document Date");
            IF Liquidity."Consider Pmt. Disc. Tol. Date" THEN
              "Liquidity Date" := CALCDATE(GLSetup."Payment Discount Grace Period","Liquidity Date");
          END ELSE
    ...
    Replacement code
    ...
        Customer.GET(ServiceHeader."Bill-to Customer No.");
        IF Customer."Payment Terms Code" <> '' THEN BEGIN
          PaymentTerms.GET(Customer."Payment Terms Code");

          // Add the following line.
          IF Liquidity."Consider Discount" AND (ServiceHeader."Payment Discount %" <> 0) THEN BEGIN

            "Liquidity Date" := CALCDATE(PaymentTerms."Discount Date Calculation",ServiceHeader."Document Date");
            IF Liquidity."Consider Pmt. Disc. Tol. Date" THEN
              "Liquidity Date" := CALCDATE(GLSetup."Payment Discount Grace Period","Liquidity Date");
          END ELSE
    ...

Prerequisites

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

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

↑ Back to the top

Article Info
Article ID : 2499998
Revision : 2
Created on : 9/25/2018
Published on : 9/25/2018
Exists online : False
Views : 229