This article applies to Microsoft Dynamics NAV for the Croatian (hr) language locale.
Symptoms
Consider the following scenario in the Croatian version of Microsoft Dynamics NAV 2009 R2:
-
You select the Adjust for Payment Disc. check box in the General Ledger Setup dialog box.
-
You select the Adjust for Payment Discount check box in the VAT Posting Setup dialog box.
-
You post an invoice that is in an old period (for example, in May 2012).
-
You use the VAT date and specify the range of the allowed VAT posting dates (for example, in June 2012).
-
You post a payment that is in the allowed VAT posting dates.
In this situation, the system posts a VAT entry in which the VAT Date is outside the range of the allowed VAT posting dates.
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 RunCheck function in the "Gen. Jnl.-Check Line" codeunit (11) as follows:
Existing code...
GLSetup.GET;
IF GLSetup."Use VAT Date" THEN BEGIN
// Delete the following line.
VATDateNeeded := FALSE;
IF "Gen. Posting Type" > 0 THEN
IF VATPostingSetup.GET("VAT Bus. Posting Group","VAT Prod. Posting Group") THEN
IF NOT VATPostingSetup."Allow Blank VAT Date" THEN
VATDateNeeded := TRUE;
IF "Bal. Gen. Posting Type" > 0 THEN
IF VATPostingSetup.GET("Bal. VAT Bus. Posting Group","Bal. VAT Prod. Posting Group") THEN
IF NOT VATPostingSetup."Allow Blank VAT Date" THEN
VATDateNeeded := TRUE;
IF VATDateNeeded THEN
IF "VAT Date" <> 0D THEN BEGIN
IF VATDateNotAllowed("VAT Date") THEN
FIELDERROR("VAT Date",Text26500);
VATPeriodCheck("VAT Date");
END ELSE
TESTFIELD("VAT Date");
END;
...Replacement code
...
GLSetup.GET;
IF GLSetup."Use VAT Date" THEN BEGIN
// Add the following lines.
IF "VAT Date" <> 0D THEN
VATDateNeeded := TRUE
ELSE BEGIN
// End of the added lines.
IF "Gen. Posting Type" > 0 THEN
IF VATPostingSetup.GET("VAT Bus. Posting Group","VAT Prod. Posting Group") THEN
IF NOT VATPostingSetup."Allow Blank VAT Date" THEN
VATDateNeeded := TRUE;
IF "Bal. Gen. Posting Type" > 0 THEN
IF VATPostingSetup.GET("Bal. VAT Bus. Posting Group","Bal. VAT Prod. Posting Group") THEN
IF NOT VATPostingSetup."Allow Blank VAT Date" THEN
VATDateNeeded := TRUE;
// Add the following line.
END;
IF VATDateNeeded THEN
IF "VAT Date" <> 0D THEN BEGIN
IF VATDateNotAllowed("VAT Date") THEN
FIELDERROR("VAT Date",Text26500);
VATPeriodCheck("VAT Date");
END ELSE
TESTFIELD("VAT Date");
END;
... -
Change the code in the CalcPmtDiscIfAdjVAT function in the "Gen. Jnl.-Post Line" codeunit (12) as follows:
Existing code...
TempVatEntry := VATEntry2;
TempVatEntry."Entry No." := TempVatEntryNo;
TempVatEntry."Posting Date" := GenJnlLine."Posting Date";
TempVatEntry."Document No." := GenJnlLine."Document No.";
TempVatEntry."External Document No." := GenJnlLine."External Document No.";
TempVatEntry."Document Type" := GenJnlLine."Document Type";
...Replacement code
...
TempVatEntry := VATEntry2;
TempVatEntry."Entry No." := TempVatEntryNo;
TempVatEntry."Posting Date" := GenJnlLine."Posting Date";
// Add the following line.
TempVatEntry."VAT Date" := GenJnlLine."VAT Date";
TempVatEntry."Document No." := GenJnlLine."Document No.";
TempVatEntry."External Document No." := GenJnlLine."External Document No.";
TempVatEntry."Document Type" := GenJnlLine."Document Type";
...
Prerequisites
You must have the Croatian version of Microsoft Dynamics NAV 2009 R2 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.
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.