Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
There are some parameters of inventory planning. We can open this page on Departments->Warehouse->Administration->Inventory Setup.
You need to configure next fields on General tab:
I explain this date formulas in my previous posts: https://community.dynamics.com/nav/b/nav4construction/archive/2013/08/25/inventory-planning-part-3-microsoft-dynamics-nav.aspx#.UiIGTza-2m4
Also, you must to configure Location Mandatory fields. Specifies whether items must have a location code in order to be posted. Place a check mark in the field if you want the program to require a location code when posting item-related transactions. This field, together with the Components at Location field on Manufacturing Setup, is very important in governing how the planning system handles demand lines with/without location codes.
There are some parameters of manufacturing planning. We can open this page on Departments->Manufacturing->Administration->Manufacturing Setup.
You can assign a low-level code to each part in the product structure or the indented BOM. The top final assembly level is denoted as level 0 - the end item. The higher the low-level code number, the lower the item is in the hierarchy. When you calculate a plan, the BOM is exploded in the planning worksheet, and the gross requirements for level 0 are passed down the planning levels as gross requirements for the next planning level.
The main planning fields are on Planning tab:
If the suggested change in quantity is higher than the default dampener quantity, then the suggestion is not blocked. You use a dampener to limit insignificant action messages when a plan is being calculated. This setting applies globally, except for items that have a different value in the Dampener Quantity field on the item card.
Business Applications communities