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 dimensions are not handled correctly in the bank account reconciliation in the German version of Microsoft Dynamics NAV with the AddOn Payments included

The dimensions are not handled correctly in the bank account reconciliation in the German version of Microsoft Dynamics NAV with the AddOn Payments included

View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the German (de) language locale.

↑ Back to the top

Symptoms

When you create the bank account reconciliation in the German version of Microsoft Dynamics NAV with the AddOn Payments included, the dimensions are not handled correctly. This problem occurs if the statement number contains more than ten characters.
This problem occurs in the following products:
  • The German version of Microsoft Dynamics NAV 2009 Service Pack 1
  • The German version of Microsoft Dynamics NAV 2009
  • The German version of Microsoft Dynamics NAV 5.0 Service Pack 1
  • The German version of Microsoft Dynamics NAV 5.0

↑ 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. Add a local variable in the ValidateShortcutDimCode function in the Bank Acc. Reconciliation Line table (274), and then specify the variable as follows:
    • Name:OffSetL
    • DataType:Integer
  2. Change the code in the ValidateShortcutDimCode function in the Bank Acc. Reconciliation Line table (274) as follows:
    Existing code
    ...
    DimMgt.ValidateDimValueCode(FieldNo,ShortcutDimCode);
    IF "Statement Line No." <> 0 THEN BEGIN
      DimMgt.SaveJnlLineDim(
        DATABASE::"Bank Acc. Reconciliation Line",COPYSTR("Bank Account No.",1,10),
        COPYSTR("Statement No.",1,10),"Statement Line No.",0,FieldNo,ShortcutDimCode);
      IF MODIFY THEN;
    END ELSE
      DimMgt.SaveTempDim(FieldNo,ShortcutDimCode);
    ...
    Replacement code
    ...
    DimMgt.ValidateDimValueCode(FieldNo,ShortcutDimCode);
    IF "Statement Line No." <> 0 THEN BEGIN
      OffSetL := STRLEN("Statement No.")-9;
      IF OffSetL < 1 THEN
        OffSetL := 1;
      DimMgt.SaveJnlLineDim(
        DATABASE::"Bank Acc. Reconciliation Line",COPYSTR("Bank Account No.",1,10),
        COPYSTR("Statement No.",OffSetL,10),"Statement Line No.",0,FieldNo,ShortcutDimCode);
      IF MODIFY THEN;
    END ELSE
      DimMgt.SaveTempDim(FieldNo,ShortcutDimCode);
    ...
  3. Add a local variable in the CreateDim function in the Bank Acc. Reconciliation Line table (274), and then specify the variable as follows:
    • Name:OffSetL
    • DataType:Integer
  4. Change the code in the CreateDim function in the Bank Acc. Reconciliation Line table (274) as follows:
    Existing code 1
    ...
    SourceCodeSetup.GET;
    TableID[1] := Type1;
    No[1] := No1;
    ...
    Replacement code 1
    ...
    OffsetL := STRLEN("Statement No.")-9;
    IF OffsetL < 1 THEN
      OffsetL := 1;
    SourceCodeSetup.GET;
    TableID[1] := Type1;
    No[1] := No1;
    ...
    Existing code 2
    ...
        DATABASE::"Bank Acc. Reconciliation Line",COPYSTR("Bank Account No.",1,10),
        COPYSTR("Statement No.",1,10),"Statement Line No.",0,
        "Global Dimension 1 Code","Global Dimension 2 Code");
    ...
    Replacement code 2
    ...
        DATABASE::"Bank Acc. Reconciliation Line",COPYSTR("Bank Account No.",1,10),
        COPYSTR("Statement No.",OffsetL,10),"Statement Line No.",0,
        "Global Dimension 1 Code","Global Dimension 2 Code");
    ...
  5. Add a local variable in the ShowShortcutDimCode function in the Bank Acc. Reconciliation Line table (274), and then specify the variable as follows:
    • Name:OffSetL
    • DataType:Integer
  6. Change the code in the ShowShortcutDimCode function in the Bank Acc. Reconciliation Line table (274) as follows:
    Existing code
    ...
    IF "Statement Line No." <> 0 THEN
      DimMgt.ShowJnlLineDim(
        DATABASE::"Bank Acc. Reconciliation Line",COPYSTR("Bank Account No.",1,10),
        COPYSTR("Statement No.",1,10),"Statement Line No.",0,ShortcutDimCode)
    ELSE
      DimMgt.ShowTempDim(ShortcutDimCode);
    ...
    Replacement code
    ...
    OffSetL := STRLEN("Statement No.")-9;
    IF OffSetL < 1 THEN
      OffSetL := 1;
    IF "Statement Line No." <> 0 THEN
      DimMgt.ShowJnlLineDim(
        DATABASE::"Bank Acc. Reconciliation Line",COPYSTR("Bank Account No.",1,10),
        COPYSTR("Statement No.",OffSetL,10),"Statement Line No.",0,ShortcutDimCode)
    ELSE
      DimMgt.ShowTempDim(ShortcutDimCode);
    ...
  7. Add a local variable in the UpdateShortcutdimCode function in the Bank Acc. Reconciliation Line table (274), and then specify the variable as follows:
    • Name:OffSetL
    • DataType:Integer
  8. Change the code in the UpdateShortcutdimCode function in the Bank Acc. Reconciliation Line table (274) as follows:
    Existing code
    ...
    GLSetup.GET;
    JnlLineDim.SETRANGE("Table ID",DATABASE::"Bank Acc. Reconciliation Line");
    JnlLineDim.SETRANGE("Journal Template Name",COPYSTR("Bank Account No.",1,10));
    JnlLineDim.SETRANGE("Journal Batch Name",COPYSTR("Statement No.",1,10));
    JnlLineDim.SETRANGE("Journal Line No.","Statement Line No.");
    ...
    Replacement code
    ...
    OffSetL := STRLEN("Statement No.")-9;
    IF OffSetL < 1 THEN
      OffSetL := 1; 
    GLSetup.GET;
    JnlLineDim.SETRANGE("Table ID",DATABASE::"Bank Acc. Reconciliation Line");
    JnlLineDim.SETRANGE("Journal Template Name",COPYSTR("Bank Account No.",1,10));
    JnlLineDim.SETRANGE("Journal Batch Name",COPYSTR("Statement No.",OffSetL,10));
    JnlLineDim.SETRANGE("Journal Line No.","Statement Line No.");
    ...
  9. Add a local variable in the ShowDimension function in the Bank Acc. Reconciliation Lines form (380), and then specify the variable as follows:
    • Name:OffSetL
    • DataType:Integer
  10. Change the code in the ShowDimension function in the Bank Acc. Reconciliation Lines form (380) as follows:
    Existing code
    ...
    // CLR
    JnlLineDim.RESET;
    JnlLineDim.SETRANGE("Table ID",DATABASE::"Bank Acc. Reconciliation Line");
    JnlLineDim.SETRANGE("Journal Template Name",COPYSTR("Bank Account No.",1,10));
    JnlLineDim.SETRANGE("Journal Batch Name",COPYSTR("Statement No.",1,10));
    JnlLineDim.SETRANGE("Journal Line No.","Statement Line No.");
    ...
    Replacement code
    ...
    // CLR
    OffSetL := STRLEN("Statement No.")-9;
    IF OffSetL < 1 THEN
      OffSetL := 1;

    JnlLineDim.RESET;
    JnlLineDim.SETRANGE("Table ID",DATABASE::"Bank Acc. Reconciliation Line");
    JnlLineDim.SETRANGE("Journal Template Name",COPYSTR("Bank Account No.",1,10));
    JnlLineDim.SETRANGE("Journal Batch Name",COPYSTR("Statement No.",OffSetL,10));
    JnlLineDim.SETRANGE("Journal Line No.","Statement Line No.");
    ...
  11. Add a local variable in the ShowDimension function in the Bank Acc. Reconciliation Lines page (380), and then specify the variable as follows:
    • Name:OffSetL
    • DataType:Integer
  12. Change the code in the ShowDimension function in the Bank Acc. Reconciliation Lines page (380) as follows:
    Existing code
    ...
    // CLR
    JnlLineDim.RESET;
    JnlLineDim.SETRANGE("Table ID",DATABASE::"Bank Acc. Reconciliation Line");
    JnlLineDim.SETRANGE("Journal Template Name",COPYSTR("Bank Account No.",1,10));
    JnlLineDim.SETRANGE("Journal Batch Name",COPYSTR("Statement No.",1,10));
    JnlLineDim.SETRANGE("Journal Line No.","Statement Line No.");
    ...
    Replacement code
    ...
    // CLR
    OffSetL := STRLEN("Statement No.")-9;
    IF OffSetL < 1 THEN
      OffSetL := 1;
    JnlLineDim.RESET;
    JnlLineDim.SETRANGE("Table ID",DATABASE::"Bank Acc. Reconciliation Line");
    JnlLineDim.SETRANGE("Journal Template Name",COPYSTR("Bank Account No.",1,10));
    JnlLineDim.SETRANGE("Journal Batch Name",COPYSTR("Statement No.",OffSetL,10));
    JnlLineDim.SETRANGE("Journal Line No.","Statement Line No.");
    ...
  13. Add a local variable in the OnRun trigger in the Bank Acc. Reconciliation Post codeunit (370), and then specify the variable as follows:
    • Name:OffSetL
    • DataType:Integer
  14. Change the code in the OnRun trigger in the Bank Acc. Reconciliation Post codeunit (370) as follows:
    Existing code
    ...
        BankAccStmtLine.INSERT;
        // CLR
        AutocreateBankAccount(BankAccReconLine);
        DimMgt.DeleteDocDim(
          DATABASE::"Bank Acc. Reconciliation Line",0,
          BankAccStmtLine."Statement No.",BankAccStmtLine."Statement Line No.");
        // CLR
      UNTIL BankAccReconLine.NEXT = 0;
    ...
    Replacement code
    ...
        BankAccStmtLine.INSERT;
        // CLR
        AutocreateBankAccount(BankAccReconLine);
        OffSetL := STRLEN(BankAccReconLine."Statement No.")-9;
        IF OffSetL < 1 THEN
          OffSetL := 1;
        DimMgt.DeleteDocDim(
          DATABASE::"Bank Acc. Reconciliation Line",0,
          COPYSTR(BankAccStmtLine."Statement No.",OffSetL,10),BankAccStmtLine."Statement Line No.");
        // CLR
      UNTIL BankAccReconLine.NEXT = 0;
    ...
  15. Add a local variable in the PostGLAcc function in the Payment Gen. Jnl.-Post Line codeunit (5001910), and then specify the variable as follows:
    • Name:OffSetL
    • DataType:Integer
  16. Change the code in the PostGLAcc function in the Payment Gen. Jnl.-Post Line codeunit (5001910) as follows:
    Existing code
    ...
      IF NOT TempJnlLineDim.INSERT THEN
        TempJnlLineDim.MODIFY;
    END;
    JnlLineDim.RESET;
    JnlLineDim.SETRANGE("Table ID",DATABASE::"Bank Acc. Reconciliation Line");
    JnlLineDim.SETRANGE("Journal Template Name",COPYSTR(BankAccRecLine."Bank Account No.",1,10));
    JnlLineDim.SETRANGE("Journal Batch Name",COPYSTR(BankAccRecLine."Statement No.",1,10));
    JnlLineDim.SETRANGE("Journal Line No.",BankAccRecLine."Statement Line No.");
    ...
    Replacement code
    ...
      IF NOT TempJnlLineDim.INSERT THEN
        TempJnlLineDim.MODIFY;
    END;
    OffSetL := STRLEN(BankAccRecLine."Statement No.")-9;
    IF OffSetL < 1 THEN
      OffSetL := 1;
    JnlLineDim.RESET;
    JnlLineDim.SETRANGE("Table ID",DATABASE::"Bank Acc. Reconciliation Line");
    JnlLineDim.SETRANGE("Journal Template Name",COPYSTR(BankAccRecLine."Bank Account No.",1,10));
    JnlLineDim.SETRANGE("Journal Batch Name",COPYSTR(BankAccRecLine."Statement No.",OffSetL,10));
    JnlLineDim.SETRANGE("Journal Line No.",BankAccRecLine."Statement Line No.");
    ...

Prerequisites

You must have one of the following products installed to apply this hotfix:
  • The German version of Microsoft Dynamics NAV 2009 Service Pack 1 with the AddOn Payments included
  • The German version of Microsoft Dynamics NAV 2009 with the AddOn Payments included
  • The German version of Microsoft Dynamics NAV 5.0 Service Pack 1 with the AddOn Payments included
  • The German version of Microsoft Dynamics NAV 5.0 with the AddOn Payments included

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, kbmbspartner, kbnoloc, kbmbsquickpub, kbmbsmigrate, kbmbscodefix, kbsurveynew

↑ Back to the top

Article Info
Article ID : 2274319
Revision : 2
Created on : 9/21/2018
Published on : 9/21/2018
Exists online : False
Views : 270