|
From: bpcs-l-request@xxxxxxxxxxxx> Subject: BPCS-L Digest, Vol 6, Issue 27> To: bpcs-l@xxxxxxxxxxxx> Date: Sun, 10 Feb 2008 09:50:16 -0600> > Send BPCS-L mailing list submissions to> bpcs-l@xxxxxxxxxxxx> > To subscribe or unsubscribe via the World Wide Web, visit> http://lists.midrange.com/mailman/listinfo/bpcs-l> or, via email, send a message with subject or body 'help' to> bpcs-l-request@xxxxxxxxxxxx> > You can reach the person managing the list at> bpcs-l-owner@xxxxxxxxxxxx> > When replying, please edit your Subject line so it is more specific> than "Re: Contents of BPCS-L digest..."> > > *** NOTE: When replying to this digest message, PLEASE remove all text unrelated to your reply and change the subject line so it is meaningful.> > Today's Topics:> > 1. Re: BPCS-L Digest, Vol 6, Issue 26 (MisterBPCS@xxxxxxx)> 2. Re: BPCS-L Digest, Vol 6, Issue 26 (Don Cavaiani)> 3. Re: BPCS-L Digest, Vol 6, Issue 26 (Don Cavaiani)> > > ----------------------------------------------------------------------> > message: 1> date: Sat, 9 Feb 2008 22:20:04 EST> from: MisterBPCS@xxxxxxx> subject: Re: [BPCS-L] BPCS-L Digest, Vol 6, Issue 26> > Don,> > My recommendation would be to separate each plant into separate facilities. > I also think you should use the DRP function by the demand plant issues a > resupply order to the supplying plant. The supplying plant would do a confirm > ship to the resupply order. The receiving plant would then due a receiving > using an "H' transaction for resupply receipts. To set up each plant as a > facility, you will need to set up facility planning records (MRP140) and the DDR > records to show the relationship between each plant. This is just my view.> > Ric Weide> _MisterBPCS@xxxxxxxx (mailto:MisterBPCS@xxxxxxx) > > > In a message dated 2/8/2008 12:02:18 P.M. Central Standard Time, > bpcs-l-request@xxxxxxxxxxxx writes:> > Send BPCS-L mailing list submissions to> bpcs-l@xxxxxxxxxxxx> > To subscribe or unsubscribe via the World Wide Web, visit> http://lists.midrange.com/mailman/listinfo/bpcs-l> or, via email, send a message with subject or body 'help' to> bpcs-l-request@xxxxxxxxxxxx> > You can reach the person managing the list at> bpcs-l-owner@xxxxxxxxxxxx> > When replying, please edit your Subject line so it is more specific> than "Re: Contents of BPCS-L digest..."> > > *** NOTE: When replying to this digest message, PLEASE remove all text > unrelated to your reply and change the subject line so it is meaningful.> > Today's Topics:> > 1. Setting up Multiple facilities (Don Cavaiani)> 2. Re: Setting up Multiple facilities (Roger.Henady@xxxxxxxxxx)> 3. Re: Setting up Multiple facilities (Al Mac Wheel)> > > ----------------------------------------------------------------------> > message: 1> date: Fri, 8 Feb 2008 09:42:19 -0600> from: "Don Cavaiani" <dcavaiani@xxxxxxxxxxxxx>> subject: [BPCS-L] Setting up Multiple facilities> > > Ver 405 DC> > We have 3 plants. The people who set up BPCS in the 90's are no longer > here. They only set up one facility.> > Plant 3 is the final assembly plant, but Plant 1 and 2 only build > sub-assemblies which get supplied to Plant 3.> > We are all under the one facility code. > > Now, we are wondering how the system might look (work) if we have separate > facility codes for Plants 1 and 2, and treated their output as component > requirements for the plant 3 facility???> > TIA,> Don> Don F. Cavaiani> IT Manager> Amerequip Corp.> 920-894-7063> > "It's amazing what you can accomplish if you don't care who gets the > credit." Harry S. Truman> > > > > > ------------------------------> > message: 2> date: Fri, 8 Feb 2008 10:43:29 -0600> from: Roger.Henady@xxxxxxxxxx> subject: Re: [BPCS-L] Setting up Multiple facilities> > We setup a Facility and Warehouse for each plant. Each plant can have > its own inventory. How are the locations setup? Each inventory > location has a Warehouse and Profit center. > > If you have separate facility and Warehouse then you will have to > resupply material between plant / warehouse. MRP will not see the > sub-assemblies if they are in a different plant / facility / warehouse. > > Roger Henady> > > > > From:> "Don Cavaiani" <dcavaiani@xxxxxxxxxxxxx>> To:> <bpcs-l@xxxxxxxxxxxx>> Date:> 02/08/2008 09:41 AM> Subject:> [BPCS-L] Setting up Multiple facilities> > > > > Ver 405 DC> > We have 3 plants. The people who set up BPCS in the 90's are no longer > here. They only set up one facility.> > Plant 3 is the final assembly plant, but Plant 1 and 2 only build > sub-assemblies which get supplied to Plant 3.> > We are all under the one facility code. > > Now, we are wondering how the system might look (work) if we have separate > facility codes for Plants 1 and 2, and treated their output as component > requirements for the plant 3 facility???> > TIA,> Don> Don F. Cavaiani> IT Manager> Amerequip Corp.> 920-894-7063> > "It's amazing what you can accomplish if you don't care who gets the > credit." Harry S. Truman> > > > -- > This is the BPCS ERP System (BPCS-L) mailing list> To post a message email: BPCS-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l> or email: BPCS-L-request@xxxxxxxxxxxx> Before posting, please take a moment to review the archives> at http://archive.midrange.com/bpcs-l.> > Delivered-To: Roger.Henady@xxxxxxxxxx> > > > ------------------------------> > message: 3> date: Fri, 08 Feb 2008 10:24:01 -0600> from: Al Mac Wheel <macwheel99@xxxxxxxxxx>> subject: Re: [BPCS-L] Setting up Multiple facilities> > We also Ver 405 CD. Over the years we have had facilities that were > opened, ran for several years, shut down. Certain customer's business got > transferred from a specific facility to another specific facility. We took > care of customer orders manually, since it was staggered what business > would overlap two facilities as it transitioned, but we got a modification > written by UPI to move the engineering data (routings, BOM, costs, etc.) > across the relevant facilities, since we have some coding that is facility > specific.> > For example our main factory has> facility 20 ... all warehouses prefixed 2, with last digit being type of > stuff there ... shipping warehouse, production warehouse, QC problems, etc.> profit center 200 into the General Ledger, with other 2 prefixes as > appropriate.> All work centers there prefixed 2, factory departments prefixed 2.> We have vendor and customer #s for each facility, also using this # system.> > This way it is crystal clear to everyone what facility some data is in.> > I suggest you take a hard look at DRP and RO (resupply orders).> This manages work that is in transition between facilities.> You can have a customer order in one facility, to be delivered to another > facility.> The purpose of this is to treat other facilities like customers and > vendors, without the hassle of having to pay the financials, while managing > inventory and orders same way as for outside customers & vendors.> You can have facilities specializing in different production skills. Just > make sure the engineering defines a discrete item for what gets transferred > across facilities, and you allow enough move time if the factories are not > in close proximity.> > When you receive inventory from a different facility, you use a different > transaction than when it is on a purchase order with a vendor. Shipping > out uses the same process as shipping to an outside customer.> > If you have 2 facilities with different cost structures ... e.g. > distribution vs. manufacturing ... you don't want to be doing ordinary > transfers of inventory between them, because when the part moves, it drags > its cost structure along with it, so you can end up with inappropriate > costs in the target facility.> > We use BPCS special pricing to offer discounts to customers that buy larger > quantities, because this reduces the impact of setup and other > costs. Unfortunately the special price file does not allow for different > pricing structures by facility for same customer item combination.> > There are people who need to manage what's going on facility by facility, > and there are people who want to look at the big picture for the entire > corporation. We have had to do a few modifications to make sure both > interests are adequately served.> > > >Ver 405 DC> >> >We have 3 plants. The people who set up BPCS in the 90's are no longer > >here. They only set up one facility.> >> >Plant 3 is the final assembly plant, but Plant 1 and 2 only build > >sub-assemblies which get supplied to Plant 3.> >> >We are all under the one facility code.> >> >Now, we are wondering how the system might look (work) if we have separate > >facility codes for Plants 1 and 2, and treated their output as component > >requirements for the plant 3 facility???> >> >TIA,> >Don> >Don F. Cavaiani> >IT Manager> >Amerequip Corp.> >920-894-7063> >> >"It's amazing what you can accomplish if you don't care who gets the > >credit." Harry S. Truman> > > > > ------------------------------> > -- > This is the BPCS ERP System (BPCS-L) digest list> To post a message email: BPCS-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l> or email: BPCS-L-request@xxxxxxxxxxxx> Before posting, please take a moment to review the archives> at http://archive.midrange.com/bpcs-l.> > > > End of BPCS-L Digest, Vol 6, Issue 26> *************************************> > > > > > **************Biggest Grammy Award surprises of all time on AOL Music. > (http://music.aol.com/grammys/pictures/never-won-a-grammy?NCID=aolcmp003000000025> 48)> > > ------------------------------> > message: 2> date: Sun, 10 Feb 2008 07:06:45 -0600> from: "Don Cavaiani" <dcavaiani@xxxxxxxxxxxxx>> subject: Re: [BPCS-L] BPCS-L Digest, Vol 6, Issue 26> > Ric and others,> > I really appreciate your views on this. I will be trying out these> suggestions.> > Thanks> Don C. > > -----Original Message-----> From: bpcs-l-bounces+dcavaiani=amerequip.com@xxxxxxxxxxxx> [mailto:bpcs-l-bounces+dcavaiani=amerequip.com@xxxxxxxxxxxx] On Behalf> Of MisterBPCS@xxxxxxx> Sent: Saturday, February 09, 2008 9:20 PM> To: bpcs-l@xxxxxxxxxxxx> Subject: Re: [BPCS-L] BPCS-L Digest, Vol 6, Issue 26> > Don,> > My recommendation would be to separate each plant into separate> facilities. > I also think you should use the DRP function by the demand plant issues> a resupply order to the supplying plant. The supplying plant would do a> confirm ship to the resupply order. The receiving plant would then due a> receiving using an "H' transaction for resupply receipts. To set up each> plant as a facility, you will need to set up facility planning records> (MRP140) and the DDR records to show the relationship between each> plant. This is just my view.> > Ric Weide> _MisterBPCS@xxxxxxxx (mailto:MisterBPCS@xxxxxxx) > > > In a message dated 2/8/2008 12:02:18 P.M. Central Standard Time,> bpcs-l-request@xxxxxxxxxxxx writes:> > Send BPCS-L mailing list submissions to bpcs-l@xxxxxxxxxxxx> > To subscribe or unsubscribe via the World Wide Web, visit> http://lists.midrange.com/mailman/listinfo/bpcs-l> or, via email, send a message with subject or body 'help' to> bpcs-l-request@xxxxxxxxxxxx> > You can reach the person managing the list at bpcs-l-owner@xxxxxxxxxxxx> > When replying, please edit your Subject line so it is more specific> than "Re: Contents of BPCS-L digest..."> > > *** NOTE: When replying to this digest message, PLEASE remove all text> unrelated to your reply and change the subject line so it is> meaningful.> > Today's Topics:> > 1. Setting up Multiple facilities (Don Cavaiani) 2. Re: Setting up> Multiple facilities (Roger.Henady@xxxxxxxxxx) 3. Re: Setting up> Multiple facilities (Al Mac Wheel)> > > ----------------------------------------------------------------------> > message: 1> date: Fri, 8 Feb 2008 09:42:19 -0600> from: "Don Cavaiani" <dcavaiani@xxxxxxxxxxxxx>> subject: [BPCS-L] Setting up Multiple facilities> > > Ver 405 DC> > We have 3 plants. The people who set up BPCS in the 90's are no longer> here. They only set up one facility.> > Plant 3 is the final assembly plant, but Plant 1 and 2 only build> sub-assemblies which get supplied to Plant 3.> > We are all under the one facility code. > > Now, we are wondering how the system might look (work) if we have> separate facility codes for Plants 1 and 2, and treated their output as> component requirements for the plant 3 facility???> > TIA,> Don> Don F. Cavaiani> IT Manager> Amerequip Corp.> 920-894-7063> > "It's amazing what you can accomplish if you don't care who gets the> credit." Harry S. Truman> > > > > > ------------------------------> > message: 2> date: Fri, 8 Feb 2008 10:43:29 -0600> from: Roger.Henady@xxxxxxxxxx> subject: Re: [BPCS-L] Setting up Multiple facilities> > We setup a Facility and Warehouse for each plant. Each plant can have > its own inventory. How are the locations setup? Each inventory > location has a Warehouse and Profit center. > > If you have separate facility and Warehouse then you will have to > resupply material between plant / warehouse. MRP will not see the > sub-assemblies if they are in a different plant / facility / warehouse.> > > Roger Henady> > > > > From:> "Don Cavaiani" <dcavaiani@xxxxxxxxxxxxx>> To:> <bpcs-l@xxxxxxxxxxxx>> Date:> 02/08/2008 09:41 AM> Subject:> [BPCS-L] Setting up Multiple facilities> > > > > Ver 405 DC> > We have 3 plants. The people who set up BPCS in the 90's are no longer> > here. They only set up one facility.> > Plant 3 is the final assembly plant, but Plant 1 and 2 only build > sub-assemblies which get supplied to Plant 3.> > We are all under the one facility code. > > Now, we are wondering how the system might look (work) if we have> separate > facility codes for Plants 1 and 2, and treated their output as> component > requirements for the plant 3 facility???> > TIA,> Don> Don F. Cavaiani> IT Manager> Amerequip Corp.> 920-894-7063> > "It's amazing what you can accomplish if you don't care who gets the > credit." Harry S. Truman> > > > -- > This is the BPCS ERP System (BPCS-L) mailing list> To post a message email: BPCS-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l> or email: BPCS-L-request@xxxxxxxxxxxx> Before posting, please take a moment to review the archives> at http://archive.midrange.com/bpcs-l.> > Delivered-To: Roger.Henady@xxxxxxxxxx> > > > ------------------------------> > message: 3> date: Fri, 08 Feb 2008 10:24:01 -0600> from: Al Mac Wheel <macwheel99@xxxxxxxxxx>> subject: Re: [BPCS-L] Setting up Multiple facilities> > We also Ver 405 CD. Over the years we have had facilities that were > opened, ran for several years, shut down. Certain customer's business> got > transferred from a specific facility to another specific facility. We> took > care of customer orders manually, since it was staggered what business > would overlap two facilities as it transitioned, but we got a> modification > written by UPI to move the engineering data (routings, BOM, costs,> etc.) > across the relevant facilities, since we have some coding that is> facility > specific.> > For example our main factory has> facility 20 ... all warehouses prefixed 2, with last digit being type> of > stuff there ... shipping warehouse, production warehouse, QC problems,> etc.> profit center 200 into the General Ledger, with other 2 prefixes as > appropriate.> All work centers there prefixed 2, factory departments prefixed 2.> We have vendor and customer #s for each facility, also using this #> system.> > This way it is crystal clear to everyone what facility some data is in.> > I suggest you take a hard look at DRP and RO (resupply orders).> This manages work that is in transition between facilities.> You can have a customer order in one facility, to be delivered to> another > facility.> The purpose of this is to treat other facilities like customers and > vendors, without the hassle of having to pay the financials, while> managing > inventory and orders same way as for outside customers & vendors.> You can have facilities specializing in different production skills.> Just > make sure the engineering defines a discrete item for what gets> transferred > across facilities, and you allow enough move time if the factories are> not > in close proximity.> > When you receive inventory from a different facility, you use a> different > transaction than when it is on a purchase order with a vendor.> Shipping > out uses the same process as shipping to an outside customer.> > If you have 2 facilities with different cost structures ... e.g. > distribution vs. manufacturing ... you don't want to be doing ordinary > transfers of inventory between them, because when the part moves, it> drags > its cost structure along with it, so you can end up with inappropriate > costs in the target facility.> > We use BPCS special pricing to offer discounts to customers that buy> larger > quantities, because this reduces the impact of setup and other > costs. Unfortunately the special price file does not allow for> different > pricing structures by facility for same customer item combination.> > There are people who need to manage what's going on facility by> facility, > and there are people who want to look at the big picture for the entire> > corporation. We have had to do a few modifications to make sure both > interests are adequately served.> > > >Ver 405 DC> >> >We have 3 plants. The people who set up BPCS in the 90's are no> longer > >here. They only set up one facility.> >> >Plant 3 is the final assembly plant, but Plant 1 and 2 only build > >sub-assemblies which get supplied to Plant 3.> >> >We are all under the one facility code.> >> >Now, we are wondering how the system might look (work) if we have> separate > >facility codes for Plants 1 and 2, and treated their output as> component > >requirements for the plant 3 facility???> >> >TIA,> >Don> >Don F. Cavaiani> >IT Manager> >Amerequip Corp.> >920-894-7063> >> >"It's amazing what you can accomplish if you don't care who gets the > >credit." Harry S. Truman> > > > > ------------------------------> > -- > This is the BPCS ERP System (BPCS-L) digest list> To post a message email: BPCS-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l> or email: BPCS-L-request@xxxxxxxxxxxx> Before posting, please take a moment to review the archives> at http://archive.midrange.com/bpcs-l.> > > > End of BPCS-L Digest, Vol 6, Issue 26> *************************************> > > > > > **************Biggest Grammy Award surprises of all time on AOL Music.> > (http://music.aol.com/grammys/pictures/never-won-a-grammy?NCID=aolcmp003> 000000025> 48)> -- > This is the BPCS ERP System (BPCS-L) mailing list> To post a message email: BPCS-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l> or email: BPCS-L-request@xxxxxxxxxxxx> Before posting, please take a moment to review the archives> at http://archive.midrange.com/bpcs-l.> > Delivered-To: dcavaiani@xxxxxxxxxxxxx> > > ------------------------------> > message: 3> date: Sun, 10 Feb 2008 09:51:34 -0600> from: "Don Cavaiani" <dcavaiani@xxxxxxxxxxxxx>> subject: Re: [BPCS-L] BPCS-L Digest, Vol 6, Issue 26> > Now I see that DRP is not "installed" on our system. I can't imagine> there is a way to get the cd405 versions of DRP activated on our system.> We do not have BPCS maintenance. > > -----Original Message-----> From: bpcs-l-bounces+dcavaiani=amerequip.com@xxxxxxxxxxxx> [mailto:bpcs-l-bounces+dcavaiani=amerequip.com@xxxxxxxxxxxx] On Behalf> Of MisterBPCS@xxxxxxx> Sent: Saturday, February 09, 2008 9:20 PM> To: bpcs-l@xxxxxxxxxxxx> Subject: Re: [BPCS-L] BPCS-L Digest, Vol 6, Issue 26> > Don,> > My recommendation would be to separate each plant into separate> facilities. > I also think you should use the DRP function by the demand plant issues> a resupply order to the supplying plant. The supplying plant would do a> confirm ship to the resupply order. The receiving plant would then due a> receiving using an "H' transaction for resupply receipts. To set up each> plant as a facility, you will need to set up facility planning records> (MRP140) and the DDR records to show the relationship between each> plant. This is just my view.> > Ric Weide> _MisterBPCS@xxxxxxxx (mailto:MisterBPCS@xxxxxxx) > > > In a message dated 2/8/2008 12:02:18 P.M. Central Standard Time,> bpcs-l-request@xxxxxxxxxxxx writes:> > Send BPCS-L mailing list submissions to bpcs-l@xxxxxxxxxxxx> > To subscribe or unsubscribe via the World Wide Web, visit> http://lists.midrange.com/mailman/listinfo/bpcs-l> or, via email, send a message with subject or body 'help' to> bpcs-l-request@xxxxxxxxxxxx> > You can reach the person managing the list at bpcs-l-owner@xxxxxxxxxxxx> > When replying, please edit your Subject line so it is more specific> than "Re: Contents of BPCS-L digest..."> > > *** NOTE: When replying to this digest message, PLEASE remove all text> unrelated to your reply and change the subject line so it is> meaningful.> > Today's Topics:> > 1. Setting up Multiple facilities (Don Cavaiani) 2. Re: Setting up> Multiple facilities (Roger.Henady@xxxxxxxxxx) 3. Re: Setting up> Multiple facilities (Al Mac Wheel)> > > ----------------------------------------------------------------------> > message: 1> date: Fri, 8 Feb 2008 09:42:19 -0600> from: "Don Cavaiani" <dcavaiani@xxxxxxxxxxxxx>> subject: [BPCS-L] Setting up Multiple facilities> > > Ver 405 DC> > We have 3 plants. The people who set up BPCS in the 90's are no longer> here. They only set up one facility.> > Plant 3 is the final assembly plant, but Plant 1 and 2 only build> sub-assemblies which get supplied to Plant 3.> > We are all under the one facility code. > > Now, we are wondering how the system might look (work) if we have> separate facility codes for Plants 1 and 2, and treated their output as> component requirements for the plant 3 facility???> > TIA,> Don> Don F. Cavaiani> IT Manager> Amerequip Corp.> 920-894-7063> > "It's amazing what you can accomplish if you don't care who gets the> credit." Harry S. Truman> > > > > > ------------------------------> > message: 2> date: Fri, 8 Feb 2008 10:43:29 -0600> from: Roger.Henady@xxxxxxxxxx> subject: Re: [BPCS-L] Setting up Multiple facilities> > We setup a Facility and Warehouse for each plant. Each plant can have > its own inventory. How are the locations setup? Each inventory > location has a Warehouse and Profit center. > > If you have separate facility and Warehouse then you will have to > resupply material between plant / warehouse. MRP will not see the > sub-assemblies if they are in a different plant / facility / warehouse.> > > Roger Henady> > > > > From:> "Don Cavaiani" <dcavaiani@xxxxxxxxxxxxx>> To:> <bpcs-l@xxxxxxxxxxxx>> Date:> 02/08/2008 09:41 AM> Subject:> [BPCS-L] Setting up Multiple facilities> > > > > Ver 405 DC> > We have 3 plants. The people who set up BPCS in the 90's are no longer> > here. They only set up one facility.> > Plant 3 is the final assembly plant, but Plant 1 and 2 only build > sub-assemblies which get supplied to Plant 3.> > We are all under the one facility code. > > Now, we are wondering how the system might look (work) if we have> separate > facility codes for Plants 1 and 2, and treated their output as> component > requirements for the plant 3 facility???> > TIA,> Don> Don F. Cavaiani> IT Manager> Amerequip Corp.> 920-894-7063> > "It's amazing what you can accomplish if you don't care who gets the > credit." Harry S. Truman> > > > -- > This is the BPCS ERP System (BPCS-L) mailing list> To post a message email: BPCS-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l> or email: BPCS-L-request@xxxxxxxxxxxx> Before posting, please take a moment to review the archives> at http://archive.midrange.com/bpcs-l.> > Delivered-To: Roger.Henady@xxxxxxxxxx> > > > ------------------------------> > message: 3> date: Fri, 08 Feb 2008 10:24:01 -0600> from: Al Mac Wheel <macwheel99@xxxxxxxxxx>> subject: Re: [BPCS-L] Setting up Multiple facilities> > We also Ver 405 CD. Over the years we have had facilities that were > opened, ran for several years, shut down. Certain customer's business> got > transferred from a specific facility to another specific facility. We> took > care of customer orders manually, since it was staggered what business > would overlap two facilities as it transitioned, but we got a> modification > written by UPI to move the engineering data (routings, BOM, costs,> etc.) > across the relevant facilities, since we have some coding that is> facility > specific.> > For example our main factory has> facility 20 ... all warehouses prefixed 2, with last digit being type> of > stuff there ... shipping warehouse, production warehouse, QC problems,> etc.> profit center 200 into the General Ledger, with other 2 prefixes as > appropriate.> All work centers there prefixed 2, factory departments prefixed 2.> We have vendor and customer #s for each facility, also using this #> system.> > This way it is crystal clear to everyone what facility some data is in.> > I suggest you take a hard look at DRP and RO (resupply orders).> This manages work that is in transition between facilities.> You can have a customer order in one facility, to be delivered to> another > facility.> The purpose of this is to treat other facilities like customers and > vendors, without the hassle of having to pay the financials, while> managing > inventory and orders same way as for outside customers & vendors.> You can have facilities specializing in different production skills.> Just > make sure the engineering defines a discrete item for what gets> transferred > across facilities, and you allow enough move time if the factories are> not > in close proximity.> > When you receive inventory from a different facility, you use a> different > transaction than when it is on a purchase order with a vendor.> Shipping > out uses the same process as shipping to an outside customer.> > If you have 2 facilities with different cost structures ... e.g. > distribution vs. manufacturing ... you don't want to be doing ordinary > transfers of inventory between them, because when the part moves, it> drags > its cost structure along with it, so you can end up with inappropriate > costs in the target facility.> > We use BPCS special pricing to offer discounts to customers that buy> larger > quantities, because this reduces the impact of setup and other > costs. Unfortunately the special price file does not allow for> different > pricing structures by facility for same customer item combination.> > There are people who need to manage what's going on facility by> facility, > and there are people who want to look at the big picture for the entire> > corporation. We have had to do a few modifications to make sure both > interests are adequately served.> > > >Ver 405 DC> >> >We have 3 plants. The people who set up BPCS in the 90's are no> longer > >here. They only set up one facility.> >> >Plant 3 is the final assembly plant, but Plant 1 and 2 only build > >sub-assemblies which get supplied to Plant 3.> >> >We are all under the one facility code.> >> >Now, we are wondering how the system might look (work) if we have> separate > >facility codes for Plants 1 and 2, and treated their output as> component > >requirements for the plant 3 facility???> >> >TIA,> >Don> >Don F. Cavaiani> >IT Manager> >Amerequip Corp.> >920-894-7063> >> >"It's amazing what you can accomplish if you don't care who gets the > >credit." Harry S. Truman> > > > > ------------------------------> > -- > This is the BPCS ERP System (BPCS-L) digest list> To post a message email: BPCS-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l> or email: BPCS-L-request@xxxxxxxxxxxx> Before posting, please take a moment to review the archives> at http://archive.midrange.com/bpcs-l.> > > > End of BPCS-L Digest, Vol 6, Issue 26> *************************************> > > > > > **************Biggest Grammy Award surprises of all time on AOL Music.> > (http://music.aol.com/grammys/pictures/never-won-a-grammy?NCID=aolcmp003> 000000025> 48)> -- > This is the BPCS ERP System (BPCS-L) mailing list> To post a message email: BPCS-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l> or email: BPCS-L-request@xxxxxxxxxxxx> Before posting, please take a moment to review the archives> at http://archive.midrange.com/bpcs-l.> > Delivered-To: dcavaiani@xxxxxxxxxxxxx> > > ------------------------------> > -- > This is the BPCS ERP System (BPCS-L) digest list> To post a message email: BPCS-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l> or email: BPCS-L-request@xxxxxxxxxxxx> Before posting, please take a moment to review the archives> at http://archive.midrange.com/bpcs-l.> > > > End of BPCS-L Digest, Vol 6, Issue 27> *************************************_________________________________________________________________
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
