Hello,
We had this happen recently and below are my notes on what we did. It seems to have worked for us. We are on 6.04, so I don't know how it lines up with your version. Good Luck! ~Chad
Shop Order - Purge Old Shop Orders 7/18/2013 - CMS
We are going to run out of shop order numbers in about a month. We are at 989348 and the field is only 6 digits long. If we do nothing, the shop order number will roll and start again at 000000.
I spoke with Infor to find out how to proceed. They told me that we can simply SQL delete really old shop orders and set our sequence to 000001. She said that the only files we need to worry about are FSO, FOD, and FMA. And we should run SFC990 after the purge. We can run this at any time, but users should be off of the system.
I googled the issue and found a couple of more files you should look at:
ESN - the notes file, can have S, M, or R type notes for the shop orders. I looked in this file and found 2 notes with R type for really old shop orders. Other than that, the only ESN records are in the 900,000 range currently, so something must clean these up along the way. I deleted the 2 old notes using SFC190.
FLT - the labor transaction history file contains labor reporting. We are already archiving FLT records, so this should be clear for really old shop orders, but it should be checked as well. I found 1 old shop order in FLT. I discovered that it was never archived because the shop order had a status of 'SX' instead of 'SZ'. This was probably caused on accident during a manual close. I updated the FSO status to 'SZ' so in theory it would archive on Sunday when the scheduled job ran(FLTPURGE - BPCSUSR60/FLTA01BC). However, I plan to purge the FSO records prior to Sunday night, so I am moving the records to archive manually.
Purging Steps - Run when everyone is off the system:
1.) File Checking (need to eliminate any records within you range)
a. SELECT * FROM esn WHERE SNCUST >= 0 and SNCUST < 200000 and SNTYPE in('S','M','R')
b. SELECT * FROM flt WHERE TORD >= 0 and TORD < 200000
c. SELECT * FROM fso WHERE sord >= 0 and sord < 200000 and SID <> 'SZ'
2.) Back Up The Old Data
a. CPYF FROMFILE(V64BPCSF/FSO) TOFILE(BPCSUSRF60/FSO130721) CRTFILE(*YES)
b. CPYF FROMFILE(V64BPCSF/FOD) TOFILE(BPCSUSRF60/FOD130721) CRTFILE(*YES)
c. CPYF FROMFILE(V64BPCSF/FMA) TOFILE(BPCSUSRF60/FMA130721) CRTFILE(*YES)
d. CPYF FROMFILE(V64BPCSF/IIM) TOFILE(BPCSUSRF60/IIM130721) CRTFILE(*YES)
3.) Verify the records you are going to delete are very old by scanning the created date.
a. SELECT SORD, SPROD, SOENDT FROM FSO WHERE SORD >= 0 and SORD < 200000
b. SELECT OORD, ODENDT FROM FOD WHERE OORD >= 0 and OORD < 200000
c. SELECT MORD, MAENDT FROM FMA WHERE MORD >= 0 and MORD < 200000
4.) Purge The Files
a. DELETE FROM FSO WHERE SORD >= 0 and SORD < 200000
i. 159017 rows deleted from FSO in V64BPCSF.
b. DELETE FROM FOD WHERE OORD >= 0 and OORD < 200000
i. 605399 rows deleted from FOD in V64BPCSF.
c. DELETE FROM FMA WHERE MORD >= 0 and MORD < 200000
i. 434325 rows deleted from FMA in V64BPCSF.
5.) From BPCS Program Name Line, run SFC990 - Cleanup Shop Ops & Mtrl Files
a. Started at 8:51, Finished at 8:53, Took 2 Minutes
6.) Only do this step if we are about to roll over the 999999 shop order number.
a. SYS800 - Position to JIT Shop Floor Parameters - JIT820D
i. Option 2 and change last Shop Order Used to 000001.
-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On Behalf Of DeeDee Virgei
Sent: Thursday, September 19, 2013 4:37 PM
To: BPCS ERP System
Subject: Re: [BPCS-L] Roll-over of BPCS Shop Order #
Hi,
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.
440-329-0400
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,
John.
________________________________
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.
--
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.
midrange.com
