Open AngelaIp opened 5 years ago
This sounds like a pretty straightforward use case. Do you think this should be a separate action (Export MBOM Pick List/Get Pick List) or an option in the current export settings (MBOM vs Pick List)?
Hi Eli, I am not sure if a separate Action or an additional option is preferable. Which option is easier to expand and maintain? I can imagine users want to add additional report variants for other use cases on the long term run.
I had a few thoughts on the pick list. This one is normally an ERP related task, as you need inventory information. In addition, the pick list is normally created order-related because we typically manufacture a larger number of products the same time. And of course you have to consider effectivity! It´s shouldn´t be difficult to use additional federated properties in the picklist, but this is of course a customer specific task. So the pick list that can provided within this project is mainly a basis. But also a simple pick list is already a useful export option, cause people often just need a quick overview of the used components. I remember me using these kind of reports in my previous company for assembling prototypes of new products. It´s an real interesting** task! . You can keep it simple or you can build a very complex report! I try to make a sample for the simple picklist. The advanced pick list with federated data is then a nice showcase of how to expand this project.
**it´s funny how "interesting" is somehow the German equivalent for the American "awesome". :grin:
Similar to the Elis idea to add MPP icons to the export, it would also be helpful to add thumbnail images. If manufacturing prepares to build a product, someone have to pick the various components from the storage area. A pick list that contains images of the needed products helps to collect stuff faster.
This use case is probably better solved in an additional one level report which is mainly intended to be used as picklist. For this use case, a multilevel bom would be contraproductive.