BeyondERP.Newsletter
Menu

Setup step on the Engineering change management parameters page · Engineering change management

Set up Engineering change management parameters

Use this page to decide how item, BOM and route names are assigned on release, whether inactive BOMs or routes may be released, whether releases need manual acceptance, and to set default category, priority, severity calculation and BOM release depth for change orders.

Used by
Product engineer, Product engineering manager
Business process
Define product policies
Menu item
EngChgProductParameters
Main table
EngChgProductParametersLocal
Setup steps
1 on this page
Show what matters for
SETUP GUIDEHow to set it up8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA setup page, per company, holding the parameters that control how products are received when released from the engineering company (Release control tab) and the defaults and rules for engineering change requests and orders (Engineering change management tab).
What you do hereUse this page to decide how item, BOM and route names are assigned on release, whether inactive BOMs or routes may be released, whether releases need manual acceptance, and to set default category, priority, severity calculation and BOM release depth for change orders.
ExampleFor example, in the operational company you set Product acceptance to Manual so that releases from engineering must be reviewed on the Open product releases page before they become released products.
Engineering change management parameters page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

Setup steps on this page

Set up Engineering change management parameters

Use this page to decide how item, BOM and route names are assigned on release, whether inactive BOMs or routes may be released, whether releases need manual acceptance, and to set default category, priority, severity calculation and BOM release depth for change orders.

Steps from Microsoft

  1. Go to Engineering change management > Setup > Engineering change management parameters.
  2. On the Release control tab, set Item number rule, BOM name rule and Route name rule.
  3. Set Run BOM check and the release behaviour for inactive BOMs and routes.
  4. Set Product acceptance to Manual or Automatic.
  5. On the Engineering change management tab, set the default Category and Priority and the Severity rule.
  6. Set Re-release impacted products and BOM levels to release, then save.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansTable column
Item number ruleWhether a released product keeps the engineering product number or takes the next local product number sequence value.Microsoft Learn ReleaseItemNumberRule
BOM name ruleWhether the received BOM is named after the engineering name or the receiving item number.Microsoft Learn ReleaseBOMNameRule
Route name ruleWhether the received route is named after the engineering name or the receiving item number.Microsoft Learn ReleaseRouteNameRule
Run BOM checkWhether a BOM check runs when the product is received.Microsoft Learn AutoCheckBOM
Release behavior of inactive BOMAccept, warn or refuse releasing a product whose BOM is inactive.Microsoft Learn
Product acceptanceManual adds an acceptance step on Open product releases; Automatic shows the product on Released products straight away.Microsoft Learn ProductReleaseControlRule
Severity ruleWhether change order severity is entered manually, calculated on demand, or calculated automatically from severity rule sets.Microsoft Learn EcmSeverityRuleType
BOM levels to releaseHow many BOM levels are released with a product; deeper levels are not released.Microsoft Learn EcmMaxBOMLevelRestriction

Test checklist

  1. Check the BOM number sequence (and the formula number sequence if formulas are used) is set to Automatic.
  2. In an operational company set Product acceptance to Manual, then release an engineering product to it from the engineering company.
  3. In the operational company open Engineering change management > Common > Product releases > Open product releases and check the product shows Pending acceptance.
  4. Select Accept and check the item appears on Released products with the number the Item number rule predicts.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Set up Engineering change management parametersItem number rule = Engineering product number when operational companies must use the same product number as the engineering company; Product acceptance = Manual in companies that must review products before they become released productsLearn says to select Engineering product number when the number in the receiving legal entity should match the engineering company, and Manual adds an acceptance step through the Open product releases page before the product reaches Released products.Should a released product keep the engineering product number or take a local number in each operational company?Building severity rule sets but leaving Severity rule at Manual. The rule sets are only used when Severity rule is Calculate or Calculate automatically, so change orders keep a hand-typed severity.Test: Calculated severity on a change order

Feature management and licence

Feature to turn onEngineering Change Management (Mandatory, on by default)
Licence or add-inEngineering Change Management configuration key (License configuration > Trade); Product dimension - Version key if you track versions in transactions

Microsoft Learn

Solution architect

5Design impact

Can it be undoneReversible: The release-control fields apply when a product is released to a legal entity and the change management fields are defaults for new change requests. Changing them affects later releases and new requests; products already released keep their numbers and names.
If you change it laterChanging Product acceptance switches a company between automatic release (products appear directly on Released products) and manual review on Open product releases; the other release-control rules change how item numbers, BOM and route names are assigned on every future release. Microsoft Learn
Technical architect

6Technical

Menu itemEngChgProductParameters Checked in Dynamics 365
FormEngChgProductParameters Checked in Dynamics 365
TableEngChgProductParametersLocalShown as “PRODUCT PARAMETERS” in Record infoChecked in Dynamics 365
Who can open itPrivilegesManage engineering change management parameters EngChgProductParametersMaintainView engineering change management parameters EngChgProductParametersViewDutiesInquire into engineering change management policies EngChgEngineeringChangeManagementPoliciesInquireEnable the engineering change management process EngChgEngineeringChangeManagementProcessEnable
2 security rolesProduct engineer EngChgProductEngineerProduct engineering manager EngChgProductEngineeringManager
Checked in Dynamics 365
Roles to set it up and use itTo set it up or change itProduct engineering manager EngChgProductEngineeringManagerTo use itProduct engineer EngChgProductEngineerGive people one of these roles. On this system, 2 roles can open this page.Checked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=EngChgProductParameters
Everyone

8Sources

To cite this step: EC-SETUP-010, Set up Engineering change management parameters. Beyond ERP Atlas Hub, 2026-11-11. https://www.beyonderp.cloud/atlas/step/EC-SETUP-010