Symptoms
There is an issue with the VAT CASH functionality when you use together with APPLY Entries, setting the INVOICE in the Header and applying VS the Payment in the Spanish version of Microsoft Dynamics NAV 2009. If you do that and have some invoices posted in a range in the middle of the VAT CASH Invoice and payment, then those invoices are skipped in the 340 Declaration. Follow the steps in the code changes section to solve this issue. This problem occurs in the following products:
-
The Spanish version of Microsoft Dynamics NAV 2009 R2
-
The Spanish version of Microsoft Dynamics NAV 2009 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 Make 340 Declaration report (10743) as follows:
Existing code 1...
OnAfterGetRecord=BEGIN
VATBuffer.DELETEALL;
CASE Type OF
Type::Sale:
BEGIN
...Replacement code 1
...
OnAfterGetRecord=BEGIN
VATBuffer.DELETEALL;
// Add the following lines.
TempVATEntry.SETRANGE(Type,Type);
TempVATEntry.SETRANGE("Document No.","Document No.");
TempVATEntry.SETRANGE("Document Type","Document Type");
TempVATEntry.SETRANGE("Bill-to/Pay-to No.","Bill-to/Pay-to No.");
IF NOT TempVATEntry.ISEMPTY THEN
CurrReport.SKIP;
// End of the added lines.
CASE Type OF
Type::Sale:
BEGIN
...Existing code 2
...
BookTypeCode := 'R';
END;
END;
END;
TotalFields=Base,Amount;
...Replacement code 2
...
BookTypeCode := 'R';
END;
END;
// Add the following lines.
TempVATEntry.RESET;
IF TempVATEntry.FINDLAST THEN;
TempVATEntry."Entry No." := TempVATEntry."Entry No." + 1;
TempVATEntry.Type := Type;
TempVATEntry."Document No." := "Document No.";
TempVATEntry."Document Type" := "Document Type";
TempVATEntry."Bill-to/Pay-to No." := "Bill-to/Pay-to No.";
TempVATEntry.INSERT;
// End of the added lines.
END;
TotalFields=Base,Amount;
...Existing code 3
...
END;
END;
OnPostDataItem=BEGIN
VATEntry := VATEntry2;
END;
TotalFields=Base,Amount;
DataItemLink=Type=FIELD(Type), Document Type=FIELD(Document Type), Document No.=FIELD(Document No.), Bill-to/Pay-to No.=FIELD(Bill-to/Pay-to No.);
}
...Replacement code 3
...
END;
END;
// Delete the following lines.
OnPostDataItem=BEGIN
VATEntry := VATEntry2;
END;
// End of the deleted lines.
TotalFields=Base,Amount;
DataItemLink=Type=FIELD(Type), Document Type=FIELD(Document Type), Document No.=FIELD(Document No.), Bill-to/Pay-to No.=FIELD(Bill-to/Pay-to No.);
}
... -
Change the code in Global Variables in the Make 340 Declaration report (10743) as follows:
Existing code...
ServiceCrMemoHeader@1100013 : Record 5994;
VATEntryTemporary@1100078 : TEMPORARY Record 254;
TempDeclarationLines@1100149 : TEMPORARY Record 10744;
CommonDialogMgt@1100015 : Codeunit 412;
OutFile@1100016 : File;
DeclarationNum@1100017 : Text[4];
...Replacement code
...
ServiceCrMemoHeader@1100013 : Record 5994;
VATEntryTemporary@1100078 : TEMPORARY Record 254;
TempDeclarationLines@1100149 : TEMPORARY Record 10744;
// Add the following line.
TempVATEntry@1100007 : TEMPORARY Record 254;
// End of the added line.
CommonDialogMgt@1100015 : Codeunit 412;
OutFile@1100016 : File;
DeclarationNum@1100017 : Text[4];
...
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 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.
