[ http://issues.apache.org/jira/browse/OFBIZ-343?page=comments#action_12444013 ] Jacopo Cappellato commented on OFBIZ-343: -----------------------------------------
Ricardo, no problem, I've left this issue in the resolved status (instead of closing it) to leave you the time you need to test your changes in all the scenarios). Are we shure it is a good idea to allow to modify the fixed assets assigned to a production run AFTER that the production run has been approved (i.e. from the production run declaration screen)? Do you really need this? > Handle the association of many machines to a production run task > ---------------------------------------------------------------- > > Key: OFBIZ-343 > URL: http://issues.apache.org/jira/browse/OFBIZ-343 > Project: OFBiz (The Open for Business Project) > Issue Type: New Feature > Components: manufacturing > Reporter: Ricardo Chavez > Assigned To: Jacopo Cappellato > Attachments: ProdRun-FixedAsset-screenbug.patch, > ProdRun-FixedAsset-v2.patch, ProdRun-FixedAsset-v3.patch, > ProdRun-FixedAsset.patch > > > Hello everybody > The idea of this feature is to cover the case in which many machines are used > to complete a production task, e.g. having 20 sewing machines working to > complete a production task of 100 T-shirts. It'd also be useful is this could > allow the user to keep track of things like how many T-shirts has produced > each machine, among others. > As suggested by Jacopo Cappellato on the ofbiz-user mailing list, this can be > implemented in many ways: > > a) expanding the concept of FixedAsset groups (so that the data model will > > be left mostly unchanged); you create a fixed asset of type group (e.g. > > 'sewing machines of room A') and this fixed asset is associated to the > > task; then you link each sewing machine (other fixed assets) to the fixed > > asset group > > > > b) (more complex) add new association entities to link a task (WorkEffort) > > to one or more machines (FixedAsset). > Comments and suggestions are always welcome! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
