BeyondERP.Newsletter
Menu

Setup page · Engineering change management

Product release policies

A setup page where you define release policies: the parameters used when products are released to operational companies, including the template released product per company and whether BOM and route approval and activation status are copied.

Used by
Product engineer, Product engineering manager
Business process
Define product policies
Menu item
EngChgProductReleasePolicy
Main table
EngChgProductReleasePolicy
Data entity
EngChgProductReleasePolicyEntity
Setup steps
1 on this page
Show what matters for
PAGE GUIDEWhat the page does and how to use it8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA setup page where you define release policies: the parameters used when products are released to operational companies, including the template released product per company and whether BOM and route approval and activation status are copied.
What you do hereUse this page to decide, per receiving company, which product data (product, BOM, route, effectivity) is released and which template released product supplies the company-specific field values. Assign the policy to an engineering product category so it applies to all products in that category.
ExampleFor example, operational companies that manufacture a product usually need the BOM, while companies that only sell it do not, so a release policy can release the BOM only to the manufacturing companies.
Product release policies 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

Business processDevelop product strategy › Define product policies
Menu pathEngineering change management › Setup › Product release policies
Set up firstReleased products (template released product) Microsoft Learn
Used next byEngineering product category details Microsoft Learn Release product structure Microsoft Learn
Related pagesEngineering change management parameters Microsoft Learn Open product releases Microsoft Learn
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 Product release policies

Use this page to decide, per receiving company, which product data (product, BOM, route, effectivity) is released and which template released product supplies the company-specific field values. Assign the policy to an engineering product category so it applies to all products in that category.

Steps from Microsoft

  1. Go to Engineering change management > Setup > Product release policies.
  2. Select New on the Action Pane and enter a Name and Description.
  3. On the General FastTab, set Product type, Apply templates and Active.
  4. On the All products FastTab, add a row for each company you release to, and set the Template released product and the copy BOM/route options.
  5. On the Option parameters for engineering products FastTab, set Template BOM, Template route, Copy effectivity and Automatically add to release proposal for each company.
  6. Assign the policy to an engineering product category on its Release policy FastTab.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansTable column
NameThe name of the policy.Microsoft Learn Name
Product typeWhether the policy applies to items or services; it cannot be changed after saving.Microsoft Learn ProductType
Production typeShown only with formula change management enabled; the kind of production (co-product, by-product, none, planning item, BOM or formula) the policy is for.Microsoft Learn PmfProductType
Apply templatesWhether a template released product is always, optionally or never used when releasing.Microsoft Learn ApplyTemplates
ActiveMarks the policy as in use; a policy assigned to a category cannot be deactivated and only inactive policies can be deleted.Microsoft Learn IsActive
Company accounts IDThe receiving company that the row on the All products FastTab applies to.Microsoft Learn CompanyId
Template released productThe released product whose company-specific values are copied to the released product.Microsoft Learn TemplateItem
Automatically add to release proposalWhether products in categories using this policy are automatically proposed for release from an engineering change order to this company.Microsoft Learn AutoRelease

Test checklist

  1. Create a policy with Product type = Item, Apply templates = Always and a row per receiving company with a Template released product.
  2. Try to save with one company row missing a template and check you get an error.
  3. Assign the policy to an engineering product category.
  4. Release a product from the category and check the receiving company's released product takes field values from the template and copies BOM approval and activation as set.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Set up Product release policiesApply templates = Always, with a Template released product on every receiving company row.The release policy for the receiving company must have a product template, because company-specific fields such as item model group are needed to create a BOM; Always makes the policy refuse to save without a template per company.Choosing the wrong Product type. It can't be changed after the policy is saved, and a policy assigned to an engineering product category can't be deactivated.Test: Release policy template fills company-specific fields

Feature management and licence

Feature to turn onRelease multiple BOMs/formulas for Engineering Change Management (Mandatory, on by default)

Microsoft Learn

Solution architect

5Design impact

Can it be undoneOne-way: Warning: Product type can't be changed after saving. To retire a policy, remove it from every engineering product category, set Active to No, then delete it. Microsoft Learn
If you change it laterA release policy that is assigned to an engineering product category cannot be deactivated, and a policy can only be deleted after it is set to inactive; releases of products in the category default to the policy's settings. Microsoft Learn
Technical architect

6Technical

Menu itemEngChgProductReleasePolicy Checked in Dynamics 365
FormEngChgProductReleasePolicy Checked in Dynamics 365
TableEngChgProductReleasePolicyShown as “RELEASE POLICY” in Record infoKey field: NameChecked in Dynamics 365
Data entitiesEngChgProductReleasePolicyEntityEngChgProductReleasePolicyEntity Checked in Dynamics 365
Who can open itPrivilegesMaintain product release policies EngChgProductReleasePolicyMaintainView product release policies EngChgProductReleasePolicyViewDutiesInquire 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=EngChgProductReleasePolicy
Integrate withEngChgProductReleasePolicyEntity data entity Checked in Dynamics 365
Everyone

8Sources