×
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.
We are 405 CD mixed mode, modified, and our cycle counts are all ****
mucked up.
There are two different methods for cycle counting in the BPCS
documentation, but actually there is more going on there than meets the
documented eye. You might want to look at the Cycle Counting documentation
in the BPCSDOC file for starters, to familiarize yourself with the official
party line, before getting into nuances of undocumented exceptions.
The challenge here is that for ERP to work right, the PEOPLE have to do a
LOT of things right, but some people expect BPCS to do the work, and that
aint gonna work with cycle counting. You have to comprehend what the ****
is going on, and have a set of business rules that all your people gonna
adhere to.
Check your transaction effects and reason codes ... You can use a unique
transaction and reason for reporting your cycle counting, then if all your
work force consistent with the plan, you can then use inventory history to
find the last time you did specific transaction with specific reason.
Check your transaction effects ... do you want date of last activity
updated just because you found some obsolete parts in your physical
inventory ... in other words we have not REALLY used this part in 3 years,
but it shows up as last activity last month because that was our last
physical inventory.
There is an ABC code in BPCS item some place, where you can set some rules
for the system to tell you which items to count based on most heavily used
and how long since last cycle counted. I suspect that is what you are
being told does not work satisfactorily.
We have items that we run out of (in actuality) when BPCS says there's plenty.
The items that sort of thing happens to are those I think ought to be cycle
counted frequently after we get the new in, to see if we are consuming more
than BPCS being told about.
Likewise, I think the items, that show up in physical inventory with bad
variances, should be flagged for more frequent cycle counting, to see if
the problem leading up to physical is still going on.
You can create your own report ... show what proportion of the total
inventory action on some item is due to use in actual production, purchase,
sales and what proportion is due to the on-hand being fixed with an
adjustment. Those items with high proportion of adjustments, would be the
ones you want to audit. We had some that were 100% adjustments, the last
time I ran these "proportionality" reports, which has been some time since
I was looking into this.
Unfortunately, transferring inventory from one place to another is recorded
in 405 CD as an adjustment, so this makes report design a bit challenging.
You do not have to use BPCS to determine which items ought to be cycle counted.
You can send BPCS reports to a PC spread sheet and have your own set of
rules to determine on what basis items should be cycle counted.
This PC spread sheet might include all the reasons I cited above why some
items might be in need of more frequent cycle counting.
-
Al Macintyre http://www.ryze.com/go/Al9Mac
Find BPCS Documentation Suppliers
http://radio.weblogs.com/0107846/stories/2002/11/08/bpcsDocSources.html
BPCS/400 Computer Janitor at http://www.globalwiretechnologies.com/
We are on v 6.04 mixed mode, heavily modified. Has anyone been able to
develop a cycle count program that actually tracks the last time an item
was cycle counted and when the item is due to be cycle counted? My IT
department tells me cycle counting in Bpcs doesn't work and it may work in
a newer release. This is too critical to our operation to ignore.
Thanks,
Brenda Engel
574-254-4015 ext. 109
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.