This functionality is only available for certain module packages. Info / Copyright

Parts Management: Basics

The following terms and definitions are important to working efficiently with parts management:

Principles of operation of the program

Analogous to the other master data, all of the necessary information on parts required for independent work with a project are stored in the project itself. There are always two parts databases (redundant data management): the central parts database for all projects and the project's internal parts database, which only contains parts placed into the project.

Within a project, the parts from the parts project database are referenced, i.e., a part that is used 10 times is stored only once, and is referenced 10 times in the project (via the part number). Parts data can therefore be easily changed and synchronized via the central parts database.

Window structure of parts management

The main window of parts management is split vertically, just as in Windows Explorer. In the left half of the dialog, the data to be managed is displayed in a tree or list.

The individual part numbers are displayed at the lowest hierarchy level in the tree. If more than one variant of the part exists, these variants are shown below the part.

As an alternative to the tree, you can also display the data in a list, where the scope of the display is set using the Popup menu > Configure representation. Here, the list shows all parts, but no manufacturers, suppliers, or customers, and only those properties are shown which all parts have (such as for example, part number, product group, and so on).

In the right half of the dialog, you see the information belonging to the elements selected in the left window. There are tabs available for all part types (such as General, Prices / Other, etc.), and tabs with special input options for a specific part type (such as Module, Assembly, etc.).

Adapting the tree structure

To allow customer-related selection of parts by technical information without selecting them by part number, you can adapt the tree view to suit your requirements (so-called "tree configuration"). For example, you can create certain structure nodes and save specific criteria for the planning selection under a name. The part search then occurs in the tree structure based on multi-level device description criteria and not the part number.

See also