web
You’re offline. This is a read only version of the page.
close
  • Allow cross docking PO - Prod order and Prod order- PRod order

    This idea is an enhancement for the existing cross docking framework. The scenarios described below are very common in the discrete industry, especially in the complex equipment industry. scenario 1; No advanced warehousing. A production order has been released and started but there are material shortages that are expected to be resolved soon When the Purchase order with the short part number arrives, the system searches for started production orders that needs this item (quantity would show as "on order". A marked production order would get priority . When the user clicks "prod receipt" a window comes up "want add to picklist of prod order xxx? Y/N". When Yes, the system will receive this item and also immediately create a picklist for the production order and post it . We call this "receiving into WIP". The exact same functinality exists when I do RAF for a production order and this item happens to be short in another prod order that is waiting for it. Prod order needs to be started, quantity for the item is 'on order'. Scenario 2: advanced warehousing is used. Purchase order receiving into WIP: when the user says yes to the questoin, the pick for purchase receiving is done but the put is suspended to become a put right into the input locatoin of the resource group on operation 10 (or higher) of the production order with the shortage. Cross docking. Prod order receiving into WIP: the exact same. the Put is suspended and becomes a put directly to the input location of the resource group in the routing of the prod order waiting for this part.

  • Make unpicking easier

    When using advanced warehousing it may happen that a prod order is erroneously picked and we have to 'reverse the pick".when my Prod BOM has 40 or more lines, this is a tremendous job. Each individual line has to be unpicked. The idea is to provide an unpick transaction wiht one click for the entire order. It is kinda like 'reverse work' or "undo".

  • Add zoom in zoom out to gANTT chart for production

    The GANTT chart for production has a timescale feature that allows you to switch from days to hours or from days to weeks etc. This is rather inefficient and not very intuitive in today's world where all graphical displays have a zoom feature. We request if we can have a zoom feature on the chart. using a button just like on map applications. This would make the user a lot happier and the chart would be used more.

  • GANTT chart for operation scheduling

    GANTT chart only available for Job scheduled prod orders is a pity and it seems a limitation that has not very profound reasons. Many customers in MFG are using operation scheduling. They would like to use the GANTT chart also

  • BOM DESIGNER should show more decimals

    The BOM designer shows quantities (Net quantity of BOM line) however only in two decimals. The BOM net qty field has 4 decimals and these should show in the designer also.

  • Raw material picking work PRINT report

    The WOrk Report for Raw material picking and sales order picking can be printed. However: it has no print status. If you want to run a batch that prints new open picking work that is generated, (the batch can be set up) it will never work because you can not filter on Work that has not been printed yet. It will print the same work again and again until the work is no longer in open status. We need a field on the picking work that is like document status that is on PO's Without that, no good business process can be implemented. Without that batch, a person is necessary every time I need to print picking work. Printed picking work is the only available trigger for a picking person to get to work. The mobile app does not have a "push" mechanism like an inbox where newly generate picking work is presented.

  • Unpick for prodution orders

    When doing a manual unpick for Production orders, the item ends up as on hand in the Input location not in the original storage location. so the item is not really unpicked because the process is not really reversed. The consequence is that the next prod order that needs this item will see it in the Input location, and will not create warehouse work, confusing the user. This problem arose because there is no advanced warehousing unpick functionality. The unpick we can use , the only one that is available, is the standard AX one from the old days. This makes unpicking for prod orders in essence not possible. The unpick I can do makes inventory avaiable again but I would have to transfer it after the unpick to really restore the situation to how it was.

  • Floorstock .. we have no solution

    There is no solution for Floorstock in D365. It should not be hard to get a solution for it. We need a line type on the BOM and the PROD BOM that will make sure this floorstock item: - is not showing up on the Picklist - is not creating a "remaining quantity" on the PRod BOM - so does not require a consumption transaction. Floorstock is an item that is NOT inventory managed in the system. We need a solution for that. The service item, a logical choice for this floorstock behavior, is completely behaving like an inventoried item. I need to consume it... and it wants to have inventory for this service item . A strange contradiction. (we cant pick negative becuae that would affect all normal items too)

  • Warehouse app improvement

    The warehouse app allows t he Report as Finished and put away for production orders. The default value of "end job" parameter = "no". This is unlike the D365 mothership where the default is "yes". One can safely say that the vast majority of discrete manufacturing companies and certainly the make to order engineer to order companies only use "no" rarely. Most of the time I RAF the quantity of the order and I am done. The mothership D365 seems to understand that. For some reason the app has the other default which creates unnecessary clicks. Especially in ETO, most order quantities are 1 EA. Every time I have to flip to "yes" , end job. This is not acceptable. The default has to change to "yes". Or make it a parameter! and one nice refinement would be this: if the order quantity = 1 EA, the parameter necessary flips to YES.
  • End job Yes/No

    When doing RAF and putaway on handheld terminal warehouse app.. the parameter "end job" yes/no is set to "no". Most customers would prefer "yes". In the mothership D365 the user can set this parameter to yes in his defaults. But the handheld RAF has no such option. We think we need that option there and we can follow the idea for quantity validation here. Make the parameter in the Prod order defaults (that are controlling mfg execution RAF) work for the handheld warehousing app. With adv warehousing the PRod Order defaults for MFG execution would say "NO" to the RAF transaction but the parameters there would still work. That was done for qty validation , very logical solution and it works.