"The transaction cannot be completed because it will cause inconsistencies in the G/L Entry table" error message when you apply a LCY payment to FCY invoices in a cash receipt journal in the North American version of Microsoft Dynamics NAV 5....


Rapidly Published articles provide information directly from within the Microsoft support organization. The information that is contained herein is created in response to emerging or unique topics, or is intended to supplement other Knowledge Base information.
This article applies to Microsoft Dynamics NAV for the following countries and language locales.
  • English (Canada) (en-ca)
  • English (United States) (en-us)

  • Spanish (Mexico) (es-mx)

  • French (Canada) (fr-ca)

Symptoms


Assume that you use the Cronus Mexico S.A. Company in the North American version of Microsoft Dynamics NAV 5.0 Service Pack 1. When you apply a local currency (LCY) payment to multiple foreign currency (FCY) invoices in a cash receipt journal, you receive the following error message:
The transaction cannot be completed because it will cause inconsistencies in the G/L Entry table.
Check where and how the CONSISTENT function is used in the transaction to find the reason of the error.
Contact your system administrator.
Tables can be market as inconsistent during comprehensive task, such as posting. This prevents data from being updated incorrectly.

Cause


This problem occurs because the general ledger entries and tax entries are incorrect if the following conditions are true:
  • You post a cash receipt journal by using a payment in the local currency against invoices in a foreign currency.
  • The Mexico unrealized value-added tax (VAT) is used.

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 5.0 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, 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. Change the code in the ApplyCustLedgEntry function in the Gen. Jnl.-Post Line codeunit (12) as follows:
    Existing code
    ...
    CalcCurrencyUnrealizedGainLoss(
    OldCVLedgEntryBuf,DtldCVLedgEntryBuf,
    GenJnlLine,-OldAppliedAmount,OldRemainingAmtBeforeAppln);
    CalcCurrencyRealizedGainLoss(
    NewCVLedgEntryBuf,DtldCVLedgEntryBuf,
    GenJnlLine,AppliedAmount,AppliedAmountLCY,RealizedGainLossLCY);
    VATRealizedGainLossLCY := RealizedGainLossLCY;

    CalcCurrencyRealizedGainLoss(
    OldCVLedgEntryBuf,DtldCVLedgEntryBuf,GenJnlLine,-OldAppliedAmount,-AppliedAmountLCY,RealizedGainLossLCY);

    CalcApplication(
    NewCVLedgEntryBuf,OldCVLedgEntryBuf,DtldCVLedgEntryBuf,
    GenJnlLine,AppliedAmount,AppliedAmountLCY,OldAppliedAmount,
    NewCVLedgEntryBuf2,OldCVLedgEntryBuf3);
    ...
    Replacement code
    ...
    CalcCurrencyUnrealizedGainLoss(
    OldCVLedgEntryBuf,DtldCVLedgEntryBuf,
    GenJnlLine,-OldAppliedAmount,OldRemainingAmtBeforeAppln);
    CalcCurrencyRealizedGainLoss(
    NewCVLedgEntryBuf,DtldCVLedgEntryBuf,
    GenJnlLine,AppliedAmount,AppliedAmountLCY,RealizedGainLossLCY);
    VATRealizedGainLossLCY := RealizedGainLossLCY;

    CalcCurrencyRealizedGainLoss(
    OldCVLedgEntryBuf,DtldCVLedgEntryBuf,GenJnlLine,-OldAppliedAmount,-AppliedAmountLCY,RealizedGainLossLCY);

    // Add the following line.
    VATRealizedGainLossLCY := RealizedGainLossLCY;

    CalcApplication(
    NewCVLedgEntryBuf,OldCVLedgEntryBuf,DtldCVLedgEntryBuf,
    GenJnlLine,AppliedAmount,AppliedAmountLCY,OldAppliedAmount,
    NewCVLedgEntryBuf2,OldCVLedgEntryBuf3);
    ...
  2. Change the code in the CustUnrealizedVAT function in the Gen. Jnl.-Post Line codeunit (12) as follows:
    Existing code
    ...
    //what is LCY value of VAT and VAT Base at posting date (cash basis)
    IF (VATPostingSetup."Unrealized VAT Type" = VATPostingSetup."Unrealized VAT Type"::"Cash Basis") AND
    (GainLossLCY <> 0) THEN BEGIN
    VATBaseFCY := ROUND(
    CurrExchRate.ExchangeAmtLCYToFCY(
    PostingDate,CustLedgEntry2."Currency Code",VATBase,CustLedgEntry2."Original Currency Factor"));
    ...
    Replacement code
    ...
    //what is LCY value of VAT and VAT Base at posting date (cash basis)
    IF (VATPostingSetup."Unrealized VAT Type" = VATPostingSetup."Unrealized VAT Type"::"Cash Basis") AND
    (GainLossLCY <> 0) THEN BEGIN

    // Add the following line.
    CurrencyFactor := CurrExchRate.ExchangeRate(PostingDate,CustLedgEntry2."Currency Code");

    VATBaseFCY := ROUND(
    CurrExchRate.ExchangeAmtLCYToFCY(
    PostingDate,CustLedgEntry2."Currency Code",VATBase,CustLedgEntry2."Original Currency Factor"));
    ...
  3. Change the code in the ApplyVendLedgEntry function in the Gen. Jnl.-Post Line codeunit (12) as follows:
    Existing code
    ...
    CalcCurrencyUnrealizedGainLoss(
    OldCVLedgEntryBuf,DtldCVLedgEntryBuf,
    GenJnlLine,-OldAppliedAmount,OldRemainingAmtBeforeAppln);
    CalcCurrencyRealizedGainLoss(
    NewCVLedgEntryBuf,DtldCVLedgEntryBuf,
    GenJnlLine,AppliedAmount,AppliedAmountLCY,RealizedGainLossLCY);
    VATRealizedGainLossLCY := RealizedGainLossLCY;
    CalcCurrencyRealizedGainLoss(
    OldCVLedgEntryBuf,DtldCVLedgEntryBuf,
    GenJnlLine,-OldAppliedAmount,-AppliedAmountLCY,RealizedGainLossLCY);

    CalcApplication(
    NewCVLedgEntryBuf,OldCVLedgEntryBuf,DtldCVLedgEntryBuf,
    GenJnlLine,AppliedAmount,AppliedAmountLCY,OldAppliedAmount,
    NewCVLedgEntryBuf2,OldCVLedgEntryBuf3);
    ...
    Replacement code
    ...
    CalcCurrencyUnrealizedGainLoss(
    OldCVLedgEntryBuf,DtldCVLedgEntryBuf,
    GenJnlLine,-OldAppliedAmount,OldRemainingAmtBeforeAppln);
    CalcCurrencyRealizedGainLoss(
    NewCVLedgEntryBuf,DtldCVLedgEntryBuf,
    GenJnlLine,AppliedAmount,AppliedAmountLCY,RealizedGainLossLCY);
    VATRealizedGainLossLCY := RealizedGainLossLCY;
    CalcCurrencyRealizedGainLoss(
    OldCVLedgEntryBuf,DtldCVLedgEntryBuf,
    GenJnlLine,-OldAppliedAmount,-AppliedAmountLCY,RealizedGainLossLCY);

    // Add the following line.
    VATRealizedGainLossLCY := RealizedGainLossLCY;

    CalcApplication(
    NewCVLedgEntryBuf,OldCVLedgEntryBuf,DtldCVLedgEntryBuf,
    GenJnlLine,AppliedAmount,AppliedAmountLCY,OldAppliedAmount,
    NewCVLedgEntryBuf2,OldCVLedgEntryBuf3);
    ...
  4. Change the code in the VendUnrealizedVAT function in the Gen. Jnl.-Post Line codeunit (12) as follows:
    Existing code
    ...
    //what is LCY value of VAT and VAT Base at posting date (cash basis)
    IF (VATPostingSetup."Unrealized VAT Type" = VATPostingSetup."Unrealized VAT Type"::"Cash Basis") AND
    (GainLossLCY <> 0) THEN BEGIN
    VATBaseFCY := ROUND(
    CurrExchRate.ExchangeAmtLCYToFCY(
    PostingDate,VendLedgEntry2."Currency Code",VATBase,VendLedgEntry2."Original Currency Factor"));
    ...
    Replacement code
    ...
    //what is LCY value of VAT and VAT Base at posting date (cash basis)
    IF (VATPostingSetup."Unrealized VAT Type" = VATPostingSetup."Unrealized VAT Type"::"Cash Basis") AND
    (GainLossLCY <> 0) THEN BEGIN

    // Add the following line.
    CurrencyFactor := CurrExchRate.ExchangeRate(PostingDate,VendLedgEntry2."Currency Code");

    VATBaseFCY := ROUND(
    CurrExchRate.ExchangeAmtLCYToFCY(
    PostingDate,VendLedgEntry2."Currency Code",VATBase,VendLedgEntry2."Original Currency Factor"));
    ...

Prerequisites

You must have the North American version of Microsoft Dynamics NAV 5.0 Service Pack 1 installed to apply this hotfix.

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.
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED IN THE DOCUMENTS AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALS”) FOR ANY PURPOSE.

THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.