We've had this happen a while back...

I'm guessing your shop order historical files are outside of BPCS (since the FSH,FMH, and FOH came in later releases). I would first identify your smallest shop order # on the FSO (or at least that is still active); use query or sequel... Then back up (archive) your FSO, FMA, FOD, historical files and remove records w/ shop order # less than smallest active shop order number (or whatever # works best). Set your shop order #s back to 1 in the BPCS system parm... Make sure variance costs are captured...

I know you will have issues with sorted reports and will have to look thru some programs and I'm over simplifying..

Good luck!

Best Regards,

DeeDee Virgei
Project Manager
Office:  440-329-0487;  Cell:  440-670-3331

Nelson Stud Welding, Inc.
A DONCASTERS Group Limited Company

-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On Behalf Of Kelly, John (Limerick)
Sent: Thursday, September 19, 2013 2:56 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] Roll-over of BPCS Shop Order #

Hi BPCS-L members,

The company I work for are running BPCS 3.6. Pretty old right! It has been heavily customized over the years with the result that it continues to support the business here in our facility.

By the very nature of its age we are on the verge of seeing our Shop Order number hit its maximum possible value of 999,999. The relevant field is six numeric in length.

With the roll-over date likely to occur within the next couple of weeks we do not have the scope to implement an update to increase the Shop Order number field size.

My business (i.e. non IT) colleagues do not have a major concern about this event, as the Lot/Trace Code is the unique ID of choice for our product range as opposed to the Shop Order #. From an IT perspective though we do have a number of risks associated with the roll-over, as we will start generating Shop Order numbers we have already used in the past once the roll-over happens. We will see duplicate Shop Order numbers in our Shop Order historical files which if referenced by program could cause problems if the incorrect version is selected for processing.

I would like to ask the BPCS_L group have you experienced this event in the past and if so can you provide any information on how you worked through it, lessons learned etc.

Kind regards,

The information contained in this e-mail message and any attachments may contain proprietary and confidential information and is intended only for the individual or entity to whom it is addressed. Any use, interception, dissemination, distribution, publication, copying or disclosure by any other person is strictly prohibited. If you are not the intended recipient, you should delete this message and kindly notify the sender via reply e-mail and confirm that you will destroy or delete all copies of the email message and any attachments from your system.
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,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/bpcs-l.

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