× 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 LaFlamme wrote:

> We're trying to use Lot Control for a couple items in our BPCS V4.03
> system. I don't necesarrily mean BPCS Lot Control...
> 
> Suppose we have an item (A) that the customer
> requires us to control in 3,000 piece lots. We have an order for 51,000
> pieces. This equates to 17 lots. What would be the correct way to cut a
> shop order for this product? Must we manually cut 17 shop orders,
> allowing BPCS to assign the lot number each time? Or can we have one
> work order with 17 releases with 17 different lot numbers that the
> system creates during shop packet print? Labor reported against the shop
> order/operation combo must maintain lot traceability.
> 

Paul,

The way I understand lot assignment to work is if a receipt contains a
lot number, that is the lot number assigned (unless it already exists
for another part number).  If the receipt doesn't contain a lot number,
it will assign one according to the system parameter logic.

So.. In your situation I would cut one S/O and make 17 receipts.


Bill Robins
MIS Manager
Arlon Adhesives

+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to "BPCS-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe BPCS-L' in the body of your message.
| Questions should be directed to the list owner: dasmussen@aol.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.