Drew Lencsak
Forum Replies Created
-
Are you using DMF or attempting to publish updates through the Data entity using Open in Excel? In the past, I have often imported forecasting using the Open in Excel feature and the Default forecast sequence number can be populated automatically. I cannot remember 100% when using DMF and importing a file, but have you tried importing with the column left off and out of your mapping and have D365 attempt to create it during import?
-
Hi, non-WMS warehouses still use locations. However, the form to set up the locations is in a different menu path. They are not configured/created in the Warehouse management module. You set up aisles and locations for nonWMS warehouse in the Inventory management module > Setup > Inventory Breakdown > Inventory aisles and Inventory Locations.
If you configure an aisle against your nonWMS warehouse, you should then be able to go into Inventory locations and create a location for it as well. After that, it can be assigned as a Default receipt and/or issue location on the Warehouse form.
-
Correct, out of the box, there is one Country of origin field on a released product linked to the Foreign trade setup in the Tax module. If using batch controlled items, you do have the opportunity to record 2 Vendor batch COOs. However, if you are manufacturing the goods in multiple countries and you move a unit from where it is manufactured to another country where it is distributed, and it is the same Released product, you are correct that you would not individually have the COO tracked on any given SKU worldwide when it could have been manufactured and distributed in one of many countries. You can sort of make it work but it is not robust enough often for companies. The COO is a value of the stock/inventory itself, not the Released product/SKU number. The previous reply about batch attributes is a common approach I have seen to handle this along with similar workarounds or added fields to track COO at the batch level
-
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.
-
Sorry for the months late reply, I had access issues š Dave’s reply sounded like it answered the question. I’m not sure if there is any sort of workaround like trying to use the “Change BOM item” function under Product Information Management > Periodic > Bills of materials and formulas > Change BOM Item functionality to replace the phantom item with itself on BOM lines after the change was made or if that does not work.
