web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / After a CU13 upgrade, ...
Microsoft Dynamics AX (Archived)

After a CU13 upgrade, MRP will not complete

(0) ShareShare
ReportReport
Posted on by Tom Woodman

After upgrading the environment to CU13, we are unable to get a completed master scheduling run. Isolated testing shows that the BOM recalculation will also not complete. Without being able to create new planned orders, the customer is unable to ship product.

Any suggestions?

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at

    Hi Tom,

    Not sure if it's the same scenario, but I faced an issue while running a master plan after upgrade to CU11.

    In my case, the problem occured when I tried to run more than one "filtered" master plan in sequence (when I say "filtered" I mean that no master plan was run for whole items but for a group of them). While trying that, the execution was stopped and I received the error:

    "Cannot delete a record in Net requirements (ReqTrans). An update conflict occurred due to another user process deleting the record or changing one or more field in the record."

    I created an incident in Microsoft support team and they released a hotfix. Here you have the link if you would like to check:

    https://fix.lcs.dynamics.com/Home/Index/0/kb/4057156?bugId=3910157&permission=Download&qc=895b65ae632f8b36599b6306a72c8e14963cf5809d44a3738db43732d1c1ef9d

    I cann't help you further than this.

    Hope it helps.

  • Verified answer
    Tom Woodman Profile Picture
    Tom Woodman on at

    The problem was indeed the BOM recalculation. This client has a very high number of items and BOMs that are no longer in use. They need to continue to keep the items and BOMs in the database. The BOM recalc was running over the entire list of items and BOMs without regard for items that actually have any demand. We modified the query that decides which items/BOMs need to have a BOM level recalc. I suspect others may trip over this if they are in construction-related industries or any other industries that must maintain a large list of inactive BOMs. One solution could be to set the expiration date on the old BOMs. This would have accomplished the same goal without need of any customization.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Basit Profile Picture

Basit 1

#1
GL-01081504-0 Profile Picture

GL-01081504-0 1

#1
Roya Profile Picture

Roya 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans