Specifies whether to immediately assign and calculate low-level codes for each component in the product structure. If you have large amounts of data, this function can have negative effects on the program's performance, for example during automatic cost adjustment. Note that this is not a retroactive function, so it is a good idea to consider the use of this facility beforehand.

As an alternative to the automatic calculation that occurs dynamically if the field is selected, you can run the Calculate Low-Level Code batch job from the Manufacturing menu by clicking Product Design, Calculate Low-Level Code.

You can assign a low-level code to each part in the product structure or the indented BOM. The top final assembly level is denoted as level 0 - the end item. The higher the low-level code number, the lower the item is in the hierarchy. For example, end items have low-level code 0, and the item parts that go into the assembly of the end item have low-level codes 1, 2, 3, and so on. The result is the planning of component parts coordinated with the requirements of all higher-level part numbers. When you calculate a plan, the BOM is exploded in the planning worksheet, and the gross requirements for level 0 are passed down the planning levels as gross requirements for the next planning level.

Important
If you do not select the Dynamic Low-Level Code field, then you must run the Calculate Low-Level Code batch job before you calculate a supply plan (the Calculate Plan batch job).

Note
Even with the Dynamic Low-Level Code field selected, the low-level codes of component items are not changed dynamically if a parent BOM is deleted or set to non-certified. This may result in difficulty to add new items to the end of the product structure as it might exceed the maximum number of low-level codes. Therefore, for large product structures that reach the low-level code limit, it is encouraged to run the Calculate Low Level Code batch job frequently to maintain the structure .

Tip

See Also