× 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 4.03 and BIL600
  • From: MikeB60046 <MikeB60046@xxxxxxx>
  • Date: Wed, 13 May 1998 20:33:09 EDT

the post ship billing sequence (like the BIL500 series uses data areas and
busy flags to control the process.  when the process is interrupted, it leaves
files in an unsynchronized manner.  Your problem sounds like it occurred in
the BIL620 series of programs.  However, based upon your message I am not sure
if you are talking about one instance or a combination of them which left the
files in different stages of update.  

The way to most easily fix this is to identify the files which have been
updated and the ones not yet updated, similar to what you have described.
Don't forget the GJW.
Then determine if a different order type will provide you with the appropriate
update of the remaining files. (i.e. do not update inventory, do not update
A/R etc.) If you can find one satisfying this, then re-enter the orders again
using that order type and reprocess them.  You may have a problem relating
order numbers to invoice numbers.

Don't forget to get rid of the old records in ECL (workstation member) and BBL
(workstation member and BBL member.
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@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 ...


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.