|
We wrote programs and run them each night to clear the ECH/inuse and to also reset bbh/date fields BINVD to be 8 digits. Also deletes PDW records . We've have had some problems in fields (BHDOCN BHWSID BLWSID) not clearing but only after a botched billing. We only clear said fields after a botched billing (power outage, accidentally cancelled, etc.) We customized the load portion generation so we really didn't have problems with load records after startup. We did fix the situations that caused them in pick confirm..... We also experienced billing not running for all records ready to invoice because of orphan bbh or bbl records. I forgot which situation (orphan bbl or orphan bbh) that cause invoicing not to run...... Anyway we will report and delete orphans nightly programmatically. It does not happen often but raises *cane when it does happen. -----Original Message----- From: cmassoglia@voyager.net [mailto:cmassoglia@voyager.net] Sent: Saturday, January 27, 2001 7:52 PM To: BPCS-L@midrange.com Cc: vaneeb@gte.net Subject: Hung Invoices We have a number of invoices which appear to be hung. From looking in the BPCS Midrange-L digest, we found the following: Check all the following fields, if you have plenty of orders that do not show up for billing then the cause could be in a load shared for all these orders. Check also the loads for the orders. ECH record: HINUSE field should be blank. BBH record: 1) BHID field (Record ID) should be in BH status. 2) BHDOCN field(Document Number) should be blank. 3) BHWSID (Workstation ID) should be blank. BBL record. 1) BLID (Record Status) should be BL. 2) BSTAT field (Invoice Status) should be blank. 3) BLLOAD (Load Number) should be the correct load number that the order is currently attached to. 5) BLSTS3 (Ready for Ship Confirm)field should have a value of 0. 6) The BLSTS4 (Ready for Invoicing) field should have a value of 1. 7) (Workstation ID) field should be blank. LLM Record : LMSTAT (Load Status) should have a value of 3. LLH Record : LHSTAT (Load Status) should have a value of 3. LLX Record: LXSTAT (Load Staus) should have a value of 3. Is there a way we can just write a program to fix records using logic as shown above or should we only attempt to fix the invoices records we know are hung? Also, is there a report we can run to provide us a list of the invoices which appear to be hung? Thanks in advance. +--- | 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 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.