× 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: CEA -- ACP500 model setup approach
  • From: MAndreen1@xxxxxxx
  • Date: Sun, 16 Jul 2000 09:53:00 EDT

Good morning,

    CEA is indeed very flexible. Some companies when implementing CEA have
their A/P personnel separate invoices between into two batches (with Purchase 
Orders and without Purchase Orders) on a daily basis before entry into ACP500.
This reduces concern over multiple reason code utilization driving to 
corresponding
events / models. However, depending on the A/P personnel's level of comfort, 
a single reason code (single event / single model) could suffice, thereby, 
eliminating any concerns over multiple reason codes and invoice batch 
separation. If your A/P personnel is indeed very comfortable, then a macro 
event could also drive to a model specifically tailored to a particular 
vendor (telephone and electric bills tend to be prime examples) or default to 
your single standard model for both invoices with POs and invoices without 
POs.

            have  a  good  day                                     Curt 
+---
| 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 ...


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.