The Order Planning function calculates incorrect "Qty. to Order" suggestions when you use a Make-to-Order environment in Microsoft Dynamics NAV

View products that this article applies to.

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

Symptoms

The Order Planning function calculates incorrect "Qty. to Order" suggestions when you use a Make-to-Order environment in Microsoft Dynamics NAV. This problem occurs if you use multilevel bill of material (BOM).
This problem occurs in the following products:

Microsoft Dynamics NAV 2009 R2
Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
Microsoft Dynamics NAV 2009
Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1)

↑ Back to the top

Cause

The system uses recursive function which always changes quantity for found item (The BOM creates "tree" where some items can occur one or more times). However, this is an incorrect behavior, because all children for updated item should be either deleted or updated.

↑ 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, 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:

Create a local function UpdateRelatedComponent in the codeunit (99000809):

...
LOCAL PROCEDURE UpdateRelatedComponent@15(ParentReqLine@1000 : Record 246);
WITH PlanningComponent DO BEGIN
SETCURRENTKEY("Worksheet Template Name","Worksheet Batch Name","Worksheet Line No.","Item No.");
SETRANGE("Worksheet Line No.",ParentReqLine."Line No.");
SETFILTER("Item No.",'<>%1','');
SETFILTER("Expected Quantity",'<>0');
SETFILTER("Planning Level Code",'<>0');
IF FIND('-') THEN
REPEAT
IF LineHasBeenCreated(ChildReqLine,PlanningComponent) THEN BEGIN
UpdateRelatedComponent(ChildReqLine);
IF ChildReqLine.Quantity <> "Expected Quantity" THEN BEGIN
// qty has to be updated, there is a new need of component
ChildReqLine.BlockDynamicTracking(Blocked);
ChildReqLine.VALIDATE(Quantity,ChildReqLine.Quantity - "Expected Quantity");
ChildReqLine.MODIFY;

// updating qty of component for parent
VALIDATE("Quantity per","Quantity per");
MODIFY;
END ELSE
// line will be recreated
ChildReqLine.DELETE(TRUE);
END;
UNTIL NEXT = 0;
END;
...

Add the following parameters in the function:

Name: PlanningComponent; DataType: Record (99000829)
Name: ChildReqLine; DataType: Record (246)

Create a local function LineHasBeenCreated in the codeunit (99000829):

...
LOCAL PROCEDURE LineHasBeenCreated@18(VAR ChildReqLine@1000 : Record 246;PlanningComponent@1001 : Record 99000829) : Boolean;
WITH ChildReqLine DO BEGIN
SETCURRENTKEY("Worksheet Template Name","Journal Batch Name",Type,"No.");
SETRANGE("Worksheet Template Name",PlanningComponent."Worksheet Template Name");
SETRANGE("Journal Batch Name",PlanningComponent."Worksheet Batch Name");
SETRANGE(Type,Type::Item);
SETRANGE("No.",PlanningComponent."Item No.");
SETRANGE("Variant Code",PlanningComponent."Variant Code");
SETRANGE("Ref. Order Type","Ref. Order Type"::"Prod. Order");
SETRANGE("Ref. Order Status",PlanningComponent."Ref. Order Status");
SETRANGE("Ref. Order No.",PlanningComponent."Ref. Order No.");
SETFILTER("Planning Level",'>%1',0);
EXIT(FINDFIRST);
END;
...

Change the code in the InsertPlanningLine function the codeunit (99000809) as follows:
Existing code

...
 IF ReqLine2."Planning Level" < ReqLine."Planning Level" THEN
ReqLine2."Planning Level" := ReqLine."Planning Level";

ReqLine2.MODIFY; 
...

Replacement code

...
 IF ReqLine2."Planning Level" <ReqLine."Planning Level" THEN
ReqLine2."Planning Level" := ReqLine."Planning Level";

// the ReqLine2 can have children which has to be delete or updated
// Add the following line.
UpdateRelatedComponent(ReqLine2);

ReqLine2.MODIFY;  
...

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)
Microsoft Dynamics NAV 2009
Microsoft Dynamics NAV 5.0 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