BeyondERP.Newsletter
Menu

Job page · Product information management

Change lifecycle state for obsolete products

A periodic task that finds obsolete released products and product variants and assigns them a new product lifecycle state, either as a simulation or as an update.

Business process
Prevent transactions for a product in Dynamics 365 Supply Chain Management
Menu item
action:EcoResReleasedProductInactivator
Show what matters for
PAGE GUIDEWhat the page does and how to use it7 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA periodic task that finds obsolete released products and product variants and assigns them a new product lifecycle state, either as a simulation or as an update.
What you do hereUse this task to identify products that have no demand within a period and no master data that can result in demand, review the simulation results, and then set the obsolete lifecycle state on them.
Change lifecycle state for obsolete products 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 processRetire products › End product sales › Prevent transactions for a product in Dynamics 365 Supply Chain Management
Menu pathProduct information management › Periodic tasks › Change lifecycle state for obsolete products
Set up firstProduct lifecycle state Microsoft Learn
Used next byProduct lifecycle state maintenance history 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.

When to run it

When to run itWhen you clean up the product range, after demand and master data have been reviewed. Run all analyses and updates in the same legal entity.
How oftenOn demand, for example as part of a periodic product range review.
Batch settingsRun the simulation and the update in batch when many products are involved, outside the most active working hours.
What the output showsOn Product lifecycle state maintenance history, the products and variants found to be obsolete: no recent transactions, no open orders, no forecast, no minimum stock, no kanban rules and no use in an active BOM. Too many products found usually means the day values are too short.

Source: Microsoft Learn

Steps from Microsoft

  1. Go to Product information management > Periodic tasks > Change lifecycle state for obsolete products.
  2. In New product lifecycle state, select the lifecycle state your company uses for obsolete products.
  3. Set Run simulation without updating product data to Yes for the first run, and enter values in Exclude products created within this number of days and Exclude products used in transactions (in number of days).
  4. To limit the scope, filter on Records to include, and run large simulations in batch outside the busiest working hours.
  5. Review the result on Product lifecycle state maintenance history, then run again with Run simulation without updating product data set to No and the same filter.

Source: Microsoft Learn

Fields on the page

FieldWhat it means
New product lifecycle stateThe lifecycle state assigned to the products that the task identifies as obsolete.Microsoft Learn
Run simulation without updating product dataWhen set to Yes, the task only simulates the change. When set to No, it updates the products.Microsoft Learn
Exclude products created within this number of daysExcludes newly released products created within the number of days entered.Microsoft Learn
Exclude products used in transactions (in number of days)Excludes products that have inventory transactions within the number of days entered.Microsoft Learn

Test checklist

  1. The simulation result lists only products you expect to be obsolete.
  2. After the update, those products show the new lifecycle state.
  3. Maintenance history shows the expected changes.

Source: Microsoft Learn

Solution architect

4Design impact

Can it be undonePartly: A simulation changes nothing. After the real update, you have to set the previous lifecycle state back on the products yourself. Microsoft Learn
If you change it laterWithout simulation, the job sets the new product lifecycle state on all products and variants it identifies as obsolete, which can block them in business processes. Microsoft Learn
Technical architect

5Technical

Menu itemaction:EcoResReleasedProductInactivator
Roles to set it up and use itTo use itProduct designer BOMProductDesignerGive people one of these roles. On this system, 1 role can run this page.Checked in Dynamics 365
Developer

6Developer

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

7Sources