Re: ORD get rid of selectively

[Kevin_Catlin@xxxxxxxxxxxx]

     We created an online utility based on the vanilla order purge that 
     would blow away order and all related records (including load).
     
     Kevin_Catlin@gm.cytec.com


______________________________ Reply Separator _________________________________
Subject: ORD get rid of selectively
Author:  BPCS-L@midrange.com at Internet
Date:    3/9/99 12:56 AM


Can we zap customer order history selectively, such as by a combination of 
item customer facility, or on a specific order?
     
Example 61805 was entered in error & is no longer valid on ORD500 or RMA 
maintenance, and has no apparent effect on MRP, but it shows up on ORD300 as a 
negative requirement & the sales dept is worried that it might adversely affect 
the next order for the part.  We currently retain history 365 days & we want to 
keep history on valid orders on active parts.
     
When we are no longer making some part for some customer from some facility, 
we might want to selectively purge just the history on what we won't be making 
again.
     
Similarly when there has been human error by production, shipping, billing, 
RMA, QC, MIS ... it doesn't matter ... no one wants audit trail of garbage, in 
the inquiry areas used every day by many end users, they just want to zap it 
out without messing up whatever the related files might be.  I suspect the 
auditors might have another opinion on the idea of erasing audit trails.
     
Ideally I would want menu option(s) - user keys in combination of what is to 
be removed, with an "Are you sure" El Typo Insurance.
     
Al Macintyre
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com. 
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. 
| Questions should be directed to the list owner: dasmussen@aol.com
+---
Received: from st.cytec.com (164.84.1.253) by stnt01.cytec.com with SMTP
  (IMA Internet Exchange 2.12 Enterprise) id 00103703; Tue, 9 Mar 99 02:06:18
-0500
Received: from gw.cytec.com (igw.cytec.com) by st.cytec.com (4.1/SMI-4.1)
        id AA28988; Tue, 9 Mar 99 02:07:38 EST
Received: by gw.cytec.com; id VAA00148; Mon, 8 Mar 1999 21:01:02 -0500
Received: from kitten.mcs.com(192.160.127.90) by gw.cytec.com via smap (3.2)
        id xma000142; Mon, 8 Mar 99 21:00:36 -0500
Received: from uucphost.mcs.net (Uucp1.mcs.net [192.160.127.93]) by
Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id BAA12076; Tue, 9 Mar 1999 01:04:41
-0600 (CST)
Received: (from uucp@localhost)
        by uucphost.mcs.net (8.8.8/8.8.8) id BAA07655;
        Tue, 9 Mar 1999 01:04:41 -0600 (CST)
Received: (from majordom@localhost)
        by midrange.com (8.9.1/8.9.1) id AAA14585
        for bpcs-l-outgoing; Tue, 9 Mar 1999 00:45:31 -0600
Received: (from uucp@localhost)
        by midrange.com (8.9.1/8.9.1) with UUCP id AAA14542
        for BPCS-L@midrange.com; Tue, 9 Mar 1999 00:30:12 -0600
From: MacWheel99@aol.com
Received: from imo25.mx.aol.com (imo25.mx.aol.com [198.81.17.69])
        by uucphost.mcs.net (8.8.8/8.8.8) with ESMTP id AAA06215
        for <BPCS-L@midrange.com>; Tue, 9 Mar 1999 00:02:07 -0600 (CST)
Received: from MacWheel99@aol.com
        by imo25.mx.aol.com (IMOv19.3) id iWKNa19622
         for <BPCS-L@midrange.com>; Tue, 9 Mar 1999 00:56:52 -0500 (EST)
Message-Id: <9f89832d.36e4b824@aol.com>
Date: Tue, 9 Mar 1999 00:56:52 EST
To: BPCS Users Mailing List <BPCS-L@midrange.com>
Mime-Version: 1.0
Subject: ORD get rid of selectively
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 3.0 16-bit for Windows sub 38
Sender: owner-bpcs-l@midrange.com
Precedence: bulk
Reply-To: BPCS-L@midrange.com
X-List-Name: BPCS Users Mailing List (BPCS-L@midrange.com)