Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I wanted to share some information surrounding run numbers and MRP. Have you ever noticed the run number between the MRP1010 and the MPPS0130 do not always correlate after an MRP run? Well, let me give you a little information surrounding those tables and what I found.
You might think there is an issue if you find your run numbers do not match between certain tables after running MRP run especially if you use these tables for building reports. But rest assured it’s not an issue. There is little to no information I could find out there so I thought I would share what I had.
So, what are these two tables you might ask?
So, the question is, is that an issue with GP? Short answer, no. GP works just fine if the numbers do not correlate. We have found no issues with how GP generates suggestions when the numbers do not tie, but it might be something you want to be aware of if you are building reports off these tables. If you find specific situations where they don't tie when an item does change, feel free to comment below and share your findings!
Have a good one!
Angela Ebensteiner | Sr. Technical Advisor | Microsoft Dynamics GP
Business Applications communities