This is a summary of what has been added so far for 2002 (collectively will be referred to as version 5.12d):
5.12d release #1 summary - released 4/2/02 (1st quarter 2002):
(release #1 is available at no charge for users who have purchased updates thru 2001, i.e. 5.12c, and who obtain the update via the web or via E-mail; for users who would rather receive a CD containing these updates, the cost is $10.00)
Supplier part code look-up - this has been added to IC-A.(January 2002)
Units refresh in IC-A - when selecting an item from the look-up list, the units initially showing on the screen could reflect inaccurate values until the user pressed ENTER to proceed past the product code field (February 2002)
ALT-I - pressing ALT-I a second time while already having pressed ALT-I created GPF's and was a previously known issue but had not previously been fully resolved (March 2002)
Expiring sales order report - a new option under "Print reports" in the recurring sales order entry program (SO-I) provides the ability to report on expiring or expired recurring sales orders; parameter error that came up after selecting a report and coming back to the SO-I screen fixed. (January 2002)
EOM terms - in programs AP-B, AR-B and SO-F the calculated due date in the event of an "E" calc how in the terms set-up would result in the DOS mode of an incorrect default due date and in the Windows mode, the program would quit. (February 2002)
Purchase order line items - when entering the 250 maximum, a user could then not receive that PO under the PO receive program. (February 2002); internal screen issues and "how paid" validation in the receive PO program updated (February 2002)
Print open S/O list - issues relating notes attached to message lines: (1) when sorting by product code, a note attached to a message line would show up with the first portion of the note as the being the product code (fixed); (2) when sorting by customer code, a "file not opened" message could be received because the BKSONOTE file was not being opened; also an internal line number relating to the appropriate message line was not being referenced so that the note would not display correctly (all fixed). Comment: the open S/O list does NOT currently print notes attached to product codes even when the "print detail" option is selected. Only message lines or notes attached to message lines currently are printed and only when sorting by customer. (February 2002)
Addsum utilities - the synchronization utilities has been changed to offer the ability to automatically delete any and all stranded sales order and purchase order line items (and without regard to product code which is important in connection with potentially stranded message lines or notes attached to messages lines); several internal improvements (February 2002); new utility in the Inventory utilities section allowing a user to merge one inventory code into another (March 2002); the balance GL to inventory utility updated to reflect 5.12c changes and updated to be able to select GL account-dept combinations rather than just GL accounts. (March 2002)
File reindex - this program would sometimes not allow a user to reindex a file because of a lack of disk space even though the user may have ample available disk space - user can now override and proceed to reindex (February 2002)
Inventory availability (IC-D) - re-synch to location units when doing reorder level, etc. comparison (March 2002).
Receiving PO's when automatically expensing inventory via JC: In the job cost configuration, there is an option for "automatically expensing inventory" which was disabled in early 1997 due to some problems that some users were having when using that option. That option has been re-enabled. So when answering "Y" to the question "Automatically expense inventory items (to COGS) when received?" (see screen clip below), the program will expense type "R" items and will accordingly not update inventory units (nor average cost). When answering "N" (and previously regardless of what the answer was), the purchase order receipt program will post to the inventory asset associated with the item's location and update units and average cost.
5.12d release #2 summary - (released July 2002 as a cumulative update with changes in #1):
Weights: In inventory option A, there is now an entry field for WEIGHT which can be optionally used to input and item's weight. (This can then potentially be used in the SO module to calculate the weight of an order and more importantly in the PO module to be potentially used to allocate freight/tax thru via a new/yet to be added PO receipts/transaction file.)
940 report: several new features, was locking history files (fixed), provide ability to report on prior year and regardless of whether payrolls had been processed since the 1st of the year (gives user the ability to literally do a 940 for any past year and include even terminated employees), accumulate SUTA amounts to provide a default number for SUTA paid, fix screen reference
941 report: somewhat like the 940 report program, allow the user to run the report for a prior year, especially important when running a 4th quarter/prior report after that W-2's have been run and employees terminated, numerous internal changes
Purchase order receipts: when making invoice price changes, items could appear that had previously been received in full or which had not been received at all.
Payroll history report: enhanced to allow for a from/thru division range.
Quotes transfer: previously this program was not allowing a note attached to a message line to be transferred.
Sales order entry: maximum possible is actually 249 rather than 250, added internal support in the event limit is reached; inventoriable items could be added to a sales order without a location.
Purchase order entry: maximum possible is actually 249 rather than 250, added internal support in the event limit is reached; inventoriable items could be added to a sales order without a location; duplicate purchase orders number could be created under certain situations.
Receiving PO's when automatically expensing inventory via JC: related to re-enabling this in the earlier release, when using type "N" (non-inventoriable) items, postings were going to the clearing account; "received quantities" were also not being updated when the JC expense flag was enabled. Unrelated to JC, type "N" items could be creating harmless but unnecessary inventory location (BKICLOC) records.
5.12d release #3 summary - (released August 2002 as a cumulative update with changes in #1 and #2):
Clear data (BKCLRDAT): was not working when clearing data, support for other files that were not previously being cleared or deleted added (August 2002)
Detail trial balance (GL-E): balance forward handling with respect to income/expense accounts significantly enhanced, prior fiscal year end closing amounts shown in current retained earnings account when running a detailed trial balance and the balance forward amounts only include appropriate year to date balances for income/expense accounts to resolve the illusion that previously existed (that income/expense accounts were not getting cleared) and to help preventing users from trying to adjust their GL transaction file in any way (August 2002)
File reindex - the newer reindex program was requiring that the user input the file name and company code twice because of some internal issues; program enhanced to be able to make a back-up copy of the file being reindexed (August 2002)
Inventory maintenance (IC-A) - in the event a non-inventoriable item for some reason had some unit on hand or other value, add some logic to the synchronization routine to zero out any and all unit values (other programs in the system that have inventory look-ups won't reflect this change until they are re-compiled); when deleting an inventory item, add additional checking to make sure that the item (regardless of "type") isn't on a pending sales order, purchase order or bill of material before even allowing it the ability to be deleted. (August 2002)
Main menu program - the set date/time option has been disabled (because users should not be selecting that and nothing in Advanced Accounting requires it) and the program changed internally to call the new file reindex program (August 2002)
Reclose prior years (SY-L) - make the "roll" beginning balance question relating to the GL transaction file a "toggle" option so that the user never has to make the decision whether to actually do this and therefore help eliminate the chance that a user accidentally clears their GL transaction file - somewhat also related to the GL-E change (August 2002)
AR aging (AR-F) - when doing an A/R aging and choosing customer totals only, program was not performing as quickly as the detail/open items only and could also provide different totals (related not to software integrity but past user data integrity issues) (August 2002)
Build/unbuild process (BM-F) - users historically have been confused between the "number of sets" and "units built" and for the vast majority of users, these numbers should be the same, so in this program as now changed, the user has to press F5 to enter the units built which are otherwise set equal to the number of sets; further checking added so that if the number of sets and the units built are not the same, the user is asked whether that is really what is desired; also the F3/display build history has been enhanced to provided a larger display and more information including the location and the number of sets and units built. (August 2002)
Run POS register (POS-A) - when using the change salesperson function key (F9), a user could enter the newly desired salesperson but instead of entering the password, press ESCape and the program would change to the newly entered salesperson code (resolved); when doing an old sale (F7) or reprint (F8) program was allowing the user to bring up voided transactions (June/August 2002)
5.12d release #4 summary (includes changes in #1 , #2 and #3):
Inventory maintenance (IC-A) - turn off the F5/F6/F7/F8/F9 keys (better ways to search include using ALT-I and F2 in the product code field - these provide more options and will never unnecessarily lock a record).
Enter/change voucher (AP-B) - if the mouse is turned on (see Set Configuration), users could bypass vendor code, voucher number and invoice date; added additional validation to prevent this from occurring. This was not an issue in the Windows mode, only the DOS mode. NOTE: we generally recommend that DOS users turn off the mouse under Set Configuration.
AR record payments (AR-C) - improve program flow concerning regarding the initial payment description including any backout reason.
Run POS register (POS-A) - F7/reverse could create a zero numbered invoice.
Print bill of material (BM-B) - if an item had no units on hand of any kind, average cost would show as zero on this report, even though average cost values were available in the system - change to look for average cost values in the inventory location file in the event the computed average cost is zero.
Purchase order receipts (PO-D): the overall "last cost" of an item was not being updated (even though the location's average cost was) creating a problem in that (a) the last cost reference of the CTRL-K option in IC-A would not show the last overall cost and (b) when entering a purchase order for relating to a vendor/item that did not have a catalog cost, the program then would not be able to bring in the overall last cost.
AP check printing (AP-F): when the system was printing a "voided" check (whether dot matrix or laser), the city/state/zip relating to the prior vendor's address in a check run would be printed rather than the actual vendor's city/state/zip.
Generate recurring G/J trans (GL-N): was allowing "out of balance" entries saved in GL-M to be posted.
BM-F and PO-D: Inventory movements dollar amounts could be inaccuratey stated by not taking into account previously posted amounts (e.g. price changes in PO-D).
No updates made at 11/25/02 - no year end/payroll 2002 update required. See 2003 payroll changes however for payrolls starting on January 1, 2003.
Users should make changes under system maintenance option M (SY-M) add/chg/del related fields as follows:
CUSTOMER CODE: add BKAR.CHKH.CODE, instances "M" to the end of this list
PRODUCT CODE: add BKIC.TRN.PCODE, instances "M" and BKIC.VND.PCODE, instances "M" to the end of this list
IMPORTANT: this should be done in each "company" that you actively use.
New program BKSOIEXP is called from BKSOI
New key added to BKICVEND
Weights are being saved in the BKICMSTR field, BKIC.PROD.TO.