Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Symptoms

The Electronic Payments functionality provides the possibility to you to export electronic payments from Journal and from Cartera (Payment Orders) in the Spanish version of Microsoft Dynamics NAV 2009. Only the exportation from Cartera through a payment order is possible by using SEPA (XML). You should have the possibility to export SEPA from Journal for Credit Transfer (CT) also. 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

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.

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 Controls in the Payment Journal form (256) as follows:
    Existing code 1

    ...     
    OnValidate=BEGIN
    GenJnlManagement.GetAccounts(Rec,AccName,BalAccName);
    ShowShortcutDimCode(ShortcutDimCode);
    END;
    }
    { 11 ;Label ;0 ;0 ;0 ;0 ;ParentControl=10;
    ...

    Replacement code 1

    ...         
    OnValidate=BEGIN
    GenJnlManagement.GetAccounts(Rec,AccName,BalAccName);
    ShowShortcutDimCode(ShortcutDimCode);

    // Add the following line.
    CheckRecipientBankAccount;
    // End of the added line.

    END;
    }
    { 11 ;Label ;0 ;0 ;0 ;0 ;ParentControl=10;
    ...

    Existing code 2

    ...
    SourceExpr="Reason Code" }
    { 70 ;Label ;0 ;0 ;0 ;0 ;ParentControl=69;
    InColumnHeading=Yes }
    { 24 ;Frame ;220 ;6160 ;16060;1430 ;HorzGlue=Both;
    VertGlue=Bottom;
    ShowCaption=No }
    ...

    Replacement code 2

    ...
    SourceExpr="Reason Code" }
    { 70 ;Label ;0 ;0 ;0 ;0 ;ParentControl=69;
    InColumnHeading=Yes }

    // Add the following lines.
    { 1100012;TextBox ;71517;1100 ;1700 ;440 ;ParentControl=1;
    InColumn=Yes;
    SourceExpr="Recipient Bank Account" }
    { 1100013;Label ;0 ;0 ;0 ;0 ;ParentControl=1100012;
    InColumnHeading=Yes }
    // End of the added lines.

    { 24 ;Frame ;220 ;6160 ;16060;1430 ;HorzGlue=Both;
    VertGlue=Bottom;
    ShowCaption=No }
    ...

    Existing code 3

    ...
    CaptionML=ENU=Export;
    OnPush=VAR
    Text1100000@1100000 : TextConst 'ENU=Nothing to export.';
    BEGIN
    // es0006.begin
    GenJnlLine.RESET;
    ...

    Replacement code 3

    ...
    CaptionML=ENU=Export;
    OnPush=VAR
    Text1100000@1100000 : TextConst 'ENU=Nothing to export.';

    // Add the following line.
    Selection@1100004 : Integer;
    // End of the added line.

    BEGIN
    // es0006.begin
    GenJnlLine.RESET;
    ...

    Existing code 4

    ...
    GenJnlLine.SETRANGE("Journal Batch Name","Journal Batch Name");
    IF NOT GenJnlLine.FIND('-') THEN
    ERROR(Text1100000);
    GenJnlLine.TESTFIELD("Elect. Pmts Exported",FALSE);
    REPORT.RUNMODAL(REPORT::"Export Electronic Payments",TRUE,FALSE,GenJnlLine);
    // es0006.end
    END;
    }
    ...

    Replacement code 4

    ...
    GenJnlLine.SETRANGE("Journal Batch Name","Journal Batch Name");
    IF NOT GenJnlLine.FIND('-') THEN
    ERROR(Text1100000);

    // Add the following lines.
    Selection := STRMENU(ExportFormatTypeTxt,2);
    CASE Selection OF
    1:
    BEGIN
    IF ExportedPmtExist(GenJnlLine) THEN
    IF NOT CONFIRM(ExportAgainQst) THEN
    EXIT;
    CODEUNIT.RUN(CODEUNIT::"SEPA CT-Export File",GenJnlLine);
    END;
    2:
    BEGIN
    // End of the added lines.

    GenJnlLine.TESTFIELD("Elect. Pmts Exported",FALSE);
    REPORT.RUNMODAL(REPORT::"Export Electronic Payments",TRUE,FALSE,GenJnlLine);

    // Add the following lines.
    END;
    END;
    // End of the added lines.
    // es0006.end
    END;
    }
    ...

    Existing code 5

    ...
    // es0006.end
    END;
    }
    { ID=65;
    CaptionML=ENU=Void Check;
    OnPush=BEGIN
    ...

    Replacement code 5

    ...
    // es0006.end
    END;
    }

    // Add the following lines.
    { ID=1100014;
    PushAction=RunObject;
    MenuLevel=1;
    CaptionML=ENU=Show Export File Errors;
    RunObject=Form 1228;
    RunFormLink=Journal Template Name=FIELD(Journal Template Name),
    Journal Batch Name=FIELD(Journal Batch Name) }
    // End of the added lines.

    { ID=65;
    CaptionML=ENU=Void Check;
    OnPush=BEGIN
    ...
  2. Change the code in Global Variables in the Payment Journal form (256) as follows:
    Existing code

    ...
    ShowTotalBalance@1017 : Boolean;
    ShortcutDimCode@1018 : ARRAY [8] OF Code[20];
    OpenedFromBatch@1019 : Boolean;

    LOCAL PROCEDURE UpdateBalance@1();
    BEGIN
    ...

    Replacement code

    ...     
    ShowTotalBalance@1017 : Boolean;
    ShortcutDimCode@1018 : ARRAY [8] OF Code[20];
    OpenedFromBatch@1019 : Boolean;

    // Add the following lines.
    ExportFormatTypeTxt@1100001 : TextConst 'ENU=SEPA,N34.1';
    ExportAgainQst@1100000 : TextConst 'ENU=One or more of the selected lines have already been exported. Do you want to export again?';
    // End of the added lines.

    LOCAL PROCEDURE UpdateBalance@1();
    BEGIN
    ...
  3. Change the code in ExportedPmtExist function in the Payment Journal form (256) as follows:
    Existing code

    ...    
    CurrForm.TotalBalance.VISIBLE := ShowTotalBalance;
    END;

    BEGIN
    {
    <changelog>
    ...

    Replacement code

    ...      
    CurrForm.TotalBalance.VISIBLE := ShowTotalBalance;
    END;

    // Add the following lines.
    LOCAL PROCEDURE ExportedPmtExist@1100002(GenJournalLine@1100000 : Record 81) : Boolean;
    VAR
    GenJnlLine3@1100001 : Record 81;
    BEGIN
    GenJnlLine3.COPYFILTERS(GenJnlLine);
    GenJnlLine3.SETRANGE("Exported to Payment File",TRUE);
    EXIT(NOT GenJnlLine3.ISEMPTY);
    END;

    LOCAL PROCEDURE CheckRecipientBankAccount@1100000();
    VAR
    VendorBankAccount@1100000 : Record 288;
    CustomerBankAccount@1100001 : Record 287;
    BEGIN
    IF ("Account No." <> xRec."Account No.") THEN
    VALIDATE("Recipient Bank Account",'');
    END;
    // End of the added lines.

    BEGIN
    {
    <changelog>
    ...
  4. Change the code in Properties in the Payment Journal page (256) as follows:
    Existing code

    ...
    END;
    END;
    }
    { 1900000004;0 ;ActionContainer;
    ActionContainerType=ActionItems }
    { 40 ;1 ;ActionGroup;
    ...

    Replacement code

    ...
    END;
    END;
    }

    // Add the following lines.
    { 1100050 ;2 ;ActionGroup;
    CaptionML=ENU=Electronic Payments }
    { 1100051 ;3 ;Action ;
    CaptionML=ENU=Export;
    OnAction=VAR
    Text1100000@1100000 : TextConst 'ENU=Nothing to export.';
    Selection@1100004 : Integer;
    BEGIN
    // es0006.begin
    GenJnlLine.RESET;
    GenJnlLine := Rec;
    GenJnlLine.SETRANGE("Journal Template Name","Journal Template Name");
    GenJnlLine.SETRANGE("Journal Batch Name","Journal Batch Name");
    IF NOT GenJnlLine.FIND('-') THEN
    ERROR(Text1100000);

    Selection := STRMENU(ExportFormatTypeTxt,2);
    CASE Selection OF
    1:
    BEGIN
    IF ExportedPmtExist(GenJnlLine) THEN
    IF NOT CONFIRM(ExportAgainQst) THEN
    EXIT;
    CODEUNIT.RUN(CODEUNIT::"SEPA CT-Export File",GenJnlLine);
    END;
    2:
    BEGIN
    GenJnlLine.TESTFIELD("Elect. Pmts Exported",FALSE);
    REPORT.RUNMODAL(REPORT::"Export Electronic Payments",TRUE,FALSE,GenJnlLine);
    END;
    END;
    // es0006.end
    END;
    }
    { 1100052 ;3 ;Action ;
    CaptionML=ENU=Void;
    OnAction=VAR
    VoidElecPayments@1101100000 : Report 10722;
    BEGIN
    // es0006.begin
    GenJnlLine.RESET;
    GenJnlLine := Rec;
    GenJnlLine.SETRANGE("Journal Template Name","Journal Template Name");
    GenJnlLine.SETRANGE("Journal Batch Name","Journal Batch Name");
    CLEAR(VoidElecPayments);
    VoidElecPayments.SETTABLEVIEW(GenJnlLine);
    VoidElecPayments.RUNMODAL;
    // es0006.end
    END;
    }
    { 1100014 ;3 ;Action ;
    CaptionML=ENU=Show Export File Errors;
    RunObject=Page 1228;
    RunFormLink=Journal Template Name=FIELD(Journal Template Name),Journal Batch Name=FIELD(Journal Batch Name) }
    // End of the added lines.

    { 1900000004;0 ;ActionContainer;
    ActionContainerType=ActionItems }
    { 40 ;1 ;ActionGroup;
    ...
  5. Change the code in Controls in the Payment Journal page (256) as follows:
    Existing code 1

    ...
    OnValidate=BEGIN
    GenJnlManagement.GetAccounts(Rec,AccName,BalAccName);
    ShowShortcutDimCode(ShortcutDimCode);
    END;
    }
    ...

    Replacement code 1

    ...
    OnValidate=BEGIN
    GenJnlManagement.GetAccounts(Rec,AccName,BalAccName);
    ShowShortcutDimCode(ShortcutDimCode);

    // Add the following line.
    CheckRecipientBankAccount;
    // End of the added line.

    END;
    }
    ...

    Existing code 2

    ...
    SourceExpr="Reason Code";
    Visible=FALSE }

    { 24 ;1 ;Group }

    { 1903561801;2;Group ;
    ...

    Replacement code 2

    ...
    SourceExpr="Reason Code";
    Visible=FALSE }

    // Add the following lines.
    { 1100012;2;Field ;
    SourceExpr="Recipient Bank Account" }
    // End of the added lines.

    { 24 ;1 ;Group }

    { 1903561801;2;Group ;
    ...
  6. Change the code in Global Variables in the Payment Journal page (256) as follows:
    Existing code

    ...
    ShowTotalBalance@1017 : Boolean;
    ShortcutDimCode@1018 : ARRAY [8] OF Code[20];
    OpenedFromBatch@1019 : Boolean;
    BalanceVisible@19073040 : Boolean INDATASET;
    TotalBalanceVisible@19063333 : Boolean INDATASET;
    ...

    Replacement code

    ...
    ShowTotalBalance@1017 : Boolean;
    ShortcutDimCode@1018 : ARRAY [8] OF Code[20];
    OpenedFromBatch@1019 : Boolean;

    // Add the following lines.
    ExportFormatTypeTxt@1100001 : TextConst 'ENU=SEPA,N34.1';
    ExportAgainQst@1100000 : TextConst 'ENU=One or more of the selected lines have already been exported. Do you want to export again?';
    // End of the added lines.

    BalanceVisible@19073040 : Boolean INDATASET;
    TotalBalanceVisible@19063333 : Boolean INDATASET;
    ...
  7. Change the code in ExportedPmtExist function in the Payment Journal page (256) as follows:
    Existing code

    ...
    TotalBalanceVisible := ShowTotalBalance;
    END;

    LOCAL PROCEDURE CurrentJnlBatchNameOnAfterVali@19002411();
    BEGIN
    CurrPage.SAVERECORD;
    ...

    Replacement code

    ...
    TotalBalanceVisible := ShowTotalBalance;
    END;

    // Add the following lines.
    LOCAL PROCEDURE ExportedPmtExist@1100002(GenJournalLine@1100000 : Record 81) : Boolean;
    VAR
    GenJnlLine3@1100001 : Record 81;
    BEGIN
    GenJnlLine3.COPYFILTERS(GenJnlLine);
    GenJnlLine3.SETRANGE("Exported to Payment File",TRUE);
    EXIT(NOT GenJnlLine3.ISEMPTY);
    END;

    LOCAL PROCEDURE CheckRecipientBankAccount@1100000();
    VAR
    VendorBankAccount@1100000 : Record 288;
    CustomerBankAccount@1100001 : Record 287;
    BEGIN
    IF ("Account No." <> xRec."Account No.") THEN
    VALIDATE("Recipient Bank Account",'');
    END;
    // End of the added lines.

    LOCAL PROCEDURE CurrentJnlBatchNameOnAfterVali@19002411();
    BEGIN
    CurrPage.SAVERECORD;
    ...
  8. Change the code in Properties in the SEPA CT pain.001.001.03 xmlport (1000) as follows:
    Existing code

    ...
    ELEMENTS
    {
    { [{0EA1BA75-FB56-4C05-946C-A299E4809E84}]; ;Document ;Element ;Table ;
    SourceTable=Table81 }

    { [{596E5521-E230-4D9C-B0F7-DF29388F515B}];1 ;xmlns ;Attribute;Text ;
    VariableName=XMLNamespace }
    ...

    Replacement code

    ...
    ELEMENTS
    {
    { [{0EA1BA75-FB56-4C05-946C-A299E4809E84}]; ;Document ;Element ;Table ;
    SourceTable=Table81;

    // Add the following line.
    MaxOccurs=Once }
    // End of the added line.

    { [{596E5521-E230-4D9C-B0F7-DF29388F515B}];1 ;xmlns ;Attribute;Text ;
    VariableName=XMLNamespace }
    ...
  9. Change the code in InitData function in the SEPA CT pain.001.001.03 xmlport (1000) as follows:
    Existing code

    ...
    PaymentGroupNo@1000 : Integer;
    BEGIN
    SEPACTFillExportBuffer.FillExportBuffer("Gen. Journal Line",PaymentExportData);
    PaymentExportData.GetRemittanceTexts(TempPaymentExportRemittanceTxt);

    NoOfTransfers := FORMAT(PaymentExportData.COUNT);
    ...

    Replacement code

    ...
    PaymentGroupNo@1000 : Integer;
    BEGIN
    SEPACTFillExportBuffer.FillExportBuffer("Gen. Journal Line",PaymentExportData);

    // Add the following lines.
    "Gen. Journal Line".SETRANGE("Journal Template Name",'');
    "Gen. Journal Line".SETRANGE("Journal Batch Name",'');
    // End of the added lines.

    PaymentExportData.GetRemittanceTexts(TempPaymentExportRemittanceTxt);

    NoOfTransfers := FORMAT(PaymentExportData.COUNT);
    ...

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.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

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.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×