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.

Records from the "Standard Cost Worksheet" table are not removed when you delete the item from the item card in Microsoft Dynamics NAV


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 an item has at least one line in the "Standard Cost Worksheet" form in Microsoft Dynamics NAV 2009 with Service Pack 1 (SP1) or in Microsoft Dynamics NAV 5.0 with SP1. When you delete the item from the item card, records from the "Standard Cost Worksheet" table are not removed. Therefore, if you then try to run the Implement Standard Cost Changes function in the "Standard Cost Worksheet" form for this item, you receive the following error message:
Item No. 'Item_number' does not exist.
In this error message, the Item_number placeholder represents an actual item number.

↑ 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 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 work around this problem, change the code in the following objects as follows:
  • he Item table (27)
  • he Work Center table (99000754)
  • he Machine Center table (99000758)

  1. Change the code in the OnDelete trigger of the Item table (27) as follows:
    • Add a local variable as follows:
      • Name: StdCostWksh
      • Type: Record
      • SubType: 5841
    • Change the code as follows:
      Existing code
      ...
      IF ItemJnlLine.FIND('-') THEN
      ERROR(Text023,TABLECAPTION,"No.",ItemJnlLine.TABLECAPTION);

      RequisitionLine.SETCURRENTKEY(Type,"No.");
      RequisitionLine.SETRANGE(Type,RequisitionLine.Type::Item);
      RequisitionLine.SETRANGE("No.","No.");
      ...
      Replacement code
      ...
      IF ItemJnlLine.FIND('-') THEN
      ERROR(Text023,TABLECAPTION,"No.",ItemJnlLine.TABLECAPTION);

      StdCostWksh.RESET;
      StdCostWksh.SETRANGE(Type,StdCostWksh.Type::Item);
      StdCostWksh.SETRANGE("No.","No.");
      IF NOT StdCostWksh.ISEMPTY THEN
      ERROR(Text023,TABLECAPTION,"No.",StdCostWksh.TABLECAPTION);

      RequisitionLine.SETCURRENTKEY(Type,"No.");
      RequisitionLine.SETRANGE(Type,RequisitionLine.Type::Item);
      RequisitionLine.SETRANGE("No.","No.");
      ...
  2. Change the code in the OnDelete trigger of the Work Center table (99000754) as follows:
    • Add a local variable as follows:
      • Name: StdCostWksh
      • Type: Record
      • SubType: 5841
    • Change the code as follows:
      Existing code
      ...
      IF CapLedgEntry.FIND('-') THEN
      ERROR(Text010,TABLECAPTION,"No.",CapLedgEntry.TABLECAPTION);

      CalendarEntry.SETCURRENTKEY("Capacity Type","No.");
      CalendarEntry.SETRANGE("Capacity Type",CalendarEntry."Capacity Type"::"Work Center");
      CalendarEntry.SETRANGE("No.","No.");
      ...
      Replacement code
      ...
      IF CapLedgEntry.FIND('-') THEN
      ERROR(Text010,TABLECAPTION,"No.",CapLedgEntry.TABLECAPTION);

      StdCostWksh.RESET;
      StdCostWksh.SETRANGE(Type,StdCostWksh.Type::"Work Center");
      StdCostWksh.SETRANGE("No.","No.");
      IF NOT StdCostWksh.ISEMPTY THEN
      ERROR(Text010,TABLECAPTION,"No.",StdCostWksh.TABLECAPTION);

      CalendarEntry.SETCURRENTKEY("Capacity Type","No.");
      CalendarEntry.SETRANGE("Capacity Type",CalendarEntry."Capacity Type"::"Work Center");
      CalendarEntry.SETRANGE("No.","No.");
      ...
  3. Change the code in the OnDelete trigger of the Machine Center table (99000758) as follows:
    • Add a local variable as follows:
      • Name: StdCostWksh
      • Type: Record
      • SubType: 5841
    • Change the code as follows:
      Existing code
      ...
      IF CapLedgEntry.FIND('-') THEN
      ERROR(Text007,TABLECAPTION,"No.",CapLedgEntry.TABLECAPTION);

      CalendarEntry.SETRANGE("Capacity Type",CalendarEntry."Capacity Type"::"Machine Center");
      CalendarEntry.SETRANGE("No.","No.");
      CalendarEntry.DELETEALL;
      ...
      Replacement code
      ...
      IF CapLedgEntry.FIND('-') THEN
      ERROR(Text007,TABLECAPTION,"No.",CapLedgEntry.TABLECAPTION);

      StdCostWksh.RESET;
      StdCostWksh.SETRANGE(Type,StdCostWksh.Type::"Machine Center");
      StdCostWksh.SETRANGE("No.","No.");
      IF NOT StdCostWksh.ISEMPTY THEN
      ERROR(Text007,TABLECAPTION,"No.",StdCostWksh.TABLECAPTION);

      CalendarEntry.SETRANGE("Capacity Type",CalendarEntry."Capacity Type"::"Machine Center");
      CalendarEntry.SETRANGE("No.","No.");
      CalendarEntry.DELETEALL;
      ...

Prerequisites

You must have Microsoft Dynamics NAV 2009 SP1 or Microsoft Dynamics NAV 5.0 SP1 installed to apply this hotfix.

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: kbsurveynew, kbnoloc, kbmbsquickpub, kbmbscodefix, kbqfe, kbmbsmigrate, kberrmsg, kb, kbmbspartner

↑ Back to the top

Article Info
Article ID : 2305227
Revision : 2
Created on : 9/20/2018
Published on : 9/20/2018
Exists online : False
Views : 495