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 calculation for the "Total Remittee (LCY)" field does not work as expected when you filter to an SEPA type export protocol for payment journals in the Belgian version of Microsoft Dynamics NAV 2009 with the SEPA updates installed

The calculation for the "Total Remittee (LCY)" field does not work as expected when you filter to an SEPA type export protocol for payment journals in the Belgian version of Microsoft Dynamics NAV 2009 with the SEPA updates installed

View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the Belgian (be) language locale.

↑ Back to the top

Symptoms

Consider the following scenario in the classic client in the Belgian version of Microsoft Dynamics NAV 2009:
  • You install the Support for ISABEL6 and SEPA Credit Transfer feature.
  • You install the Support for SEPA and Non-EURO SEPA feature.
  • You have several payment journals that use different export protocols.
  • You filter to an SEPA type export protocol for the payment journals.
In this scenario, the Total Remittee (LCY) field is not displayed. Additionally, the Total Remittee (LCY) field is populated with an incorrect amount in the RoleTailored client (RTC). This problem occurs in the following products:
  • The Belgian version of Microsoft Dynamics NAV 2009 R2 with the SEPA updates installed
  • The Belgian version of Microsoft Dynamics NAV 2009 Service Pack 1 with the SEPA updates installed
For more information about the Support for ISABEL6 and SEPA Credit Transfer feature, go to the following Microsoft website:
Microsoft Dynamics NAV 6.0 SP1 Support for ISABEL6 and SEPA Credit Transfer - Belgium
For more information about the Support for SEPA and Non-EURO SEPA feature, go to the following Microsoft website:
Belgium SEPA and Non-EURO SEPA Summarized Payments

↑ 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 Keys section in the Payment Journal Line table (2000001) as follows:
    Existing code
    ...
    Clustered=Yes }
    { ;Account Type,Account No.,Currency Code,Applies-to ID,Separate Line,Applies-to Doc. Type,Applies-to Doc. No.;
    SumIndexFields=Amount,Amount (LCY) }
    { ;ISO Currency Code ;SumIndexFields=Amount,Amount (LCY) }
    { ;Bank Account,Beneficiary Bank Account No.,Status,Account Type,Account No.,Currency Code,Posting Date,Instruction Priority,Code Expenses }

    // Delete the following line.
    { ;Journal Template Name,Journal Batch Name,Account Type,Account No.;

    SumIndexFields=Amount,Amount (LCY);
    MaintainSQLIndex=No;
    MaintainSIFTIndex=No }
    }
    FIELDGROUPS
    ...
    Replacement code
    ...
    Clustered=Yes }
    { ;Account Type,Account No.,Currency Code,Applies-to ID,Separate Line,Applies-to Doc. Type,Applies-to Doc. No.;
    SumIndexFields=Amount,Amount (LCY) }
    { ;ISO Currency Code ;SumIndexFields=Amount,Amount (LCY) }
    { ;Bank Account,Beneficiary Bank Account No.,Status,Account Type,Account No.,Currency Code,Posting Date,Instruction Priority,Code Expenses }

    // Add the following line.
    { ;Journal Template Name,Journal Batch Name,Account Type,Account No.,Export Protocol Code,Bank Account;

    SumIndexFields=Amount,Amount (LCY);
    MaintainSQLIndex=No;
    MaintainSIFTIndex=No }
    }
    FIELDGROUPS
    ...
  2. Change the code in the CalculateTotals function in the PmtJnrlManagement codeunit (2000000) codeunit as follows:
    Existing code 1
    ...
    PROCEDURE CalculateTotals@1010013(VAR PaymentJnlLine@1000 : Record 2000001;LastPaymentJnlLine@1001 : Record 2000001;VAR Balance@1002 : Decimal;VAR TotalAmount@1003 : Decimal;VAR ShowAmount@1004 : Boolean;VAR ShowTotalAmount@1005 : Boolean);
    VAR
    TempPaymJnlLine@1011006 : Record 2000001;
    BEGIN
    TempPaymJnlLine.COPYFILTERS(PaymentJnlLine);
    IF TempPaymJnlLine.CALCSUMS("Amount (LCY)") THEN BEGIN
    IF PaymentJnlLine."Line No." <> 0 THEN // 0 = new record
    TotalAmount := TempPaymJnlLine."Amount (LCY)"
    ELSE BEGIN
    TotalAmount := TempPaymJnlLine."Amount (LCY)" + LastPaymentJnlLine."Amount (LCY)";
    ...
    Replacement code 1
    ...
    PROCEDURE CalculateTotals@1010013(VAR PaymentJnlLine@1000 : Record 2000001;LastPaymentJnlLine@1001 : Record 2000001;VAR Balance@1002 : Decimal;VAR TotalAmount@1003 : Decimal;VAR ShowAmount@1004 : Boolean;VAR ShowTotalAmount@1005 : Boolean);
    VAR
    TempPaymJnlLine@1011006 : Record 2000001;
    BEGIN
    TempPaymJnlLine.COPYFILTERS(PaymentJnlLine);

    // Add the following lines.
    TempPaymJnlLine.SETCURRENTKEY(
    "Journal Template Name","Journal Batch Name","Account Type","Account No.","Export Protocol Code","Bank Account");
    // End of the lines.

    IF TempPaymJnlLine.CALCSUMS("Amount (LCY)") THEN BEGIN
    IF PaymentJnlLine."Line No." <> 0 THEN // 0 = new record
    TotalAmount := TempPaymJnlLine."Amount (LCY)"
    ELSE BEGIN
    TotalAmount := TempPaymJnlLine."Amount (LCY)" + LastPaymentJnlLine."Amount (LCY)";
    ...
    Existing code 2
    ...
    ShowTotalAmount := FALSE;
    END;
    IF PaymentJnlLine."Line No." <> 0 THEN BEGIN // 0 = New record
    IF PaymentJnlLine."Account No." <> '' THEN BEGIN

    // Delete the following line.
    TempPaymJnlLine.SETCURRENTKEY("Account Type","Account No.");

    TempPaymJnlLine.SETRANGE("Account Type",PaymentJnlLine."Account Type");
    TempPaymJnlLine.SETRANGE("Account No.",PaymentJnlLine."Account No.");
    IF TempPaymJnlLine.CALCSUMS("Amount (LCY)") THEN BEGIN
    Balance := TempPaymJnlLine."Amount (LCY)";
    ShowAmount := TRUE;
    ...
    Replacement code 2
    ...
    ShowTotalAmount := FALSE;
    END;
    IF PaymentJnlLine."Line No." <> 0 THEN BEGIN // 0 = New record
    IF PaymentJnlLine."Account No." <> '' THEN BEGIN
    TempPaymJnlLine.SETRANGE("Account Type",PaymentJnlLine."Account Type");
    TempPaymJnlLine.SETRANGE("Account No.",PaymentJnlLine."Account No.");
    IF TempPaymJnlLine.CALCSUMS("Amount (LCY)") THEN BEGIN
    Balance := TempPaymJnlLine."Amount (LCY)";
    ShowAmount := TRUE;
    ...

Prerequisites

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

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, kbmbsquickpub, kbfix, kbmbspartner, kb, kbqfe, kbmbsmigrate

↑ Back to the top

Article Info
Article ID : 2751367
Revision : 1
Created on : 1/7/2017
Published on : 1/17/2013
Exists online : False
Views : 229