cleaning up data orphans in purchasing and elsewhere --- BPCS + ERP LX

<vendor>



Good morning ...

The way to fix that is to use the HPH file as a starting point and then
compare data in all the dependent files to HPH. If there is no match, then
archive the dependent file record(s). Locksmith software does that. It works
equally well in the other principle business processes.
(www.unbeatenpath.com/software/locksmith/archiving.pdf )

It's conceivable that the problems that Al and Dick cite were caused because
at some prior time, an analyst decided to purge HPH records without knowing
all the places to look for dependent data. Locksmith archiving software
arrives with all of those data dependencies pre-configured. In the case of
customer orders, I believe at least 13 dependent files are involved. So, it's
no small trick to avoid a case of BPCS/ERP LX data orphans when you purge.

Warm regards,
Milt Habeck
Unbeaten Path
(888) 874-8008
+262-681-3151


</vendor>





From: On Behalf Of Bailey, Dick
Sent: Tuesday, September 06, 2011 8:41 AM
To: BPCS ERP System
Subject: Re: [BPCS-L] 405CD HPO HPH

Al - How about PO Notes, file ASN? We deleted some old PO history at one
point and when we reused PO numbers, the original notes were attached to
them. Made for considerable confusion. Had to delete the notes too.

Sounds a bit similar.

Dick Bailey
MCFA, Inc.



-----Original Message-----
From: On Behalf Of Al
Sent: Tuesday, September 06, 2011 2:11 AM
To: 'BPCS ERP System'
Subject: [BPCS-L] 405CD HPO HPH

I have found suspected file corruption & want to confirm my understanding
before deleting what is not wanted.

One problem found are records in HPO for order #s, for which there is no
corresponding HPH summary record.

HPO is supposed to contain detail lines of PO or Requisitions, and a unique
line #, which ties into count of line #s in HPH, so if we were to delete HPO
lines, we would need to revise corresponding HPH count of lines. There's not
supposed to be anything else in HPO than PO lines and Requisition lines.

HPH is supposed to have one header summary record per valid PO or
Requisition. So there would be no harm to BPCS by removing any HPO records
which do not have a corresponding HPH header for the same PO?

If we manually removed HPO records, outside of BPCS programs, there would be
no need to run any reorganization programs to get other files totals in sync
with remaining HPH HPO records? The normal MRP, end fiscal, would straighten
everything out?

-Al Mac-