smartplant materials bill of materials (bom) b.20.03...

SmartPlant Materials Bill of Materials (BOM) B.20.03 Advanced BOM Maintenance

Version 2011 SP1 (7.0.1) September 2010 DMAR1-PE-200063B

Copyright Copyright © 2006-2010 Intergraph Corporation. All Rights Reserved.

Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and international treaty, and may not be provided or otherwise made available without proper authorization.

Restricted Rights Legend Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was developed at private expense and is “restricted computer software” submitted with restricted rights in accordance with subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal Acquisition Regulations (“FAR”) and its successors, and is unpublished and all rights are reserved under the copyright laws of the United States. For units of the Department of Defense (“DoD”): This is “commercial computer software” as defined at DFARS 252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3. Unpublished – rights reserved under the copyright laws of the United States. Intergraph Corporation Huntsville, Alabama 35894-0001

Warranties and Liabilities All warranties given by Intergraph Corporation about equipment or software are set forth in your purchase contract, and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such warranties. Intergraph believes the information in this publication is accurate as of its publication date.

The information and the software discussed in this document are subject to change without notice and are subject to applicable technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document.

The software discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this license.

No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by Intergraph or its affiliated companies. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.

Trademarks Intergraph, the Intergraph logo, PDS, SmartPlant, SmartSketch, FrameWorks, INtools, MARIAN, and IntelliShip are registered trademarks and SupportModeler and SupportManager are trademarks of Intergraph Corporation. Microsoft and Windows are registered trademarks of Microsoft Corporation. Other brands and product names are trademarks of their respective owners.

Table of Contents

Table of Contents Preface .................................................................................................................................5

Introduction ........................................................................................................................6

Advanced BOM Maintenance (B.20.03) ..........................................................................7

Tree Section ..................................................................................................................9 Operations ......................................................................................................................... 10

Node Property and Attributes Section ........................................................................17 Property Page .................................................................................................................... 18 Attribute Page ................................................................................................................... 20 Operations ......................................................................................................................... 20

Flat BOM Controls and Flat BOM Section ................................................................21 Display Flat BOM ............................................................................................................. 22 Operations ......................................................................................................................... 31

Search and Advanced Search Section ........................................................................40 Search ................................................................................................................................ 40 Advanced Search .............................................................................................................. 41 Search Results ................................................................................................................... 42 Operations ......................................................................................................................... 42

Adv. Maint. BOM– Add Root Node/Add Child Node ...............................................44 Property Page .................................................................................................................... 44 Attribute Page ................................................................................................................... 45 Operations ......................................................................................................................... 45

Adv. Maint. BOM – Copy-Paste Node .......................................................................47 Copy Structure (B.20.03.08) ............................................................................................. 47 Copy Positions (B.20.03.14) ............................................................................................. 49

BOM Position Views ........................................................................................................52

Multi Position View ....................................................................................................55 Single Bulk Material View .........................................................................................77

Position Values ................................................................................................................. 83 Commodity Details ........................................................................................................... 85 Ident Values ...................................................................................................................... 86

Single Tag Material View ...........................................................................................90 Ident Values ...................................................................................................................... 95 Position Values ................................................................................................................. 96

Multi Status View .......................................................................................................98

BOM Procedures / Macros ..............................................................................................99

Execution of BOM Procedures / Macros ..................................................................100

Ident History ..................................................................................................................110

SmartPlant Materials Bill of Materials (BOM) B.20.03 Advanced BOM Maintenance 3

Table of Contents

4 SmartPlant Materials Bill of Materials (BOM) B.20.03 Advanced BOM Maintenance

Compare Ident Values ..............................................................................................112 Operations ....................................................................................................................... 114

Flashback ..................................................................................................................115 Operations ....................................................................................................................... 116

Ident History .............................................................................................................118 Operations ....................................................................................................................... 119

Preface

Preface This document is a user’s guide for SmartPlant Materials.

Send documentation comments or suggestions to [email protected].


mailto:[email protected]?subject=Documentation%20Comments

Introduction

Introduction The new Advanced BOM Maintenance (B.20.03) user interface provides better capabilities and functionalities for BOM maintenance. The objective of the new UI is to provide an easy-to-use UI to the user along with easy and short steps for various BOM maintenance-related activities.

The new UI provides a single place for various advanced functionalities in an easy-to-use manner. Some of those functionalities are:

• Creating several BOM nodes, editing, and deleting them in one operation through the BOM Flat View.

• Moving BOM sub trees through simple Cut and Paste commands.

• Locating a particular node in the BOM tree through Search functionality.

• Advanced search further enables the user to search and locate a particular node depending on its structure type, or description, position/position values, or Ident values, etc.

• Flat view of the BOM also enables the user to query the nodes in the BOM.

• Provides all position views (Multi Positions, Single Position, and Single Tag Material view) attached to a BOM node in a single window.

• Navigation among different position views (Multi Positions, Single Position, and Single Tag Material view) for a selected position value.

• Provides option to view BOM position views while navigating in the BOM Tree view.

• Dynamic order functionality is available for Multi position view, Position values, Commodity details, and Ident values.

• Ident values are displayed in the form of a Tree structure.

The new rich UI provides very intuitive commands and steps for various BOM-related functions. Each operation needs fewer number of steps and commands. The new UI is intended to replace the old Maintain BOM (B.20.01) UI.


Advanced BOM Maintenance (B.20.03)

Advanced BOM Maintenance (B.20.03) The figure below details the appearance of the “Advanced BOM Maintenance (B.20.03)” UI.

Tree Section

Flat BOM Controls

and Flat BOM

Section

Node Property and

Attributes Section

Fig 1.1 – Advanced BOM Maintenance B.20.03

As shown in the above figure, the complete UI is divided into the following major sections.

Search and

Advanced Search Section

• Tree Section: Displays the BOM as a tree structure and enables the user to carry out various operations on the BOM trees structure such as Add/Delete/Move nodes.

• Flat BOM Controls and Flat BOM Section: Displays the BOM as a flat structure and enables the user to carry out various operations on the BOM trees structure such as Add/Update Node Names/Delete nodes. The Flat BOM controls additionally help the user to expand the view either to the right or to the left or to both sides. It also provides functionality to arrange the view by sorting the various columns in an ascending or descending manner.

• Node Property and Attributes Section: Displays all properties and associated attributes and their values of a node selected either in the tree or the flat BOM.



• Search and Advanced Search Section: This section enables the user to search for a node in the tree or in the flat BOM structure. A node can be searched either by its name (Simple Search) or by using other values like description, structure type, commodity code, attribute value, etc (Advanced Search).



Tree Section This section presents the BOM in a tree structure. It behaves like Windows Explorer in the Windows environment and supports operations like Add, Remove, Cut and Paste, and Refresh through a pop-up menu. The BOM tree displays all the nodes created in the logged in project and discipline as well as nodes in other disciplines of the project. All operations like Add/Delete/Cut and Paste are applicable for the nodes of the logged in project and discipline, not for the nodes of other disciplines. However, you can add a node under the nodes of other disciplines. Depending upon the locked/unlocked and same discipline/other discipline attributes, tree nodes are represented by different icons. The following table lists the node icons and their meaning.

Icon Meaning

Yellow Folder

Node belongs to the currently logged in discipline and is not locked (released).

Yellow Lock

Node belongs to the currently logged in discipline and is locked (released).

Red Folder Node does not belong to the currently logged in discipline and is not locked (released).

Red Lock Node does not belong to the currently logged in discipline and is locked (released).

Blue Folder Node is locked from B.40.31 Manually Lock BOM.

All the operations like Add/Delete/Cut and Paste are supported through a pop-up menu. By right-clicking the mouse, the user will get a pop-up menu. A desired action can be selected from the pop-up menu. Details of these operations are described in subsequent sections.



Yellow Icons Indicate Nodes from Logged In

Discipline

Red Icons Indicate Nodes from Other

Disciplines

Fig 1.2 – Tree Section of Advanced BOM Maintenance B.20.03

Operations • Add Root Node: This option will be enabled only when more than one

master node (Root Nodes) are allowed in the discipline (Refer to Valid Settings A.60.63 and Project Defaults A.20.12). On selection of this option from the pop up menu, the user will be provided with an “Add Root Node” child window where he will be able to specify node name, type, and other properties and attribute values (Refer to “Advanced BOM Maintenance – Add Root Node/Add Child Node”). On successful completion, this will add a node at the root level of the existing BOM.



• Add Child Node: On selection of this option from the pop-up menu, the user will be provided with an “Add Child Node” child window where he will be able to specify node name, type, and other properties and attribute values (Refer to “Advanced BOM Maintenance – Add Root Node/Add Child Node”). On successful completion, this will add a node below the node currently selected by the user in the tree.

• Delete Node: This option allows the user to delete a node from the BOM tree. The node currently selected and all its child nodes will be deleted. Please note that if the node that has been selected for deletion has a sub tree under it (the tree of child nodes), the whole sub tree along with the selected node will be deleted. If you need to preserve the nodes below the selected node, then first move them (Refer to Cut and Paste operation) to the appropriate location in the tree and then delete the node that needs to be deleted. When you select delete from the pop-up menu, the software will ask you to confirm the delete operation. See the figure below:

Fig 1.3: Delete Menu Item and Delete Confirmation Message

You can either abort the delete operation by clicking the “Cancel” button, or you can continue the delete operation by clicking the “Continue” button. A node cannot be deleted if it has been released (Release indicator set to yes. See the release indicator on the ‘Property Page’ in the “Node Property and Attributes Section), or if the node



belongs to the non-login discipline. If you try to delete a released node or if node belongs to the non-login discipline, the software will display an error message as shown below:

Fig 1.4: Delete is not possible



• Cut and Paste: These menu items together will simulate the move node operation. Select the node that you want to move elsewhere in the tree, and then select the ‘Cut’ menu item. The software will identify the selected node as the source node to move to some other destination in the tree. Now select the destination node in the tree (the node under which you want to move the previously selected (source node) node). After selecting the destination node, select the ‘Paste’ menu item from the pop-up menu. This will bring the source node under the selected (destination) node.

Fig 1.5: Cut and Paste Menu Items



If the project default ‘Free BOM Structure?’ Parameter in E+PI (BOM) parameter list is set to yes (Refer to A.20.12 Project Defaults), any node can be moved under any other node in the tree. The node type (Structure Type) does not matter in this case. But, if the parameter is set to no and the BOM is built using the structure type hierarchy defined (Refer to B.10.07 Node Type Hierarchy), the destination node type (structure type) is validated. In that case, a node can only be moved (pasted) under the node with the same type as the parent node of the source node.

Fig 1.6: Cannot move the node when parent type is not the same



• Copy and Paste: These menu items together will simulate the operation of copying a selected node at some other location of the BOM. Select the node that you want to copy elsewhere in the tree, and then select the ‘Copy’ menu item. The software will identify the selected node as the source node to copy to some other destination in the tree. Now select the destination node in the tree (the node under which you want to copy the previously selected (source node) node). After selecting the destination node, select the ‘Paste’ menu item from the pop-up menu. This will pop up the Copy-Paste option window as shown below.

Fig 1.5: Copy and Paste Options

If the user selects ‘Copy Structure’, in that case, only the structure of the selected node will be copied under the destination node. In case the user opts for ‘Copy Positions’, the positions from the source node will be copied to the destination node.

In the above child window, if the user selects the Copy Structure option, the software invokes B.20.03.08 with the required fields already completed with the Source and Destination information. The UI B.20.03.08 captures additional options in order to copy the structure from the Source node to the Destination node. (Refer to Adv. BOM Maint. – Copy-Paste Node)

On the other hand, if the user selects the Copy Positions option, the software invokes B.20.03.14 with the required fields already completed with the Source and Destination information. The UI for B.20.03.14 captures additional options in order to copy the positions of the Source node to the Destination node. (Refer to Adv. BOM Maint. – Copy-Paste Node).



• List Download: This pop-up menu option is used to Export the multiposition data into either OMI format or Excel format at the tree level. When the user selects this pop-up menu option, the List Download B.20.01.44 form will appear. It will contain two radio buttons that will allow the user to specify the predefined format to export the position data. The two options are OMI Export and Excel Export, respectively. When the user selects OMI Export, the multi position data will be exported into a predefined OMI format. On the other hand, if the user selects Excel Export, the multi position data will be exported to a predefined Excel format.

• Attach Documents: This pop-up menu option is used to attach or link documents to the positions and to the nodes in the BOM. When the user selects this pop-up menu option, D.10.21 Attached Documents screen will appear. Here the user can see all documents that have been attached to the node or to the position. The user can also attach or remove the documents to a BOM node or to a position of a node.



Node Property and Attributes Section This section displays the property values and attributes values of a BOM node selected in either the Tree or in the flat BOM section. This section is organized as a collection of two tab pages – “Property” and “Attributes”. This section also supports operations like editing of the BOM node property values and attribute values, and un-releasing a released node. The user can apply these operations to the currently selected BOM node in either the tree or in the flat view of the BOM. These operations are applicable only to the BOM nodes of the logged in project and discipline. The figure below displays both the tab pages of this section. The user can navigate between the pages by clicking a tab.

Attributes Attached to

the Node

Property and Attribute

Tabs

Fig 1.7: Property and Attribute Tab Pages



Property Page This tab page displays the following property values of a selected node:

• Path: Complete path of the selected node starting from the root node level.

• Name: Name of the selected BOM node.

• Node Type: Structure Type (Refer to B.10.03 ) of the selected BOM Node.

• Generated Name: Name of the selected BOM node generated from the user defined algorithm (Refer to the ‘Description Rule’ field in the ‘Node Types’ block of B.10.03).

• Short Description and Description: Comments attached to the selected node.

• QTY Factor: The structure quantity of the node. The quantity 1 is the default.

• Rev1 and Rev2: Revision values.

• Released: This indicator shows that the selected BOM node is released (if checked) or not (un-checked).

The user can edit the values of the Name, Short Description, Description, and QTY Factor fields. The fields like Path, Node Type, Generated Name, Rev1, Rev2, and Released are non-editable fields. You cannot edit their values in any way. However, all the above mentioned editable fields also become non-editable if the currently selected node:

• Belongs to some other discipline than the logged in discipline.

• Is a Released node.

• If the Issue Status or List Status columns are set to Visible in the Flat BOM.



In the case of the released node, the name field displays the text in a red color indicating that the node is released and hence is not editable. This also enables the “Unrelease” button, which you can use to un-release the currently selected BOM node. If the currently selected BOM node is not a released one, this button (“Unrelease”) remains unavailable. See the following figure:

Fig 1.8: A Released/Locked node shown on the Property tab

Red Color Text represents a node that is

Released.

‘Unrelease’ button is enabled.



Attribute Page This tab page displays all the attributes of the selected node. The list of attributes contains both the attributes mapped to the structure type (Refer to B.10.03 Assign Attributes Section) of the selected node as well as the attributes inherited from the parent node(s). Some attributes may have a list of values (LOV) attached to them or some specific values defined for them. For such attributes, the user will have to select/specify one of the values from that list. The LOV tool bar button gets enabled when the cursor is kept in the value field for such an attribute. If nothing is defined or attached to the attribute, the user can enter any value. The user can edit the values of the attributes. However, the values of attributes become non-editable if the currently selected node :

• Belongs to some other discipline than the logged in discipline.

• Is a Released/Locked node.

Operations • Edit Node Properties

The user can edit the property values of a node only if it is not released or it does not belong to some other discipline. In order to edit the values, select the node either in the BOM tree or in the flat view of the BOM. Once the node is selected, the property and attribute tab pages will be populated with the current values for the selected node. Change the values for the editable properties (Name, Short Description, Description, QTY Factor, etc) and press F10 or click the Save toolbar button ( ). This will save the changes. The Short Description and Description field values can also be changed:

1. Using the NLS tool bar button. Keep the focus either in the Short Description or Description fields, and click the NLS toolbar button. The system opens a child window with the current values of the Short Description and Description for the node for all NLS values. Change the Short Description or Description and press F10 or click the Save toolbar button ( ). This will save the changes.

2. Directly changing the values in the Short Description or Description fields.



• Edit Attribute Values

The user can edit the attribute values of a node only if it is not released or it does not belong to some other discipline. In order to edit the values, select the node either in the BOM tree or in the flat view of the BOM. Once the node is selected, the property and attribute tab pages will be populated with the current values for the selected node. Change the values for the attribute that you want to edit and press F10 or click the Save toolbar button ( ). This will save the changes.

Note

• If an attribute has an LOV attached to it, you need to pick one of the values from that LOV. You cannot change an attribute value to a value not in the LOV. The LOV toolbar button becomes enabled when the cursor moves to the value field of an attribute with an LOV attached to it. See the figure below: LOV toolbar

button is enabled when the attribute has an LOV

attached to it.

Fig 1.9: Node attribute with an LOV attached to it

Flat BOM Controls and Flat BOM Section The Flat BOM Controls and Flat BOM section provide a set of functionalities to work on the BOM in an easy manner. The main purpose of this section is to provide a spreadsheet type utility where the user can work on a bigger part of the tree. Unlike the Tree section where the add/edit/delete operations can be done for one node at a time, this section allows the user to create several nodes or tree branches, modify the names of several BOM nodes, and delete the BOM node in one operation. The user can type in the name of a parent node and then a child node, and so on in one row to create the branch in the tree. The other controls provide:

• Facility to extend the spreadsheet further towards the right, hiding the Property/Attribute section.

• Facility to extend the spreadsheet further towards the left, hiding the Tree section.

• Whether to display the flat view or not for the BOM tree.

• Ordering the flat view with respect to selected columns and displaying the columns accordingly.



• The configuration management functionality enables the user to:

• Hide / Display desired columns.

• Add CIP (Custom Installable Procedures) fields in the Flat BOM.

• Increase / Decrease space between columns.

• Drag and Drop columns within the flat BOM structure.

• Resize the columns within the flat BOM structure.

Display Flat BOM Consider the BOM tree as described below:

• Area1

• Unit1

• Line1

• Line2

• Unit2

• Line3

• Line4

• Area2

• Unit3

• Unit 4

• Line7

• Unit23Line8

The above tree when converted into a flat view will appear in a tabular manner as represented by the table given below:

Area1 Unit1 Line1

Area1 Unit1 Line2

Area1 Unit2 Line3

Area1 Unit2 Line4

Area2 Unit3

Area2 Unit 4 Line7

Area2 Unit 4 Unit23Line8



Basically, each leaf node is traversed up to the root. The whole path creates a row in the flat view. In the flat view, this row is represented from left to right starting from the root node up to the leaf. In our example tree, ‘Line1’ is a leaf that has ‘Unit1’ as a parent and ‘Area1’ as a grandparent node. So the row will be created starting from Area1 to Line1. Area1 -> Unit1 -> Line1 (See the first row in the above table.)

There is no child under the Unit3 node; hence, Unit3 itself is a leaf. So the row will be created like: Area2 -> Unit3

The figure below displays a flat BOM view:

Fig 1.10: Flat view of a BOM Tree

In the flat view shown above, the labels of column change according to the parameter set in the project default under the ‘Free BOM Structure?’ E+PI (BOM) parameter list. If it is set to Y (yes) (Refer to A.20.12 Project Defaults), the labels will appear as Level 1, Level 2……to Level10, representing the level of the tree. This means under the Level 1 column, all nodes that are at level 1 of the tree will appear. But if the Parameter is set to N (no) and the BOM is built using the structure type hierarchy defined (Refer to B.10.07 Node Type Hierarchy), the labels are set as the structure type of the node in that column.



The figure below shows different labels of the flat view column in two different situations:

Column labels as Structure Type

of the node

Fig 1.11: Column labels as node type or level of the node in the tree

Column labels as Level of tree

In the case when the ‘Free BOM Structure?’ Parameter is set to N (no) and the BOM tree includes nodes from other queryable disciplines, column labels for some levels of these nodes may appear as Level 4, Level 5 ….Level 10. This will happen only for those nodes and levels that are beyond the hierarchy defined for the logged in discipline. Suppose the logged in discipline has only three levels defined as Area -> Unit -> Line. The column labels for the first three columns will be Area, Unit, and Line. Now a node that belongs to some other discipline can have a level beyond these three levels (this means the node type hierarchy in that discipline is bigger), say level 4 and Level 5. The flat BOM will display all those nodes accordingly, only the labels of the 4th and 5th column will be Level 4, Level 5, and so on.

Fig 1.12: Column labels for the nodes of queryable disciplines

Labels for the columns for

the nodes beyond the

hierarchy of logged in

discipline are displayed as

Level 4, Level 5 …

However, there is a limitation with the flat view. The flat view of the BOM tree can handle displays of up to a maximum of 10 columns. This means if the BOM tree’s depth is greater than 10, the flat view related operation will not work. Creation/Editing or Delete operations are also supported only for BOM trees having a depth of 10 or less.



The Flat BOM, apart from the nodes from BOM tree, also displays the following additional data:

• Discipline: Discipline of the last visible node in the row.

• Object Code: Object Code of the last visible node in the row.

• Released Indicator: Release Indicator (“Release” field) of the last visible node in the row.

• Issue Status: The last visible node may have multiple positions attached to it. All these positions may have different issue statuses. Once the issue status column is selected for display, the software finds out all distinct issue statuses for the last node and displays them, creating the same row as many times as many distinct issue statuses are available with the positions of the last visible node.

• List Status: The last visible node may have multiple positions attached to it. All these positions may have a different list status. Once the list status column is selected for display, the software finds out all distinct list status for the last node and displays them, creating the same row as many times as many distinct list statuses are available with the positions of the last visible node.



Please see the figure below, which shows the five additional fields in the flat BOM.

Additional Columns

Fig 1.13: Five additional columns displaying data of last visible node.

A flat BOM also supports the display of records as per visual attribute rules defined in A.30.14 Visual Attributes. In the figure given below, the background colors orange and green are displayed because of the visual attribute rules defined in A.30.14. Please refer to A.30.14 documentation for how to define visual attribute rules for the records of a block.

!

The back-ground color is set as per

visual attribute rules

defined on A.30.14.

Fig 1.14: Flat BOM after applying visual attribute rules



The figure below displays the Flat BOM controls that act upon the Flat view to generate different views of the BOM tree in a flat manner.

Fig 1.15: Various Flat View Controls

‘Flat View’ Check Box, ‘Selected Node’, and ‘Full Tree’ Radio Buttons The user can switch on or switch off the generation and display of the flat view. This can be done by checking or un-checking the “Flat View” check box. The flat view of the BOM tree is generated and all operations related to the flat view are available only when this check box is checked. When this is un-checked, all the above functionalities are disabled.

As soon as the user checks the “Flat View” check box, the “Selected Node” and “Full Tree” radio buttons are enabled. By default, the “Selected Node” radio button is selected and the view is generated accordingly. The user can select the “Full Tree” radio button to generate the flat view on a complete BOM tree. In this case, all the leaves in the entire tree will be taken into account to create the rows in the flat view as explained earlier.

By default, the flat view is generated depending on the selected node in the tree section. This means that instead of the complete BOM tree, only leaves under the currently selected node will be considered to create the flat view. The view is ordered using all the columns starting from column one, in sequence, in ascending order.

Selection of a node in the Flat BOM or in the Tree is always synchronized. If you select a node in the tree and “Display Flat View” is checked, the same node will be highlighted (blue color background) in the flat view. On the other hand, if you select a node in the flat view (placing the cursor in the cell), the same node in the tree will appear as selected. Properties and attributes for the currently selected node in the flat view or tree are displayed in the Property/Attribute section.

If a Released or locked node in the flat view gets focus or is selected, the color of the text turns red, indicating that the node is locked and hence is not editable.

The nodes from other disciplines (Queryable disciplines) are displayed with Red icons in the tree. These nodes are displayed in the flat BOM also but cannot be edited or deleted. However, you can add a node under the nodes of queryable disciplines. In the flat BOM, the Text of the corresponding Node turns Red, which indicates that the node belongs to a Queryable Discipline and hence is locked for any updates.



The following figure shows data from Queryable Disciplines as shown in the Flat BOM.

Red icons indicate

nodes from other

(queryable)

disciplines.

Fig 1.16: Nodes from other (queryable) disciplines.



Expansion of Flat View (Right/Left/Both ways) The flat view of the tree can be expanded to the right, thereby hiding the Property/Attribute section. This can be done by clicking the Show/Hide Property Window button. This button works in toggle mode. The first time you click this button, it hides the Property/Attribute section. If you click it again, it brings back the section.

Show/ Hide

Property

Property/ Attribute Section is removed and

Flat View is expanded.

Fig 1.17: Expanding the flat BOM view to the right

The flat view of the tree can be expanded to the left, thereby hiding the Tree section. This can be done by clicking Show/Hide BOM Tree. This button also works in toggle mode. The first time you click this button, it hides the Tree section. If you click it again, it brings back the section.

Show/Hide BOM Tree

Tree Section is removed and Flat View is expanded.

Fig 1.18: Expanding the flat BOM view to the left



The user can even remove both sections and have only the flat view expanded completely over the entire window. To do so, click both buttons, one after the other, thereby hiding both sections.

Fig 1.19: Expanding the flat BOM view to occupy the whole window.

‘DRAG and DROP’ Check Box The ‘Drag and Drop’ check box enables the user to rearrange and resize the fields that are displayed in the flat BOM, which includes the Nodes and the five additional fields, namely Discipline, Released Indicator, Object Code, Issue, and List Status. The check box gets enabled only if the ‘Flat View’ Check box is checked. The ‘Drag and Drop’ functionality is applicable to the Flat BOM view only (that is, the user cannot drag a node in the Flat view to the tree or to the Property Tab section). Each Drag and Drop action will create a configuration entry on the A.30.13 - Configurations screen.



Operations • Add Node

New nodes can be added in the BOM tree from the flat view. This operation is supported only when the project default ‘Free BOM Structure?’ is set to ‘N’ and a strict node type hierarchy is maintained by the BOM tree. You can type the name of the new node in a blank cell and save your work by either pressing F10 or clicking the Save toolbar button ( ). This will create a node with the name as supplied, under the node in the cell to the immediate left and in the path represented by that particular row. For example:

Suppose our BOM tree looks like:

• Area1

• Unit1

• Line1

• Line2

• Unit2

• Line3

• Line4

• Area2

• Unit3

• Unit 4

• Line7

• Unit23Line8

The corresponding flat view for the above tree will look like:

Area Unit Line

Area1 Unit1 Line1

Area1 Unit1 Line2

Area1 Unit2 Line3

Area1 Unit2 Line4

Area2 Unit3

Area2 Unit4 Line7


Enter the new node name “Test” in this

cell.



Now suppose we want to add a new node with the name “Test” of type “Line”. If we type the name “Test” in the blank cell available to the right of the node “Unit 3”, this will create a new node having the name “Test” under the node “Unit3” and in the path “\Area2\Unit3”. The path for the newly created node will be “\Area2\Unit3\Test”. While creating a node, the values for the other node properties are assigned automatically as given below:

• Node Type: This is the type of the column as represented by the caption of the column. Please note that if the project default ‘Free BOM Structure?’ is set to Y, adding a new node is not possible from the flat BOM view because columns in that case only represent the level of the tree and not the structure type at that level.

• Short Description and Description: This is set as the name of the node itself. In the case mentioned above, it will be “Test” and “Test”.

• QTY Factor: This is set to 1.

The attributes are not assigned any values. After creating the node(s) from the flat BOM, you can edit the property values and attribute values for a node following the steps already described in the “Property/Attributes Section”.

Though we have used only one node in the above example, you can create as many nodes in the tree as required in one operation. Type all the names in the appropriate row (path) and cell (level and structure type), and then save your work either by pressing F10 or clicking the Save toolbar button ( ). This will create all the nodes with the properties and attributes as mentioned above.

The first column in the flat BOM view represents the nodes at the root level of the BOM tree. If you enter a new name in a cell of the first column, this will create a new root node. If the project default for one master node (Root Nodes) is set to ‘Y’ in the discipline (Refer to Valid Settings A.60.63 and Project Defaults A.20.12), the user will not be able to enter the value in the first column, and for each new row, the existing root node name will be copied.

• Edit Node Name

The flat BOM view only allows editing the name of the node. In the view, if you change the name of a node and save it, the name of that particular node will be changed to the supplied name. In the case of a locked/released node, the cell will be locked from editing the name and hence this operation will not be applicable.



In our previous example in the add operation, we added a node with the name “Test”. After adding the node, the flat BOM will look like the following:

Area Unit Line

Area1 Unit1 Line1

Area1 Unit1 Line2

Area1 Unit2 Line3

Area1 Unit2 Line4

Area2 Unit3 Test

Area2 Unit4 Line7


Edit the name “Test” to

“Test123”.

Suppose we change the name “Test” to “Test123” and save. The flat BOM will reflect the change made as given below.

Area Unit Line

Area1 Unit1 Line1

Area1 Unit1 Line2

Area1 Unit2 Line3

Area1 Unit2 Line4

Area2 Unit3 Test123

Area2 Unit4 Line7


Node name is changed to “Test123”.

Like the “Add Node’ operation, the “Edit Node Name” operation can also change the names of multiple nodes at a time. Type all the name changes in the appropriate row (path) and cell (level and structure type), and then save your work either by pressing F10 or clicking the Save toolbar button ( ). This will change all the nodes to the new names.



• Delete Node

This operation enables the user to delete a particular node from the BOM tree. It should be noted that when you delete a node, all the nodes under the node that you chose to delete will also be deleted. In order to delete a node from the flat BOM view, just delete the entry from that cell. Suppose in the flat BOM view given below, you want to delete the node “Test123”:

Area Unit Line

Area1 Unit1 Line1

Area1 Unit1 Line2

Area1 Unit2 Line3

Area1 Unit2 Line4

Area2 Unit3 Test123

Area2 Unit4 Line7


In order to delete this node, delete the entry

from this cell.

After deleting the entry, it will look like:

Area Unit Line

Area1 Unit1 Line1

Area1 Unit1 Line2

Area1 Unit2 Line3

Area1 Unit2 Line4

Area2 Unit3

Area2 Unit4 Line7


“Test123” is deleted.

Now save your work either by pressing F10 or clicking the Save toolbar button ( ). This will delete the node “Test123” from the tree.



In the above example, if you delete the entry “Unit2” in the third row, this will cause deletion of nodes “Line 3” and “Line 4” along with “Unit2”, as both of the lines are children of node “Unit 2”. The flat BOM will appear as given below.

Area Unit Line

Area1 Unit1 Line1

Area1 Unit1 Line2

Area2 Unit3

Area2 Unit4 Line7


• Ordering Columns

The columns of the flat BOM view can be ordered in an ascending or descending manner. The sorting can be done using more than one column with any combination of ascending and descending types. The user will have to select the column that he wants to sort, keeping the cursor in it. Then on a right mouse click, a pop-up menu is provided with the following four options: 1. Order By This Field ASC 2. Order By This Field DESC 3. Add This Field in Order By ASC 4. Add This Field in Order By DESC

Fig 1.20: Flat BOM view with pop-up menu



Add Field: This will open up an LOV containing the list of columns that can be added in the flat BOM view. In total, there are 25 columns, 10 for 10 levels of the BOM tree, 10 for the CIP fields, and 5 columns for Discipline, Object Code, Released Indicator, Issue Status, and List Status. The LOV will show up in the columns out of the 25 columns that are not presently displayed. The selected column from the LOV is added in the flat view next to the column where the cursor was while selecting this option from the pop-up menu.

The addition of CIP fields is treated a bit differently. The software allows the user to add CIP fields; a maximum of 10 such fields can be added in the flat BOM. When the user selects a CIP field to add from the LOV of columns, a child window pops up as shown below.

Fig 1.21. Specify CIP Name Child Window

The user will have to specify the CIP for the column in this window. The field provides an LOV with all CIPs defined in the system. The user can select one of them and can click the ‘Add Field’ Button to add that CIP as a column in the flat BOM. This newly added CIP column will display the computed value from the CIP for the last displayed node in the row.

Remove Field: This does the exact opposite of the Add Field button as described above. The user can hide or remove a column from the flat BOM display. After selecting a column (click the mouse or move the focus using Tab ), the user can choose this option and the selected column will be removed. The same can be added again using ‘Add Field’ on the pop-up menu.



Set Column Spacing: This menu option allows the user to increase or decrease the space between two columns. Put the cursor in any of the columns and select this option from the pop-up menu. This will bring up a child window as shown below. The user can enter the units by which he/she wants to separate the columns in the view, and then click the ‘Set Column Spacing’ button. This will set the space between the columns of the flat BOM as specified by the user.

Fig 1.22: Set Column Spacing Child Window

Order By This Field ASC: This will sort in an ascending manner the data of the currently selected column. Any previous ordering will be replaced with the new results. The ‘Order By’ field above the flat view will display the column name that has been used to sort the column.

Order By This Field DESC: This will sort in a descending manner the data of the currently selected column. Any previous ordering will be replaced with the new results. The ‘Order By’ field above the flat view will display the column name that has been used to sort the column.

Add This Field In Order By ASC: This will first add the currently selected column in an ascending manner at the end of the previous sorting clause (See the value in the ‘Order By’ field above the flat view before sorting). Then the whole view will be sorted according to the newly generated sorting clause. This new clause will also be displayed in the ‘Order By’ field above the flat view.



Add This Field In Order By DESC: This will first add the currently selected column sorted by a descending manner to the end of the previous sorting clause (See the value in the ‘Order By’ field above the flat view before sorting). Then the whole view will be sorted according to the newly generated sorting clause. This new clause will also be displayed in the ‘Order By’ field above the flat view.

Increase Field Size using Mouse: This operation enables the user to increase the size of the field using the mouse. The size of the fields can only be increased on the right. The user should click on a point near the right end of the Selected field and drag it to the right to increase the field. He can drag it to the left to decrease the field. This operation is not available when the ‘Drag and Drop’ check box is not checked.

Drag and Drop using Mouse: This operation enables the user to rearrange the arrangement of items in the flat BOM by dragging a selected column to a new position in the Flat View using the mouse. The user should click and hold the mouse on the selected field. When the mouse cursor changes to ‘Move’, the user can then drag it to the right or left to move it to a new position, thereby changing the order of the fields displayed in the Flat View. This operation is not available when the ‘Drag and Drop’ check box is not checked. Each Drag and Drop operation creates a new configuration that is stored in the ‘A.30.13-Configurations’ screen.

Configuration Fast-Call The Toolbar includes a configuration Fast-Call List-box that shows the latest configuration of the Flat BOM that the user is using.

Fig 1.23: Configuration Fast-Call in Toolbar

For each of the Add field/Remove field/Set space between column operations that the user performs on the Flat View, the configuration will be stored on the ‘A.30.13-Configurations’ screen. The user can navigate to the A.30.13 screen by double-clicking the Configuration Fast-Call List box on the toolbar.

Configuration Fast-Call control on the Toolbar



Fig 1.24: A.30.14-Configuration from Fast-Call on B.20.03

The user can also change the display of the Flat BOM by selecting any one of the configurations that are available in the Configuration Fast-Call on the Toolbar.

Flat BOM Operation Constraints • The user cannot Add/Update/Delete through the Flat BOM when any one

or all of the following columns are included in the Flat BOM display.

• Issue Status

• List Status

• The user cannot update or delete nodes from other disciplines ( that is, queryable disciplines).

• The user cannot remove all the Node Columns from the Flat BOM. At least one Node column has to be visible.

• When the user adds new rows or nodes through the flat BOM, all columns of the hierarchy must be present in the flat BOM. If the user has removed any of them, the software will not allow the operations until the columns are added again in the display.



Search and Advanced Search Section This section provides the utility to search for a node in the BOM tree. The utility is divided into two parts: “Search” and “Advanced Search”. The “Search” is a simple search utility that allows the user to search for a node on the basis of its name. The “Advanced Search” utility provides a more complex searching mechanism. The user can specify logical conditions like matching all words or matching at least one word of the search string. In addition, the user can also specify other properties such as Node Name, Node Type, Node Descriptions, Ident Value, etc. The search includes all criteria specified by the user. All the matching nodes are listed in a separate child result window. In addition to the name of the matching node, the result window displays the node type and complete path. If the user wants to navigate to a particular node from the search results, he can double-click that node name, and the software will locate the node in the BOM tree and flat view (if it is enabled).

Search The figure below shows the main UI search section. In the “Search For” field, the user can type in a string. The software searches for a node in the BOM tree with that name or with the string as a sub-string in the name. This field only allows searching for the node name, not for any other attributes. The “Search” button triggers this simple search operation. The “Advanced Search” button opens another child window where the user can specify more complex criteria for the search.

Enter the node name you want to

search.

Fig 1.25: Search Section



Advanced Search The figure below illustrates the Advanced Search child window. The value in the “Search For” field is copied from the main UI’s “Search For” field, if there is a value. The user can also enter some other values or change the copied value. The user can specify a search string having multiple words and can also specify how those words shall be used while searching. In addition, this functionality also allows the user to set the scope of the search. It enables the user to specify the areas where the search shall be performed, with properties such as “Node Name”, “Node Type”, “Node Descriptions”, “Attribute Values”,”Position and Position Values”, “Ident Value”, and “Ident Value History”, etc. The user must specify at least one of these properties for the search.

Search Criteria

Search Scope

Fig 1.26: Advanced Search Window

The “Include All” button selects all the scopes for the search. The “Include None” button deselects all of them. The “Search” button starts the search process. The results display in another search window.



Search Results This button will show the Search result window with the last searched results.

Operations Simple Search The user can perform a simple search by entering a string in the “Search For” field and then clicking the “Search” button on the main UI. The software will try to find all the nodes in the BOM tree with the same name as the search string or with the search string as a sub-string in their name. All the nodes meeting the search criteria are listed along with their type and complete path as shown below.

Double-click the Node name to locate it in the BOM tree.

Fig 1.27: Search Results Window

Advanced Search In order to perform an advanced search, click the “Advanced Search” button on the main UI. This will open the “Advanced Search” UI. The user can enter the search string in the “Search For” field. After this, the user must specify one of the search criteria from the list given below.

• With All Words: All the words in the search string are taken together to match. (Default criteria)

• With Exact Phrase: The search must match exactly the string mentioned in the “Search For” field.

• With At Least One Word: At least one of the words in the search string must match.

After this, the user must specify the scope of the search. The user will have to specify where exactly he is looking for the match of the search string. The following properties are the search scope:

• Node Name: Nodes with the node name matching the search string.



• Node Type: Nodes with the type matching the search string.

• Description: Nodes with the search string in their description or short description.

• Attribute Value: Nodes with the search string as a value of any of their attributes.

• Positions: Nodes with the position matching the search string.

• Positions Values: Nodes with the position values matching the search string.

• Ident Value: Nodes with the ident values matching the search string.

• Ident Value History: Nodes with the historical values (old or previous values) of the idents associated to them matching the search string.

It is mandatory to choose at least one of the search scopes. You can specify all of them (“Include All” button) or any combination of them to define the exact scope of the search.

After the search finishes, the matched nodes are displayed in the child result window as shown below.

Fig 1.28: Search Results Window



Adv. Maint. BOM– Add Root Node/Add Child Node The user can access this child window from the pop-up menu in the Tree Section. There are two pop-up menu options: “Add Root Node” and “Add Child Node”. Depending upon the selected option, either the “Add Root Node” or “Add Child Node” window appears in the foreground. Both the child windows look similar except for one difference: in the “Add Root Node” window, the node type field LOV will provide only the node types defined for a root node. On the other hand, in the “Add Child Node” window, the node type field LOV will provide the node types depending on the level at which you are adding the node. This is decided on the basis of the currently selected node under which you want to add the child node. The “Add Root Node” option will be disabled when the “Only One Master Node” project default is set to ‘Y’ (yes).

Both the UIs have two tab pages similar to the “Property/Attributes Section”. This enables the user to specify the properties and attribute values for the node that he wants to create at the same time. There are two buttons (“Ok” and “Cancel”) to confirm and to cancel creation of the new node.

Property Page The user will first have to supply property values for the new node. Among all the property tab fields, the Name, Type, and QTY Factor are mandatory fields (represented by the green background). The user cannot get to the “Attribute” page without supplying values for these three fields. The “QTY Factor” field defaults to 1 and can be changed to some other value.

Fig 1.29: Add Node Child Window



Attribute Page This page allows the user to provide values for the attributes mapped to the structure type of the new node. The user can access this page only after supplying values for the mandatory fields on the property tab page. If an attribute has an LOV attached to it, the LOV toolbar button is enabled when the cursor moves to the value field of that attribute.

Fig 1.30: Attribute Page of the Add Node Child Window

Operations OK Clicking the “OK” button confirms the creation of the new BOM node. The new node is created at the appropriate level, and focus is set to the created node in the BOM tree. The user can click the “OK” button immediately after supplying the values for the required properties. This will create the node without the values for the attributes. The user can later modify the attributes in the “Property/Attributes Section”. The user can supply both properties and attribute values at the same time and can click “OK”. This will create the node with the given properties along with the values for the attributes.

• If the “Add Child Node” menu option is selected, then the node will be created under the currently selected node in the BOM tree.

• If the “Add Root Node” menu option is selected, then the node will be created at the root level of the BOM tree.



Cancel Upon clicking “Cancel”, the user cancels the creation of the new node. All the values supplied for properties and attributes are discarded, and the child window is closed. The focus returns to the BOM tree.



Adv. Maint. BOM – Copy-Paste Node In B.20.03 Advance Maintain BOM, when the user selects a node in the tree structure of a BOM and selects Copy from the right mouse click menu, this selected node is marked as a source node for a copy operation. When the user selects another node and selects Paste from the right mouse click menu, this node is marked as a destination node to complete the Copy. What exactly needs to be copied from the source node to the destination node is specified by the user in the Copy Options child window. As per the options selected, one of the B.20.03.08 or B.20.03.14 windows pop up to capture the other required parameters.

Copy Structure (B.20.03.08) This window pops up if the user selects the Copy Structure option from the Copy Options window. Depending upon the parameters supplied by the user, this will copy the selected node structure under the destination node of the BOM.

Fig 1.29: Copy-Paste Copy Structure Window



Node Path: This field will display the complete path of the node selected to copy (source node).

Short Description: Short description of the source node.

Description: Description of the source node.

Structure/Positions

Only Structure: If checked, only structure will be copied.

With Structure and Positions: If it is checked, the source node is copied along with the positions. If selected, the ‘Keep Item Number’, ‘With Assemblies’, ‘Issue Status From’, ‘Best Qty’, and ‘Issue Status To’ fields are enabled to capture values. (Note that these fields will not be available on selection of Only Structure).

Keep Item Number: If checked, the item numbers of the positions of the source node will be kept as-is while copying.

With Assemblies: If checked, the positions will be copied along with the assemblies.

Issue Status From: The user can specify the specific issue status of the positions to be copied.

Best Qty: If checked, only the list positions with best quantity will be copied.

Destination Node Path: Complete path of the BOM node where the paste operation has to be completed.

Issue Status To: The user can specify the specific issue statuses for the destination node. The LOV on this item displays all the Issue Statuses, excluding those Issue Statuses with the "No Display" Check box checked for the logged-in discipline on the B.10.08 Window-2 screen.



Operations OK

Clicking the “OK” button confirms the copy operation of the selected BOM node at the destination. The user can click the “OK” button immediately after supplying the values for the required properties.

Cancel

Upon clicking “Cancel”, the user cancels the copy of the selected node. All the values supplied are discarded, and the child window is closed. The focus returns to the BOM tree.

Copy Positions (B.20.03.14) This window pops up if the user selects the ‘Copy Positions’ option from the Copy Options window. Depending upon the parameters supplied by the user, this will copy the positions of the selected node structure under the destination node of the BOM. The structure of the source node will not be copied in this case.

Fig 1.29: Copy-Paste Copy Positions Window

Node Path: This field will display the complete path of the node selected to copy (source node).



From Position: Specify the From position of the source node. This position is the starting point of the positions that need to be copied to the destination node.

To Position: Specify the To position of the source node. This position is the ending point of the positions that need to be copied to the destination node.

Issue Status: Specify the issue status; only positions with this issue status will be copied to the destination.

List Status: The list status from which the position is to be copied. The user can select a value for this field using the LOV.

Keep Item Number: Keeps the item number of the positions, if checked.

With Assemblies: Positions will be copied along with the assemblies, if checked.

Attribute Options:

Only Position Attributes: This option will copy all position attribute values (along with the position to the target) that have either the manual check box checked (indicating that this value must always be retained), or are assigned directly to the BOM position.

All Attributes: This option will copy all position attribute values along with the position to the target, regardless of whether the attribute is on the position level or has been propagated from the node level.

Destination Node Path: Complete path of the destination node where the copy operation has to be done.

Issue Status: The issue status under which the position is to be copied. The default is always the project default ZB_STAT_ID (A.20.11/12/13). The user can select a value for this field using the LOV. The LOV on this item displays all the Issue Statuses, excluding those Issue Statuses with the "No Display" check box checked for the logged-in discipline on the B.10.08 Window-2 screen.

List Status: The list status under which the position is to be copied. The default value is always the project default ZB_LST_ID (A.20.11/12/13). The user can select a value for this field using the LOV.

Operations OK

Clicking the “OK” button confirms the copy operation of the selected BOM node at the destination. The user can click the “OK” button immediately after supplying the values for the required properties.



Cancel

Upon clicking “Cancel”, the user cancels the copy of the selected node. All the values supplied are discarded, and the child window is closed. The focus returns to the BOM tree.


BOM Position Views

BOM Position Views Table LIST_POS contains all the positions allocated to a terminal node. Management of the positions is effected within Window 2.

In a position, a part number (Ident in the SmartPlant Materials sense) is generally allocated with a quantity and identity-shaping attributes.

All terminal positions are usually taken into account within demand assessment. The exceptions here are positions with the release status or with the demand assessment code equal to N. In this situation, the requirements explosion goes as far as the hierarchy of the position above.

A double-click on a node in the BOM tree view or a double-click on the BOM flat view will invoke BOM position views [Window 2]. This window consists of the following views.

1. Multi Position View. 2. Single Bulk Material View. 3. Single Tag Material View.

BOM View Name The view name represents the BOM-User-View defaulted for the Multi Position View. It is defined on B.10.06. The default view can be changed using the View Name list item. This view name will be used to define the BOM attribute catalog in the Multi position view of the BOM Position views. This list item is visible on the second window of B.20.03 under the Multi Position View page.

List item for View Name

Fig 2.1 – View Name for Multi Position


BOM Position Views

Issue Status The value of this item determines the order / select condition of Position values.

Possible Values are Highest, Lowest, All asc, All desc, Selected, and Best Quantity.

Highest

Records corresponding to the highest available Issue Status on this BOM will be displayed.

Lowest

Records corresponding to the lowest available Issue Status on this BOM will be displayed.

All desc

All records will be displayed with position value (Pos) in descending order.

All asc

All records will be displayed with position value (Pos) in ascending order.

Selected

Another list is displayed when the user selects the ‘Selected’ option. It shows all defined Issue Statuses from B.10.08. The user can select the required value. Records corresponding to the selected Issue Status will be displayed.

Best Quantity

Records corresponding to the defined best quantity will be displayed.

With the Project Default ZB_ISSUE, the user can define which Issue Status is the default in B.20.03.

Possible values are:

• ALL_ASC

• ALL_DESC

• HIGHEST

• LOWEST

• BEST_QUANTITY

• SELECTED.

If ZB_ISSUE is not set, then HIGHEST will be taken as default.


BOM Position Views

Cascading LOV Option The Cascading LOV functionality invokes the LOV for the item automatically when the user navigates to a specified field (list given below) that has a null value. This functionality is controlled by the project default parameter ZB_AUTOLOV. This functionality has been implemented for all the position views

The Cascading LOV functionality is implemented for the following fields:

• Spec Code

• Short Code

• Option Code

• Group

• Part

• Commodity Code

• Ident Code

If this project default parameter ZB_AUTOLOV is set to ‘Y’, then an automatic LOV is invoked when the value of the item is null. After selection of the value from the LOV, the cursor automatically moves to the next field, and then its corresponding LOV is invoked (if the value is NULL). If the user selects the ‘Cancel’ option from the LOV, then the cascading LOV functionality is interrupted.

If the project default parameter ZB_AUTOLOV is set to ‘N’, then the user has the following two choices:

1. The user can enter values manually, and the cascading LOV is not invoked. 2. The user can invoke the cascading LOV by invoking the corresponding LOV on

the item(s), mentioned above.

Note

• For every record instance, the value of the project default parameter ZB_AUTOLOV is considered.


BOM Position Views

Multi Position View

Fig 2.2 – Multi Position View

Working with BOM-Attribute Catalog defined as the following: 1. by the logged on user in B.10.06 BOM Views or 2. by the current discipline in B.10.09 Discipline BOM Views.

The default display in Multi –Position will have the following fields displayed: Pos, Qty, Unit, Item Type, Tag Number, Commodity Code, Ident, and Size (1-5). By default display, we mean that the user has not selected any BOM view from the View Name list box.

Fig 2.2.1: Default Display fields in Multi-Position


BOM Position Views

If there are no items visible in the Multi Position View, the reason can be one of the following:

a) No BOM-User-View is defined on B.10.06 for Screen B.20.03 and then selected on Screen B.20.03.

b) BOM-User-View for Screen B.20.03 is defined (B.10.06) but no attributes are assigned to this view.

There are two kinds of attributes that are available for showing the items in the Multi Position view.

The first kind are the attributes that belong directly to the Position like "Spec Code", "Short Code", "Group", "Part", “Commodity Code", "Ident Code", etc.

Attributes of this kind are defined as Database Column (the Database Column check box is checked on B.10.06). The Order Sequence of these attributes has no effect on visibility. To use these kind of attributes, the user needs to select the following attributes on B.10.06 Attributes.

The Database fields that can be selected in the Multi Position view should exist in the selected BOM view. As compared to the earlier method of creation of attributes for use in the Multi-Position View, the database fields should be included only in the Selected BOM View on B.10.06.

1. SPEC_CODE 2. CG_GROUP_CODE 3. PART_CODE 4. COMMODITY_CODE 5. IDENT_CODE 6. LINK_LN_CODE 7. CONTROL_STATUS 8. REVISION_ID1 9. REVISION_ID2 10. OBJECT_CODE 11. STATUS 12. LST_CODE 13. LST_DATE 14. LST_USER 15. CREATED_BY 16. REQUISITION_IND 17. LOAD_IND (Prompt is Reload)


BOM Position Views

18. TAG_NUMBER 19. RESV_QTY 20. ISSUE_QTY 21. PLATE_NUMBER 22. INPUT_1 23. INPUT_2 24. INPUT_3 25. INPUT_4 26. INPUT_5 27. QUANTITY 28. UNIT_CODE 29. ITY_CODE 30. REVISION_NUMBER 31. SHORT_CODE 32. OPTION_CODE

The second kind of attributes are those that are assigned in Module -B.10.03 Node-Types- and -B.10.04 Positions Attributes.

There can be a maximum of 20 additional attributes for the Multi position View, except the first kind of attributes.


BOM Position Views

Include Sub Tree Nodes of <path> - Check Box This is provided in order to allow the user to search/query the position values from the Sub-tree nodes of the selected node. Initially, this is unchecked. This is enabled in Multi Position View and Multi Status View.

Fig 2.2 – Multi Position View – Node Path

When the check box is checked:

• The Path field will be displayed in the Multi Position View.

• Position views will allow showing positions of the selected node in the BOM Tree view or in the BOM Flat view and also positions belonging to Sub tree nodes of the selected Node.

• The user can query on the Path field, by using the Node Name such as ‘LINE%’ or using the Path such as ‘UNIT2/LINE%’.

When the check box is unchecked:

• The BOM position view window will show only the positions related to the node selected in the BOM Tree view or in the BOM Flat view.

• The Path field will not be displayed in the Multi Position View.


BOM Position Views

Description of the fields Pos

This field specifies the Unique Position within this Structure-Element.

Path

This field shows the BOM Node Path.

This field is displayed only when the ‘Include Sub Tree Nodes of <path>’ check box is checked.

Spec Code

This field specifies the Specification code.

Note

• Valid spec codes are those where the flag BOM within the assigned spec rule is checked. (S.50.01 Specification Rules).

A valid spec code must have at least one entry in S.50.06 Specification Items so that the LOV of the next two items can get a valid value (short code, option code).

Updating spec code(s) does not automatically clear short code, option code, and sizes (except for commodity group, commodity part, commodity code, and ident code).

If the Project Default Parameter "ZX_DP_SPEC" is set to 'Y', then the LOV on this item does not show Specs from Non Login disciplines. If the Project Default Parameter "ZX_DP_SPEC" is set to 'N', then the LOV shows all the Specs.

Rev. No.

This field specifies the Spec Revision Number.

Short Code

This field specifies the Short Code.

On double-click of this field, the software opens the corresponding screen, S.10.08 Short Codes.

Option Code

This field specifies the Option Code.

Quantity

This field specifies the Ident-Quantity on this Position.


BOM Position Views

Unit

This field specifies the Unit Code.

Default value: The parameter called ZB_UNIT_ID in A.20.012 and / or A.20.13 can be set to a valid Unit Code (A.10.12 Units of Measure) within the Unit Group.

Size 1

This field specifies the value for Size 1.

Size 2


Size 3


Size 4


Size 5


Item Type

This field specifies the Name (code) for the item type.

Sub positions on tagged items (Item-rule in (TWM, TOM, TFM, REF)) are possible.

This functionality depends on the project parameter ZB_PCKMAIN. The default N means no sub positions are allowed on tagged items. Y means sub positions on tagged items are allowed, but the item type must be exactly the same as on the parent position.

Group

The Group field is of type code, which means this is a 10-character alphanumeric value representing a unique identifier for this commodity group. Examples of this code would be PIPE, VALVE, or FLANGE.

On double-click of this field, the software opens the corresponding screen, S.10.02 Commodity Group.


BOM Position Views

Part

This field specifies the unique name for the commodity part.

On double-click of this field, the software opens the corresponding screen, S.10.03 Commodity Part.

Commodity Code

This field specifies the Commodity Code.

On double-click of this field, the software opens the corresponding screen, S.30.01 Commodity Codes.

Ident Code

This field specifies the Ident Code.

On double-click of this field, the software opens the corresponding screen, S.80.01 Ident Management.

Link BOM

This field specifies the Link Structure Element Name (Node Name) from the BOM.

The module B.20.01.17 Link BOM can be used to allocate a bill of materials (BOM), for example, a spare parts list to a position. Only the reference to this bill of materials is recorded in the position. The items in the spare parts list are not copied.

If the position has the reference to a bill of materials (produced with B.20.01.17), Module B.20.01.18 Show BOM can be used to show the allocated bill of materials.

Ctrl

This field specifies the code indicating the approval states of the record.

Rev1

This field specifies the beginning revision number for the record.

Rev2

This field specifies the last revision number for the record.


BOM Position Views

Status

This field specifies the status for the corresponding position (Issue Status defined on B.10.08).

The LOV on this item displays all the Issue Statuses, excluding those Issue Statuses with the "No Display" Check box checked for the logged-in discipline on the B.10.08 Window-2 screen.

Object Code

This field specifies the code necessary to hold the relation to CAD-System.

List Status

The release status to be edited must be given, or in the case of creation, entered.

Lst Date

This field specifies the date this list status was set.

Lst User

This field specifies the user who set the list status for this position.

Created By

This field describes the way this record was created/updated

Req

This field specifies whether to include the quantity of this Position into MTOs.

Reload

This field specifies whether the OMI can update the corresponding record.

If this check box is checked (Y), then OMI can update the corresponding record; else not.

Tag Number

This field is an identifier for a special part.

On double-click of this field, the software opens a new dialog box called B.20.01.22 if the tag number is not empty and the item type belongs to an item rule like TOM, TWM, or TFM.

In the module, the commodity code description can be modified.


BOM Position Views

An exception to those item types of the item rule is REF. In this case, the tag number must be the same as the commodity code.

The software opens an LOV and shows data from module S.80.21 Ident Tag Numbers if the item type belongs to the item rule like SOT or SWT.

Restriction: The discipline of the position must be the same as the Login-Environment discipline.

Plate Number

This field specifies the plate number.

Reserved Qty

This quantity will be set by a forecast allocation run (Type: Reservation).

Issued Qty

This field specifies the issued quantity.

Sub Positions A sub-position can include an assembly defined in the parts master. A hierarchical structure is possible, and a depth of 14 levels of hierarchy sub-positions is allowed.

If a sub-position exists for any position, then a plus-sign (+) is displayed before the POS item in the Multi Position View. When the cursor focus is on a record in the main block (MPV), its sub-positions, if any, are displayed in the Sub Positions block. The Sub Positions block is for viewing purposes only (that is, it is not editable).

The Parent Position information is shown in the Parent Position Tree block.

The Sub Position block displays the following information:

• Pos

• Quantity

• Unit

• Commodity Code

• Ident Code

• Description

While the user navigates among the position views (MPV, SBMV, STMV), the Sub Positions block and Parent Position Tree block information are preserved.


BOM Position Views

Pop-up Menu options

Fig 2.3 – Multi Position View – Pop-up Menu

Customize View

‘Customize View’ will allow the user to customize the attributes to the current BOM view defined on B.10.06 and in the Multi Position View.

Fig 2.3.1 – Pop-up Menu Option ‘Customize View’


BOM Position Views

This will bring up the Multi Selection LOV for all available columns. The user can then select the columns that he wants to add to the existing view, or he can create a new view. He can also arrange the display ordering of the items in the Multi Position View by using the ‘Up’ and ‘Down’ buttons in the Multi Selection LOV.

When he clicks the ‘Select’ button, he will be prompted to create a new view with the selected items as shown in the figure below:

Fig 2.3.2: Message to User for creating New BOM View.

If the user selects ‘No’, the selected fields will be added to the existing BOM View for the Multi Position and will get displayed. However, if he selects ‘Yes’, a New BOM View will be created with the selected items and it will be set as the View Name for Multi-Position. The name for the BOM view will follow ‘Username’ + ’Running Sequence Number’ (for example, LOGIN23, etc).

A user can only allocate attributes to a List View (A.20.06.11) if he has access to them. This is established by the allocation of a List View, defined on A.20.06.11 Attribute Security, to the environment on A.20.06.01 or A.20.06.02 or added to the Role under A.30.03-Roles/Menus.

However, if the Current BOM being worked on by the user is of Type ‘Discipline Wise’ or of type ‘Project Wise’, then the user will not be permitted to customize the view using the ‘Customize View’ option. Instead, the following message will pop up and a new view will be created with the selected items in the Multi Selection LOV.

Fig 2.3.3: Message when trying to update Discipline/Project type view.

All the attributes in the Multi Position are configurable except the ‘Position’ field.


BOM Position Views

So a user can only view those List Views that are created by himself / herself and have a pointer to the List View in the current login environment.

Remove Field : <Field Name>

The Remove field will allow the user to delete attributes from the current BOM view defined on B.10.06 and the Multi Position View.

The fields Pos, Quantity, Unit, and Item Type can never be deleted.

The fields Rev. No, Short Code, Option Code, and Size 1 - Size 5 cannot be deleted directly. If the user deletes SPEC_CODE, then Rev. No, Short Code and Option Code will be deleted. Similarly, if the user deletes both SPEC_CODE and IDENT_CODE, then Size 1 - Size 5 will be deleted.

Set Column Spacing

'Set Column Spacing' influences the distance between the individual fields.

Order By Asc : <Field Name>

‘Order By Asc’ will sort data in ascending order according to the field name.

Order By Desc : <Field Name>

‘Order By Desc’ will sort data in descending order according to the field name.


BOM Position Views

Tile with BOM Tree View

Fig 2.4 – Multi Position View – Tile with BOM Tree View

Tile with BOM Tree view is a toggle option.

When this option is checked, the BOM Position Views window will tile with the BOM Tree view. The software will reduce the width of Window 1 and change the position of Window 2.

When this option is unchecked, the software will resize the Window 1 to normal size and change the position of Window 2.

Generally, Position values of a node will be shown when the user double-clicks on a Tree node or double-clicks on the Flat view. But, when Tile with BOM tree view is selected, then the user can get the position values of a node with a single mouse click on a tree node or by navigating in the BOM tree using the keyboard.


BOM Position Views

Auto Filter:

Fig 2.5 – Multi Position View – Auto Filter

Auto Filter is a quick and easy way to find and work with a subset of data. Auto Filter displays only the rows that meet the criteria you specify / select for a column.

Auto Filter is a toggle option. When the Auto Filter menu option is checked, drop down list items are shown below the column labels. The drop down list elements include (ALL), (CUSTOM) for default, distinct values of that particular column, and (NULL) and (NOT NULL) in case a column value is NULL for at least one record.

You can also use the Custom option to display rows that meet more than one condition for a column. For example, you might display rows that contain values within a specific range. When the Custom drop down list element is selected, a dialog box appears (as shown below), and the user can enter the search criteria.

Fig 2.6 – Multi Position View – Auto Filter - Custom


BOM Position Views

When you apply a filter to a column, the values in other filters are considered corresponding to the applied filter(s); that is, this functionality allows you to apply cascading filter(s).

Populate Downwards:

In general, when “Populate Downwards” is invoked from an item, the item values of all the records below the current record (from which this functionality is invoked) are updated to that of the current record’s item value. However, there are certain conditions under which an update is allowed and these conditions depend on the item under consideration (the item from which the functionality is invoked). Also, an update on one item may also result in an update of dependent items.

1. Populate Downwards functionality is provided only for the following items:

• Spec Code

• Short Code

• Option Code

• Input Sizes

• Object Code

• Status

• List Status

• Req

• Reload and

• All Position Attributes

• Quantity

• Quantity Unit

• Ident Code 2. Populate Downwards is not applicable when:

• The discipline of record is not equal to the login discipline.

• A corresponding BOM node is released.

• The Tag Number is NOT NULL and the item type is ‘TWM’ / 'TOM' / 'TFM' / 'TAB'.

Exceptions to the above mentioned point are:

a) All position attributes

b) Status, List Status, Req, Quantity, and Quantity Unit when the Project default ZB_TAG_UPD is set to 'Y’.

3. Populate Downwards functionality when invoked from the items Spec Code, Short Code, Option Code:


BOM Position Views

a) The following options show up for Spec Code:

• Copy Spec Code only

• Copy Spec Code, Short Code

• Copy Spec Code, Short Code, Option Code

• Copy Spec Code, Short Code, Option Code, Sizes

b) The following options show up for Short Code:

• Copy Short Code only

• Copy Spec Code, Short Code



c) The following options show up for Option Code:

• Copy Option Code only



The following are the only valid combinations (listed in Table: 1) of a record in the Multi Position View:

Case Spec Code Short Code Option Code 1 NULL NULL NULL 2 √ NULL NULL 3 √ √ NULL 4 √ √ √ Table: 1

Note

• ‘√’ means data is present and is NOT NULL.

The following sub-section explains the populate downward functionality options (listed in point 3 a / b / c) in detail:

Copy Spec Code only:

a) If the Spec Code to be populated is NULL.

Case 1, 2, 3, and 4 (Ref Table: 1)

Nullifies Spec Code, Short Code, and Option Code.

b) If the Spec Code to be populated is NOT NULL.

Case 1 and 2 (Ref Table: 1):


BOM Position Views

Update Spec Code.

Case 3 (Ref Table: 1):

If the Short Code exists in the Spec Code to be populated, then update the Spec Code; otherwise, update the Spec Code, nullifying the Short Code.

Case 4 (Ref Table: 1):

If the Short Code and Option Code exist in the Spec Code to be populated, then update the Spec Code and do the Ident Consistency Check; otherwise, update the Spec Code, nullifying the Short Code and Option Code.

Copy Short Code only:

a) If Short Code to be populated is NULL.

Case 1 and 2:

Do nothing.

Case 3:

Nullify Short Code.

Case 4:

Nullify Short Code and Option code.

b) If Short Code to be populated is NOT NULL.

Case 1:

Do nothing.

Case 2 and 3:

If the Short Code to be updated exists in the Spec Code, then update Short Code.


BOM Position Views

Case 4:

If the Short Code to be updated exists in the Spec Code, then check if the Short Code to be updated, Option Code, and Spec Code combination exists. If it exists, update the Short Code and do the Ident Consistency Check; otherwise, update the Short Code, nullifying the Option code

Copy Option Code only:

a) If Option Code to be populated is NULL.

Case 1, 2, and 3:

Do nothing.

Case 4:

Nullify Option Code.

b) If Option Code to be populated is NOT NULL.

Case 1 and 2:

Do nothing.

Case 3 and 4:

If the Option Code to be populated exists in the Spec Code and Short Code, then update the Option code.

Copy Spec Code, Short Code:

a) If both the Spec Code and Short Code to be populated are NULL.

Case 1, 2, 3, and 4:

Nullify Spec Code, Short code, and Option Code.

b) If Spec Code is NOT NULL and Short Code is NULL.

Case 1, 2, and 3:

Update Spec Code and Short Code.

Case 4:

Update Spec Code and Short Code, nullifying Option Code.


BOM Position Views

c) If Spec Code is NOT NULL and Short Code is NOT NULL.

Case 1, 2, and 3:

Update Spec Code and Short Code.

Case 4:

If the Option Code exists in the Spec Code and the Short Code combination to be updated, then update the Spec Code and Short Code; otherwise, update the Spec Code and Short Code, nullifying the Option Code.

Copy Spec Code, Short Code, Option Code:

Case 1, 2, 3, and 4:

Update Spec Code, Short Code, and Option Code.

If all of the Spec Codes, Short Codes, and Option Codes to be populated are NOT NULL, then do the Ident Consistency Check.

Copy Spec Code, Short Code, Option Code, Sizes:

Case 1, 2, 3, and 4:

Update Spec Code, Short Code, Option Code, and Sizes.

If all of the Spec Codes, Short Codes, Option Codes, and Sizes to be populated are NOT NULL and if the combination is valid (that is, there exists a unique ident for this combination), then update Group, Part, Commodity Code, and Ident Code (corresponding to the ident that would result in).

Notes

In all the above mentioned options for populate downwards on Spec Code, Short Code, and Option Code, the following holds true:

• If the values of any of Spec code, Short Code, Option Code, and Sizes are not the same prior to update and after update, then all the Ident related data (Group, Part, Commodity Code, and Ident Code) are nullified unless the Ident consistency check is done, resulting in the Ident being consistent.

• The conditions listed in point 2.

• If the spec revision number of the current record (record from which the Populate Downwards functionality is invoked) is less than the maximum spec revision number, then an alert message “Do you want to update Spec Revision Number with Highest Value?” pops up.


BOM Position Views

If the user selects ‘Yes’, the Populate Downwards functionality will copy the highest revision or highest issued revision depending on whether the project default ZX_ALLSPEC is set to ‘Y’ or ‘N’, respectively.

If the user selects ‘No”, then the Populate Downwards process will stop.

d) The Populate Downwards functionality when invoked from any of the input sizes:

Updates the respective input size downwards provided the conditions listed in point 2 are satisfied.

Updates Ident related data (Group, Part, Commodity Code, and Ident Code) corresponding to the Ident resulting from the Spec Code, Short Code, Option Code, and Sizes combination. If no Ident results, then it nullifies Ident related data (Group, Part, Commodity Code, and Ident Code).

e) The Populate Downwards functionality when invoked from the Object Code, Status, List Status, Req, Reload, all position attributes, Quantity, and Quantity Unit:

The conditions stated in Point 2 apply.

f) The Populate Downwards functionality when invoked from Ident Code:

Case 1: If the Ident Code to be populated is NULL,

Populate Downwards will nullify only the Ident Code.

Case 2: If the Ident Code to be populated is NOT NULL,

Populate Downwards will give an alert message “Do you want to update Spec Code, Short Code, Option Code combination also?”.

If the user selects ‘Yes’, then the process checks to see if the spec revision number of the current record (record from which Populate Downwards functionality is invoked) is less than the maximum spec revision number; if so, another alert message “Do you want to update Spec Revision Number with Highest Value?” pops up. If the user selects ‘Yes’, Populate Downwards functionality will update the Spec Code, Short Code, Option Code, Sizes, Group, Part, Commodity Code, and Ident Code of subsequent records to that of the current record (record from which Populate Downwards is invoked). The Spec Revision will be updated to that of the highest revision or highest issued revision depending on whether the project default ZX_ALLSPEC is set to ‘Y’ or ‘N’, respectively. If the user selects ‘No”, then the Populate Downwards process will stop.


BOM Position Views

If the user selects ‘No’, then only Sizes, Group, Part, Commodity Code, and Ident Code of subsequent records are updated to that of the current record. The Spec Code, Short Code, and Option Code are nullified provided these data are not consistent with the Ident Code under consideration.

If the user selects ‘Cancel’, then the Populate Downwards process will stop.

Add/Edit Sub Pos Nodes

To list/create sub position(s), select Add/Edit Sub Pos Nodes. This is only allowed on a valid and saved position.

When the menu item “Add/Edit Sub Pos Nodes” is selected from a Pos in the main block, the following events occur:

1. The sub position records are displayed in the main block. 2. In the Parent Position Tree block, a node is added. 3. The Parent Position Tree block displays the information about Level (like Level1,

Level2, etc.), Positions path (like /20/30), and Position Values (like Pos: (20), SpecCode: (AC0014), etc.).

Fig 2.7 – Multi Position View – Parent Position Tree

Back to Parent

Use the ‘Back to Parent’ pop-up menu option to reach the preceding level. The navigation works level by level. Back to Parent is only available on sub positions. This button is disabled on the first level.

When the ‘Back to Parent’ menu item is selected, the following events occur:

1. The Main block shows the parent position information along with the position information at the present level.

2. In the Parent Position Tree, the top node (that is, the Node with the Maximum depth) is deleted.


BOM Position Views

List Download

This pop-up menu option is used to export the multiposition data into either OMI format or Excel format. When we select this pop-up menu option, the List Download B.20.01.44 dialog box will pop up. This will contain two radio buttons, which will allow the user to specify the predefined format to export the position data. The two options are OMI Export and Excel Export, respectively. When we select OMI Export, the multi position data will be exported into a predefined OMI format. On the other hand, if we select Excel Export, the multi position data will be exported to a predefined Excel format.

Attach Documents

This pop-up menu option is used to attach or link documents to the positions and to the nodes in the BOM. When the user selects this pop-up menu option, D.10.21 Attached Documents screen will appear. Here the user can see all documents that have been attached to the node or to the position. The user can also attach or remove the documents to a BOM node or to a position of a node.

Auto Column Width

This functionality automatically calculates the display length/width of each column depending on the data so that the user can automatically optimize the amount of visual data.

Auto Column Width functionality does nothing when invoked from a column of type Checkbox or List. Also, if the column from which this functionality is invoked has all NULL values, then this functionality does nothing also.

Order by Functionality

By default, the data in this block will be sorted by issue status. The ‘Order By…’ button, will allow the user to sort the data using multiple fields in a required order. The sorted order of the block will be displayed in the ‘Ordered By’ display item.


BOM Position Views

Single Bulk Material View Single Bulk Material View

Fig 2.8 – Single Bulk Material View

Description of the Fields Pos


Quantity

This field specifies the Ident-quantity on this Position.

Unit


Default value: The parameter called ZB_UNIT_ID in A.20.012 and / or A.20.13 can be set to a valid Unit Code (A.10.12 Units of Measure) within the Unit Group.


BOM Position Views

Resv%Sub Qty



BOM Position Views

Issued%Sub Qty

This field specifies the issued quantity / substitute quantity.

MLD Issue Qty

This field shows the quantity issued on the screen C.20.22 MIR by the BOM Commodity that is of the Issue Type 'Miss, Lost or Damage'. When the field is shown in red, a quantity exists that is issued for this BOM-Position but has a different qty-unit in the Issue as in the BOM.

Status

This field specifies the status for the corresponding position (Issue Status defined on B.10.08).

The LOV on this item displays all the Issue Statuses, excluding those Issue Statuses with the "No Display" check box checked for the logged-in discipline on the screen B.10.08 Window-2.

List Status


Lst Date

This field specifies the date the corresponding list status was set.

Lst User


Spec Code


Note

Valid spec codes are those where the flag BOM within the assigned spec rule is checked. (S.50.01 Specification Rules).

A valid spec code must have at least one entry on S.50.06 Specification Items so that the LOV of the next two items can get a valid value (short code, option code).

Updating the spec code(s) does not automatically clear the short code, option code, and sizes (except for commodity group, commodity part, commodity code, and ident code).


BOM Position Views

If the Project Default Parameter "ZX_DP_SPEC" is set to 'Y', then the LOV on this item does not show Specs from Non Login disciplines. If the Project Default Parameter "ZX_DP_SPEC" is set to 'N', then the LOV shows all the Specs.

The Revision number specifies the Spec Revision Number

Short Code



Option Code


Item Type


Sub positions on tagged items (item-rule in (TWM, TOM, TFM, REF)) are possible.


Group

This field specifies the Commodity Group. The field can have a 10-character alphanumeric value representing a unique identifier for this commodity group. Examples of this code could be PIPE, VALVE, or FLANGE.


Part

This field specifies the unique name for the Commodity Part.



BOM Position Views

Commodity Code



Ident Code



Tag Number


On double-click of this field, the software opens a new dialog box called B.20.01.22, if the tag number is not empty and the item type belongs to an item rule like TOM, TWM, or TFM.



The software opens an LOV and shows data from the module S.80.21 Ident Tag Numbers if the item type belongs to the item rule like SOT or SWT.


Plate Number


Size 1


Size 2


Size 3



BOM Position Views

Size 4


Size 5


Object Code

This field specifies the code necessary to hold the relation to CAD-System.

Link BOM

This field specifies the Link Structure Element Name (Node Name) from BOM.

Module B.20.01.17 Link BOM can be used to allocate a bill of materials (BOM), for example, a spare parts list to a position. Only the reference to this bill of materials is recorded in the position. The items in the spare parts list are not copied.


Created By

This field describes the way this record was created/updated.

Ctrl


Rev1


Rev2


Req



BOM Position Views

Reload



Path


Position Values

Fig 2.9 – Single Bulk Material View – Position Values

This block contains all the variable attributes and attribute values that are appended to a bill of materials position. The attributes are inherited from the bill of materials node through inheritance logic or assigned directly on the basis of the defined, discipline-specific attributes.

To make attributes and their values visible in this block, the following administration steps are necessary.

• Define a User-Group (A.20.41). Assign discipline(s) and user to this group.

• Assign User-Groups to Project-Groups (A.20.42).


BOM Position Views

Description of the Fields Attribute

This field specifies the Attribute assigned on B.10.03 to the used Node Type or B.10.04 to the discipline.

Hint Text

This field shows the hint text specified on Module A.50.01 for the given Attribute.

Manual

This field specifies whether this record can be modified manually (checked). If the record is checked, then it will not be updated by attribute propagation, unless the indicator for 'Update allowed' for this attribute is checked on A.50.01.

Value

This field specifies the attribute value of the current attribute.

If Mandatory-Flag is set (Checked) on B.10.03 / B.10.04 for the current attribute and it belongs directly to the Node-Type (Propagate-Seq = 1), the color will be GREEN.

If the color of the field is GREEN and no value is entered, a message (MAG-00078) appears as a hint.

Order by Functionality By default, the data in this block are sorted depending on the Group and Attribute values. The ‘Order By…’ button will allow sorting of the data using multiple fields in a required order. The sorted order of the block will be displayed in the ‘Ordered By’ display item.

Project default ‘ZB_SPAS’ for Showing Attributes A new Project Default for showing attributes in Single Positions has been included. The Project Default will determine whether to show All Attributes or Attributes in Attribute Security for the User, Project, Role, and Discipline.

The name of the Project default is ‘ZB_SPAS’, and its description is ‘SinglePos Attribute Security’. The values for this Project default will be set to ‘Y’ and ‘N’. The value ‘N’ is the default value for the Project Default, and the Single Position window will show all the Attributes in this situation. If the project default value is set to ‘Y’, then the Single Position will show only those attributes to which the Login User has access to.


BOM Position Views

Commodity Details

Fig 2.10 – Single Bulk Material View – Commodity Details

Here are the Attributes shown from the Module Standardization (Only for Information). The Commodity Details tab will be displayed for all item types except the ‘TAB’ item type.

Description of the fields Attribute

Tablename (S.20.02).

Value

Detail value (S.20.02 2. Block).

Description

Long Description.

Order by Functionality By default, the data in this block will be sorted depending on the Attribute values. The ‘Order By…’ button will allow sorting of the data using multiple fields in a required order. The sorted order of the block will be displayed in the ‘Ordered By’ display item.


BOM Position Views

Ident Values Ident Values

Fig 2.11 – Single Bulk Material View – Ident Values

This block contains all the standard attributes for idents and their attribute values appended to a bill of materials position. The attributes are inherited from the bill of materials node through inheritance logic or assigned directly on the basis of the defined, discipline-specific attributes. The Ident Values tab will be displayed when the item type is ‘TAB’.

Description of the Fields Group

This field specifies the short name for this attribute type.

Attribute

This field specifies the attribute code.

Value


Unit

This field specifies the unit code.


BOM Position Views

Order by Functionality By default, the data in this block will be sorted depending on the Group and Attribute values. The ‘Order By…’ button will allow sorting of the data using multiple fields in a required order. The sorted order of the block will be displayed in the ‘Ordered By’ display item.

Sub Positions A sub-position can include an assembly defined in the parts master. A hierarchical structure is possible, and a depth of 14 levels of hierarchy sub-positions is allowed.

If a sub-position exists for any position, then a plus-sign (+) is displayed after the Pos item. When the cursor focus is on a record in the main block (SBMV), its sub-positions, if any, are displayed in the Sub Positions block. The Sub Positions block is for viewing purposes only (that is, it is not editable).

The Parent Position information is shown in the Parent Position Tree block.

The Sub Position block displays the following information:

• Pos

• Quantity

• Unit

• Commodity Code

• Ident Code

• Description

While the user navigates among the position views (MPV, SBMV, STMV), the Sub Positions block and Parent Position Tree block information are preserved.

Pop-up Menu Options

Fig 2.12 – Single Bulk Material View – Pop-up Menu


BOM Position Views

Add/Edit Sub Pos Nodes

To list/create sub position(s), select Add/Edit Sub Pos Nodes. This is only allowed on a valid and saved position.

When the “Add/Edit Sub Pos Nodes” menu item is selected from a Pos in the main block, the following events occur:

• The sub position records in Sub Position block are displayed in the main block.

• In the Parent Position Tree block, a node is added.

• The Parent Position Tree block displays information about Level (like Level1, Level2, etc.), Positions path (like /20/30), and Position Values (like Pos: (20), SpecCode: (AC0014), etc.).

Fig 2.13 – Single Bulk Material View – Parent Position Tree

Back to Parent

Use the Back to Parent pop-up menu option to reach a higher level. The navigation works level by level. Back to Parent is only available on sub positions. This button is disabled on the highest level.

When the “Back to Parent” menu item is selected, the following events occur:

• The Main block shows the parent position information along with position information at this level.

• In the Parent Position Tree, the top node (that is, the Node with the Maximum depth) is deleted.

List Download

This pop-up menu option is used to export the single position data into Excel or OMI format. When we select this pop-up menu option, the List Download B.20.01.44 dialog box will pop up. This will contain two radio buttons that will allow the user to specify the predefined formats to export the position data. The two options are OMI Export and Excel Export, respectively. When we select Excel Export, the single position data will be exported to a predefined Excel format.

Attach Documents


BOM Position Views

This pop-up menu option is used to attach or link documents to the positions and to the nodes in the BOM. When the user selects this pop-up menu option, D.10.21 Attached Documents screen will appear. Here the user can see all documents that have been attached to the node or to the position. The user can also attach or remove the documents to a BOM node or to a position of a node.


BOM Position Views

Single Tag Material View

Fig 2.14 – Single Tag Material View

Description of the Felds Pos


Quantity

This field specifies the Ident quantity on this Position.

Unit


Default value: The parameter called ZB_UNIT_ID on A.20.012 and / or A.20.13 can be set to a valid Unit Code (A.10.12 Units of Measure) within the Unit Group.

Resv%Sub Qty



BOM Position Views

Issued%Sub Qty

This field specifies the issued quantity / substitute quantity.

MLD Issue Qty

This field shows the quantity issued on the screen C.20.22 MIR by the Commodity that is of the Issue Type 'Miss, Lost or Damage'. When the field is shown in red, a quantity exists for this BOM-Position but has a different qty-unit in the Issue as in the BOM.

Status

This field specifies the status for the corresponding position (the Issue Status is defined on B.10.08).

The LOV on this item displays all the Issue Statuses, excluding those Issue Statuses with the "No Display" check box checked for the logged-in discipline on the B.10.08 Window-2 screen.

List Status


Lst Date

This field specifies the date this list status was set.

Lst User


Spec Code


Note

Valid spec codes are those where the flag BOM within the assigned spec rule is checked. (S.50.01 Specification Rules).

A valid spec code must have at least one entry on S.50.06 Specification Items so that the LOV of the next two items can get a valid value (short code, option code).

Updating the spec code(s) does not automatically clear the short code, option code, and sizes (except for commodity group, commodity part, commodity code, and ident code).

The Revision number specifies the Spec Revision Number.


BOM Position Views

Short Code



Option Code


Item Type


Sub positions on tagged items (Item-rule in (TWM, TOM, TFM, REF)) are possible.


Group

This field specifies the Commodity Group. The field can have a 10-character alphanumeric value representing a unique identifier for this commodity group. Examples of this code could be PIPE, VALVE, or FLANGE.


Part

This field specifies the unique name for the commodity part.


Commodity Code




BOM Position Views

Ident Code



Tag Number


On double-click of this field, the software opens a new dialog box called B.20.01.22 if the tag number is not empty and the item type belongs to an item rule like TOM, TWM, or TFM.



The software opens an LOV and shows data from the module S.80.21 Ident Tag Numbers if the item type belongs to the item rule like SOT or SWT.


Plate Number


Object Code

This field specifies the code necessary to hold a relation to CAD-System.

Link BOM

This field specifies the Link Structure Element Name (Node Name) from the BOM.

Module B.20.01.17 Link BOM can be used to allocate a bill of materials (BOM), for example, a spare parts list to a position. Only the reference to this bill of materials is recorded in the position. The items in the spare parts list are not copied.



BOM Position Views

Created By

This field describes the way this record was created/updated.

Ctrl


Rev1


Rev2


Req


Reload



Path


Parent Pos Path

This field shows the parent position path information like /20, which means that the position displayed in STMV is a child of position 20 (one level up in the hierarchy). This is the only indication of sub-positions in the Single Tag Material View.


BOM Position Views

Ident Values Ident Values

Fig 2.15 – Single Tag Material View – Ident Values

This block contains all the standard attributes for idents and their attribute values appended to a bill of materials position. The attributes are inherited from the bill of materials node through inheritance logic or assigned directly on the basis of the defined, discipline-specific attributes. The Ident Values tab will be displayed when the item type is ‘TAB’.

Description of the Tree View The Ident values will be represented in the form of a Tree view. The root nodes in this tree will represent ‘Group’. The Child nodes will represent a combination of Attribute and Value (<Attribute> : <Value>).

Description of the Fields Group

This field specifies the short name for this attribute type.

Attribute

This field specifies the attribute code.

Value



BOM Position Views

Unit

This field specifies the unit code.

Order by Functionality By default, the data in this block will be sorted depending on the Group and Attribute values. The ‘Order By…’ button will allow sorting of the data using multiple fields in the required order. The sorted order of the block will be displayed in the ‘Ordered By’ display item.

Position Values

Fig 2.16 – Single Tag Material View –Position Values

This block contains all the variable attributes and attribute values that are appended to a bill of materials position. The attributes are inherited from the bill of materials node through inheritance logic or assigned directly on the basis of the defined, discipline-specific attributes.

To make attributes and their values visible in this block, the following administration steps are necessary.

• Define a User-Group (A.20.41). Assign discipline(s) and users to this group.

• Assign User-Groups to Project-Groups (A.20.42).


BOM Position Views

Description of the Fields Attribute

This field specifies the Attribute assigned on B.10.03 to the used Node Type or B.10.04 to the discipline.

Hint Text

This field shows the hint text specified in Module A.50.01 for the given Attribute.

Manual

This field specifies whether this record can be modified manually (checked). If the record is checked, then it will not be updated by attribute propagation, unless the indicator for 'Update allowed' for this attribute is checked on A.50.01.

Value


If the Mandatory-Flag is set (Checked) on B.10.03 / B.10.04 for the current attribute and it belongs directly to the Node-Type (Propagate-Seq = 1), the color will be GREEN.

If the color of the field is GREEN and no value is entered, a message (MAG-00078) will appear as a hint..

Order by Functionality By default, the data in this block will be sorted depending on the Group and Attribute values. The ‘Order By…’ button will allow sorting of the data using multiple fields in a required order. The sorted order of the block will be displayed in the ‘Ordered By’ display item.


BOM Position Views

Multi Status View

This new tab page will display the positions grouped according to the issue status. The tab page will have three blocks. Each block will display positions with a particular issue status. Which block will display positions with which issue status depends upon the values of the project defaults ZB_MSV_IS1, ZB_MSV_IS2, and ZB_MSV_IS3. There will be no default values for these project defaults and if the user does not specify any value for a project default, then the block corresponding to that project default will not display any records.

All of the three blocks support add/modify and delete functions. The configuration set to MPV will also be reflected here. All three blocks will have the same configuration. The user can also set the configuration at any block and the configuration will be propagated to the rest of the two blocks and MPV automatically. Similarly, other functions available on the MPV tab page like sorting, column width and spacing, document attachment, etc are also available here.

For the details of the fields and various supported operations, refer to the Multi Position View section of this document.


BOM Procedures / Macros

BOM Procedures / Macros There may be instances where a set of logical statements is needed to be executed for the BOM Positions.

The functionality of BOM Procedures/Macros allows the user to define a set of logical statements as BOM Procedures. The functionality also allows the user to execute the defined BOM Procedure / Macro corresponding to the BOM Nodes or BOM Positions.

If the user needs to execute a set of BOM Procedures cumulatively, then he / she can define a BOM Macro to which a set of BOM Procedures can be associated. While executing BOM Procedures / Macros, the user can also give appropriate parameter values.

BOM Procedures / Macros are defined on the screen B.10.21 BOM & SA Procedures/Macros.

Please refer to the document corresponding to B.10.21 BOM & SA Procedures/Macros for detailed functionality associated with the screen.

The user can execute the BOM Procedure / Macro on the screen B.20.03 Advance Maintain BOM. The BOM Procedures are available for execution to those users/roles having certain privileges (EXE_ALL_BOM_PROCEDURES).

The BOM Macro can also be executed resulting in cumulative execution of all the associated BOM Procedures.

While executing the BOM Procedures (corresponding to BOM Nodes), the user has the flexibility to select the Node(s) ( or its hierarchy) corresponding to which the BOM Procedures / Macros can be executed.

While executing the BOM Procedures (corresponding to BOM Positions), the user has the flexibility to select the Issue Status of the positions to which the BOM Procedures/Macros are to be applied. The user also has the flexibility of whether to include the hierarchy under the selected node (sub-tree) to apply the BOM Procedures/Macros.

A summary for the executed BOM Procedure / Macro is generated on execution. The log generated during execution of BOM Procedure / Macro is recorded, and the user can review the log messages.



Execution of BOM Procedures / Macros For execution of BOM Procedures/Macros, the user/role must have the EXEC_ALL_BOM_PROCEDURES privilege. This privilege is defined on the screen A.30.06 Menu Settings and A.20.06.04 User Privileges.

Fig 3.1 – Assigning privilege through A.30.06 Menu Settings

Fig 3.2 – Assigning Menu Privilege through A.20.06.04 User Privileges

It should be noted that BOM Procedures can be executed against BOM Nodes (LN_ID) or against BOM Positions (LP_ID). In other words, BOM Procedures / Macros are executed for either for the selected (through the option screen) Nodes (LN_ID) or for all BOM positions (LP_ID) for the selected Node(s) (LN_ID).

BOM Procedures / Macros can be invoked from three places on B.20.03:

• From the Pop-up Menu of the BOM Tree

• From the Pop-up Menu of the Flat View

• From fast call buttons

At any time, there can be a maximum of 10 BOM Procedures and 10 BOM Macros that are available for execution through the pop-up menu(s). Also, there can be 4 BOM Procedures and/or Macros that are available for execution through fast call



buttons. All these options are set on the screen B.10.21 BOM & SA Procedures/Macros.

Fig 3.3 – Selecting BOM Procedure from pop-up menu of BOM Tree

Fig 3.4 – Selecting BOM Macro from pop-up menu of BOM Tree



Fig 3.5 – Selecting BOM Procedure from pop-up menu of Flat View

Fig 3.6 – Selecting BOM Procedure from pop-up menu of Flat View

Fig 3.7 – Selecting BOM Procedure or Macro from fast call buttons



If the user does not have the privileges for execution of BOM Procedures or Macros, and if the user selects execution of a BOM Procedure or Macro, the following message will appear, and the user cannot execute the BOM Procedures or Macros.

Fig 3.8 – Alert for privilege

The user should also note that the BOM Procedures/Macro cannot be executed on a Node that has been released. If the user tries to execute a BOM Procedure/Macro under a released node, the following message will appear, and the user cannot execute the BOM Procedure or Macro.

Fig 3.9 – Alert for Released Node

After the user selects a BOM Procedure or Macro for execution, the parameter screen is displayed where the user can select / enter the values.

The title of the window displays the name of the BOM Procedure or BOM Macro that has been selected for execution.



Fig 3.10 – Parameter Screen for BOM Procedures / Macros (to be executed against Nodes)

Fig 3.11 – Parameter Screen for BOM Procedures / Macros (to be executed against Positions)



The user can also give the appropriate value of the corresponding parameters.

Fig 3.12 – Parameter Screen (Procedure Parameters) for BOM Procedures / Macros

The user can then continue with execution of the BOM Procedure / Macro.

On successful execution of the BOM Procedure / Macro, the summary of the transaction is displayed.

Fig 3.13 –BOM Procedures / Macros Execution Summary screen

The user can then view the log details by clicking the ‘Show Log’ button.



Fig 3.14 –BOM Procedures / Macros Execution Logs screen

The log screen can also be invoked through the pop-up menu of the BOM Tree or Flat View.

Fig 3.15 –Execution Logs screen selection from BOM Tree



Fig 3.16 –Execution Logs screen selection from Flat View



If any BOM Procedure (even those that are associated with a BOM Macro) is not in a valid state (that is, not compiled successfully), if the user decides to execute that particular BOM Procedure, the following message appears:

Fig 3.17 –Alert for invalid BOM Procedure

The software opens screen B.10.21 BOM & SA Procedures/Macros with the corresponding procedure queried.

Fig 3.18 – B.10.21 BOM & SA Procedures/Macros screen with invalid BOM Procedure



The user can then correct the BOM Procedure.

Fig 3.19 – B.10.21 BOM & SA Procedures/Macros screen (Edit Procedure)

The user must compile the BOM Procedure successfully before trying to execute it again.


Ident History


Ident History The figure below details the appearance of the Ident History screen. This screen is invoked from the Single Tag Materials tab page of Position Views.

Note

• To access the Ident History screen, double-click on the attribute Value field in the Ident Values tab in the Single Tag Materials tab. The Ident Values tab is visible only for tagged attribute based BOM positions.

Fig 4.1 – Ident History UI

As shown in the above figure, the UI contains the following three tab pages.

Compare: On this page, the user can compare the attribute values of the ident between two dates. The user can supply two dates and times as From date and To date. The attributes and their values on these two dates are picked up from the history and are displayed in the comparative format.

Flashback: This tab page allows the user to view the attributes and values of an ident on some date and time. The philosophy of 'as it has been seen at that time' is used. The flashback values are displayed in a comparative format along with the current values of the attributes. This page also allows the user to set the flashback values as current values for the ident.

Compare Idents, Flashback Idents, and Ident History tab pages.

Ident and Ident Code for which Ident History is

invoked.

Dates to Compare attribute values of the Ident.

Attribute Group and Attribute

Code

Values of Attributes of the Ident on

From and To Dates

Ident History

History: This tab page provides the utility of viewing all historical changes made to the values of the attributes of the ident. The change history can be viewed between two dates. All the historical records between these two dates are fetched and displayed.


Ident History

Compare Ident Values This tab page enables the user to compare the values of the attributes of an ident on two dates and times. This provides the following two viewing options:

Show All Attributes: If this option is selected, then all the attributes and values for both the date and time are displayed, regardless if there is a change in the value or not.

Show Changed Attributes: If this option is selected, only the attributes that have different values on the given two dates and times are displayed. In case none of the attributes have different values, none of them will be displayed.

Any comment associated to the attribute value is displayed as a tool tip. The first 100 characters of the stored comment are displayed in the tool tip. In order to view the tool tip, put the focus in the value field and drag the mouse to that field.

Fig 4.2 – Comment associated with a value of an attribute displayed as tool tip.


Ident History

In order to view the complete comment associated with the value of the attribute, the user can double-click on that value field. This will open a small child window as shown below. The window displays the entire comment.

Fig 4.3 – Comment child window displaying the full comment.

The comparison table displays the following fields related to the ident:

• Attribute Group: This field displays the group code for the attribute.

• Attribute Code: This field displays the attribute code for the attributes for the ident.

• Value as on From Date: This field displays the value for the attributes on the From date and time supplied by the user. The label of this field changes dynamically and includes the date and time supplied in the From date field.

Note

• If an attribute is not there in the ident on some given date or the attribute is deleted, the value field will display ‘Attribute Not Found’. If an attribute is there but the value specified for it is null, the value field will display ‘No Value Specified’.

• Value as on To Date: This field displays the value for the attributes on the To Date and time supplied by the user. The label of this field changes dynamically and includes the date and time supplied in the To date field.

Note



Ident History

Operations • Compare: This operation enables the user to compare the values of the

attributes on two dates and times. The user will have to supply the date and time for the From Date and Time and for the To Date and Time. On click of the Compare button, the values on these two dates are fetched and displayed.

• Show Changed Attributes: Selection of this option enables the user to view only the attributes that had their values changed. If there are already comparative data displayed and the user selects the option after clicking Compare, the previous result display will update, and only the changed attributes will be listed.

• Show All Attributes: Selection of this option enables the user to view all the attributes regardless of whether there is a change in the values or not. If there are already comparative data displayed with the ‘Show Changed Attributes’ option, and the user selects this option, the previous result display will update, and all attributes will be listed.

• Display Comment: Double-clicking an attribute value field opens a comment child window and displays the comment associated with that value. If there are no comments specified, the child comment window displays ‘No Comments Specified’ as the comment.


Ident History


Flashback This tab page enables the user to view the values of the attributes of an ident on some date and time. This works on the philosophy of ‘the values as seen on that date and time’.

Like the ‘Compare Idents’ tab page, the comment associated to the attribute value is displayed as a tool tip. The first 100 characters of the stored comment are displayed as a tool tip. In order to view the tool tip, put the focus in the value field and drag the mouse to that field.

In order to view the complete comment associated with the value of the attribute, the user can double-click on that value field. This will open a small child window as shown on the ‘Compare Idents’ tab page, which further displays the entire comment.

Fig 4.4 – Flashback Idents tab page

Minute part of time field can be incremented or decremented by this value.

Type in the value and click + button to increment or – button to decrement.

Set Current – This will set the

Flashback attribute values as the current

values. Flashback the

attribute values as of

this date and time.

Ident History

The comparison table displays the following fields related to the ident:


• Attribute: This field displays the attribute code for the attributes for the ident.

• Value as on Flashback Date: This field displays the values for the attributes on the flashback date and time supplied by the user. The label of this field changes dynamically and includes the date and time as supplied in the flashback date field.

Note


• Current Value: This field displays the values for the attributes on the current date and time. The values in this column display the recent values of the attributes of the ident as compared to the flashback date.

Note


Operations • Flashback: This operation enables the user to view the values of the

attributes on a given date and time (Flashback Date and time). The user will have to supply the date and time for the Flashback Date and Time field. When the user clicks the Flashback button, the values on that date are fetched and displayed along with the current or recent values.

• Set Current: This button resets the values of the attributes of an ident to the values on some previous date and time (Flashback Date and Time). The button initially remains disabled. After supplying a date, when the user clicks and fetches the values from the flashback date, the Set Current button gets enabled. Now, if the user clicks the Set Current button, the software will set the flashback values as the current or recent values for the attributes. Before doing so, the software will pop up a message asking the user to confirm the action.


Ident History

• Display Comment: When the user double-clicks the mouse on an attribute value field, the software opens a comment child window and displays the comment associated with that value. If there is no comment specified, the child comment window displays ‘No Comments Specified’ as the comment.


Ident History

Ident History This tab page enables the user to view the historical values of the attributes of an ident between two given dates and times.

Like the ‘Compare’ or ‘Flashback’ tab pages, the comment associated to the attribute value is displayed as a tool tip. The first 100 characters of the stored comment are displayed as a tool tip. In order to view the tool tip, put the focus in the value field and drag the mouse to that field.

In order to view the complete comment associated with the value of the attribute, the user can double-click on that value field. This will open a small child window as shown on the ‘Compare’ tab page. The window further displays the entire comment.

Fig 4.5 –Ident History Tab page

The data table displays the following fields related to the ident:


• Attribute: This field displays the attribute code for the attributes for the ident.

• Attr Value: This field displays the value for an attribute before the change made on the date and time shown in the Mod. Date field.


Ident History


• Mod. Date: This field shows the date on which the value of the attribute was modified.

• Modified By: This field displays the user who modified the value of the attribute.

Operations • Show History: This operation enables the user to fetch and view the

historical values of the attributes between two dates and times (From and To Date and time). The user will have to supply the dates and times for the historical records. When the user clicks the Show History button, all the historical records for the attributes and their values between the two supplied dates are fetched and displayed.

• Display Comment: When the user double-clicks on an attribute value field, the software opens a comment child window and displays the comment associated with that value. If there is no comment specified, the child comment window displays ‘No Comments Specified’ as the comment.