The planning results are illogical when you run the "Calculate Regenerative Plan" function on a planning worksheet if you use safety stock in Microsoft Dynamics NAV 2009 SP1

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 install this hotfix, change the code in the CopyProdLines function in the Copy Production Order Document codeunit (99000854) as follows:

1. Create a new function "ShallSupplyBeClosed". To do this, follow these steps:
   1. Add a local variable as follows:

      CloseSupply@1003 : Boolean;
      

   2. Add the code for the ShallSupplyBeClosed function. The code of created function is as follows:

      ShallSupplyBeClosed@89(SupplyInventoryProfile@1000 : Record 99000853;DemandDueDate@1001 : Date;IsReorderPointPlanning@1002 : Boolean) : Boolean;
      
      IF SupplyInventoryProfile."Is Exception Order" THEN BEGIN
        IF TempSKU."Reordering Policy" = TempSKU."Reordering Policy"::"Lot-for-Lot" THEN
          // Supply within Reorder Cycle will be summed up with exception order.
          CloseSupply := CALCDATE(TempSKU."Reorder Cycle",SupplyInventoryProfile."Due Date") <DemandDueDate
        ELSE
          // Only demand in the same day as the exception will be summed up.
          CloseSupply := SupplyInventoryProfile."Due Date" <> DemandDueDate;
      END ELSE
        CloseSupply := IsReorderPointPlanning;
      
      EXIT(CloseSupply);
      

2. Change the code of the PlanItem function as follows:
   Existing code

    ...
            NextState::MatchQty:
               BEGIN
                 IF Supply."Untracked Quantity" < Demand."Untracked Quantity" THEN BEGIN
   // Delete the following lines.
                   IF (Supply."Is Exception Order" AND (Supply."Due Date" <> Demand."Due Date")) OR
                       (IsReorderPointPlanning AND NOT Supply."Is Exception Order")
                   THEN
   // The end of the deleted lines.
                     NextState := NextState::CloseSupply
                   ELSE
   ...
   
   

   Replacement code

   ...
             NextState::MatchQty:
               BEGIN
                 IF Supply."Untracked Quantity" < Demand."Untracked Quantity" THEN BEGIN
   // Add the following line.
                   IF ShallSupplyBeClosed(Supply,Demand."Due Date",IsReorderPointPlanning) THEN
   
                     NextState := NextState::CloseSupply
                   ELSE
   ...
   

Prerequisites

You must have Microsoft Dynamics NAV 2009 SP1 installed to apply this hotfix. 

Removal information

You cannot remove this hotfix.