|
I agree in principle. However, some caveats.* There are some people who are not fond of having all zeros for some important numbers like Invoice # for example, and in all sorts of reports where leading zeros suppressed, the number all zeros might show up as blank and confuse people. * If the number range offered by BPCS is far beyond what your company really needs, consider the advantages of using 1-9,999 when it comes to applications with lots of data entry, such as access to shop orders. But you need to avoid returning to some # range while there is still history out there from the last time those #s were used. BPCS not handle that well. * In some cases the high #s are kind of invisible to the mass of users. So for example, we have blanket customer orders where we constantly adding new order lines, and finishing old order lines. There might only be a score or so lines active at any one time on an order, but over time, there might be an aggregate of 800 lines there, and it might be nice if people knew before we hit the 999 ceiling that we were getting close.
Hello, I think that the counters are no need to manually maintenance. Once the countere reach 9999999999, it will auto reset to 0. This is because of the counter field's length limitted. Example: Order Number Counters fields length are 6 digits, when the order counter reached 999999, if the order number +1, the number will become 1000000. Due to 6 digits, the system will auto cut off extra digit, therefore the counter will become 0. Hope you will understand what I explained. >From :Tay -- This is the SSA's BPCS ERP System (BPCS-L) mailing list To post a message email: BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/bpcs-l or email: BPCS-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/bpcs-l. Delivered-To: macwheel99@xxxxxxxxxxx
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.