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 "Document No. field" in the merged line is blank when you merge SEPA payments and the Export SEPA Payment File report (13403) does not display amounts in two decimals in the Finnish version of Microsoft Dynamics NAV

The "Document No. field" in the merged line is blank when you merge SEPA payments and the Export SEPA Payment File report (13403) does not display amounts in two decimals in the Finnish version of Microsoft Dynamics NAV

View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the Finnish (fi) language locale.

↑ Back to the top

Symptoms

You experience following symptoms in the Finnish version of Microsoft Dynamics NAV:
  • When you merge some SEPA payments that are created for a vendor, the Document No. field in the merged line is blank. However, the Document No. value in the combined line should be the Document No. value of the first SEPA payment line for the vendor.
  • The Export SEPA Payment File report (13403) does not display amounts in two decimals as expected.

This problem occurs in the following products:
  • The Finnish version of Microsoft Dynamics NAV 2009 R2
  • The Finnish version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
  • The Finnish version of Microsoft Dynamics NAV 5.0 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 ExportGroupHeader function in the Export SEPA Payment File report (13403) as follows:
    Existing code
    ...
    RefPaymentExported.SETRANGE("Applied Payments",FALSE);
    IF RefPaymentExported.FINDFIRST THEN
    AddElement(XMLNodeCurr,'NbOfTxs',FORMAT(RefPaymentExported.COUNT),'',XMLNewChild);

    // Delete the following line.
    AddElement(XMLNodeCurr,'CtrlSum',FORMAT(ControlSum,0,9),'',XMLNewChild);

    AddElement(XMLNodeCurr,'Grpg','MIXD','',XMLNewChild);
    AddElement(XMLNodeCurr,'InitgPty','','',XMLNewChild);
    XMLNodeCurr := XMLNewChild;
    ...
    Replacement code
    ...
    RefPaymentExported.SETRANGE("Applied Payments",FALSE);
    IF RefPaymentExported.FINDFIRST THEN
    AddElement(XMLNodeCurr,'NbOfTxs',FORMAT(RefPaymentExported.COUNT),'',XMLNewChild);

    // Add the following line.
    AddElement(XMLNodeCurr,'CtrlSum',FORMAT(ControlSum,0,'<Precision,2:2><Standard Format,9>'),'',XMLNewChild);

    AddElement(XMLNodeCurr,'Grpg','MIXD','',XMLNewChild);
    AddElement(XMLNodeCurr,'InitgPty','','',XMLNewChild);
    XMLNodeCurr := XMLNewChild;
    ...
  2. Change the code in the ExportPaymentInformation function in the Export SEPA Payment File report (13403) as follows:
    Existing code
    ...
    AddElement(XMLNodeCurr,'Amt','','',XMLNewChild);
    XMLNodeCurr := XMLNewChild;

    // Delete the following line.
    AddElement(XMLNodeCurr,'InstdAmt',FORMAT(RefPaymentExported.Amount,0,9),'',XMLNewChild);

    AddAttribute(XMLDomDoc,XMLNewChild,'Ccy',GetCurrencyCode(RefPaymentExported."Currency Code"));
    XMLNodeCurr := XMLNodeCurr.parentNode;
    ...
    Replacement code
    ...
    AddElement(XMLNodeCurr,'Amt','','',XMLNewChild);
    XMLNodeCurr := XMLNewChild;

    // Add the following line.
    AddElement(XMLNodeCurr,'InstdAmt',FORMAT(RefPaymentExported.Amount,0,'<Precision,2:2><Standard Format,9>'),'',XMLNewChild);

    AddAttribute(XMLDomDoc,XMLNewChild,'Ccy',GetCurrencyCode(RefPaymentExported."Currency Code"));
    XMLNodeCurr := XMLNodeCurr.parentNode;
    ...
  3. Change the code in the CombineVendPmt function in the CombineVendPmt codeunit (32000000) as follows:
    Existing code
    ...
    REPEAT
    RefPmtExport.INIT;
    RefPmtExport.TRANSFERFIELDS(TempRefPmtBuffer);
    RefPmtExport."No." := LastLineNo;
    Vendor.GET(RefPmtExport."Vendor No.");
    RefPmtExport.Description := COPYSTR(Vendor.Name,1,MAXSTRLEN(RefPmtExport.Description));
    ...
    Replacement code
    ...
    REPEAT
    RefPmtExport.INIT;
    RefPmtExport.TRANSFERFIELDS(TempRefPmtBuffer);

    // Add the following lines.
    IF (PaymentType = PaymentType::SEPA) AND (RefPmtExport1.GET(TempRefPmtBuffer."Affiliated to Line")) THEN
    RefPmtExport."Document No." := RefPmtExport1."Document No.";
    // End of the lines.

    RefPmtExport."No." := LastLineNo;
    Vendor.GET(RefPmtExport."Vendor No.");
    RefPmtExport.Description := COPYSTR(Vendor.Name,1,MAXSTRLEN(RefPmtExport.Description));
    ...

Prerequisites

You must have one of the following products installed to apply this hotfix:
  • The Finnish version of Microsoft Dynamics NAV 2009 R2
  • The Finnish version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
  • The Finnish version of Microsoft Dynamics NAV 5.0 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: kb, kbqfe, kbmbsquickpub, kbmbspartner, kbmbsmigrate, kbsurveynew, kbnoloc, kbmbscodefix

↑ Back to the top

Article Info
Article ID : 2564288
Revision : 4
Created on : 9/26/2018
Published on : 9/26/2018
Exists online : False
Views : 212