ManufacturingKnowledge

Managing and tracking changes > Using ECNs and MCNs

Setting MCN requirements by a structure's root node type and release status

By default, manufacturing change notices (MCNs) are applied to process structures based on the process plan's root node type. If you are using the same structure (for example, a plant BOP) to define multiple projects, and each project requires that an MCN be set when the project moves to a specific phase or release status, you can set Teamcenter to require that an MCN be manually created before work can proceed on the structure.

Use the preference MEMCN_change_notice_mandatory_types to define a list of mandatory change revisions for BOP topline item types. The topline item types can optionally include a release status name. For example, if you have multiple plant BOPs, a value of Mfg0PlantBOP;Pending in MEMCN_change_notice_mandatory_types mandates that an MCN must be manually created for each plant BOP when its release status is pending. Until the association is completed, such structures cannot be edited. Similarly, Process;TCM Released applies an MCN to any bill of process whose status changes to TCM Released. If anyone attempts to change the structure after the defined status is reached, they will receive an error informing them that they must apply an MCN revision to the structure.

Note

  • The separator ; in the MEMCN_change_notice_mandatory_types example values above should be the same as that defined in the preference TcServices_field_separator. The default value is ;.

  • You must restart the server after adding or changing the preference values.

Source: https://docs.sw.siemens.com/en-US/doc/282219420/PL20251212545240207.mse/xid1446032 · retrieved 2026-07-11