Dear Don, <vendor>
Flashing red lights on the STRSQL idea !!!
That would cause an avalanche of problems. Some insight:

STRSQL would not perform any type of referential integrity check
of other BPCS files when removing/inactivating old IIM records. All
the necessary files (over 20) would have to be addressed
individually. The potential for misses using this manual approach
is extremely high.

Also if you're using STRSQL, you must know when to use an UPDATE
and inactivate the record, and when to use a DELETE so as to
physically remove the record from the BPCS database. BPCS handles
deletes differently for different files.

One of the reasons the BPCS approach to deactivate items (INV100) causes
such enormous frustration is because it enforces a painstaking digging project
to remove all instances of the item according to BPCS rules. Every user we've
ever talked with has told us that INV100 is so complicated they just give up
and put a "DANGER - DON'T USE" message in the item description.

We've invented a product that puts obsolete items to rest with much less
digging. It's called Item Undertaker. Here's the link:

One Item Undertaker user took out well over 30,000 items from a defunct
category of their business during a single weekend.

The software even nominates items that merit a deactivation analysis;
you can obtain that intellectual property from the free demo.

Warm regards,
Milt Habeck
Unbeaten Path International

(888) 874-8008
+(262) 261-3151

From: Bill
To: bpcs-l@xxxxxxxxxxxx
Sent: Thursday, June 11, 2009 4:35 PM
Subject: Re: [BPCS-L] Taking out old part numbers

Don Cavaiani wrote:
> Any warnings/caveats regarding use of strsql to delete very old
part numbers out of the database -e.g., IIM/CIC/HPO/MBM/ITH/

Don, the warnings might be different depending upon which release the
data resides. I'll assume that you've done a full interrogation of the
database looking for every file that stores a part number field.

Warnings off the top of my head:

1) Complete data analysis (usually it's sales) can no longer be
performed on historical data due to missing information.
2) Some times people don't investigate fully the chain reaction impact
of deleting a part number that resides in the BCHLD field in MBM.

What we did when we split data out when a portion of the business became
it's own entity, we set the record id codes to their current values but
in lower case. Then we let the data sit for a number of months, and
then we started deleting.


This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by 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].