-
Overhead on Costing sheets working for purchase orders also for other inventory models than standard cost
In the production module the costing sheet creates a pre calculation based on the costing sheet including overhead based on surcharges. The production posting also creates indirect postings. This is independent of the active cost principle chosen for the items. (e.g. FIFO or Std cost) On purchase orders this principle only works for standard cost based items. I suggest to introduce costing sheet with overheads also on purchase orders for other cost principles. At least this could be parameter in the inventory model for the items.
-
Data entity or API for reception of constraint based product configurations from external sales processes
We are experiencing quite a growing group of customers who has implemented external sales processes using constraint based configurators. The reason for using an external configurator are mainly based on requirements related to Web based sales processes. I would like to suggest to have a data entity or API developed for D365FO, which will enable a Configuration import function together with a sales order import function. This means creating a configuration from imported external set Attribute values per sales line. The values should be imported and validated in the constraint motor exactly as they were typed in, but of cause throwing execution errors in a log. If the validation is succesfull the system goes on by creating BOM, routing an pricing calculation in exactly the same ways as if they we typed in.
-
Expansion of the Manual Forecast Entry Edata entity with
The Manual forecast entity is missing some fields for proper export/import if you are using the Period allocation fields. The fields missing are: Method, Per, Period Key, Days, End We have several customers using the forecasts for export import and who is using the Date allocation system, which seems to be an integrated part of the forecast and hence is wondering why these fields are missing.
-
Problem with disabled configuration possibilities in IC sales orders
We have experienced that its is not possible to enter the "Configure line" function from a sales order if an intercompany order has already been created related to the sales order. This implies both for the present line but also for any other sales line on the sales order. We would like to suggest that the it should be possible to edit/create a sales configuration on the original sales order at any time - Disregarding that any other line has created an intercompany chain order. The present work-around is the to create the full sales order, and the activate the "direct delivery" function from the sales order header. But this is cumbersome if the product has already be ticked with direct delivery, which is populated into the sales line. The operator the has to turn in off on the sales lines.
-
Periodic Demand forecasts lines should be active for the whole period
Its possible to create demand forecast lines which cover for a period e.g one week or one month. The system will create an inventory forecast for each demandperiod, but the demand is placed on the first day of the period. This gives the result that as soon as the start date of the period is sur passed this requirement is not recognized the by MRP anymore. The suggestion is that, the a demand forecast requirement for a period is active as long as the start and the end date for the period is still valid for the MRP. This will much less maintenance of the demand forecast and what should the periode be used for, if not for that