Previously we had written a custom front end program for doing tag
entry/reports for Physical Inventory - that allowed us, among other
things, to have multiple tickets for a part in the same location. Last
step of the process combined the tickets so only had one part number per
location, then went to traditional BPCS Physical inventory - generated
tags. Ran a couple of custom programs that brought the inventory over
and booked/created tickets, ran other program that zeroed out any unused
traditional BPCS tags - ran some cross reference reports - (many tags
entered - to BPCS traditional tag#), then finished posting
inventory/reports through traditional BPCS programs.

Upgraded to 8.3.04, moved to new box. Tried to reduce "Custom" items.
Thought we could use plain regular BPCS physical inventory. Almost
could - but show stopper surprised me. Still can only have one tag per
part per location. Why do they not have some sort of front end on
traditional BPCS for multiple tags, that then combines down to the one
ticket location so can update the ILI file? We have several examples of
why we need more than one ticket for a part in a production location -
product may not be physically next to each other - same material may be
at several workstations - but is same production floor location. We
want to inventory it where it is - not move it all around and then move
it back. We also do not want to add finite locations to the production
floor - general areas, yes, but not finite like in our stores area...

How do all of you get around this? Does anyone use just the plain BPCS
version or has everyone had to modify or use custom to some degree? We
are going to bring back our old custom front end program for now.

Wendy Bunch
Cost Accountant
Wabash Technologies

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2022 by 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.