Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The service corrective entries have to report the difference between invoice amount and credit memo amount in the Italian version of Microsoft Dynamics NAV


View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the Italian (it) language locale.

↑ Back to the top


Symptoms

According to the Intrastat law, when you report service corrective entries, you must report the net amount between the corrected invoice and the credit memo. For example, if you have an invoice of 1000 and a credit memo of 200, in the service corrective Intrastat entry, you must report 800 in the amount. However, in the Italian version of Microsoft Dynamics NAV, when you use the Get Intrastat entry functionality, the service corrective entry displays the credit memo amount incorrectly.
This issue occurs in the following products:
  • The Italian version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
  • The Italian version of Microsoft Dynamics NAV 2009 R2
  • The Italian version of Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1)

↑ Back to the top


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.


↑ Back to the top




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 SetVATEntryFilters function in the table (263) as follows:
    Existing code
    ...
    SETRANGE(Type,VATEntry.Type::Sale);

    // Delete the following lines.
    IF IntrastatJnlBatch."Corrective Entry" THEN
    SETRANGE("Document Type",VATEntry."Document Type"::"Credit Memo")
    ELSE
    // End of the deleted lines.

    SETRANGE("Document Type",VATEntry."Document Type"::Invoice);
    END;
    ...
    Replacement code
    ...
    SETRANGE(Type,VATEntry.Type::Sale);

    // Add the following line.
    IF NOT IntrastatJnlBatch."Corrective Entry" THEN
    // End of the added line.

    SETRANGE("Document Type",VATEntry."Document Type"::Invoice);
    END;
    ...
  2. Change the code in the VAT Entry - OnPreDataItem trigger in the report (594) as follows:
    Existing code
    ...
    SETRANGE(Type,Type::Sale);

    // Delete the following lines.
    IF IntrastatJnlBatch."Corrective Entry" THEN
    SETRANGE("Document Type","Document Type"::"Credit Memo")
    ELSE
    // End of the deleted lines.

    SETRANGE("Document Type","Document Type"::Invoice);
    SETRANGE("Operation Occurred Date",StartDate,EndDate);
    ...
    Replacement code
    ...
    SETRANGE(Type,Type::Sale);

    // Add the following line.
    IF NOT IntrastatJnlBatch."Corrective Entry" THEN
    // End of the added line.

    SETRANGE("Document Type","Document Type"::Invoice);
    SETRANGE("Operation Occurred Date",StartDate,EndDate);
    ...
  3. Change the code in the InsertEUServiceLine function in the report (594) as follows:
    Add the following variable:
    • Name: IntrastatAmount
    • DataType: Decimal
    Existing code
    ...
    // Delete the following lines.
    WITH IntrastatJnlLine DO BEGIN
    INIT;
    "Line No." := "Line No." + 10000;
    "Source Type" := "Source Type"::"VAT Entry";
    "Source Entry No." := "VAT Entry"."Entry No.";
    IF IntrastatJnlLine.Type = IntrastatJnlLine.Type::Shipment THEN
    "Country/Region of Payment Code" := GetIntrastatCountryCode("VAT Entry"."Country/Region Code")//new line
    ELSE
    "Country/Region of Payment Code":= CompanyInfo."Country/Region Code";
    ValidateSourceEntryNo("Source Entry No.");
    IF IntrastatJnlBatch."Corrective Entry" THEN BEGIN
    "Custom Office No." := CustomsOfficeNo;
    "Corrected Intrastat Report No." := CorrectedIntrastatRepNo;
    END;
    INSERT;
    END;
    // End of the deleted lines.
    ...
    Replacement code
    ...
    WITH IntrastatJnlLine DO BEGIN
    SETRANGE("Service Tariff No.","VAT Entry"."Service Tariff No.");
    IF NOT FINDFIRST THEN BEGIN
    INIT;
    "Line No." := "Line No." + 10000;
    "Source Type" := "Source Type"::"VAT Entry";
    "Source Entry No." := "VAT Entry"."Entry No.";
    ValidateSourceEntryNo("Source Entry No.");
    IF IntrastatJnlBatch."Corrective Entry" THEN BEGIN
    "Custom Office No." := CustomsOfficeNo;
    "Corrected Intrastat Report No." := CorrectedIntrastatRepNo;
    END;
    INSERT;

    END ELSE BEGIN
    IntrastatAmount := Amount;
    ValidateSourceEntryNo("VAT Entry"."Entry No.");
    Amount := Amount + IntrastatAmount;
    MODIFY;
    END;
    END;
    ...

Prerequisites

You must have one of the following products installed to apply this hotfix:
  • The Italian version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
  • The Italian version of Microsoft Dynamics NAV 2009 R2
  • The Italian version of Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1)


Removal information

You cannot remove this hotfix.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


References

VSTF DynamicsNAV SE: 238983

↑ Back to the top


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.

↑ Back to the top


Keywords: kb, kbqfe, kbmbsquickpub, kbmbsmigrate, kbmbspartner, kbmbscodefix, kbsurveynew

↑ Back to the top

Article Info
Article ID : 2548011
Revision : 4
Created on : 9/20/2018
Published on : 9/20/2018
Exists online : False
Views : 280