× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



We have multiple scenarios of glitches in need of clean up.
For example, inventory on a dead facility.

I found out about the dead PO records last week, and thought it might be a
simple solution, but ask BPCS-L in case I had overlooked some scenario,
since this is a topic I seldom explore, and BPCS documentation is
incomplete, not in any one consistent location, and often as clear as mud.

We do not have ASN in our system.

We do have ESN which can have notes for PO CO and more ... there are seven
different types ... I had previously discovered what I thought were notes on
long dead orders, so that was on my list of glitches to deal with.
MPN has notes for engineering, items routings etc. also appears to contain
some obsolete content.

We have experienced a problem, similar to what Dick said, with reusing SO
numbers when there is still labor history on the former use of those SO
numbers. When you do inquiry into the new use of them, you see activity on
the former use of same orders.

There is an opposite side to this issue, if we do vigorous purging of
history. Final purge of shop orders needs access to ALL history on those
same orders ... inventory, labor. Vanilla BPCS purge of history apparently
does not hang onto history which may still be needed for any orders kept
open extra long time for whatever reason.

Some 405CD problems may be fixed in later versions of BPCS.
-
Al Mac


-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] 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: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] 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-

- Allowing one's computer to be unprotected, while connected to the
internet, can be compared to owning a handgun and putting it out on your
doorstep every night, in case a passing robber might be in need of one.
Unfortunately millions of people are doing exactly that, while thousands of
them do so through networks of companies and government agencies that they
manage.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.