|
Hi Paul, What we do to mark the lots with the facility where they are created is the following: Every night we schedule a job that checks from the lots that are created that day in which facility the lot is created. The way we do this is by retrieving the facility of the warehouse where the 1st transaction of a lot took place. This facility is written into the Manufacturer field of the lot master (LNMGR from ILN). Example: On 4th of Dec 100 KG of Lot ABC123 from item DEF created on Production Reporting in Warehouse SF. In Transaction History (file ITH) you will find the following record: Tdate Ttype Lot Item Qty Whse 20061204 PR ABC123 DEF 100 SF In Warehouse Master (IWM) the facility from whse SF is retrieved. The Manufacturer field in Lot Master record (ILN) from lot ABC123 is updated with the facility. With this solution we can still use standard BPCS lot creation logic like YYMM + 6 digit sequence number and we can trace the source facility of a lot even when the lot is transferred from one facility the the other. Regards, Harold Swaanen Bladel, the Netherlands
From: bpcs-l-request@xxxxxxxxxxxx> Subject: BPCS-L Digest, Vol 4, Issue 262> To: bpcs-l@xxxxxxxxxxxx> Date: Mon, 4 Dec 2006 12:00:02 -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. Lot Control at Multiple Facilities (Paul Hirschmann)> 2. Re: Lot Control at Multiple Facilities (Davide Roveda)> 3. FW: Lot Control at Multiple Facilities (Paul Hirschmann)> 4. Re: Lot Control at Multiple Facilities (Frederick C Davy)> >----------------------------------------------------------------------> >message: 1> date: Mon, 4 Dec 2006 10:54:30 -0500> from: "Paul Hirschmann" <PHirschmann@xxxxxxxxx>> subject: [BPCS-L] Lot Control at Multiple Facilities> > Hi everyone,> > > > My name is Paul Hirschmann and I work for a snack food manufacturer. The> > > company has multiple facilities in the U.S. and Canada and is in the> process of > > implementing BPCS LX. We would like to use Lot Control at all of the > > facilities for stock rotation and recall however, we have a problem. The> same > > product, with the same item number, can be made at different facilities.> Based > > on my research, BPCS LX doesn't support this in Lot Control. In other> words,> > we need to have a way to distinguish from what facility that item was> manufactured> > in while using the lot control number. Any help would be greatly> appreciated.> > > >Thanks,> > Paul> > > > Paul Hirschmann> > Lance, Inc.> > Business Analyst( IT Logistics)> > Email: phirschmann@xxxxxxxxx> > Office: 704-557-8350> > >------------------------------> > message: 2> date: Mon, 4 Dec 200617:27:17 +0100> from: "Davide Roveda" <davide.roveda@xxxxxxxxx>> subject: Re: [BPCS-L] Lot Control at Multiple Facilities> > Hello> > You can configure how the lot code can be set, and for LX in API820 you have from the Help on your system --> "4": > > 0 = Manual > 1 = YYMM + 6 digit sequence number (within the month) > 2= YY + 8 digit number (with the year) > 3 = Julian Date (5) + 5 digit sequence number > 4 = a call to a user created lot numbering program > 5 = CCYYMM + 19 digit sequence number (within the month)> 6 = CCYY + 21 digit sequence number (within the year) > 7 = CCYYNNN, Julian Date (7) + 18 digit sequence number > > When a lot is created, selecting lot numbering method 4 calls a user > written (and installed) program which must be named USR901. > This program can provide any lot numbering scheme developed by a user which operates within the field size available (25,A). > > ---> > So, you have to follow on USR901 the facility needs, you are describing. > > Thanks > > Regards> > Davide Roveda | Technical Mgr, ISeries Area | Infor | > Address: SSA Global Italia S.r.l. | Via Torri Bianche, 9 | 20059 Vimercate > > -----Original Message-----> From: bpcs-l-bounces+davide.roveda=infor.com@xxxxxxxxxxxx [mailto:bpcs-l-bounces+davide.roveda=infor.com@xxxxxxxxxxxx] On Behalf Of Paul Hirschmann> Sent: luned? 4 dicembre 2006 16.55> To: bpcs-l@xxxxxxxxxxxx> Subject: [BPCS-L] Lot Control at Multiple Facilities> > Hi everyone,> > > > My name is Paul Hirschmann and I work for a snack food manufacturer. The> > > company has multiple facilities in the U.S. and Canada and is in the> process of > > implementing BPCS LX. We would like to use Lot Control at all of the >facilities for stock rotation and recall however, we have a problem. The>same > > product, with the same item number, can be made at different facilities.> Based > > on my research, BPCS LX doesn't support this in Lot Control. In other> words,> > we need to have a way to distinguish from what facility that item was> manufactured> > in while using the lot control number. Any help would be greatly> appreciated.> > > > > > Thanks,> > Paul> >Paul Hirschmann> > Lance, Inc.> > Business Analyst ( IT Logistics)> >Email: phirschmann@xxxxxxxxx> > Office: 704-557-8350> > > > > > -- > This is the SSA's 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: davide.roveda@xxxxxxxxx> > > > ------------------------------> > message: 3> date: Mon, 4 Dec 2006 11:25:59 -0500> from: "Paul Hirschmann" <PHirschmann@xxxxxxxxx>> subject: [BPCS-L] FW: Lot Control at Multiple Facilities> > I'm trying to submit this again.> > > > Thanks,> > > > Paul Hirschmann> > Lance, Inc.> > Business Analyst ( IT Logistics)> > Email: phirschmann@xxxxxxxxx> > Office: 704-557-8350> > > > ________________________________> > From: Paul Hirschmann > Sent: Monday, December 04, 2006 10:55 AM> To: 'bpcs-l@xxxxxxxxxxxx'> Subject: Lot Control at Multiple Facilities> > > > Hi everyone,> > > > My name is Paul Hirschmann and I work for a snack food manufacturer. The> > > company has multiple facilities in the U.S. and Canada and is in the> process of > > implementing BPCS LX. We would like to use Lot Control at all of the > > facilities for stock rotation and recall however, we have a problem. The> same > > product, with the same item number, can be made at different facilities.> Based > > on my research, BPCS LX doesn't support this in Lot Control. In other> words,> > we need to have a way to distinguish from what facility that item was> manufactured> > in while using the lot control number. Any help would be greatly> appreciated.> > > > > > Thanks,> > Paul> > > > Paul Hirschmann> > Lance, Inc.> > Business Analyst ( IT Logistics)> > Email: phirschmann@xxxxxxxxx> > Office: 704-557-8350> > > > > > > > ------------------------------> > message: 4> date: Mon, 4 Dec 2006 11:53:38 -0500> from: Frederick C Davy <fcdavy@xxxxxxxxxxxx>> subject: Re: [BPCS-L] Lot Control at Multiple Facilities> > Paul,> > To expand on what Davide has said, I have worked with several companies > that use BPCS lot control at several different facilities and many of them > made the same product at more than one location. I would suggest that you > use Davide's suggestion to create your own lot number generation program > (one we that I have seen work well is to use the first digit of the lot > number to be an alpha designation of the facility that is creating the > lot). The only other way to control what lot numbers are used at each > facility would be to assign a block of numbers for each location, use a > log, and manually assign the lot numbers. This is VERY ugly, and I don't > suggest trying to do it, but it is an option. Good luck.> > Frederick C. Davy, CPIM, PMP> Business Systems Analyst> Interface Solution, Inc.> Phone: (315) 592-8101> Fax: (315) 592-8481> e-mail: fcdavy@xxxxxxxxxxxx> > > > > "Davide Roveda" <davide.roveda@xxxxxxxxx> > Sent by: bpcs-l-bounces+fcdavy=sealinfo.com@xxxxxxxxxxxx> 12/04/2006 11:28 AM> Please respond to> SSA's BPCS ERP System <bpcs-l@xxxxxxxxxxxx>> > > To> "SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx>> cc> > Subject> Re: [BPCS-L] Lot Control at Multiple Facilities> > > > > > > Hello> > You can configure how the lot code can be set, and for LX in API820 you > have from the Help on your system --> "4": > > 0 = Manual > 1 = YYMM + 6 digit sequence number (within the month) > 2= YY + 8 digit number (with the year) > 3 = Julian Date (5) + 5 digit sequence number > 4 = a call to a user created lot numbering program > 5 = CCYYMM + 19 digit sequence number (within the month)> 6 = CCYY + 21 digit sequence number (within the year) > 7 = CCYYNNN, Julian Date (7) + 18 digit sequence number > > When a lot is created, selecting lot numbering method 4 calls a user > written (and installed) program which must be named USR901. > This program can provide any lot numbering scheme developed by a user > which operates within the field size available (25,A). > > ---> > So, you have to follow on USR901 the facility needs, you are describing. > > Thanks > > Regards> > Davide Roveda | Technical Mgr, ISeries Area | Infor | > Address: SSA Global Italia S.r.l. | Via Torri Bianche, 9 | 20059 Vimercate >-----Original Message-----> From:bpcs-l-bounces+davide.roveda=infor.com@xxxxxxxxxxxx > [mailto:bpcs-l-bounces+davide.roveda=infor.com@xxxxxxxxxxxx] On Behalf Of > Paul Hirschmann> Sent: luned? 4 dicembre 2006 16.55> To: bpcs-l@xxxxxxxxxxxx> Subject: [BPCS-L] Lot Control at Multiple Facilities> > Hi everyone,> > > > My name is Paul Hirschmann and I work for a snack food manufacturer. The> > > company has multiple facilities in the U.S. and Canada and is in the> process of > > implementing BPCS LX. We would like to use Lot Control at all of the >facilities for stock rotation and recall however, we have a problem. The>same > > product, with the same item number, can be made at different facilities.> Based > > on my research, BPCS LX doesn't support this in Lot Control. In other> words,> > we need to have a way to distinguish from what facility that item was> manufactured> > in while using the lot control number. Any help would be greatly> appreciated.> > > > > > Thanks,> > Paul> >Paul Hirschmann> > Lance, Inc.> > Business Analyst ( IT Logistics)> >Email: phirschmann@xxxxxxxxx> > Office: 704-557-8350> > > > > > -- > This is the SSA's 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: davide.roveda@xxxxxxxxx> > -- > This is the SSA's 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: fcdavy@xxxxxxxxxxxx> > > > ------------------------------> > -- > This is the SSA's 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 4, Issue 262> **************************************
_________________________________________________________________ Probeer Live.com: jouw leven online met nieuws, sport, weer en nog veel meer. http://www.live.com/getstarted
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.