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 Prod. Order Rtng Comment Line already exists" error message when you refresh a firm planned production order in Microsoft Dynamics NAV 2009

"The Prod. Order Rtng Comment Line already exists" error message when you refresh a firm planned production order 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 delete a routing that has operation comments in a planning worksheet in Microsoft Dynamics NAV 2009. When you refresh the firm planned production order in the planning worksheet, you receive the following error message:
The Prod. Order Rtng Comment Line already exists.
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 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. 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, use the following steps:
  1. Change the code in the TransferRouting function in the Calculate Prod. Order Codeunit (99000773) as follows:
    Existing code
    ...
    ProdOrderRtngLine."Starting Date" := ProdOrderLine."Starting Date";
    ProdOrderRtngLine."Ending Time" := ProdOrderLine."Ending Time";
    ProdOrderRtngLine."Ending Date" := ProdOrderLine."Ending Date";
    ProdOrderRtngLine.UpdateDatetime;
    ProdOrderRtngLine.INSERT;
    UNTIL RtngLine.NEXT = 0;

    // Delete the following line.
    TransferTaskInfo(ProdOrderLine);
    // End of the deleted line.
    ...
    Replacement code
    ...
    ProdOrderRtngLine."Starting Date" := ProdOrderLine."Starting Date";
    ProdOrderRtngLine."Ending Time" := ProdOrderLine."Ending Time";
    ProdOrderRtngLine."Ending Date" := ProdOrderLine."Ending Date";
    ProdOrderRtngLine.UpdateDatetime;
    ProdOrderRtngLine.INSERT;
    UNTIL RtngLine.NEXT = 0;
    ...
  2. Change all the code in the TransferTaskInfo function in the Calculate Prod. Order Codeunit (99000773) as follows:
    TransferTaskInfo@3(VAR FromProdOrderRtngLine@1000 : Record 5409;VersionCode@1010 : Code[20]);
    RtngLineTool.SETRANGE("Routing No.",FromProdOrderRtngLine."Routing No.");
    RtngLineTool.SETRANGE("Operation No.",FromProdOrderRtngLine."Operation No.");
    RtngLineTool.SETRANGE("Version Code",VersionCode);
    IF RtngLineTool.FIND('-') THEN
    REPEAT
    ProdOrderRoutTool.TRANSFERFIELDS(RtngLineTool);
    ProdOrderRoutTool.Status := FromProdOrderRtngLine.Status;
    ProdOrderRoutTool."Prod. Order No." := FromProdOrderRtngLine."Prod. Order No.";
    ProdOrderRoutTool."Routing Reference No." := FromProdOrderRtngLine."Routing Reference No.";
    ProdOrderRoutTool.INSERT;
    UNTIL RtngLineTool.NEXT = 0;

    RtngLinePersonnel.SETRANGE("Routing No.",FromProdOrderRtngLine."Routing No.");
    RtngLinePersonnel.SETRANGE("Operation No.",FromProdOrderRtngLine."Operation No.");
    RtngLinePersonnel.SETRANGE("Version Code",VersionCode);
    IF RtngLinePersonnel.FIND('-') THEN
    REPEAT
    ProdOrderRtngPersonnel.TRANSFERFIELDS(RtngLinePersonnel);
    ProdOrderRtngPersonnel.Status := FromProdOrderRtngLine.Status;
    ProdOrderRtngPersonnel."Prod. Order No." := FromProdOrderRtngLine."Prod. Order No.";
    ProdOrderRtngPersonnel."Routing Reference No." := FromProdOrderRtngLine."Routing Reference No.";
    ProdOrderRtngPersonnel.INSERT;
    UNTIL RtngLinePersonnel.NEXT = 0;

    RtngLineQltyMeas.SETRANGE("Routing No.",FromProdOrderRtngLine."Routing No.");
    RtngLineQltyMeas.SETRANGE("Operation No.",FromProdOrderRtngLine."Operation No.");
    RtngLineQltyMeas.SETRANGE("Version Code",VersionCode);
    IF RtngLineQltyMeas.FIND('-') THEN
    REPEAT
    ProdOrderRtngQltyMeas.TRANSFERFIELDS(RtngLineQltyMeas);
    ProdOrderRtngQltyMeas.Status := FromProdOrderRtngLine.Status;
    ProdOrderRtngQltyMeas."Prod. Order No." := FromProdOrderRtngLine."Prod. Order No.";
    ProdOrderRtngQltyMeas."Routing Reference No." := FromProdOrderRtngLine."Routing Reference No.";
    ProdOrderRtngQltyMeas.INSERT;
    UNTIL RtngLineQltyMeas.NEXT = 0;

    RtngComment.SETRANGE("Routing No.",FromProdOrderRtngLine."Routing No.");
    RtngComment.SETRANGE("Operation No.",FromProdOrderRtngLine."Operation No.");
    RtngComment.SETRANGE("Version Code",VersionCode);
    IF RtngComment.FIND('-') THEN
    REPEAT
    ProdOrderRtngComment.TRANSFERFIELDS(RtngComment);
    ProdOrderRtngComment.Status := FromProdOrderRtngLine.Status;
    ProdOrderRtngComment."Prod. Order No." := FromProdOrderRtngLine."Prod. Order No.";
    ProdOrderRtngComment."Routing Reference No." := FromProdOrderRtngLine."Routing Reference No.";
    ProdOrderRtngComment.INSERT;
  3. Change the code in the InsertProdOrderLine function in the Carry Out Action Codeunit (99000813) as follows:
    Existing code
    ...
    DimMgt.MoveJnlLineDimToProdDocDim(
    FromJnlLineDim,DATABASE::"Prod. Order Line",
    ProdOrder.Status,ProdOrder."No.",
    ProdOrderLine."Line No.",0);

    // Delete the following line.
    CalcProdOrder.TransferTaskInfo(ProdOrderLine);
    // End of the deleted line.

    ReserveReqLine.TransferPlanningLineToPOLine(ReqLine,ProdOrderLine,ReqLine."Net Quantity (Base)",FALSE);
    IF ReqLine.Reserve AND NOT (ProdOrderLine.Status = ProdOrderLine.Status::Planned) THEN
    ReserveBindingOrderToProd(ProdOrderLine,ReqLine);

    ProdOrderLine.MODIFY;
    ...
    Replacement code
    ...
    DimMgt.MoveJnlLineDimToProdDocDim(
    FromJnlLineDim,DATABASE::"Prod. Order Line",
    ProdOrder.Status,ProdOrder."No.",
    ProdOrderLine."Line No.",0);

    CalcProdOrder.TransferTaskInfo(ProdOrderLine);

    ReserveReqLine.TransferPlanningLineToPOLine(ReqLine,ProdOrderLine,ReqLine."Net Quantity (Base)",FALSE);
    IF ReqLine.Reserve AND NOT (ProdOrderLine.Status = ProdOrderLine.Status::Planned) THEN
    ReserveBindingOrderToProd(ProdOrderLine,ReqLine);

    ProdOrderLine.MODIFY;
    ...
  4. Change the code in the TransferRouting function in the Carry Out Action Codeunit (99000813) as follows:
    Existing code
    ...
    ProdOrderRtngLine."Expected Operation Cost Amt." := PlanningRtngLine."Expected Operation Cost Amt.";
    ProdOrderRtngLine."Expected Capacity Ovhd. Cost" := PlanningRtngLine."Expected Capacity Ovhd. Cost";
    ProdOrderRtngLine."Expected Capacity Need" := PlanningRtngLine."Expected Capacity Need";

    ProdOrderRtngLine.UpdateDatetime;
    ProdOrderRtngLine.INSERT;
    UNTIL PlanningRtngLine.NEXT = 0;
    ...
    Replacement code
    ...
    ProdOrderRtngLine."Expected Operation Cost Amt." := PlanningRtngLine."Expected Operation Cost Amt.";
    ProdOrderRtngLine."Expected Capacity Ovhd. Cost" := PlanningRtngLine."Expected Capacity Ovhd. Cost";
    ProdOrderRtngLine."Expected Capacity Need" := PlanningRtngLine."Expected Capacity Need";

    ProdOrderRtngLine.UpdateDatetime;
    ProdOrderRtngLine.INSERT;

    // Add the following line.
    CalcProdOrder.TransferTaskInfo(ProdOrderRtngLine,ReqLine."Routing Version Code");
    // End of the added line.

    UNTIL PlanningRtngLine.NEXT = 0;
    ...

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 Usefor other considerations.

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2788020
Revision : 1
Created on : 1/7/2017
Published on : 3/15/2013
Exists online : False
Views : 265