Wrong Operation Date in 340 Model in the Spanish version of Microsoft Dynamics NAV 2009

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:

1. Change the code in Keys in the Sales Shipment Header table (110) as follows:
   Existing code

   ...  
   {    ;Bill-to Customer No.                     }
       {    ;Sell-to Customer No.,External Document No. }
       {    ;Sell-to Customer No.,No.                 }
   
   // Delete the following line.
   {    ;Posting Date                             }
   // End o the deleted line.
   
     }
     FIELDGROUPS
     {
   ...

   Replacement code

   ... 
   {    ;Bill-to Customer No.                     }
       {    ;Sell-to Customer No.,External Document No. }
       {    ;Sell-to Customer No.,No.                 }
   
   // Add the following line.
   {    ;Posting Date,Order No.                   }
   // End of the added line.
   
     }
     FIELDGROUPS
     {
   ...

2. Change the code in GetSalesShipmentDate function in the Make 340 Declaration report (10743) as follows:
   Existing code

   ...  
   IF SalesShipmentLine.GET(ItemLedgEntry."Document No.",ItemLedgEntry."Document Line No.") THEN BEGIN
                     IF SalesShipmentHeader.GET(SalesShipmentLine."Document No.") THEN BEGIN
                       IF SalesShipmentHeader."Order No." <> '' THEN BEGIN
   
   // Delete the following line.
   SalesShipmentHeader.SETCURRENTKEY("Order No.");
   // End of the deleted line.
   
                         SalesShipmentHeader.SETRANGE("Order No.", SalesShipmentHeader."Order No.");
                         IF SalesShipmentHeader.FINDFIRST THEN
                           EXIT(SalesShipmentHeader."Posting Date");
   ...

   Replacement code

   ... 
   IF SalesShipmentLine.GET(ItemLedgEntry."Document No.",ItemLedgEntry."Document Line No.") THEN BEGIN
                     IF SalesShipmentHeader.GET(SalesShipmentLine."Document No.") THEN BEGIN
                       IF SalesShipmentHeader."Order No." <> '' THEN BEGIN
   
   // Add the following line.
   SalesShipmentHeader.SETCURRENTKEY("Posting Date");
   // End of the added line.
   
                         SalesShipmentHeader.SETRANGE("Order No.", SalesShipmentHeader."Order No.");
                         IF SalesShipmentHeader.FINDFIRST THEN
                           EXIT(SalesShipmentHeader."Posting Date");
   ...
   
   

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.