RSMUS.comIt happened to me and it could happen to you. Starting a new Microsoft Dynamics 365 (formerly Dynamics AX) implementation is exciting. I enjoy learning about the business and operations of a company. After several discovery sessions, one of the first modules I set up and configured was the Master Planning Module. After the functionality was reviewed and approved, I proceeded to perform the same configuration within the future Dynamics 365 “production” environment. Several weeks later, the first refresh of the 365 environment was performed. Additionally, all needed data was loaded to test Master Planning. As a result, planned orders were created as expected. By successfully configuring this module, I could now focus on other project related tasks. So here I was, three-quarters of the way through the AX (365) implementation and several refreshes later, preparing for a mock “go-live.” I ran Master Scheduling and checked my Planned Orders, and nothing displayed. Therefore, I went back and ran the Master Scheduling again. I thought it was going to work the second time. Right? Wrong!
Now I was in troubleshooting mode. I reviewed the Master Planning configurations. I reviewed the master data setup to ensure all aspects had been imported. I reviewed the import files to see if there were any causes for Master Planning to stop planning. Everything I reviewed appeared to be correct. I then decided to create an item manually within the AX (365) test environment and ran Master Planning again. Success! The one item that I had just created planned as I had anticipated, which confirmed the module configurations were correct.
I then performed a review of the future AX “production” environment and noticed one item was set up in “Released Products.” The creation of this one item in the future AX “production” environment was the reason why my Master Planning had stopped planning. Would deleting the item from “Released Products” solve my problem? No. Within the AOT there is a table named “ReqItemLevel.” View the image below, and you can see there was just one item in the ReqItemLevel. The ReqItemLevel AOT table must be completely empty before running the first Master Schedule.
If you find yourself in the same situation as I did— in the middle of an implementation, actively working towards a “go live” and where Master Planning does not generate any planned orders, review the ReqItemLevel table within the AOT. I deleted this one line (shown above) from the AOT. I then ran Master Scheduling twice without any filters. After the second run, all of my planned orders displayed.
What did I do to solve my problem?
- I simply deleted the one line shown above from the AOT.
- I ran Master Scheduling (without any filters), which did NOT show me any planned orders the first time (running master scheduling the first time caused this table (ReqItemLevel) to auto populate with all items set up in Released Products).
- I then ran Master Scheduling again (without any filters). As a result, all of my planned purchase and transfer orders displayed.
If you need help with Microsoft Dynamics 365 (formerly Dynamics AX) contact our Microsoft Dynamics ERP experts or call us at 855-437-7202
By Jason Greto for RSM
