"Routing line of a production order is referring to non-existent next/previous operation" error message when you run the production schedule in Microsoft Dynamics NAV 2009

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

Symptoms

When you run the production schedule in Microsoft Dynamics NAV 2009, you receive the following error message:
Routing line of a production order is referring to non-existent next/previous operation.
However, the error message does not specify where the broken production routing is located. 
This problem occurs in the following products:
  • Microsoft Dynamics NAV 2009 R2
  • Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)

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.



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 CreateOutboundXML function in the Production Schedule Management codeunit (5500) as follows:
    Existing code
    ...
    ScheduleOrder.SETDESTINATION(OStream);
    ScheduleOrder.InitializeHeader(InitialProdOrder1,Editable1);
    IF ScheduleOrder.EXPORT THEN BEGIN
    ProdSchedSetup.GanttXML.CREATEINSTREAM(IStream);
    OutboundXML.load(IStream);

    // Delete the following lines.
    END ELSE
    ERROR(Text002);
    // End of the lines.

    END
    END;
    END;

    PROCEDURE ConvertFromDDMMYY@2(DateIn@1000 : Text[30]) : Text[30];
    ...
    Replacement code
    ...
    ScheduleOrder.SETDESTINATION(OStream);
    ScheduleOrder.InitializeHeader(InitialProdOrder1,Editable1);
    IF ScheduleOrder.EXPORT THEN BEGIN
    ProdSchedSetup.GanttXML.CREATEINSTREAM(IStream);
    OutboundXML.load(IStream);

    // Add the following lines.
    END ELSE BEGIN
    CLEAR(ProdSched);
    ERROR(Text002);
    END;
    // End of the lines.

    END
    END;
    END;

    PROCEDURE ConvertFromDDMMYY@2(DateIn@1000 : Text[30]) : Text[30];
    ...
  2. Change the code in the Export Production Schedule XMLport (5500) as follows:
    Existing code 1
    ...
    { [{86CA14B5-EAF7-4A37-ADCC-ED8FB40C86E7}];6 ;PrevOperationNo ;Element ;Field ;
    DataType=Code;
    SourceField=Prod. Order Routing Line::Previous Operation No. }
    ...
    Replacement code 1
    ...
    { [{86CA14B5-EAF7-4A37-ADCC-ED8FB40C86E7}];6 ;PrevOperationNo ;Element ;Field ;
    DataType=Code;
    SourceField=Prod. Order Routing Line::Previous Operation No.;
    Export::OnBeforePassField=BEGIN
    IF CheckOperationNo("Prod. Order Routing Line","Prod. Order Routing Line"."Previous Operation No.") THEN
    ERROR(Text000,"Prod. Order Routing Line"."Prod. Order No.","Prod. Order Routing Line".FIELDCAPTION("Previous Operation No."),
    "Prod. Order Routing Line"."Previous Operation No.");
    END;
    }
    ...
    Existing code 2
    ...
    { [{81A88AA3-07E1-43BF-B7A4-6F00E038BD51}];6 ;NextOperationNo ;Element ;Field ;
    DataType=Code;
    SourceField=Prod. Order Routing Line::Next Operation No. }
    ...
    Replacement code 2
    ...
    { [{81A88AA3-07E1-43BF-B7A4-6F00E038BD51}];6 ;NextOperationNo ;Element ;Field ;
    DataType=Code;
    SourceField=Prod. Order Routing Line::Next Operation No.;
    Export::OnBeforePassField=BEGIN
    IF CheckOperationNo("Prod. Order Routing Line","Prod. Order Routing Line"."Next Operation No.") THEN
    ERROR(Text000,"Prod. Order Routing Line"."Prod. Order No.","Prod. Order Routing Line".FIELDCAPTION("Next Operation No."),
    "Prod. Order Routing Line"."Next Operation No.");
    END;
    }
    ...
    Existing code 3
    ...
    xProdOrderNo@1001 : Code[20];
    xProdOrderStatus@1002 : 'Simulated,Planned,Firm Planned,Released,Finished';
    xRoutingNo@1005 : Code[20];
    ...
    Replacement code 3
    ...
    xProdOrderNo@1001 : Code[20];
    xProdOrderStatus@1002 : 'Simulated,Planned,Firm Planned,Released,Finished';
    xRoutingNo@1005 : Code[20];
    Text000@1101 : TextConst 'ENU=The routing in production order number %1 uses %2 %3, which does not exist.';
    ...
  3. Add a new function in the Export Production Schedule XMLport (5500) as follows:
    PROCEDURE CheckOperationNo@15(ProdOrderRoutingLine@1001 : Record 5409;OperationNo@1000 : Code[20]) : Boolean;

    VAR
    CheckedProdOrderRoutingLine@1002 : Record 5409;
    BEGIN
    IF OperationNo = '' THEN
    EXIT(FALSE);
    WITH CheckedProdOrderRoutingLine DO BEGIN
    RESET;
    SETCURRENTKEY("Prod. Order No.","Routing Reference No.",Status,"Routing No.","Operation No.");
    SETRANGE("Prod. Order No.",ProdOrderRoutingLine."Prod. Order No.");
    SETRANGE("Routing Reference No.",ProdOrderRoutingLine."Routing Reference No.");
    SETRANGE(Status,ProdOrderRoutingLine.Status);
    SETRANGE("Routing No.",ProdOrderRoutingLine."Routing No.");
    SETRANGE("Operation No.",OperationNo);
    EXIT(ISEMPTY);
    END;
    END;

    BEGIN
    END

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.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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.
Propriétés

ID d'article : 2697850 - Dernière mise à jour : 29 juin 2012 - Révision : 1

Commentaires