× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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

 

 


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.