-
Support Cross LE retail operations
Retail operations in a franchise model are not well supported. A franchise model is often setup using multiple Legal Entities. The franchise giver 'delivers' the products and the franchise taker 'sells' them which requires cross LE flows. All franchise shops however, should operate as a 'one brand chain', allowing multi-channel processes. This is not well supported in Dynamics 365 FO/retail. Consider scenario's like * buy from shop X and pick up in shop Y (shop x and y being different LE's) * buy online (e-channel in mother company) and pick up in shop Y * see stock situation in shop Y from shop X * return goods from shop Y to central warehouse (other LE) * ...
-
Integrated Case Management across Dynamics 365
As many customers are using the entire D365 platform, an Integrated Case Management solution is required that spans across Dynamics 365. The current D365 FO Case management is perfect to associate D365 FO records and that is still highly required and we use it for Returns processes (RMA), Finance Collections management and Product Change requests. However we miss the integration with the cases in D365 Customer Service, especially for the references to Accounts/Customers and Contacts. Cases in both systems make up the 'Customer timeline' or a customers 360° view so a solution is needed that allows for an D365 FO user to create cases that end up in D365 Customer Service but that also allow them to associate D365 FO entities to it. D365 Customer Service Insights doesn't integrate D365 FO cases out of the box yet. I see nothing in the roadmap for Dual Write either pointing in that direction either. -
Integrated Case Management in Dynamics 365 platform
As many customers are using the entire D365 platform, an Integrated Case Management solution is required that spans across Dynamics 365. The current D365 FO Case management is perfect to associate D365 FO records and that is still highly required and we use it for Returns processes (RMA), Finance Collections management and Product Change requests. However we miss the integration with the cases in D365 Customer Service, especially for the references to Accounts/Customers and Contacts. Cases in both systems make up the 'Customer timeline' or a customers 360° view so a solution is needed that allows for an D365 FO user to create cases that end up in D365 Customer Service but that also allow them to associate D365 FO entities to it. D365 Customer Service Insights doesn't integrate D365 FO cases out of the box yet. I see nothing in the roadmap for Dual Write either pointing in that direction either. -
Consolidated batch orders for packed items with variants: bulk item conversion
Currently, consolidated batch orders for packed items based on product masters are/seem not supported. We cannot setup a bulk item conversion between a 'packed product master'. So we cannot setup packed products with variants (like in cans of 0,5l, 1l, 2,5l, 5l, 10l) and need to make different products per 'size'. We cannot setup a different 'Bulk Item conversion' per variant. It would make product setup much easier if we could... -
Engineering Change Management - Change request export - Change order import
With the Engineering Change management functionality added to the solution, we can better support companies that have an 'Engineering' process in place. A lot of companies already have some other PLM/PDM solution in place, mostly used to manage the BOMs or Formulas. This PLM/PDM is also typically the 'master' solution for the Engineering products. However, sometimes changes that required to those products may arise from D365 FO (production, sales, purchase,..) In that situation, we would create a Engineering Change Request (in D365 FO) and like to send it to the PLM/PDM where the engineers will investigate and create a Engineering Change 'Order' (in PLM/PDM). They will do the necessary changes to the products and BOMs and send the results back to D365 FO. We would receive those changes in D365 FO as a Engineering Change Order and process the order subsequently in D365 FO. Focus can be on the BOMs/Forula's as in most situations, the 'routes' are not going to be maintained in the external PLM/PDM system. Therefore: we need an entity to Export all information from the EC Request and an entity to import an EC Order (with all related changes included) -
Easily add multiple products (variants) to a the impacted products list of an engineering change order (and ECR)
Currently, the only way to add multiple products at once to the impacted product list of an engineering change order is via the 'where used' function on the engineering change order impacted product (or the ECO header).
However, the list of products that need to be updated cannot always be derived from a 'where used' query. Think of scenario's where you have a lot of variants (eg. combination of configuration, color, size,...) and they all need an additional component (eg. a product manual). In this case, there's no 'where used' to be run. A users needs to be able to select multiple products (or released product variants) from a list or a query and get them in the impacted products list of the Engineering Change order in one go.
In the current solution, this can only be done one-by-one (click 'new' > 'Add existing product' > open the product dropdown and search for the product > start over again) which is not realistic if you have to update eg. 20, 30,..100 variants. A user will not know the 'product number' (which is the variant...) but would filter on eg. 'product name' or would like to filter on the product dimensions and mark multiple variants and add them in one go to the 'impacted product' list.
A similar form as the 'where used' list could be used to, provided that is allows filtering from the entire product list instead of just the where-used products search result.
-
Keep pegging for firmed orders
In 10.0.43, a new feature is introduced to 'Keep pegging for approved planned orders'. This feature helps in MTO scenario's. This feature would need to be extended to also 'Keep pegging for firmed orders' because pegging might change after running planning optimization again after firming. Next to that, the parameter should be set on the master plan and/or coverage group and/or Item coverage as the requested behaviour might be different depending on the item coverage group (Similar to the other MTO parameters 'Use latest possible supply')
Following scenario shows why keeping the pegging also for firmed orders can be useful:
- Create 2 salesorders for the same product, to 'Produce'
- SO1 with delivery date 13 March, qty of 10
- SO2 with delivery date 14 March, qty of 2
- Negative days is set to 2, coverage for the product is 'Requirement'
- Run Planning optimization, you will get 2 planned production orders, one for each SO
- That's fine for MTO :-)
- Firm the planned order associated with SO2, so for a production order of 2 pcs
- Now run Planning Optimization again, you will get
- Planned PO for 8 pcs, pegged to SO1
- Planned PO for 2 pcs, pegged to SO2
- Set negative days to 0 and set the delivery date of SO1 to the same date as SO2, run planning optimization
- Planned PO for 8 pcs, pegged to SO1
- Planned PO for 2 pcs, pegged to SO2
So, even if planning optimization has proposed a dedicated production order for SO2, this is not maintained after firming as then, the firmed production order becomes 'Existing supply' and it becomes pegged to the SO1 instead of 'Keeping it pegged to the SO2' for which it was intended (by the planner). It becomes perhaps even more complex when the production order gets RAF'ed because then we have 'on-hand'. Then the other settings about 'Consume on-hand inventory' and 'Use latest possible supply' come into play as well to influence pegging so the 'Keep pegging for firmed orders' may need to be integrated with those to as an additional option.
'Marking' when firming can solve this but only if there is no 'cut' in the supply chain between the SO and the Production order. Keeping the pegging should be configurable as we understand that it may be conflicting with the 'optimization' of the supply chain. In our situation, there's a transfer order in between (to bring finished goods from production to DC) that we don't firm for operations reasons, so we can't 'mark'.
-
MTO: support for 'Item coverage' settings when using coverage planning by Batchid
We want to use 'batchid' to efficiently put a link between a specific demand and supply (and stock) to support real MTO flow. Using the batch (and fill it with eg. the sales line inventtransid) we have a unique reference to the salesline: from the planned order, any transferorder, production or purchase order or even on-hand. An update of the planning optimization will not ruin the association... confirmed dates can be maintained and we can control which order will get the products and when.
The batch tracking dimension can be enabled for 'Coverage planning': planning optimization will nicely calculate demand and supply and split it up per 'batchid'. However, after enabling the 'Coverage planning' flag for the batch tracking dimension, you cannot use Item specific coverage settings anymore: the batchid cannot be specified on the item coverage lines.
So for 'popular' products, we would like to use a 'fixed' batch and configure a min/max for this but this is not possible.
Please enable the use of batchid on the item coverage (just like eg. 'inventory status') so we can track MTO supply decently.
You’re offline. This is a read only version of the page.
