|
We use a front end program for out physical inventory -- After we are finished with physical we generate Bpcs tags and then run a program to populate the bpcs tags. Then another program to set unpopulated tags to zero. At each month end - after Inv903 ran, then we run Inv970- lot/loc/container, Inv972 - reset whs level per loc inv, Inv973 delete zero balance records. We have found with the BPCS tag generation, if I wait to create the BPCS tags after this process (INV970, INV972, INV973) we end up with few or no bogus BPCS tags for locations with no inventory. -----Original Message----- From: bpcs-l-bounces+wbunch=wabashtech.com@xxxxxxxxxxxx [mailto:bpcs-l-bounces+wbunch=wabashtech.com@xxxxxxxxxxxx]On Behalf Of bpcs-l-request@xxxxxxxxxxxx Sent: Monday, December 06, 2004 1:00 PM To: bpcs-l@xxxxxxxxxxxx Subject: BPCS-L Digest, Vol 2, Issue 236 Send BPCS-L mailing list submissions to bpcs-l@xxxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit http://lists.midrange.com/mailman/listinfo/bpcs-l or, via email, send a message with subject or body 'help' to bpcs-l-request@xxxxxxxxxxxx You can reach the person managing the list at bpcs-l-owner@xxxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of BPCS-L digest..." Today's Topics: 1. INV970 INV973 SYS120 RGZPFM in EOM (Alister Wm Macintyre) 2. RE: INV970 INV973 SYS120 RGZPFM in EOM (Daniel Warthold) ---------------------------------------------------------------------- message: 1 date: Sun, 05 Dec 2004 13:44:24 -0600 from: Alister Wm Macintyre <macwheel99@xxxxxxxxxxx> subject: [BPCS-L] INV970 INV973 SYS120 RGZPFM in EOM I just finished another month's end fiscal. Because we will be doing physical inventory at end of December, I tried to clear out those locations whose inventory and requirements had gone to zero, because each valid ILI record can become a printed physical inventory tag, which I figure we only need on item-warehouse-location combinations active in December. It has been a while since I included this "zero purge" in end-fiscal, because it takes a while to run. I recognize that certain steps are only safe to run at certain points in an end fiscal cycle. 100% of the update jobs were run from the main console with the system in restricted state except for subsystems QBATCH and QSPL going ... I do it this way to prevent any co-worker from signing on while I am in the midst of critical stuff. You see, except for people intimately involved in end-fiscal stuff, most users are freed from needing to comprehend the implications of disobeying "stay off until I tell you that you can get back on." So by doing it this way, they are incapable of such disobedience, so I not have to worry about it. This sandwiched between backup/400 GO SAVE 21 to different backup tapes before and after the whole shebang. Right after INV900 I ran INV970, pausing only to check record counts via DSPFD IWI = 37,436 with none deleted ILI = 62,618 with none deleted that's in IBM file terms before & after, none changed but audit trail says it found 10,218 ILI records to be zero and claimed to delete them ... Oh they have record id LZ not LI so they are coded for BPCS deletion but not actually gone so I ran SYS120 expecting that to remove them, but it did not and I was signed off while SYS120 was running (I was signed on with a user-id that is not part of live environment to check to see when it got done) since I have learned that the reorg skips any files in use when it gets to them Nothing else running concurrent with any of these steps then I looked at INV973 code ... incidentally the program title is misleading ... then ran it that took us to IWI = 27,131 records with 10,305 deleted in IBM terms But we still have 62,618 ILI records with a sizeable volume coded LID = 'LZ' I was getting fatigued ... I had been at this for many hours, partly because we run a lot of end fiscal reports, and partly because I am looking at results at various steps to see if stuff seems Ok ... so I continued on to other steps Later I plan to do SYS120 again to see if it removes any ILI whose related IWI now gone. Then if the ILI record count has not gone down, after another backup I plan a later nite or weekend to do an IBM reorg where I tell RGZPFM to get rid of all ILI where LID is LZ. I almost never touch RGZPFM since I consider it extremely dangerous ... what if I make a keying error? I suspect some of these LZ have been there from past deletion efforts. Is this how it is supposed to work? Am I missing something? We are V5R1 AS/400 mixed mode BPCS 405 CD Rel 2 with mountain of Y2K BMRs. - Al Macintyre http://www.ryze.com/go/Al9Mac Find BPCS Documentation Suppliers http://radio.weblogs.com/0107846/stories/2002/11/08/bpcsDocSources.html ------------------------------ message: 2 date: Mon, 6 Dec 2004 11:08:10 -0500 from: Daniel Warthold <daniel.warthold@xxxxxxxxx> subject: RE: [BPCS-L] INV970 INV973 SYS120 RGZPFM in EOM Hi Al, Me too I noticed the reorg programs do not physically delete ILI or IWI records. I ended up deleting the empty records with some sql statememts, else they will stay there forever. DELETE FROM ILI where LID= 'LZ' or DELETE FROM ILI WHERE LOPB=0 AND LISSU=0 AND LADJU=0 AND LRCT=0 AND LIALOC=0 Then, I delete IWI records with the following sql statement: delete from IWI where WID 'WZ' or delete from iwi where wadj = 0 and wrct = 0 and wiss = 0 and wopb = 0 and wcusa = 0 Because we dont use cycle count functionality, I dont care about the value of ILI.LCYCF. I dont recommend deleting the ILI records, like shown here, if the cycle count functionality is used, else they will lose the records flagged to be cycle counted. I run these any day of the month, but I will catch more records to delete right after month end is done INV903D, which resets the LISSU, LADJU, LRCT fields to zero (same with IWI fields wadj, wrct, wiss). Daniel -----Original Message----- From: Alister Wm Macintyre [mailto:macwheel99@xxxxxxxxxxx] Sent: Sunday, December 05, 2004 14:44 To: BPCS_L discussion Subject: [BPCS-L] INV970 INV973 SYS120 RGZPFM in EOM I just finished another month's end fiscal. Because we will be doing physical inventory at end of December, I tried to clear out those locations whose inventory and requirements had gone to zero, because each valid ILI record can become a printed physical inventory tag, which I figure we only need on item-warehouse-location combinations active in December. It has been a while since I included this "zero purge" in end-fiscal, because it takes a while to run. I recognize that certain steps are only safe to run at certain points in an end fiscal cycle. 100% of the update jobs were run from the main console with the system in restricted state except for subsystems QBATCH and QSPL going ... I do it this way to prevent any co-worker from signing on while I am in the midst of critical stuff. You see, except for people intimately involved in end-fiscal stuff, most users are freed from needing to comprehend the implications of disobeying "stay off until I tell you that you can get back on." So by doing it this way, they are incapable of such disobedience, so I not have to worry about it. This sandwiched between backup/400 GO SAVE 21 to different backup tapes before and after the whole shebang. Right after INV900 I ran INV970, pausing only to check record counts via DSPFD IWI = 37,436 with none deleted ILI = 62,618 with none deleted that's in IBM file terms before & after, none changed but audit trail says it found 10,218 ILI records to be zero and claimed to delete them ... Oh they have record id LZ not LI so they are coded for BPCS deletion but not actually gone so I ran SYS120 expecting that to remove them, but it did not and I was signed off while SYS120 was running (I was signed on with a user-id that is not part of live environment to check to see when it got done) since I have learned that the reorg skips any files in use when it gets to them Nothing else running concurrent with any of these steps then I looked at INV973 code ... incidentally the program title is misleading ... then ran it that took us to IWI = 27,131 records with 10,305 deleted in IBM terms But we still have 62,618 ILI records with a sizeable volume coded LID = 'LZ' I was getting fatigued ... I had been at this for many hours, partly because we run a lot of end fiscal reports, and partly because I am looking at results at various steps to see if stuff seems Ok ... so I continued on to other steps Later I plan to do SYS120 again to see if it removes any ILI whose related IWI now gone. Then if the ILI record count has not gone down, after another backup I plan a later nite or weekend to do an IBM reorg where I tell RGZPFM to get rid of all ILI where LID is LZ. I almost never touch RGZPFM since I consider it extremely dangerous ... what if I make a keying error? I suspect some of these LZ have been there from past deletion efforts. Is this how it is supposed to work? Am I missing something? We are V5R1 AS/400 mixed mode BPCS 405 CD Rel 2 with mountain of Y2K BMRs. - Al Macintyre http://www.ryze.com/go/Al9Mac Find BPCS Documentation Suppliers http://radio.weblogs.com/0107846/stories/2002/11/08/bpcsDocSources.html _______________________________________________ This is the SSA's 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. Delivered-To: daniel.warthold@xxxxxxxxx ------------------------------ _______________________________________________ This is the SSA's BPCS ERP System (BPCS-L) digest 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. End of BPCS-L Digest, Vol 2, Issue 236 ************************************** This is an e-mail from Wabash Technologies, Incorporated. It is confidential to the ordinary user of the above e-mail address. It may contain copyright and/or legally privileged information. No other person may read, print, store, copy, forward, or act in reliance on it or its attachments. If you received this in error, please e-mail to humanresources@xxxxxxxxxxxxxx
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.