to purge or not to purge /// BPCS Labor Tickets

Good morning,

Locksmith for BPCS software will archive all of the data
in your production files (including Labor Tickets). To avoid 
orphaned data, the archive process carefully sustains all of 
the BPCS file relationships. Here's more information: 

http://www.unbeatenpathintl.com/locksmith_bpcs.htm

If the vanilla BPCS Labor Ticket purge functionality is used,
there will be unfavorable consequences:

   First: data related to Labor Tickets in other production files
   will not be removed.

   Second: Traceability for production timings, costings, etc.
   will be forfeited.

   Third: a purge physically deletes data from files; the 
   information is permanently destroyed.

   And more: take a look at Al Macintrye's response.

Locksmith software improves response time without destroying
data. The archived information can be accessed at any future time
as if the data had never been removed from your production files.

Please consider calling us; we take the tarnish off BPCS:
http://www.unbeatenpathintl.com/Tarnish_off_BPCS.pdf

Warm regards and peace to you,

Milt Habeck
Unbeaten Path International

Toll free North America:  (888) 874-8008
International voice: (262) 681-3151
mhabeck@xxxxxxxxxx
www.unbeatenpathintl.com




++++++++    +++++++    +++++++    +++++++    +++++++

From: Alister Wm Macintyre
Sent: Monday, January 26, 2004 2:05 PM
Subject: Re: BPCS 6.02 Labor Ticket Purge Question.

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.

[ .... ]

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.

[ .... ]




++++++++    +++++++    +++++++    +++++++    +++++++

----- Original Message ----- 
From: WASHBURNCCINC@xxxxxxx
To: bpcs-l@xxxxxxxxxxxx
Sent: Monday, January 26, 2004 10:05 AM
Subject: BPCS 6.02 Labor Ticket Purge Question.

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.