You cannot create lines for kit components in the requisition worksheet in the North American version of Microsoft Dynamics NAV 2009

Symptoms

You cannot create lines for kit components in the requisition worksheet in the North American version of Microsoft Dynamics NAV 2009. However, the lines for the kit components can be created in the requisition worksheet in the North American version of Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1).
This problem occurs in the following products:

The North American version of Microsoft Dynamics NAV 2009 R2
The North American version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)

Cause

This problem occurs because certain code that manages the kit components in the Inventory Profile Offsetting codeunit (99000854) from the Planning Update Rollup for Microsoft Dynamics NAV 5.0 Service Pack 1 is missing.

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.

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, change the code in the DemandtoInvProfile function in the Inventory Profile Offsetting codeunit (99000854) as follows:
Existing code 1

...
        PlanningComponent.SETCURRENTKEY("Item No.","Variant Code","Location Code","Due Date");
        PlanningComponent.SETRANGE("Item No.",Item."No.");
        Item.COPYFILTER("Location Filter",PlanningComponent."Location Code");
        Item.COPYFILTER("Variant Filter",PlanningComponent."Variant Code");
        PlanningComponent.SETFILTER("Due Date",'>%1&<=%2',0D,ToDate);

        // Delete the following line.
        IF PlanningComponent.FIND('-') THEN

          REPEAT
            InventoryProfile.INIT;
            InventoryProfile."Line No." := NextLineNo;
            InventoryProfile."Item No." := Item."No.";
            InventoryProfile.TransferFromPlanComponent(PlanningComponent,TempItemTrkgEntry);
...

Replacement code 1

...
 PlanningComponent.SETCURRENTKEY("Item No.","Variant Code","Location Code","Due Date");
        PlanningComponent.SETRANGE("Item No.",Item."No.");
        Item.COPYFILTER("Location Filter",PlanningComponent."Location Code");
        Item.COPYFILTER("Variant Filter",PlanningComponent."Variant Code");
        PlanningComponent.SETFILTER("Due Date",'>%1&<=%2',0D,ToDate);

        // Add the following line.
        IF PlanningComponent.FIND('-') THEN BEGIN

          REPEAT
            InventoryProfile.INIT;
            InventoryProfile."Line No." := NextLineNo;
            InventoryProfile."Item No." := Item."No.";
            InventoryProfile.TransferFromPlanComponent(PlanningComponent,TempItemTrkgEntry);

Existing code 2

...
            InventoryProfile.TransferFromPlanComponent(PlanningComponent,TempItemTrkgEntry);
            IF InventoryProfile.IsSupply THEN
              InventoryProfile.ChangeSign;
            InventoryProfile.INSERT;
          UNTIL PlanningComponent.NEXT = 0;

        TransferReqLine.SETCURRENTKEY(Type,"No.","Variant Code","Transfer-from Code","Transfer Shipment Date");
        TransferReqLine.SETRANGE("Replenishment System",TransferReqLine."Replenishment System"::Transfer);
        TransferReqLine.SETRANGE(Type,TransferReqLine.Type::Item);
        TransferReqLine.SETRANGE("No.",Item."No.");
        Item.COPYFILTER("Location Filter",TransferReqLine."Transfer-from Code");
...

Replacement code 2

...
            InventoryProfile.TransferFromPlanComponent(PlanningComponent,TempItemTrkgEntry);
            IF InventoryProfile.IsSupply THEN
              InventoryProfile.ChangeSign;
            InventoryProfile.INSERT;
          UNTIL PlanningComponent.NEXT = 0;

        // Add the following lines.
        END ELSE BEGIN
          KitSalesLine.SETCURRENTKEY("Document Type",Type,"No.","Variant Code","Location Code","Shipment Date");
          KitSalesLine.SETRANGE("Document Type",KitSalesLine."Document Type"::Order);
          KitSalesLine.SETRANGE(Type,KitSalesLine.Type::Item);
          KitSalesLine.SETRANGE("No.",Item."No.");
          Item.COPYFILTER("Location Filter",KitSalesLine."Location Code");
          Item.COPYFILTER("Variant Filter",KitSalesLine."Variant Code");
          KitSalesLine.SETFILTER("Outstanding Qty. (Base)",'<>0');
          KitSalesLine.SETFILTER("Shipment Date",'>%1&<=%2',0D,ToDate);
          IF KitSalesLine.FINDFIRST THEN
            REPEAT
              InventoryProfile.INIT;
              InventoryProfile."Line No." := LineNo;
              InventoryProfile.TransferFromKitSalesLine(KitSalesLine,TempItemTrkgEntry);
              IF
               InventoryProfile.IsSupply THEN
                InventoryProfile.ChangeSign;
              InventoryProfile.INSERT;
              LineNo := LineNo + 1;
            UNTIL KitSalesLine.NEXT = 0;
        END;
        // End of the lines.

        TransferReqLine.SETCURRENTKEY(Type,"No.","Variant Code","Transfer-from Code","Transfer Shipment Date");
        TransferReqLine.SETRANGE("Replenishment System",TransferReqLine."Replenishment System"::Transfer);
        TransferReqLine.SETRANGE(Type,TransferReqLine.Type::Item);
        TransferReqLine.SETRANGE("No.",Item."No.");
        Item.COPYFILTER("Location Filter",TransferReqLine."Transfer-from Code");
...

Prerequisites

You must have one of the following products installed to apply this hotfix:

The North American version of Microsoft Dynamics NAV 2009 R2
The North American version of Microsoft Dynamics NAV 2009 Service Pack 1

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.