Use this activity to associate similar PM actions, where the action in the
PM Action field includes the tasks done in the Replaces PM Action
field and therefore it is not required to generate the second PM action. Note
that the replacement will take place for Calendar, Event and Condition generation but only
when both PM actions are selected in the same generation process. The
replacement functionality could be summarized as in the following table. Note
that Yes in Connected column means that either one or both of the PM actions in
the PM Action field and the Replaces PM Action field is/are
connected.
| PM Action | Replaces PM No | Connected | Allowed |
| B | A | No | Yes |
| C | B | No | Yes (It is possible to have multi layered replacements) |
| PM Action | Replaces PM No | Connected | Allowed |
| B | A | Yes | No (Connection and Replacement not allowed together) |
| PM Action | Replaces PM No | Connected | Allowed |
| B | A | No | Yes |
| C | A | No | Yes (a PM action can be replaced by more than one PM action) |
| PM Action | Replaces PM No | Connected | Allowed |
| C | A | No | Yes |
| C | B | No | Yes (a PM action can replace many other PM actions) |
As a result of this activity, a PM action is included in a replacement structure.
Material demand of the PM action to be replaced will not be available for the Inventory Part Availability Planning for the corresponding PM plan lines.