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. SEPA Credit Transfer and Electronic Payments do not work well together in Spanish version of Microsoft Dynamics NAV 2009

SEPA Credit Transfer and Electronic Payments do not work well together in Spanish version of Microsoft Dynamics NAV 2009

View products that this article applies to.

Symptoms

Electronic Payments: Old functionality in the ES database. It helped to export the Payment Orders (N34.1) in txt format.
SEPA CT: New functionality to export Payment Orders in XML Format (N34.14)
Both should work in the current database, but this is not the case.
After you implement the SEPA CT objects, if you try to export a payment order in SEPA format, even although you did not set the Electronic Payments as TRUE in the vendor bank or the payment order header, the payment order header gets Elect. Pmts Exported set to YES. This issue causes that you cannot change the payment order. Follow the steps in the code changes section to solve this issue. This problem occurs in the following products:
  • The Spanish version of Microsoft Dynamics NAV 2009 R2
  • The Spanish version of Microsoft Dynamics NAV 2009 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 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. However, 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 Dynamics NAV client users are logged off the system. This includes Microsoft Dynamics NAV Application Server (NAS) services. 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 Properties in the Dept - Country menusuite (1030) as follows:
    Existing code
    ...   
    Visible=Yes;
                                                                    NextNodeID=[{7790AED6-E794-4997-8E9F-4F312BACB177}];
                                                                    DepartmentCategory=Reports and Analysis }

    // Delete the following lines.
    { MenuItem       ;[{7790AED6-E794-4997-8E9F-4F312BACB177}] ;Name=Void PO - Export N34.1;
    CaptionML=ENU=Void PO - Export N34.1;
    // End of the deleted lines.
                                                               
    MemberOfMenu=[{99D76781-B94A-4B67-8FDD-B40C43BAC2BC}];
                                                                    RunObjectType=Report;
                                                                    RunObjectID=7000061;
    ...
    Replacement code
    ...   
    Visible=Yes;
                                                                    NextNodeID=[{7790AED6-E794-4997-8E9F-4F312BACB177}];
                                                                    DepartmentCategory=Reports and Analysis }

    // Add the following lines.
    { MenuItem       ;[{7790AED6-E794-4997-8E9F-4F312BACB177}] ;Name=Void PO - Export;
    CaptionML=ENU=Void PO - Export;
    // End of the added lines.
                                                              
    MemberOfMenu=[{99D76781-B94A-4B67-8FDD-B40C43BAC2BC}];
                                                                    RunObjectType=Report;
                                                                    RunObjectID=7000061;
    ...
  2. Delete an object and add an object as follows:
    Existing code
    ...
    // Delete the following line.
    OBJECT Report 7000061 Void PO - Export N34.1
    // End of the deleted line.
    ...
    Replacement code
    ...
    // Add the following line.
    OBJECT Report 7000061 Void PO - Export
    // End of the added line.
    ...
  3. Change the code in Properties in the Dept - Country report (7000061) as follows:
    Existing code
    ...
    }
      PROPERTIES
      {
       CaptionML=ENU=Void PO - Export N34.1;
        ProcessingOnly=Yes;
        OnPreReport=BEGIN
                      "Payment Order".GET("Payment Order"."No.");
    ...
    Replacement code
    ...
     }
      PROPERTIES
      {

    // Delete the following line.
    CaptionML=ENU=Void PO - Export N34.1;
    // End of the deleted line.

        ProcessingOnly=Yes;
        OnPreReport=BEGIN
                      "Payment Order".GET("Payment Order"."No.");
    ...
  4. Change the code in Fields in the Payment Order table (7000020) as follows:
    Existing code
    ...
     Type=CONST(Payable)));
                                                       Editable=No;
                                                       AutoFormatType=1 }

    // Delete the following line.
    { 35  ;   ;Elect. Pmts Exported;Boolean        }
    // End of the deleted line.

        { 36  ;   ;Export Electronic Payment;Boolean  ;OnValidate=BEGIN
                                                                    TESTFIELD("Elect. Pmts Exported",FALSE);
                                                                  END;
    ...
    Replacement code
    ...
                                                                                                                    Type=CONST(Payable)));
                                                       Editable=No;
                                                       AutoFormatType=1 }

    // Add the following lines.
    { 35  ;   ;Elect. Pmts Exported;Boolean       ;OnValidate=VAR
    CarteraDoc@1100000 : Record 7000002;
    BEGIN
    CarteraDoc.SETRANGE(Type,CarteraDoc.Type::Payable);
    CarteraDoc.SETRANGE("Bill Gr./Pmt. Order No.","No.");
    CarteraDoc.MODIFYALL("Elect. Pmts Exported",TRUE);
    END;
    }
    // End of the added lines.

    { 36  ;   ;Export Electronic Payment;Boolean  ;OnValidate=BEGIN
                                                                    TESTFIELD("Elect. Pmts Exported",FALSE);
                                                                  END;
    ...
  5. Change the code in ExportToFile function in the Payment Order table (7000020) as follows:
    Existing code 1
    ...
    GenJnlLine@1100000 : Record 81;
          BankAccount@1100001 : Record 270;
        BEGIN
          IF "Elect. Pmts Exported" THEN
            IF NOT CONFIRM(ExportAgainQst) THEN
              EXIT;
    ...
    Replacement code 1
    ...
    GenJnlLine@1100000 : Record 81;
          BankAccount@1100001 : Record 270;
        BEGIN

    // Add the following lines.
    SETRECFILTER;
    TESTFIELD("Export Electronic Payment",TRUE);

    // End of the added lines.

    IF "Elect. Pmts Exported" THEN
            IF NOT CONFIRM(ExportAgainQst) THEN
              EXIT;
    ...
    Existing code 2
    ...
    GenJnlLine."Bal. Account No." := BankAccount."No.";
          CODEUNIT.RUN(CODEUNIT::"SEPA CT-Export File",GenJnlLine);
          FIND;

    // Delete the following line.
    "Elect. Pmts Exported" := TRUE;
    // End of the deleted line.

          MODIFY;
        END;
    ...
    Replacement code 2
    ...
     GenJnlLine."Bal. Account No." := BankAccount."No.";
          CODEUNIT.RUN(CODEUNIT::"SEPA CT-Export File",GenJnlLine);
          FIND;

    // Add the following line.
    VALIDATE("Elect. Pmts Exported",TRUE);
    // End of the added line.

          MODIFY;
        END;
    ...

Prerequisites

You must have one of the following products installed to apply this hotfix:
  • The Spanish version of Microsoft Dynamics NAV 2009 R2
  • The Spanish version of Microsoft Dynamics NAV 2009 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.
See the article SEPA Credit Transfer release for NAV2009Sp1/R2 ES for more information.

↑ 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 Usefor other considerations.

↑ Back to the top

Keywords: kbqfe, kbmbspartner, kbmbsquickpub, kbmbsmigrate, kbsurveynew, kbnoloc, kbmbscodefix, kb

↑ Back to the top

Article Info
Article ID : 3036825
Revision : 1
Created on : 1/7/2017
Published on : 2/11/2015
Exists online : False
Views : 210