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.

Duplicate reservation entries are generated when you run the planning engine for an item for two times in Microsoft Dynamics NAV 2009


View products that this article applies to.

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

↑ Back to the top


Symptoms

Assume that you run the planning engine for an item with a demand included in Microsoft Dynamics NAV 2009. You run the planning engine for the item again. In this situation, if the demand is not included in the second time running, duplicate reservation entries are generated. 
Note This problem occurs whether the locations use the warehouse functionality or not.
This problem occurs in the following products:
  • Microsoft Dynamics NAV 2009 R2
  • Microsoft Dynamics NAV 2009 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 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 CloseReservEntry function in the Reservation Engine Mgt. codeunit (99000831) as follows: 
    Existing code
    ...
    ReservEntry2.MODIFY;
    ReservEntry2."Quantity (Base)" :=
    ReservMgt.MatchSurplus(ReservEntry2,SurplusReservEntry,ReservEntry2."Quantity (Base)",NOT ReservEntry2.Positive,
    AvailabilityDate,Item."Order Tracking Policy");
    IF ReservEntry2."Quantity (Base)" = 0 THEN BEGIN
    ReservEntry2.DELETE(TRUE);
    END ELSE BEGIN
    ReservEntry2.MODIFY;

    IF Item."Order Tracking Policy" = Item."Order Tracking Policy"::"Tracking & Action Msg." THEN BEGIN
    ModifyActionMessageDating(ReservEntry2);
    IF DeleteAll THEN
    ReservMgt.IssueActionMessage(ReservEntry2,FALSE,ReservEntry)
    ELSE
    ...
    Replacement code
    ...
    ReservEntry2.MODIFY;
    ReservEntry2."Quantity (Base)" :=
    ReservMgt.MatchSurplus(ReservEntry2,SurplusReservEntry,ReservEntry2."Quantity (Base)",NOT ReservEntry2.Positive,
    AvailabilityDate,Item."Order Tracking Policy");
    IF ReservEntry2."Quantity (Base)" = 0 THEN BEGIN
    ReservEntry2.DELETE(TRUE);
    END ELSE BEGIN

    // Add the following line.
    ReservEntry2.VALIDATE("Quantity (Base)");

    ReservEntry2.MODIFY;

    IF Item."Order Tracking Policy" = Item."Order Tracking Policy"::"Tracking & Action Msg." THEN BEGIN
    ModifyActionMessageDating(ReservEntry2);
    IF DeleteAll THEN
    ReservMgt.IssueActionMessage(ReservEntry2,FALSE,ReservEntry)
    ELSE
    ...
  2. Add a new key in the Inventory Profile table (99000853) as follows: 
    { ;Source Type,Source Order Status,Source ID,Source Batch Name,Source Ref. No.,Source Prod. Order Line,IsSupply,Due Date }
  3. Add a new local parameter in the DeleteTracking function in the Inventory Profile Offsetting codeunit (99000854) as follows:
    Existing code
    LOCAL PROCEDURE DeleteTracking@25(VAR SKU@1000 : Record 5700;ToDate@1001 : Date);
    Replacement code
    LOCAL PROCEDURE DeleteTracking@25(VAR SKU@1000 : Record 5700;ToDate@1001 : Date;VAR SupplyInventoryProfile@1002 : Record 99000853);
  4. Add a new local variable in the DeleteTracking function in the Inventory Profile Offsetting codeunit (99000854), and then specify the variable as follows:
    • Name: ResEntryWasDelete
    • DataType: Boolean
  5. Change the code in the DeleteTracking function in the Inventory Profile Offsetting codeunit (99000854) as follows:
    Existing code
    ...
    IF FIND('-') THEN
    REPEAT
    IF (("Reservation Status" <> "Reservation Status"::Reservation) AND
    ("Expected Receipt Date" <= ToDate) AND
    ("Shipment Date" <= ToDate)) OR
    ((Binding = Binding::"Order-to-Order") AND ("Shipment Date" <= ToDate))
    THEN BEGIN

    // Delete the following lines.
    ActionMsgEntry.SETRANGE("Reservation Entry","Entry No.");
    DELETE;
    ActionMsgEntry.DELETEALL;
    END;
    // End of the lines.

    UNTIL NEXT = 0;
    END;
    ...
    Replacement code
    ...
    IF FIND('-') THEN
    REPEAT
    IF (("Reservation Status" <> "Reservation Status"::Reservation) AND
    ("Expected Receipt Date" <= ToDate) AND
    ("Shipment Date" <= ToDate)) OR
    ((Binding = Binding::"Order-to-Order") AND ("Shipment Date" <= ToDate))
    THEN BEGIN

    // Add the following lines.
    ResEntryWasDeleted := TRUE;
    DELETE;
    END ELSE
    ResEntryWasDeleted := CloseTracking(ReservEntry,SupplyInventoryProfile,ToDate);

    IF ResEntryWasDeleted THEN BEGIN
    ActionMsgEntry.SETRANGE("Reservation Entry","Entry No.");
    ActionMsgEntry.DELETEALL;
    END;
    // End of the lines.

    UNTIL NEXT = 0;
    END;
    ...
  6. Add a new CloseTracking function in the Inventory Profile Offsetting codeunit (99000854) as follows:
    LOCAL PROCEDURE CloseTracking@92(ReservEntry@1000 : Record 337;VAR SupplyInventoryProfile@1001 : Record 99000853;ToDate@1002 : Date) : Boolean;
    VAR
    xSupplyInventoryProfile@1003 : Record 99000853;
    ReservationEngineMgt@1004 : Codeunit 99000831;
    Closed@1005 : Boolean;


    WITH ReservEntry DO BEGIN
    IF "Reservation Status" <> "Reservation Status"::Tracking THEN
    EXIT(FALSE);

    xSupplyInventoryProfile.COPY(SupplyInventoryProfile);
    Closed := FALSE;

    IF ("Expected Receipt Date" <= ToDate) AND
    ("Shipment Date" > ToDate)
    THEN BEGIN
    // tracking exists with demand in future
    SupplyInventoryProfile.SETCURRENTKEY(
    "Source Type","Source Order Status","Source ID","Source Batch Name","Source Ref. No.","Source Prod. Order Line",IsSupply);
    SupplyInventoryProfile.SETRANGE("Source Type","Source Type");
    SupplyInventoryProfile.SETRANGE("Source Order Status","Source Subtype");
    SupplyInventoryProfile.SETRANGE("Source ID","Source ID");
    SupplyInventoryProfile.SETRANGE("Source Batch Name","Source Batch Name");
    SupplyInventoryProfile.SETRANGE("Source Ref. No.","Source Ref. No.");
    SupplyInventoryProfile.SETRANGE("Source Prod. Order Line","Source Prod. Order Line");
    SupplyInventoryProfile.SETRANGE("Due Date",0D,ToDate);

    IF NOT SupplyInventoryProfile.ISEMPTY THEN BEGIN
    // demand is either deleted as well or will get Surplus status
    ReservMgt.CloseReservEntry(ReservEntry,FALSE,FALSE);
    Closed := TRUE;
    END;
    END;
    END;

    SupplyInventoryProfile.COPY(xSupplyInventoryProfile);
    EXIT(Closed);
  7. Change the code in the PlanItem function in the Inventory Profile Offsetting codeunit (99000854) as follows:
    Existing code
    ...
    // Preliminary clean of tracking
    IF DemandExists OR SupplyExists THEN

    // Delete the following line.
    DeleteTracking(TempSKU,ToDate);

    MatchAttributes(Supply,Demand);

    // Calculate initial inventory
    ...
    Replacement code
    ...
    // Preliminary clean of tracking
    IF DemandExists OR SupplyExists THEN

    // Add the following line.
    DeleteTracking(TempSKU,ToDate,Supply);

    MatchAttributes(Supply,Demand);

    // Calculate initial inventory
    ...

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 (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


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

↑ Back to the top

Article Info
Article ID : 2583878
Revision : 2
Created on : 9/25/2018
Published on : 9/25/2018
Exists online : False
Views : 255