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 system generates unbalanced transactions in general ledger entries after you apply hotfix 2564860 in Microsoft Dynamics NAV 2009

The system generates unbalanced transactions in general ledger entries after you apply hotfix 2564860 in Microsoft Dynamics NAV 2009

View products that this article applies to.

This article applies to Microsoft Dynamics NAV for all countries and all language locales.

↑ Back to the top

Symptoms

Consider the following scenario in Microsoft Dynamics NAV 2009 R2 and in Microsoft Dynamics NAV 2009 Service Pack 1 (SP1):
  • You apply hotfix 2564860.
    For more information about hotfix 2564860, click the following article number to view the article in the Microsoft Knowledge Base:
    2564860 General ledger entries are missing when you apply a Reverse Charge Vendor invoice that uses the unrealized VAT in Microsoft Dynamics NAV
  • In general journal lines, you register transactions that contain more than a single line.
  • You enter the lines in a specific order.
In this scenario, in the general ledger entries, the transaction number in the first line differs from the transaction number in the following lines. Therefore, the single transaction number is unbalanced.
This problem occurs if a purchase invoice is registered through a purchase journal by using multiple lines. The vendor information is added in the first line and in the following line by using the same document date and the same document number. The general ledger account for the costs is added. After you post the invoice, the general ledger entry for the payables account has a different transaction number than the following lines.

↑ 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 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 ApplyCustLedgEntry function in the Gen. Jnl.-Post Line codeunit (12) as follows:
    Existing code
    ...
    TransferCustLedgEntry(NewCVLedgEntryBuf,NewCustLedgEntry,FALSE);
    CheckUnrealizedCust := TRUE;
    UnrealizedCustLedgEntry := NewCustLedgEntry;
    UnrealizedCustLedgEntry.CALCFIELDS(
    "Amount (LCY)","Original Amt. (LCY)");
    UnrealizedRemainingAmountCust := NewCustLedgEntry."Remaining Amount" - 
    NewRemainingAmtBeforeAppln;
    END;
    END;

    LOCAL PROCEDURE CalcPmtTolerance()
    ...
    Replacement code
    ...
    TransferCustLedgEntry(NewCVLedgEntryBuf,NewCustLedgEntry,FALSE);
    CheckUnrealizedCust := TRUE;
    UnrealizedCustLedgEntry := NewCustLedgEntry;
    UnrealizedCustLedgEntry.CALCFIELDS(
    "Amount (LCY)","Original Amt. (LCY)");

    // Add the following line.
    CurrentBalance := 0;

    UnrealizedRemainingAmountCust := NewCustLedgEntry."Remaining Amount" - 
    NewRemainingAmtBeforeAppln;
    END;
    END;

    LOCAL PROCEDURE CalcPmtTolerance()
    ...
  2. Change the code in the ApplyVendLedgEntry function in the Gen. Jnl.-Post Line codeunit (12) as follows:
    Existing code 1
    ...
    // Delete the following line.
    CurrentBalance := 0; 

    IF NewCVLedgEntryBuf."Amount to Apply" = 0 THEN
    EXIT;
    AllApplied := TRUE;
    IF (GenJnlLine."Applies-to Doc. No." = '') AND (GenJnlLine."Applies-to ID" = '') AND
    ...
    Replacement code 1
    ...
    IF NewCVLedgEntryBuf."Amount to Apply" = 0 THEN
    EXIT;
    AllApplied := TRUE;
    IF (GenJnlLine."Applies-to Doc. No." = '') AND (GenJnlLine."Applies-to ID" = '') AND
    ...
    Existing code 2
    ...
    TransferVendLedgEntry(NewCVLedgEntryBuf,NewVendLedgEntry,FALSE);
    CheckUnrealizedVend := TRUE;
    UnrealizedVendLedgEntry := NewVendLedgEntry;
    UnrealizedVendLedgEntry.CALCFIELDS(
    "Amount (LCY)","Original Amt. (LCY)");
    UnrealizedRemainingAmountVend := -(NewRemainingAmtBeforeAppln - NewVendLedgEntry."Remaining Amount");
    END;
    END;

    PROCEDURE VendPostApplyVendLedgEntry
    ...
    Replacement code 2
    ...
    TransferVendLedgEntry(NewCVLedgEntryBuf,NewVendLedgEntry,FALSE);
    CheckUnrealizedVend := TRUE;
    UnrealizedVendLedgEntry := NewVendLedgEntry;
    UnrealizedVendLedgEntry.CALCFIELDS(
    "Amount (LCY)","Original Amt. (LCY)");

    // Add the following line.
    CurrentBalance := 0;

    UnrealizedRemainingAmountVend := -(NewRemainingAmtBeforeAppln - NewVendLedgEntry."Remaining Amount");
    END;
    END;

    PROCEDURE VendPostApplyVendLedgEntry
    ...

Prerequisites

You must have one of the following products installed to apply this hotfix:
  • Microsoft Dynamics NAV 2009 R2
  • Microsoft Dynamics NAV 2009 Service Pack 1

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

↑ Back to the top

Article Info
Article ID : 2691132
Revision : 1
Created on : 1/7/2017
Published on : 3/23/2012
Exists online : False
Views : 268