From: Pak R. <pak...@gm...> - 2014-09-11 07:04:35
|
Hi Phil: Now it's crystal clear. Then, does it make sense to add a flag to locations table, to mark locations to be used / hiden for WO purposes? As I see it, not all locations are meant to be production locations, so it seems logicalk to show only those locations available for WO purposes. Does it sound OK? If so, I'm happy to code it. Regards, Ricard 2014-09-11 14:51 GMT+08:00 Phil Daintree <ph...@lo...>: > Hi Ricard, > > Well work centres are meant to refer to the cells within locations where > the work is done ... in a jewellery manufacturing business there might be a > stone polishing work centre, a soldering work centre, turning, annealing > and such like. Each work centre might have different overhead rate > applicable with differing machine content etc and this was the intention > with work centres. The BOMs are defined by work centre so the materials can > be specified by work centre. They are quite different to locations (AKA > inventory locations/factories or warehouses). There can be a different BOM > at a different location/factory that in turn may well refer to different > work centres. > > Phil > > Phil Daintree > Logic Works Ltd - +64 (0)275 567890http://www.logicworks.co.nz > > On 11/09/14 16:01, Pak Ricard wrote: > > Hi all: > > If I understood it properly, we do have a table called workcentres which > is supposed to contain the locations where WO can be produced. > If so, why do we use locations table to select the Factory Location when > entering a WO? > > locations table can include locations used as ready to sell warehouses, > shops, recycle bins, component warehouses, etc besides "factory > locations". > > In WorkOrderEntry (and similar scripts), should we restrict the drop > down locations list to locations being set up as work centers? > > Regards, > Ricard > > > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable.http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > > > > _______________________________________________ > Web-erp-developers mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > |