Re: BPCS 6.02 Labor Ticket Purge Question. -- BPCS-L

In 405 CD the Transaction History Parameter applies ONLY to ITH on active IIM, not to FLT labor history tickets, and only works if your end-month routine includes INV900 with the appropriate settings. If you delete an item, its history no longer gets purged, because INV900 process includes access to IIM and if the access is not an active item, then the corresponding ITH is not purged. Thus years later, if you re-use the item for some unrelated part, it starts its life, for first month with contamination by history from the earlier usage.

I did not dig into SFC905 logic as heavily as I did into INV900.
Those labor tickets you are finding in FLT that predate the purge cut-off.
You might check whether they are on valid master file records.

A great deal of BPCS only works if a record has valid current item, employee clock # etc. A terminated employee, clock # removed from CEM, means that many programs that process FLT and access CEM, suddenly cease to be included in the totals because they are related to some master record that is not there any more. This is Ok if you only want to see totals on employees still on the payroll. This is not Ok if you want to see totals on all work done on all items in your factories over some date range. You have to think through optimal sequence of purging files that have inter-related records. Under our policies, we code terminated employees in such a way as to not sabotage labor reports for current month activity, and do not actually remove them from CEM file until after everyone had opportunity to get at relevant records, plus people who want to run multi-month reports advised not to do so with employee name identified. With turn over of people who run labor reports, these nuances tend to get forgotten.

FLT labor transactions need to be purged, in vanilla 405CD by SFC905 which also has some flaws ... we wrote our own purge. Let's suppose you decide to keep labor transactions for 6 months, and let's suppose some shop order that is now past due a short time, has been open more than 6 months, but had its due date advanced forwards, as partial production done. SFC905 is not "smart enough" to recognize that some transactions before the purge date are needed for some open shop order ... INV900 same flaw. You purge those transactions and that shop order cannot be purged, because at purge time it needs access to the transactions you got rid of because they so old. The transaction purge needs to be able to exclude history on still active orders, to minimize hassle for order purge.

When we were doing history purge to tape archives, we wanted to be able to extract stuff from those archives on occasion. The vanilla naming conventions makes that darn near impossible. INV900 was easier to modify than SFC905 to use a naming convention that said what it was that was being archived (file prefix) and vintage (file suffix).

, you wrote:

In the Transaction History System Parameters option on the SYS menu we have the Labor Ticket days set to 366. The issue we have is that we have Labor Tickets dating back to 1997. The value of 366 days has been there for at least 1 year. Does anyone have any thoughts of why they are not purging out? Thanks in advance. Kevin W.

- Al Macintyre http://www.ryze.com/go/Al9Mac Find BPCS Documentation Suppliers http://radio.weblogs.com/0107846/stories/2002/11/08/bpcsDocSources.html BPCS/400 Computer Janitor at http://www.globalwiretechnologies.com/