One common sense (but not necessarily obvious) suggestion -- be absolutely
sure that Purchasing has communicated this upcoming change clearly with your
vendor(s). "LB" and "LF" are a mere ink smudge apart. And as for the nice
folks who have been entering or picking orders all day, they often work from
familiarity instead of reading your PO letter-for-letter.

Same for your own Receiving department, make sure they're aware of the
change. Yes the UOM is carried along with the PO line, but be sure they're
informed of the change so they know to count the receipt quantity in the new
units. Just in case they decide not to read their screen or the packing
slip on that particular day.

Otherwise, I advise nominal testing just to cover all the bases. Purchasing
UOM changes in BPCS are fairly well accounted for and easily implemented.

All the best,
Kevin Harper

On Wed, Jun 16, 2010 at 2:18 PM, Bill <brobins3d@xxxxxxxxx> wrote:

We're on 4.05CD. We have a couple of items that are currently purchased
in LB and stocked in LF. We'd like to change the purchasing to be LF.

What are the ramifications in changing this with open po's and po's
received but not vouchered?

I imagine chaos would ensue and so we are trying to plan a neat cutover
involving closing out open po lines and data changeovers in a particular
sequence and pilot that. Are we correct to be concerned or does the
system handle it smoothly and we're being too cautious?

This is the BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

Delivered-To: kharper@xxxxxxxxxxxxxxxxx

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-2021 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.