This article applies to Microsoft Dynamics NAV for the Spanish (es) language locale.
Symptoms
Consider the following scenario in the Spanish version of Microsoft Dynamics NAV 2009 R2 and of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1):
-
You have a customer who uses a payment method that generates bills.
-
You set up a value-added tax (VAT) posting group for unrealized VAT.
-
You have an invoice that contains more than one line.
-
Each line contains an item that has a different general product posting group specified. Therefore, when you post the invoice, different accounts are used.
-
You use the VAT posting group for unrealized VAT for each line.
-
You post the invoice.
-
You create a payment from a payment journal to apply the invoice.
-
You post the application.
In this scenario, the amount in the VAT entries is incorrect.
Note This problem is Cartera-related only.
Cause
This problem occurs because the Unrealized VAT functionality does not work as expected.
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 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, change the code in the VendUnrealizedVAT function in the Gen. Jnl.-Post Line codeunit (12) as follows:
Existing code 1
...
VendLedgEntry3.SETCURRENTKEY(VendLedgEntry3."Document No.",VendLedgEntry3."Document Type",VendLedgEntry3."Vendor No.");
VendLedgEntry3.SETRANGE(VendLedgEntry3."Document Type",VendLedgEntry3."Document Type"::Invoice);
VendLedgEntry3.SETRANGE(VendLedgEntry3."Document No.",VendLedgEntry4."Document No.");
IF VendLedgEntry3.FIND('-') THEN BEGIN
VendLedgEntry2.Open := TRUE;
VATEntry2.SETRANGE("Transaction No.",VendLedgEntry3."Transaction No.")
END ELSE
ERROR(Text1100001,VendLedgEntry3."Document No.");
END ELSE
...
Replacement code 1
...
VendLedgEntry3.SETCURRENTKEY(VendLedgEntry3."Document No.",VendLedgEntry3."Document Type",VendLedgEntry3."Vendor No.");
VendLedgEntry3.SETRANGE(VendLedgEntry3."Document Type",VendLedgEntry3."Document Type"::Invoice);
VendLedgEntry3.SETRANGE(VendLedgEntry3."Document No.",VendLedgEntry4."Document No.");
IF VendLedgEntry3.FIND('-') THEN BEGIN
// Add the following line.
VendLedgEntry3.CALCFIELDS("Original Amt. (LCY)");
VendLedgEntry2.Open := TRUE;
VATEntry2.SETRANGE("Transaction No.",VendLedgEntry3."Transaction No.")
END ELSE
ERROR(Text1100001,VendLedgEntry3."Document No.");
END ELSE
...
Existing code 2
...
IF LastConnectionNo <> VATEntry2."Sales Tax Connection No." THEN BEGIN
InsertSummarizedVAT;
LastConnectionNo := VATEntry2."Sales Tax Connection No.";
END;
// Delete the following lines.
VATPart :=
VATEntry2.GetUnRealizedVATPart(
ROUND(SettledAmount / VendLedgEntry2.GetOriginalCurrencyFactor),
PaidAmount,
VendLedgEntry2."Original Amt. (LCY)",
TotalUnrealVATAmountFirst,
TotalUnrealVATAmountLast);
// End of the lines.
IF VATPart >= 0 THEN BEGIN
IF VATPart <> 0 THEN BEGIN
CASE VATEntry2."VAT Calculation Type" OF
VATEntry2."VAT Calculation Type"::"Normal VAT",
...
Replacement code 3
...
IF LastConnectionNo <> VATEntry2."Sales Tax Connection No." THEN BEGIN
InsertSummarizedVAT;
LastConnectionNo := VATEntry2."Sales Tax Connection No.";
END;
// Add the following lines.
IF VendLedgEntry4."Document Type" = VendLedgEntry4."Document Type"::Bill THEN
VATPart :=
VATEntry2.GetUnRealizedVATPart(
ROUND(SettledAmount / VendLedgEntry3.GetOriginalCurrencyFactor),
PaidAmount,
VendLedgEntry3."Original Amt. (LCY)",
TotalUnrealVATAmountFirst,
TotalUnrealVATAmountLast)
ELSE
VATPart :=
VATEntry2.GetUnRealizedVATPart(
ROUND(SettledAmount / VendLedgEntry2.GetOriginalCurrencyFactor),
PaidAmount,
VendLedgEntry2."Original Amt. (LCY)",
TotalUnrealVATAmountFirst,
TotalUnrealVATAmountLast);
// End of the lines.
IF VATPart >= 0 THEN BEGIN
IF VATPart <> 0 THEN BEGIN
CASE VATEntry2."VAT Calculation Type" OF
VATEntry2."VAT Calculation Type"::"Normal VAT",
...
Existing code 2
...
PurchVATUnrealAccount := TaxJurisdiction."Unreal. Tax Acc. (Purchases)";
END;
END;
IF VATPart = 1 THEN BEGIN
// Delete the following lines.
IF VendLedgEntry2."Document Type" = VendLedgEntry2."Document Type"::Bill THEN BEGIN
VATBase := ROUND(PaidAmount /(1 + VATEntry2."VAT %"/100),GLSetup."Amount Rounding Precision");
VATAmount := ROUND(PaidAmount - VATBase,GLSetup."Amount Rounding Precision");
END ELSE BEGIN
VATAmount := VATEntry2."Remaining Unrealized Amount";
VATBase := VATEntry2."Remaining Unrealized Base";
VATAmountAddCurr := VATEntry2."Add.-Curr. Rem. Unreal. Amount";
VATBaseAddCurr := VATEntry2."Add.-Curr. Rem. Unreal. Base";
END
// End of the lines.
END ELSE BEGIN
VATAmount := ROUND(VATEntry2."Remaining Unrealized Amount" * VATPart);
VATBase := ROUND(VATEntry2."Remaining Unrealized Base" * VATPart);
VATAmountAddCurr :=
ROUND(
...
Replacement code 3
...
PurchVATUnrealAccount := TaxJurisdiction."Unreal. Tax Acc. (Purchases)";
END;
END;
IF VATPart = 1 THEN BEGIN
// Add the following lines.
VATAmount := VATEntry2."Remaining Unrealized Amount";
VATBase := VATEntry2."Remaining Unrealized Base";
VATAmountAddCurr := VATEntry2."Add.-Curr. Rem. Unreal. Amount";
VATBaseAddCurr := VATEntry2."Add.-Curr. Rem. Unreal. Base";
// End of the lines.
END ELSE BEGIN
VATAmount := ROUND(VATEntry2."Remaining Unrealized Amount" * VATPart);
VATBase := ROUND(VATEntry2."Remaining Unrealized Base" * VATPart);
VATAmountAddCurr :=
ROUND(
...
Prerequisites
You must have one of the following products installed to apply this hotfix:
-
The Spanish version of Microsoft Dynamics NAV 2009 R2
-
The Spanish version of Microsoft Dynamics NAV 2009 Service Pack 1
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 Use for other considerations.
