For 6.x you could use a sales history correction order type and then
this will NOT feed A/R but will keep sales history up to date. This
would get you out of deleting A/R.
In terms of deleting, 6.x does not have referential integrity for
anything we use. Seems like A/R is a deadend file. All of our reporting
comes from sales history.
Bottom line: I would not be uncomfortable with this solution - If I was
made to do it. If you have input, keep A/R on BPCS and buy a bolt on for
A/R. There are a ton of good ones and it "revitalizes" the BPCS A/R
system to the point where the users are convinced they have a shiny new
Behalf Of Al Mac Wheel
Sent: Sunday, August 10, 2008 10:04 AM
To: BPCS ERP Discussion List
Subject: [BPCS-L] RAR Downstream
We're 405 CD on V5R1 long gone off OSG.
We have BPCS tech support, but management not authorize call them unless
emergency. Instead I get string of challenges to figure out.
Latest: A/R to be handled by another system outside of BPCS to get its
from BPCS billing process, such as A/R invoice register, then invoice
to RAR file, after cut-off date, to be deleted. Invoices prior to
date to be processed old way. SIL invoice file remain intact, since it
used in massive followup to support customer service inquiry, and price
I can write program to mass delete RAR on invoices after cut-off date.
concern is unintended consequences downstream, so that I can have
alternative arrangements in place before they needed, instead of
time discovering mountains of problems. Other than invoices awaiting
customer payments, and where we apply credit debit memos, where else
BPCS use RAR file data? I don't use XRF because in 405 CD its security
For example, do ACR230 customer ranking and SAL300 sales history get
from RCM customer master, which in turn from summarization of RAR?
in shipping billing cycle are SSH SSD history totals populated with
I desire to know what else will be zapped due to RAR mass deletions,
because it relies on RAR content, so we can evaluate which of that we
live without, and which needs some replacement system.
Never Knowing enough about BPCS
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.