Microsoft KB Archive Search

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.

  1. Home
  2. The Intrastat journal lines are not suggested as expected when you run the Undo Shipment functionality in Microsoft Dynamics NAV 2009

The Intrastat journal lines are not suggested as expected when you run the Undo Shipment functionality in Microsoft Dynamics NAV 2009

View products that this article applies to.

This article applies to Microsoft Dynamics NAV 2009 for all countries and all language locales.

↑ Back to the top

Symptoms

Assume that you run the Undo Shipment functionality on the posted shipment for a non-invoiced sales order in Microsoft Dynamics NAV 2009 R2 and in Microsoft Dynamics NAV 2009 Service Pack 1 (SP1). However, when you run the Get Item Ledger Entries report (594) to prepare Intrastat lines, the Intrastat journal lines are not suggested as expected. The reversed sales shipment entries are still suggested.

↑ 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, change the code in the Get Item Ledger Entries report (594). To do this, follow these steps:
  1. Change the code of the DataItemTableView property as follows:
    Existing code
    ...
      DataItemTableView=SORTING(Country/Region Code,Entry Type,Posting Date)
                        WHERE(Entry Type=FILTER(Purchase|Sale|Transfer));
    ...
    Replacement code
    ...
      DataItemTableView=SORTING(Country/Region Code,Entry Type,Posting Date)
                        WHERE(Entry Type=FILTER(Purchase|Sale|Transfer),
                              Correction=CONST(No));
    ...
  2. Change the code in the Item Ledger Entry - OnAfterGetRecord trigger as follows:
    Existing code
    ...
       IntrastatJnlLine2.SETRANGE("Source Entry No.","Entry No.");
       IF IntrastatJnlLine2.FINDFIRST THEN
         CurrReport.SKIP;
      
       CASE TRUE OF
         "Drop Shipment":
           BEGIN
             IF ("Country/Region Code" = CompanyInfo."Country/Region Code") OR
                ("Country/Region Code" = '')
    ...
    Replacement code
    ...
       IntrastatJnlLine2.SETRANGE("Source Entry No.","Entry No.");
       IF IntrastatJnlLine2.FINDFIRST THEN
         CurrReport.SKIP;

    // Add the following lines.  
       IF "Entry Type" IN ["Entry Type"::Sale,"Entry Type"::Purchase] THEN BEGIN
         ItemLedgEntry.RESET;
         ItemLedgEntry.SETCURRENTKEY("Document No.","Document Type");
         ItemLedgEntry.SETRANGE("Document No.","Document No.");
         ItemLedgEntry.SETRANGE("Item No.","Item No.");
         ItemLedgEntry.SETRANGE(Correction,TRUE);
         ItemLedgEntry.SETRANGE("Document Type","Document Type"::"Sales Shipment");
         IF NOT ItemLedgEntry.ISEMPTY THEN
           CurrReport.SKIP;

         ItemLedgEntry.SETRANGE("Document Type","Document Type"::"Sales Return Receipt");
         IF NOT ItemLedgEntry.ISEMPTY THEN
           CurrReport.SKIP;

         ItemLedgEntry.SETRANGE("Document Type","Document Type"::"Purchase Receipt");
         IF NOT ItemLedgEntry.ISEMPTY THEN
           CurrReport.SKIP;

         ItemLedgEntry.SETRANGE("Document Type","Document Type"::"Purchase Return Shipment");
         IF NOT ItemLedgEntry.ISEMPTY THEN
           CurrReport.SKIP;
       END;
    //End of the added lines. 

       CASE TRUE OF
         "Drop Shipment":
           BEGIN
             IF ("Country/Region Code" = CompanyInfo."Country/Region Code") OR
                ("Country/Region Code" = '')
    ...

Prerequisites

You must have one of the following products installed to apply this hotfix:
  • Microsoft Dynamics NAV 2009 R2
  • Microsoft Dynamics NAV 2009 Service Pack 1

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

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: kbsurveynew, kbmbsquickpub, kbmbscodefix, kbqfe, kbmbspartner, kbnoloc, kb, kbmbsmigrate

↑ Back to the top

Article Info
Article ID : 2554765
Revision : 5
Created on : 9/26/2018
Published on : 9/26/2018
Exists online : False
Views : 213