[Drew Lencsak]

Hi Rohit. You are correct that the current recommendation is to implement Planning optimization because the master planning engine in traditional MRP is being deprecated. Currently, released 10.0.33 added support for Process manufacturing, which was one of the missing pieces that the classic MRP engine supported. Per Microsoft in their 3/5/23 TechTalk on Planning optimization, there is no timeline to fully remove the classic master planning engine although it is being deprecated. When it is fully removed, the announcement would be 12-18months ahead of the date to allow customers to migrate. So although the recommendation is to use Planning optimization, technically you can continue to use the standard planning engine (however, I’m not sure on the agreement of support). I have not seen an official release that updates from that March statement, but I could be wrong.

[Crystal Ahrens]

Many are many users are reaching out to their implementation partners. If you have any customizing around MRP it may be a place to start

[Jamie Loeks]

Rohit we recently had this same issue with MSFT support, the message was unless you were using Lean, An exception due to ISV, or you were getting no orders or a full blockage on MRP, MSFT would not work to resolve a bug in Classic MRP. I have also seen what appears to be updates for planning optimization impacting classic in some unusual ways (dates, lead times, etc.). I have been recommending our clients to move to planning optimization soon since classic is such a black box and with MSFT being more aggressive in not supporting it.