Symptoms
Assume that you set up an additional reporting currency and posted an invoice that contains a different currency code for a customer. When you apply a payment that contains a third currency and try to unapply it, you may receive the following error:
The transaction cannot be completed because it will cause inconsistencies.
This problem occurs in the following products:
-
Microsoft Dynamics NAV 2009 R2
-
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:
-
Change the code in the UnapplyCustLedgEntry function in the codeunit (12) as follows:
Existing code...
NextDtldLedgEntryEntryNo := NextDtldLedgEntryEntryNo + 1;
DtldCVLedgEntryBuf.TRANSFERFIELDS(NewDtldCustLedgEntry);
// Delete the following lines.
IF (GLSetup."Additional Reporting Currency" <> '') AND
(GLSetup."Additional Reporting Currency" = DtldCVLedgEntryBuf."Currency Code")
THEN
DtldCVLedgEntryBuf."Additional-Currency Amount" := DtldCVLedgEntryBuf.Amount
ELSE
DtldCVLedgEntryBuf."Additional-Currency Amount" :=
CalcAddCurrForUnapplication(DtldCustLedgEntry."Posting Date",DtldCVLedgEntryBuf."Amount (LCY)");
CurrencyLCY.InitRoundingPrecision;
// End of the deleted lines.
IF DtldCustLedgEntry."Transaction No." <> 0 THEN BEGIN
...Replacement code
...
NextDtldLedgEntryEntryNo := NextDtldLedgEntryEntryNo + 1;
DtldCVLedgEntryBuf.TRANSFERFIELDS(NewDtldCustLedgEntry);
// Add the following lines.
SetAddCurrForUnapplication(DtldCVLedgEntryBuf);
CurrencyLCY.InitRoundingPrecision;
// End of the added lines.
IF DtldCustLedgEntry."Transaction No." <> 0 THEN BEGIN
... -
Change the code in the UnapplyVendLedgEntry in the codeunit (12) as follows:
Existing code...
NextDtldLedgEntryEntryNo := NextDtldLedgEntryEntryNo + 1;
DtldCVLedgEntryBuf.TRANSFERFIELDS(NewDtldVendLedgEntry);
// Delete the following lines.
IF (GLSetup."Additional Reporting Currency" <> '') AND
(GLSetup."Additional Reporting Currency" = DtldCVLedgEntryBuf."Currency Code")
THEN
DtldCVLedgEntryBuf."Additional-Currency Amount" := DtldCVLedgEntryBuf.Amount
ELSE
DtldCVLedgEntryBuf."Additional-Currency Amount" :=
CalcAddCurrForUnapplication(DtldVendLedgEntry."Posting Date",DtldCVLedgEntryBuf."Amount (LCY)");
CurrencyLCY.InitRoundingPrecision;
// End of the deleted lines.
IF DtldVendLedgEntry2."Entry Type" IN [
...Replacement code
...
NextDtldLedgEntryEntryNo := NextDtldLedgEntryEntryNo + 1;
DtldCVLedgEntryBuf.TRANSFERFIELDS(NewDtldVendLedgEntry);
// Add the following lines.
SetAddCurrForUnapplication(DtldCVLedgEntryBuf);
CurrencyLCY.InitRoundingPrecision;
// End of the added lines.
IF DtldVendLedgEntry2."Entry Type" IN [
... -
Add the following function to the codeunit (12) as follows:
LOCAL PROCEDURE SetAddCurrForUnapplication@101(VAR DtldCVLedgEntryBuf@1000 : Record 383);
BEGIN
WITH DtldCVLedgEntryBuf DO
IF NOT ("Entry Type" IN ["Entry Type"::Application,"Entry Type"::"Unrealized Loss","Entry Type"::"Unrealized Gain",
"Entry Type"::"Realized Loss","Entry Type"::"Realized Gain",
"Entry Type"::"Correction of Remaining Amount"])
THEN
IF ("Entry Type" = "Entry Type"::"Appln. Rounding") OR
((GLSetup."Additional Reporting Currency" <> '') AND
(GLSetup."Additional Reporting Currency" = "Currency Code"))
THEN
"Additional-Currency Amount" := Amount
ELSE
"Additional-Currency Amount" := CalcAddCurrForUnapplication("Posting Date","Amount (LCY)");
END;LOCAL PROCEDURE SetAddCurrForUnapplication@101(VAR DtldCVLedgEntryBuf@1000 : Record 383);
Prerequisites
You must have one of the following products installed to apply this hotfix:
-
Microsoft Dynamics NAV 2009 R2
-
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.