A double-click on a node in the tree view section or in the flat view section opens window 2 with the BOM position views. This window consists of the tabs listed below.
-
Multi Position View
-
Single Bulk Material View
-
Single Tag Material View
-
Multi Status View
These tabs are described in detail in the following chapters.
Select the Include Sub Tree Nodes of <path> check box to query the positions of the selected node and all its sub-nodes. In this case, the node path is also displayed in the Path field to show to which node the position is assigned. This feature can be used in the multi position view and in the single position view.
The Path field in the single position view is displayed in the picture below.
By default, the check box is not checked and only the positions of the selected node are displayed.
Use Incompl. Specs
You may want to enter manual BOM positions by providing diameter, component type (short code), option code, specification name (spec code), even though the specification is not complete.
If you select the Use incompl. Specs check box, then
-
specs that do not contain any spec items can be used in creating a BOM position
-
all short codes and option codes defined on S.10.08 Short Codes can be used in creating a BOM position independent of the selected spec
-
all sizes of the nominal size table defined on S.40.01 Nominal Sizes, which are assigned to the spec header geometrics of the selected spec, can be used in creating a BOM position
-
once a short code is entered, you will be forced to enter the corresponding sizes
Once a short code is entered, the Unit field will be updated with the corresponding quantity unit.
If the ZB_IN_SPEC project default is set to Y, the Use Incompl. Specs check box is checked when you open window 2 of B.20.03.
Issue Status dropdown list
The value displayed in the Issue Status field indicates the display and sort order of the positions with regard to the assigned issue status. The available values are listed below.
-
Highest - Positions with the highest available issue status of the selected node are displayed.
-
Lowest - Positions with the lowest available issue status of the selected node are displayed.
-
All desc - All positions are displayed in descending order of the assigned issue status.
-
All asc - All positions are displayed in ascending order of the assigned issue status.
-
Selected - Positions with the selected issue status are displayed. When selecting this option, a further dropdown list appears where you must select a particular issue status. This list shows all issue statuses pre-defined on B.10.08.
-
Best Quantity - All positions are displayed with the highest issue status assigned.
With the setting of the ZB_ISSUE project default, you can define which issue status option is used on B.20.03. The available values are:
-
ALL_ASC
-
ALL_DESC
-
HIGHEST
-
LOWEST
-
BEST_QUANTITY
-
SELECTED
If ZB_ISSUE is not set, HIGHEST will be used as the default. You can manually change the displayed issue status by selecting a value from the dropdown list in the Issue Status field.
Cascading LOV Option
The cascading LOV feature automatically calls the LOV of a field when you navigate to this field and the field is empty. To activate this feature, set the ZB_AUTOLOV project default to Y. This feature is available on all position view tabs. The cascading LOV feature is available for the following fields:
-
Spec Code
-
Short Code
-
Option Code
-
Group
-
Part
-
Commodity Code
-
Ident Code
For example, you create a new BOM position and click into the Spec Code field, and the LOV is automatically opened. Select a spec from the list and click OK to enter the spec in the field. This will move the cursor to the Short Code field and automatically open the LOV, displaying the short codes available for the selected spec. And so forth. If you click Cancel in the LOV box, the cascading LOV functionality is interrupted.
The cascading LOVs can be used independent of the setting of the ZB_AUTOLOV project default, automatically as described above or manually if ZB_AUTOLOV is set to N. In this case, using the same example, after selecting the spec code from the LOV, the LOV in the Short Code field will be limited to the short codes assigned to the selected spec.