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.

When you create the CT CBI file in the Italian version of Microsoft Dynamics NAV 2009, the <RmtInf> section that contains the Ustrd string is not created. This problem occurs in the following products:

  • The Italian version of Microsoft Dynamics NAV 2009 R2

  • The Italian version of Microsoft Dynamics NAV 2009 Service Pack 1 (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 Global Variables in the SEPA CT-Fill Export Buffer codeunit (1221) as follows:
    Existing code

    ...
    HasErrorsErr@1007 : TextConst 'ENU=The journal lines have one or more errors. Correct the errors and try again.';
    FieldIsBlankErr@1006 : TextConst 'ENU=Field %1 must be specified.';
    SameBankErr@1000 : TextConst 'ENU=All lines must have the same bank account as the balancing account.';

    PROCEDURE FillExportBuffer@3(VAR GenJnlLine@1000 : Record 81;VAR PaymentExportData@1001 : Record 1226;SEPAFormat@1130000 : 'pain,CBI');
    VAR
    ...

    Replacement code

    ...
    HasErrorsErr@1007 : TextConst 'ENU=The journal lines have one or more errors. Correct the errors and try again.';
    FieldIsBlankErr@1006 : TextConst 'ENU=Field %1 must be specified.';
    SameBankErr@1000 : TextConst 'ENU=All lines must have the same bank account as the balancing account.';

    // Add the following line.
    RemitMsg@1001 : TextConst 'ENU=%1 %2';

    PROCEDURE FillExportBuffer@3(VAR GenJnlLine@1000 : Record 81;VAR PaymentExportData@1001 : Record 1226;SEPAFormat@1130000 : 'pain,CBI');
    VAR
    ...
  2. Change the code in the FillExportBuffer function in the SEPA CT-Fill Export Buffer codeunit (1221) as follows:
    Existing code 1

    ...
    SetBankAsSenderBank(BankAccount,SEPAFormat);
    "Transfer Date" := TempGenJnlLine."Posting Date";
    "Document No." := TempGenJnlLine."Document No.";
    Amount := TempGenJnlLine.Amount;
    IF TempGenJnlLine."Currency Code" = '' THEN
    "Currency Code" := GeneralLedgerSetup."LCY Code"
    ...

    Replacement code 1

    ...
    SetBankAsSenderBank(BankAccount,SEPAFormat);
    "Transfer Date" := TempGenJnlLine."Posting Date";
    "Document No." := TempGenJnlLine."Document No.";

    // Add the following line.
    "Applies-to Ext. Doc. No." := TempGenJnlLine."Applies-to Ext. Doc. No.";

    Amount := TempGenJnlLine.Amount;
    IF TempGenJnlLine."Currency Code" = '' THEN
    "Currency Code" := GeneralLedgerSetup."LCY Code"
    ...

    Existing code 2

    ...
    "SEPA Message ID" := MessageID;
    "SEPA Payment Information ID" := MessageID + '/' + FORMAT("Entry No.");
    "SEPA End-to-End ID" := MessageID + '/' + FORMAT("Entry No.");

    // Delete the following lines.
    AddRemittanceText(TempGenJnlLine.Description);
    IF TempGenJnlLine."Message to Recipient" <> '' THEN
    AddRemittanceText(TempGenJnlLine."Message to Recipient");
    // End of the deleted lines.

    ValidatePaymentExportData(PaymentExportData,TempGenJnlLine,SEPAFormat);
    INSERT(TRUE);
    UNTIL TempGenJnlLine.NEXT = 0;
    ...

    Replacement code 2

    ...
    "SEPA Message ID" := MessageID;
    "SEPA Payment Information ID" := MessageID + '/' + FORMAT("Entry No.");
    "SEPA End-to-End ID" := MessageID + '/' + FORMAT("Entry No.");

    // Add the following lines.
    IF "Applies-to Ext. Doc. No." <> '' THEN
    AddRemittanceText(STRSUBSTNO(RemitMsg,TempGenJnlLine."Applies-to Doc. Type","Applies-to Ext. Doc. No."))
    ELSE
    AddRemittanceText(TempGenJnlLine.Description);
    IF TempGenJnlLine."Message to Recipient" <> '' THEN
    AddRemittanceText(TempGenJnlLine."Message to Recipient");
    // End of the added lines.

    ValidatePaymentExportData(PaymentExportData,TempGenJnlLine,SEPAFormat);
    INSERT(TRUE);
    UNTIL TempGenJnlLine.NEXT = 0;
    ...
  3. Change the code in Fields in the Payment Export Data table (1226) as follows:
    Existing code

    ...
    OptionString=[ ,Company,Person] }
    { 125 ; ;SEPA Partner Type Text;Code4 }
    { 170 ; ;Creditor No. ;Code35 }
    }
    KEYS
    {
    ...

    Replacement code

    ...
    OptionString=[ ,Company,Person] }
    { 125 ; ;SEPA Partner Type Text;Code4 }
    { 170 ; ;Creditor No. ;Code35 }

    // Add the following line.
    { 173 ; ;Applies-to Ext. Doc. No.;Code35 }

    }
    KEYS
    {
    ...
  4. Change the code in Fields in the Gen. Journal Line table (81) as follows:
    Existing code

    ...
    }
    { 121 ; ;Prepayment ;Boolean }
    { 122 ; ;Financial Void ;Boolean ;Editable=No }
    { 288 ; ;Recipient Bank Account;Code10 ;TableRelation=IF (Account Type=CONST(Customer)) "Customer Bank Account".Code WHERE (Customer No.=FIELD(Account No.))
    ELSE IF (Account Type=CONST(Vendor)) "Vendor Bank Account".Code WHERE (Vendor No.=FIELD(Account No.))
    ELSE IF (Bal. Account Type=CONST(Customer)) "Customer Bank Account".Code WHERE (Customer No.=FIELD(Bal. Account No.))
    ...

    Replacement code

    ...
    }
    { 121 ; ;Prepayment ;Boolean }
    { 122 ; ;Financial Void ;Boolean ;Editable=No }

    // Add the following line.
    { 173 ; ;Applies-to Ext. Doc. No.;Code35 }

    { 288 ; ;Recipient Bank Account;Code10 ;TableRelation=IF (Account Type=CONST(Customer)) "Customer Bank Account".Code WHERE (Customer No.=FIELD(Account No.))
    ELSE IF (Account Type=CONST(Vendor)) "Vendor Bank Account".Code WHERE (Vendor No.=FIELD(Account No.))
    ELSE IF (Bal. Account Type=CONST(Customer)) "Customer Bank Account".Code WHERE (Customer No.=FIELD(Bal. Account No.))
    ...


Prerequisites

You must have one of the following products installed to apply this hotfix:

  • The Italian version of Microsoft Dynamics NAV 2009 R2

  • The Italian 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!

×