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 Fill Liquidity Journal report (5055250) displays incorrect values when an order that has the prepayment enabled is involved in the German version of Microsoft Dynamics NAV 2009

The Fill Liquidity Journal report (5055250) displays incorrect values when an order that has the prepayment enabled is involved 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

Assume that you use sales and purchase documents in the German version of Microsoft Dynamics NAV 2009. You have an order that has more than one line and the prepayment enabled. In this situation, when you run the Fill Liquidity Journal report (5055250) that has the order involved, incorrect values are displayed.
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. Add a new local variable in the Sales Line - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250), specify the variable as follows:
    • Name: CurrencyLCY
    • DataType: Record
    • Subtype: Currency (4)
  2. Add a new local variable in the Sales Line - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250), specify the variable as follows:
    • Name: PrevDocNo
    • DataType: Code
    • Length: 20
  3. Add a new local variable in the Sales Line - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250), specify the variable as follows:
    • Name: AmountLCY
    • DataType: Decimal
  4. Add a new local variable in the Sales Line - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250), specify the variable as follows:
    • Name: RemainderAmountLCY
    • DataType: Decimal
  5. Add a new local variable in the Sales Line - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250), specify the variable as follows:
    • Name: PrepmtAmtInclVAT
    • DataType: Decimal
  6. Change the code in the Sales Line - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250) as follows:
    Existing code 1
    ...
    PurchHeader.GET("Purchase Line"."Document Type","Purchase Line"."Document No.");
    WITH LiqLine2 DO BEGIN
    ...
    Replacement code 1
    ...
    PurchHeader.GET("Purchase Line"."Document Type","Purchase Line"."Document No.");

    // Add the following lines.
    IF (PurchHeader."Currency Code" <> '') AND (PrevDocNo <> PurchHeader."No.") THEN BEGIN
    RemainderAmountLCY := 0;
    PurchHeader.TESTFIELD("Currency Factor");
    CurrencyLCY.InitRoundingPrecision;
    PrevDocNo := PurchHeader."No.";
    END;
    // End of lines.

    WITH LiqLine2 DO BEGIN
    ...
    Existing code 2
    ...
    // Delete the following lines.
    IF "Purchase Line"."Prepmt. Amt. Inv." <> 0 THEN BEGIN
    PurchInvHeader.RESET;
    PurchInvHeader.SETCURRENTKEY("Prepayment Order No.");
    PurchInvHeader.SETRANGE("Prepayment Order No.","Purchase Line"."Document No.");
    IF PurchInvHeader.FIND('-') THEN REPEAT
    VendorLedgerEntry.RESET;
    VendorLedgerEntry.SETCURRENTKEY("Document No.");
    VendorLedgerEntry.SETRANGE("Document No.",PurchInvHeader."No.");
    VendorLedgerEntry.SETRANGE("Posting Date",PurchInvHeader."Posting Date");
    IF VendorLedgerEntry.FIND('-') THEN REPEAT
    VendorLedgerEntry.CALCFIELDS("Remaining Amt. (LCY)","Remaining Amount");
    "Amount (Currency)" := "Amount (Currency)" - VendorLedgerEntry."Remaining Amount";
    Amount := Amount - VendorLedgerEntry."Remaining Amt. (LCY)";
    UNTIL VendorLedgerEntry.NEXT = 0;
    UNTIL PurchInvHeader.NEXT = 0;
    END;
    // End of the lines.
    ...
    Replacement code 2
    ...
    // Add the following lines.
    PrepmtAmtInclVAT := ROUND("Purchase Line"."Prepmt. Amt. Inv." * (1 + ("Purchase Line"."Prepayment VAT %" / 100)),
    CurrencyLCY."Amount Rounding Precision");
    IF PrepmtAmtInclVAT <> 0 THEN BEGIN
    "Amount (Currency)" := "Amount (Currency)" - PrepmtAmtInclVAT;
    IF PurchHeader."Currency Code" = '' THEN
    Amount := Amount - PrepmtAmtInclVAT
    ELSE BEGIN
    AmountLCY := RemainderAmountLCY + PrepmtAmtInclVAT / PurchHeader."Currency Factor";
    RemainderAmountLCY := AmountLCY - ROUND(AmountLCY,CurrencyLCY."Amount Rounding Precision");
    Amount := Amount - ROUND(AmountLCY,CurrencyLCY."Amount Rounding Precision");
    END;
    END;
    // End of the lines.
    ...
  7. Add a new local variable in the PurchaseLine - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250), specify the variable as follows:
    • Name: CurrencyLCY
    • DataType: Record
    • Subtype: Currency (4)
  8. Add a new local variable in the PurchaseLine - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250), specify the variable as follows:
    • Name: PrevDocNo
    • DataType: Code
    • Length: 20
  9. Add a new local variable in the PurchaseLine - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250), specify the variable as follows:
    • Name: AmountLCY
    • DataType: Decimal
  10. Add a new local variable in the PurchaseLine - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250), specify the variable as follows:
    • Name: RemainderAmountLCY
    • DataType: Decimal
  11. Add a new local variable in the PurchaseLine - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250), specify the variable as follows:
    • Name: PrepmtAmtInclVAT
    • DataType: Decimal
  12. Change the code in the PurchaseLine - OnAfterGetRecord trigger in the Fill Liquidity Journal report (5055250) as follows:
    Existing code 1
    ...
    PurchHeader.GET("Purchase Line"."Document Type","Purchase Line"."Document No.");
    WITH LiqLine2 DO BEGIN
    ...
    Replacement code 1
    ...
    PurchHeader.GET("Purchase Line"."Document Type","Purchase Line"."Document No.");

    // Add the following lines.
    IF (PurchHeader."Currency Code" <> '') AND (PrevDocNo <> PurchHeader."No.") THEN BEGIN
    RemainderAmountLCY := 0;
    PurchHeader.TESTFIELD("Currency Factor");
    CurrencyLCY.InitRoundingPrecision;
    PrevDocNo := PurchHeader."No.";
    END;
    // End of the lines.

    WITH LiqLine2 DO BEGIN
    ...
    Existing code 2
    ...
    // Delete the following lines.
    IF "Purchase Line"."Prepmt. Amt. Inv." <> 0 THEN BEGIN
    PurchInvHeader.RESET;
    PurchInvHeader.SETCURRENTKEY("Prepayment Order No.");
    PurchInvHeader.SETRANGE("Prepayment Order No.","Purchase Line"."Document No.");
    IF PurchInvHeader.FIND('-') THEN REPEAT
    VendorLedgerEntry.RESET;
    VendorLedgerEntry.SETCURRENTKEY("Document No.");
    VendorLedgerEntry.SETRANGE("Document No.",PurchInvHeader."No.");
    VendorLedgerEntry.SETRANGE("Posting Date",PurchInvHeader."Posting Date");
    IF VendorLedgerEntry.FIND('-') THEN REPEAT
    VendorLedgerEntry.CALCFIELDS("Remaining Amt. (LCY)","Remaining Amount");
    "Amount (Currency)" := "Amount (Currency)" - VendorLedgerEntry."Remaining Amount";
    Amount := Amount - VendorLedgerEntry."Remaining Amt. (LCY)";
    UNTIL VendorLedgerEntry.NEXT = 0;
    UNTIL PurchInvHeader.NEXT = 0;
    END;
    // End of the lines.
    ...
    Replacement code 2
    ...
    // Add the following lines.
    PrepmtAmtInclVAT := ROUND("Purchase Line"."Prepmt. Amt. Inv." * (1 + ("Purchase Line"."Prepayment VAT %" / 100)),
    CurrencyLCY."Amount Rounding Precision");
    IF PrepmtAmtInclVAT <> 0 THEN BEGIN
    "Amount (Currency)" := "Amount (Currency)" + PrepmtAmtInclVAT;
    IF PurchHeader."Currency Code" = '' THEN
    Amount := Amount + PrepmtAmtInclVAT
    ELSE BEGIN
    AmountLCY := RemainderAmountLCY + PrepmtAmtInclVAT / PurchHeader."Currency Factor";
    RemainderAmountLCY := AmountLCY - ROUND(AmountLCY,CurrencyLCY."Amount Rounding Precision");
    Amount := Amount + ROUND(AmountLCY,CurrencyLCY."Amount Rounding Precision");
    END;
    END;
    // End of the lines.
    ...

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

↑ Back to the top

Article Info
Article ID : 2664491
Revision : 1
Created on : 1/7/2017
Published on : 1/31/2012
Exists online : False
Views : 165