|
Barcoding is the way to go. We are running 6.02 PLF Aug 98 Cum. We generated the worksheets on demand and then shoot the cycle counts to the worksheet file. Anything that is shot and not on the worksheet goes to a 999999 worksheet. We then print standard BPCS reports. After all is said and done the person doing the cycle counts can review and make changes via an interactive process. They they select the cycle counts to post. The posting takes place as 'Y0 - Y5' transaction types via CimPath. These transactions represent anything from a bookmark indicating that a cycle count was taken, a bookmark indicating that the cycle count was deleted or an inventory adjustment. The process updates all of the fields that the normal BPCS two step cycle count performs. It is really slick. We are enjoying a 99.8% finished and wip inventory accuracy. We know exactly what we have and where it is at all times. >>> KLChilds@aol.com 05/31/02 09:37AM >>> Hello JB. I can see where BPCS Cycle Count could end up being a huge task in your case. Lot control makes it even more cumbersome and labor-intensive. We had some of the problems you describe when implementing cycle count, too. One of the workarounds we deployed was to work with the cycle count number of days to make it as effective as possible. Also, if there was a huge amount of items selected on a day, we counted what we could that day and allowed BPCS to select those uncounted the next day. We also took the approach of limiting the number of items we cycle counted at first, since most of the items had not been counted for awhile so they all were selected on our first attempts. We did this by tweaking the cycle count values in the item master. It can be done but it can be a tough process to get working properly. We are currently looking to automate the process via barcoding. HTH Lynn _______________________________________________ This is the SSA's BPCS ERP System (BPCS-L) mailing list To post a message email: BPCS-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l or email: BPCS-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/bpcs-l. ------------------------------------------------------------------------------------------- Note: Please update your email address for this user to reflect the new MeadWestvaco Corporation. MeadWestvaco employee email addresses are in the format of user@MeadWestvaco.com This electronic message contains information from MeadWestvaco Corporation or subsidiary companies, which may be confidential, privileged or otherwise protected from disclosure. The information is intended to be used solely by the recipient(s) named. If you are not an intended recipient, be aware that any review, disclosure, copying, distribution or use of this transmission or its contents is prohibited. If you have received this transmission in error, please notify MeadWestvaco immediately at postmaster@MeadWestvaco.com. -------------------------------------------------------------------------------------------
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
