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.

"Max. Level of BOM Structure on 50 is too high. Current Item No. [BOM_Number]. End BOM Header No. [BOM_Number]. Level [BOM_level]" error message when you run the Calculate Low Level Code function 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

Consider the following scenario in Microsoft Dynamics NAV 2009:
  • The Dynamic Low Level Code check box is not selected in the Manufacturing Setup dialog box.
  • You create a production bill of material (BOM) version for a specific production BOM.
  • You set the Status box to Closed for the production BOM version.
  • You run the Calculate Low-Level Code function.
In this scenario, you receive the following error message:
Max. Level of BOM Structure on 50 is too high. Current Item No. BOM_Number. End BOM Header No. BOM_Number. Level BOM_level.
However, the system should exclude the production BOM from a low level calculation if you set its version status to Closed.
This problem occurs in the following products:
  • Microsoft Dynamics NAV 2009 R2
  • Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
  • Microsoft Dynamics NAV 2009

↑ 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 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 Calculate Low-Level Code codeunit (99000793). To do this, follow these steps:
  1. Change the code in the CalcLevels function. To do this, follow these steps:
    1. Add a new local variable, and then specify the variable as follows:
      • Name: ProductionBOMVersion
      • DataType: Record 99000779
    2. Add a new local variable, and then specify the variable as follows:
      • Name: CalculateDeeperLevel
      • DataType: Boolean
    3. Change the code as follows:
      Existing code
      ...
      50,Item."No.",BomHeaderNo,Level);


      // Delete the following line.
      IF ProdBOMHeader.Status = ProdBOMHeader.Status::Certified THEN BEGIN

      ProdBOMHeader."Low-Level Code" :=
      ...
      Replacement code
      ...
      50,Item."No.",BomHeaderNo,Level);

      // Add the following lines.
      IF ProdBomComponent."Version Code" <> '' THEN BEGIN
      ProductionBOMVersion.GET(ProdBomComponent."Production BOM No.",ProdBomComponent."Version Code");
      CalculateDeeperLevel := ProductionBOMVersion.Status = ProductionBOMVersion.Status::Certified;
      END ELSE
      CalculateDeeperLevel := ProdBOMHeader.Status = ProdBOMHeader.Status::Certified;

      IF CalculateDeeperLevel THEN BEGIN
      // End of the added lines.

      ProdBOMHeader."Low-Level Code" :=
      ...
  2. Change the code in the RecalcLowerLevels function. To do this, follow these steps:
    1. Add a new local variable, and then specify the variable as follows:
      • Name: ProductionBOMVersion
      • DataType: Record 99000779
    2. Add a new local variable, and then specify the variable as follows:
      • Name: CalculateDeeperLevel
      • DataType: Boolean
    3. Change the code as follows:
      Existing code
      ...
      REPEAT
      // add 2 spaces for alignment to next lines
      CASE ProdBOMLine.Type OF
      ProdBOMLine.Type::Item:
      BEGIN
      EntityPresent := CompItem.GET(ProdBOMLine."No.");
      IF EntityPresent OR (NOT IgnoreMissingItemsOrBOMs) THEN
      SetRecursiveLevelsOnItem(CompItem,LowLevelCode,IgnoreMissingItemsOrBOMs);
      END;
      ProdBOMLine.Type::"Production BOM":
      BEGIN
      EntityPresent := CompBOM.GET(ProdBOMLine."No.");
      IF EntityPresent OR (NOT IgnoreMissingItemsOrBOMs) THEN
      SetRecursiveLevelsOnBOM(CompBOM,LowLevelCode,IgnoreMissingItemsOrBOMs);
      END
      END;
      // end of adding 2 spaces
      UNTIL ProdBOMLine.NEXT = 0;
      ...
      Replacement code
      ...
      REPEAT

      // Add the following lines.
      IF ProdBOMLine."Version Code" <> '' THEN BEGIN
      ProductionBOMVersion.GET(ProdBOMLine."Production BOM No.",ProdBOMLine."Version Code");
      CalculateDeeperLevel := ProductionBOMVersion.Status <> ProductionBOMVersion.Status::Closed;
      END ELSE BEGIN
      CompBOM.GET(ProdBOMLine."Production BOM No.");
      CalculateDeeperLevel := CompBOM.Status <> CompBOM.Status::Closed;
      END;

      // closed BOMs are skipped
      IF CalculateDeeperLevel THEN
      // End of the added lines.

      CASE ProdBOMLine.Type OF
      ProdBOMLine.Type::Item:
      BEGIN
      EntityPresent := CompItem.GET(ProdBOMLine."No.");
      IF EntityPresent OR (NOT IgnoreMissingItemsOrBOMs) THEN
      SetRecursiveLevelsOnItem(CompItem,LowLevelCode,IgnoreMissingItemsOrBOMs);
      END;
      ProdBOMLine.Type::"Production BOM":
      BEGIN
      EntityPresent := CompBOM.GET(ProdBOMLine."No.");
      IF EntityPresent OR (NOT IgnoreMissingItemsOrBOMs) THEN
      SetRecursiveLevelsOnBOM(CompBOM,LowLevelCode,IgnoreMissingItemsOrBOMs);
      END
      END;
      UNTIL ProdBOMLine.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
  • Microsoft Dynamics NAV 2009

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

↑ Back to the top

Article Info
Article ID : 2589758
Revision : 1
Created on : 1/7/2017
Published on : 3/23/2012
Exists online : False
Views : 266