Hi Everyone,
I am looking for some insight about something in the Manufacturing component. This isn't a bug, complaint, critique, or issue, but rather just a roadblock in me understanding this stuff. On the ecommerce site I created four orders for configurable PCs. The first three were for identical configurations(2 Gb RAM, 500 Gb HDD, 2nd 500 Gb HDD, modem, and NIC). The fourth was a barebones system with just 1 Gb RAM and a 250 Gb HDD. When I log into the back office and go into the Manufacturing Component and do the lookup for Production Runs I get the information below for the four orders: Production Run Name Product ID Quantity Status Start Date Description Facility ID 10000 Configurable PC-PC assembly 10000 1 Created 2009-04-01 13:12:36.518 WebStoreWarehouse 10004 Configurable PC-PC assembly 10000 5 Created 2009-04-01 13:48:31.877 WebStoreWarehouse 10008 Configurable PC-PC assembly 10000 3 Created 2009-04-01 13:50:09.294 WebStoreWarehouse 10012 Configurable PC-PC assembly 10003 1 Created 2009-04-01 13:57:40.320 WebStoreWarehouse If I look at the Order Manager for each order, the productIds are 10000, 10001, 10002, and 10003 respectively. I looked in the manufacturing controller and from what I can tell the table above is getting its information from the 'WorkEffortAndGoods" view entity which gets information from Work Effort and WorkEffortGoodStandard. My question is: Why does the "WorkEffortGoodStandard" use the productid 10000 for the first three production runs instead their productids(10000, 10001, and 10002)? ***If I look in the "Product" entity, the productIds 10000, 10001, and 10002 all use the configId 10003 and the productId 10003 uses configId 10004. It seems that the productId 10000 was the first occurence of this configuration so... is it using this for any future work efforts that need to manufacture this? And if so, why not use the productIds as I asked above?** Thank you! |
Hmmm... yes it looks a bit strange.
I am wondering if this is related to the work that was done to enhance the way configurations are managed in the system. I don't know much about the details of this but if I am not wrong Bilgin worked on it, and if he is reading this he may provide some hints. Jacopo On Apr 2, 2009, at 3:10 AM, cjhorton wrote: > > Hi Everyone, > > I am looking for some insight about something in the Manufacturing > component. This isn't a bug, complaint, critique, or issue, but > rather just > a roadblock in me understanding this stuff. > > On the ecommerce site I created four orders for configurable PCs. > The first > three were for identical configurations(2 Gb RAM, 500 Gb HDD, 2nd > 500 Gb > HDD, modem, and NIC). The fourth was a barebones system with just 1 > Gb RAM > and a 250 Gb HDD. > > When I log into the back office and go into the Manufacturing > Component and > do the lookup for Production Runs I get the information below for > the four > orders: > > Production Run Name Product ID Quantity Status Start Date > Description Facility ID > 10000 Configurable PC-PC assembly 10000 1 Created 2009-04-01 > 13:12:36.518 WebStoreWarehouse > 10004 Configurable PC-PC assembly 10000 5 Created 2009-04-01 > 13:48:31.877 WebStoreWarehouse > 10008 Configurable PC-PC assembly 10000 3 Created 2009-04-01 > 13:50:09.294 WebStoreWarehouse > 10012 Configurable PC-PC assembly 10003 1 Created 2009-04-01 > 13:57:40.320 WebStoreWarehouse > > If I look at the Order Manager for each order, the productIds are > 10000, > 10001, 10002, and 10003 respectively. I looked in the manufacturing > controller and from what I can tell the table above is getting its > information from the 'WorkEffortAndGoods" view entity which gets > information > from Work Effort and WorkEffortGoodStandard. > > My question is: Why does the "WorkEffortGoodStandard" use the > productid > 10000 for the first three production runs instead their > productids(10000, > 10001, and 10002)? > > ***If I look in the "Product" entity, the productIds 10000, 10001, > and 10002 > all use the configId 10003 and the productId 10003 uses configId > 10004. It > seems that the productId 10000 was the first occurence of this > configuration > so... is it using this for any future work efforts that need to > manufacture > this? And if so, why not use the productIds as I asked above?** > > Thank you! > -- > View this message in context: http://www.nabble.com/Could-use-some-insight-for-the-Manufacturing-component-Production-Run..productId-tp22834772p22834772.html > Sent from the OFBiz - User mailing list archive at Nabble.com. > smime.p7s (3K) Download Attachment |
Thanks Jacopo.
On Thu, Apr 2, 2009 at 10:15 PM, Jacopo Cappellato < [hidden email]> wrote: > Hmmm... yes it looks a bit strange. > I am wondering if this is related to the work that was done to enhance the > way configurations are managed in the system. I don't know much about the > details of this but if I am not wrong Bilgin worked on it, and if he is > reading this he may provide some hints. > > Jacopo > > > On Apr 2, 2009, at 3:10 AM, cjhorton wrote: > > >> Hi Everyone, >> >> I am looking for some insight about something in the Manufacturing >> component. This isn't a bug, complaint, critique, or issue, but rather >> just >> a roadblock in me understanding this stuff. >> >> On the ecommerce site I created four orders for configurable PCs. The >> first >> three were for identical configurations(2 Gb RAM, 500 Gb HDD, 2nd 500 Gb >> HDD, modem, and NIC). The fourth was a barebones system with just 1 Gb >> RAM >> and a 250 Gb HDD. >> >> When I log into the back office and go into the Manufacturing Component >> and >> do the lookup for Production Runs I get the information below for the four >> orders: >> >> Production Run Name Product ID Quantity Status >> Start Date >> Description Facility ID >> 10000 Configurable PC-PC assembly 10000 1 Created >> 2009-04-01 >> 13:12:36.518 WebStoreWarehouse >> 10004 Configurable PC-PC assembly 10000 5 Created >> 2009-04-01 >> 13:48:31.877 WebStoreWarehouse >> 10008 Configurable PC-PC assembly 10000 3 Created >> 2009-04-01 >> 13:50:09.294 WebStoreWarehouse >> 10012 Configurable PC-PC assembly 10003 1 Created >> 2009-04-01 >> 13:57:40.320 WebStoreWarehouse >> >> If I look at the Order Manager for each order, the productIds are 10000, >> 10001, 10002, and 10003 respectively. I looked in the manufacturing >> controller and from what I can tell the table above is getting its >> information from the 'WorkEffortAndGoods" view entity which gets >> information >> from Work Effort and WorkEffortGoodStandard. >> >> My question is: Why does the "WorkEffortGoodStandard" use the productid >> 10000 for the first three production runs instead their productids(10000, >> 10001, and 10002)? >> >> ***If I look in the "Product" entity, the productIds 10000, 10001, and >> 10002 >> all use the configId 10003 and the productId 10003 uses configId 10004. >> It >> seems that the productId 10000 was the first occurence of this >> configuration >> so... is it using this for any future work efforts that need to >> manufacture >> this? And if so, why not use the productIds as I asked above?** >> >> Thank you! >> -- >> View this message in context: >> http://www.nabble.com/Could-use-some-insight-for-the-Manufacturing-component-Production-Run..productId-tp22834772p22834772.html >> Sent from the OFBiz - User mailing list archive at Nabble.com. >> >> > |
In reply to this post by Jacopo Cappellato-4
Jacopo, thanks for bringing up this issue, somehow I missed the
original post. CJay, thanks for your research and reporting. In r762248 I did a fix, so now new products will be created only for new configuration. If you create orders for the same configuration, the same product should be used in orders and production run. Could you check if this fixes the bug you described? Bilgin On Apr 3, 2009, at 7:15 AM, Jacopo Cappellato wrote: > Hmmm... yes it looks a bit strange. > I am wondering if this is related to the work that was done to > enhance the way configurations are managed in the system. I don't > know much about the details of this but if I am not wrong Bilgin > worked on it, and if he is reading this he may provide some hints. > > Jacopo > > On Apr 2, 2009, at 3:10 AM, cjhorton wrote: > >> >> Hi Everyone, >> >> I am looking for some insight about something in the Manufacturing >> component. This isn't a bug, complaint, critique, or issue, but >> rather just >> a roadblock in me understanding this stuff. >> >> On the ecommerce site I created four orders for configurable PCs. >> The first >> three were for identical configurations(2 Gb RAM, 500 Gb HDD, 2nd >> 500 Gb >> HDD, modem, and NIC). The fourth was a barebones system with just >> 1 Gb RAM >> and a 250 Gb HDD. >> >> When I log into the back office and go into the Manufacturing >> Component and >> do the lookup for Production Runs I get the information below for >> the four >> orders: >> >> Production Run Name Product ID Quantity Status Start Date >> Description Facility ID >> 10000 Configurable PC-PC assembly 10000 1 Created 2009-04-01 >> 13:12:36.518 WebStoreWarehouse >> 10004 Configurable PC-PC assembly 10000 5 Created 2009-04-01 >> 13:48:31.877 WebStoreWarehouse >> 10008 Configurable PC-PC assembly 10000 3 Created 2009-04-01 >> 13:50:09.294 WebStoreWarehouse >> 10012 Configurable PC-PC assembly 10003 1 Created 2009-04-01 >> 13:57:40.320 WebStoreWarehouse >> >> If I look at the Order Manager for each order, the productIds are >> 10000, >> 10001, 10002, and 10003 respectively. I looked in the manufacturing >> controller and from what I can tell the table above is getting its >> information from the 'WorkEffortAndGoods" view entity which gets >> information >> from Work Effort and WorkEffortGoodStandard. >> >> My question is: Why does the "WorkEffortGoodStandard" use the >> productid >> 10000 for the first three production runs instead their >> productids(10000, >> 10001, and 10002)? >> >> ***If I look in the "Product" entity, the productIds 10000, 10001, >> and 10002 >> all use the configId 10003 and the productId 10003 uses configId >> 10004. It >> seems that the productId 10000 was the first occurence of this >> configuration >> so... is it using this for any future work efforts that need to >> manufacture >> this? And if so, why not use the productIds as I asked above?** >> >> Thank you! >> -- >> View this message in context: http://www.nabble.com/Could-use-some-insight-for-the-Manufacturing-component-Production-Run..productId-tp22834772p22834772.html >> Sent from the OFBiz - User mailing list archive at Nabble.com. >> > |
Bilgin,
Your fix did the job. Thank You! CJ On Mon, Apr 6, 2009 at 3:22 AM, Bilgin Ibryam <[hidden email]> wrote: > Jacopo, thanks for bringing up this issue, somehow I missed the original > post. > > CJay, thanks for your research and reporting. > In r762248 I did a fix, so now new products will be created only for new > configuration. If you create orders for the same configuration, the same > product should be used in orders and production run. > Could you check if this fixes the bug you described? > > Bilgin > > > On Apr 3, 2009, at 7:15 AM, Jacopo Cappellato wrote: > > Hmmm... yes it looks a bit strange. >> I am wondering if this is related to the work that was done to enhance the >> way configurations are managed in the system. I don't know much about the >> details of this but if I am not wrong Bilgin worked on it, and if he is >> reading this he may provide some hints. >> >> Jacopo >> >> On Apr 2, 2009, at 3:10 AM, cjhorton wrote: >> >> >>> Hi Everyone, >>> >>> I am looking for some insight about something in the Manufacturing >>> component. This isn't a bug, complaint, critique, or issue, but rather >>> just >>> a roadblock in me understanding this stuff. >>> >>> On the ecommerce site I created four orders for configurable PCs. The >>> first >>> three were for identical configurations(2 Gb RAM, 500 Gb HDD, 2nd 500 Gb >>> HDD, modem, and NIC). The fourth was a barebones system with just 1 Gb >>> RAM >>> and a 250 Gb HDD. >>> >>> When I log into the back office and go into the Manufacturing Component >>> and >>> do the lookup for Production Runs I get the information below for the >>> four >>> orders: >>> >>> Production Run Name Product ID Quantity Status >>> Start Date >>> Description Facility ID >>> 10000 Configurable PC-PC assembly 10000 1 Created >>> 2009-04-01 >>> 13:12:36.518 WebStoreWarehouse >>> 10004 Configurable PC-PC assembly 10000 5 Created >>> 2009-04-01 >>> 13:48:31.877 WebStoreWarehouse >>> 10008 Configurable PC-PC assembly 10000 3 Created >>> 2009-04-01 >>> 13:50:09.294 WebStoreWarehouse >>> 10012 Configurable PC-PC assembly 10003 1 Created >>> 2009-04-01 >>> 13:57:40.320 WebStoreWarehouse >>> >>> If I look at the Order Manager for each order, the productIds are 10000, >>> 10001, 10002, and 10003 respectively. I looked in the manufacturing >>> controller and from what I can tell the table above is getting its >>> information from the 'WorkEffortAndGoods" view entity which gets >>> information >>> from Work Effort and WorkEffortGoodStandard. >>> >>> My question is: Why does the "WorkEffortGoodStandard" use the productid >>> 10000 for the first three production runs instead their productids(10000, >>> 10001, and 10002)? >>> >>> ***If I look in the "Product" entity, the productIds 10000, 10001, and >>> 10002 >>> all use the configId 10003 and the productId 10003 uses configId 10004. >>> It >>> seems that the productId 10000 was the first occurence of this >>> configuration >>> so... is it using this for any future work efforts that need to >>> manufacture >>> this? And if so, why not use the productIds as I asked above?** >>> >>> Thank you! >>> -- >>> View this message in context: >>> http://www.nabble.com/Could-use-some-insight-for-the-Manufacturing-component-Production-Run..productId-tp22834772p22834772.html >>> Sent from the OFBiz - User mailing list archive at Nabble.com. >>> >>> >> > |
Free forum by Nabble | Edit this page |