---
title: "Set up Engineering Change Management"
slug: "bc-setup-engineering-change-management"
tags: ["Task"]
updated: 2026-06-25T09:59:00Z
published: 2026-06-25T09:59:00Z
canonical: "docs.staedean.com/bc-setup-engineering-change-management"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up Engineering Change Management

## Steps

1. Choose the ![](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/image(139).png) icon (Alt+Q).
2. Type **Engineering Change Management Setup**.

| Field | Description |
| --- | --- |
| Enable ECR Services | Enables ECR and makes the ECR wizard appear in the various documents. |
| Allow Edit on Order Line | When true, **User Entry Values** lines are created, which you can edit in the ECO. |
| Show Current Value | When true, **Existing Values** lines are created and shown in the ECO (in blue). |
| Create BOM Version | When true, BOM revisions are created as new BOM versions using the revision code as the version no. |
| Create Routing Version | When true, routing revisions are created as new routing versions using the revision code as the version no. |
| Item Template | Select a template to complete new items. |
| Engineering Change Request Nos. | Select the number series for engineering change requests. |
| Engineering Change Order Nos. | Select the number series for engineering change orders. |
| Engineering Staging Nos. | Select the number series for manual engineering change orders. |
| ECR Priority | The priority of an ECR is initially calculated as Severity * Impact. You can override this suggested priority at Anywhere Mobility Solutions time. See [ECR Priority](/business-central/docs/bc-setup-engineering-change-management#ecr-priority) below. |
| User Defined Fields 01..10 | Set the captions for the user defined fields in the EC Staging and Eng. Change Order. |

### ECR Priority

**Severity** indicates the urgency of the requested change:

- **Low**: the product is fully functional but could be improved, usually in design.
- **Medium**: the product is functioning but its use is inconvenient.
- **High**: the product is still functioning but in a seriously constrained way.
- **Critical**: using the product is impossible and/or dangerous.

**Impact** indicates the financial consequences of the requested change:

- **Low**: current inventories and supply can be depleted first, phased out before the requested change is implemented.
- **Medium**: although the requested change is not interchangeable, inventories and supply on the product are low.
- **High**: the current, relatively high-value inventory must be replaced and supply orders must be cancelled.

### Delivery package

The following items are included in the Product Engineering delivery package to assist you in the setup of Engineering Change Management.

Engineering Change Management Lifecycles:

| Code | Description | File name |
| --- | --- | --- |
| Engineering Change Management-ECR | Engineering Change Management Engineering Change Request | N108 Lifecycle Engineering Change Management-ECR.xml |
| *Import in Lifecycles* |  |
| Engineering Change Management-ECR | Eng. Change Management Requests | Engineering Change Management-ECR Workflow.xml |
| *Import in Workflow* |  |

## Related

- [Engineering Change Management ](/bc-engineering-change-management.md)