× 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.


  • Subject: RE: BPCS 6.02 Conversion
  • From: "George Sagen" <gsagen@xxxxxxxxxxxxxxxxxxx>
  • Date: Mon, 5 Apr 1999 15:33:35 -0700
  • Importance: Normal

Here at Barton these folks wrote import programs to migrate legacy data into
BPCS. They had several audit reports which ran after the imports which
compared # of records imported and did all sorts of grouping and
subtotaling. The audit reports were absolutely essential to assure that all
data came across. The biggest issues we had were in auditing the referential
integrity between individual fields and the master tables from which they
are normally populated. Most of the issues were rapidly exposed, however,
during CRP and by doing spot checks.

A good example is that tax rate codes were in the tax code master and the
proper tax codes were inserted into the item, commodity, and vendor masters.
These all cleared the audit report integrity checks. However, when entering
a PO we found that the tax rate tables which show valid combinations of
Vendor and Item tax codes had not been populated. This was immediately
exposed the first time we wrote a PO for expense items during CRP.

It's extremely difficult to anticipate each and every integrity check to
make, but it is the duty of the programmers to do as much as possible and
not rely on end users to discover everything manually. Still, it is
necessary to do manual testing prior to going live. The programmers should
not do the manual testing since they would be checking their own work.

If it helps to know, these guys imported:
Item Masters
BOM's
Work Centers
Routings
Customers
Vendors
Open PO's
Open Sales Orders
Open AR
Cost Master

We had a little clean up to do, but the imports mostly worked well.


George Sagen
gsagen@primesourcetech.com <mailto:gsagen@primesourcetech.com>
PrimeSource Technologies
7373 East Doubletree Ranch Road
Suite 150
Scottsdale, AZ 85258
(801)360-6360 Direct & VM
 


|-----Original Message-----
|From: uucp@Uucp1.mcs.net [mailto:uucp@Uucp1.mcs.net]On Behalf Of Bailey,
|Dick
|Sent: Monday, April 05, 1999 10:31 AM
|To: 'BPCS-L@midrange.com'
|Subject: BPCS 6.02 Conversion
|
|
|
|
|       We are now (finally) about to go live with BPCS 6.02.  Many of our
|files are being converted mechanically (Customer Master, Vendor
|Master, Open
|Customer Orders, Purchase Orders, etc.). We're converting from customized
|MAPICS and JDEdwards.
|
|       Part of the advice we have received consistently from every SSA
|Consultant we've seen is to "Step-Through" all the files mechanically
|converted, so that we can be sure the fields that BPCS populates in its
|normal operations are populated. This seems pretty extreme - and will take
|lots of time - especially the open orders.
|
|       Those of you who have converted - what did you do? And what do you
|recommend?
|
|       Dick Bailey
|+---
|| 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
|+---
|



+---
| 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
+---


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.