Define Module Code

Relationships - Examples

The following examples show a variety of inclusive PM code relationships with details of how you can configure them using the Module Codes dialog box.

Example

1

PM code A will “only” exist when PM code B exists.

Figure 392: Code Table Example 1

Figure 393: Inclusive Configuration 1

Example

2

PM code A will “only” exist when PM codes B or C exist.

Figure 394: Code Table Example 2

Figure 395: Inclusive Configuration 2

Example

3

PM code A will “only” exist when PM codes (B and C) or D exist.

Figure 396: Code Table Example 3

Figure 397: Inclusive Configuration 3

Example

4

PM code A will “always” exist when PM code B exists.

Figure 398: Code Table Example 4

Figure 399: Inclusive Configuration 4

Example

5

PM code A will “always” exist when PM codes B or C exist.

Figure 400: Code Table Example 5

Figure 401: Inclusive Configuration 5

Example

6

PM code A will “always” exist when PM codes (B and C) or D exist.

Figure 402: Code Table Example 6

Figure 403: Inclusive Configuration 6

Restrictions

and Limitations

Examples 4, 5, and 6

Selecting one of the other module codes in the relationship in the Module Codes dialog box will not display the reverse relationship, even though the relationship is mutual.

In example 4, selecting module code B will not display an inclusive relationship with module code A. This is because the mutually inclusive relationships supported by Capital can become too complex to display in the Module Codes dialog box.

In example 6, module code A is in a mutually inclusive relationship with module codes (B and C) or with D. If you select module code B, its relationship with A cannot be shown in the Module Codes dialog box.

Parent Topic:

Functional and Production Module Code Maintenance

Capital Harness Designer User Guide, 2512

Unpublished work. © 2025 Siemens