BusinessVision Management Systems Inc. (c) 1994.
Product:      BusinessVision DELTA
Revision No.: 2.0
Release date: August 1994


Revisions & Corrections in version 2.0

ADDITIONS:


 A new order type - Layaway - has been added to the Order Entry
  capabilities.  This new feature offers many new options including;

    * The ability to accept up to 100 deposits/payments

    * Reports for tracking Layaway orders

    * Receipt printing and auditing capabilities

    * New accounting, including a new account for Layaway deposits
       (all Layaway accounting can be managed through AutoPost)

    * An export capability of the "Layaway" file

      Note: An addendum for your DELTA manual is included - please
            insert these pages in your manual today.

 The ability to "Consolidate" numerous General Ledger transactions that were
  posted (automatically), as a result of the assembly/manufacture of many
  items that have Bills of Material.  This allows a large number of
  transactions (created and posted while building Inventory items that often
  contain component parts that have different Asset {inventory-on-hand}
  classifications), to be consolidated into a single Journal Entry for a
  given month.

 An employee count has been added to the Employee Detail report and
  Timecard Journal.  The Detail report shows the number of employees
  active in payroll, and the Timecard Journal shows the number of
  employees paid within a specified range of dates.

 All Sales Analysis Summary reports now display the General Ledger
  transaction number immediately below the invoice number.  This is
  useful when reconciling Sales Analysis information with the Journal
  Entry created at the time of invoicing.

                                   -2-

CORRECTIONS & REVISIONS:


UTILITIES:

* The "Terms" and "Ship via" codes now export as a two character field
  when exporting fixed length ASCII records.  Terms and Ship via are
  also imported as two character fields.

  Note: A replacement appendix page documents this change (insert this
        in the export layouts appendix for the Customer file).

* When the invoice back-order quantity field was specified to not print
  (in the Report Formats function), and an item was sold with a "0" unit
  price, the back-order quantity was printing where the unit price would
  normally print.  The unit price now remains blank and the back-order
  amount is not printed, as specified in the Report format.


ORDER ENTRY:

* Orders which have items that are committed cannot be changed to
  Quote status.

* When assigning your own invoice numbers, pressing Escape when asked
  for the invoice number consumed a transaction number.  Transaction
  numbers are no longer consumed when an invoice is aborted by escaping.

* Quotes processed through the Invoice & Sale function (box 4 in O/E),
  were causing a 153 status code.  This has been corrected.

* When orders where modified for a second time, and the F7 key was pressed
  to bypass the Order Header, the Julian date (a representation of the
  invoice date in yyddd format), and the posting date for an item could
  differ.  This caused difficulties with the collating sequence of data held
  on file.  This has been corrected.

* Orders processed through Invoice and Sale (O/E function 4), printed
  with the proper set-up format, but printed on the printer designated
  for invoices.  They now print on the printer designated for Point-of-Sale.

* When printing Packing Slips in batch mode, Location codes were not always
  appearing.  Location codes now print where specified, both when printed
  at time of invoicing, and when printed in batches.

* When an invalid date was entered on an order, the system would accept
  the invalid date if forced through a second validation.  Now a valid
  date must be entered or you may not proceed.
                                   -3-

SUPPLIER & CUSTOMER:

* The Customer and Supplier Detail listings did not always print the postal
  code (when address line three was greater than 20 characters).  This has
  been resolved.

* Average Cost was being printed in the Current Cost field on the Re-order
  by Vendor report.  This has been resolved.


ACCOUNTS PAYABLE:

* When several users printed checks at the same time, check numbers were
  generated correctly, however the number shown in the G/L memo field
  would sometimes be cross-allocated if the users actually printed/posted
  their checks in a different sequence (in time), to the sequence in which
  the check numbers were consumed.  This caused difficulty during the
  reconciliation process.  This has been corrected.

* When exporting A/R and A/P records, the terms code was exporting as
  "nulls".  This caused some text editors and other applications to
  truncate information following the terms code in the export file.


PURCHASE ORDER:

* When utilizing Multi-warehouse inventory, and printing an On-order by
  Item report, there was no facility to select "ALL" warehouses.  Pressing
  the Enter key selected only warehouse "00".  The F2 key may now be used
  (as it exists in other inventory report functions), during the selection
  of Warehouses.

* An undocumented feature allowed you to receive multiple P.O.'s by
  pressing the F2 key to move into the header area on the P.O. receipt
  and type in another P.O. number.  This action caused P.O.'s to be merged.
  Multiple P.O. receipts can now only be processed by exiting to the menu
  between Purchase Orders, and selecting subsequent P.O.'s properly.

* When receiving P.O.'s with negative quantities, the On-order quantity
  (held on the Inventory file), would not drop below zero.  This could
  cause difficulties when receiving (entering) P.O.'s with negative
  quantities before receiving corrective P.O.'s with positive quantities.
  P.O.'s created with negative quantities will now allow the On-order
  quantity to drop below zero.

* When taxes were set to compound, (as is the case with Canadian GST and PST
  in the eastern provinces), they were not compounding properly for the
  freight cost amount on the P.O.  This has been corrected.

* When modifying a P.O. and then issuing it immediately, it was possible
  to skip totaling the purchase order, and then print it without totals.
  This is no longer possible - zero total P.O.'s cannot be printed.
                                   -4-

SALES ANALYSIS:

* The Back-order by Item report now considers the full 15 character Part
  number when determining where to print sub-totals.

* Under certain circumstances, the Browse by Customer and Browse by Item
  functions were not selecting all data when a specific territory was
  entered.  Territory is now a valid search criterion for Sales Analysis
  Browses.

* The G/L transaction number now appears on Daily Detail Sales reports.
  All Daily Sales Analysis reports now included the General Ledger
  transaction number.

* Cost information was not available when printing Sales Analysis reports
  for multiple warehouses.  Cost prices are now shown under all
  warehouse configurations.


INVENTORY:

* When printing inventory labels, a 153 status code would occur if an item
  description went past the 132 column limit - (eg. a label is specified
  to print starting in column 100 and the item description is 40 chs.
  long).  New rules have been introduced that will not allow the starting
  column specified to be such that the description could exceed the
  labels' right margin.

* When entering inventory receipts with negative quantities, the items'
  average cost was not always being computed properly if the quantity
  on-hand dropped below zero.  Any receipt of inventory will now correctly
  compute the average cost.  Note that the items' average cost remains
  positive regardless of the on-hand quantity.

* A 153 status code could occur when "Searching" an Inventory file, if the
  search started in warehouse "00" and the file contained Inventory "Comment"
  items.  This is now allowed.


SERIALIZED INVENTORY:

* When selling serialized items and moving backwards between the tendering
  screen and point-of-sale grid, serial numbers where not always being
  reallocated to the "available" list of numbers if the sale was subsequently
  canceled. The serial numbers are now reallocated under these circumstances.

                                   -5-

BILL OF MATERIALS:

* A status code 153 could occur when moving up and down multi-layered,
  complex builds.  This is now allowed.  The Bill of Materials module
  now supports the ability to "back-out" of a build, while still retaining
  the cursor position.

* Items classified as "Normal" and used within a Bill of Materials, then
  reclassified as "Manufactured" (without including build details as to the
  components required to manufacture the reclassified item), caused a status
  code error when Browsing through the Bills' details.  Bill of Materials now
  displays a warning message when an item within a Bill of Materials is
  classified as a "Manufactured item" and has no associated Bill of Materials
  for its' manufacture.

* Items listed on the Trial Build report & on the Trial Build Browse screen,
  did not indicate a shortage when an item within the Bill of Material was
  short, but the items' on-hand quantity was zero.  Bill of Materials now
  shows the shortage on-screen and also on the Trial Build report, regardless
  of the required items' on-hand quantity.

* Kits could "over build" if an order had a partial committed qty. and large
  back-order.  Kitting now evaluates the backorder amount while taking the
  committed qty. and backorder proportions into consideration.

* Canceling an order containing a Kitted item, while the order was being
  modified, would sometimes clear the Kits' committed quantity on the
  Inventory file.  The Kits' committed quantity is no longer affected when
  canceling an order subsequent to its' modification.


POINT-OF-SALE:

* The cash drawer "decimal codes" were not being sent to some types of cash
  drawers (under some circumstances).  Cash drawer codes are now sent
  whenever a Point-of-Sale transaction is processed.  In addition, a code is
  now sent to open the cash drawer when a deposit is received against a
  Layaway order.

                                   -6-

BUDGETS & FORECASTS:

* When updating the monthly "Trend percentages" for an individual budget
  account, values that exceeded 100 percent were permitted, but could cause
  the budgeted dollar values to compound incorrectly when the total
  percentage for the year was in excess of 900 percent!  The "trend line"
  can still be entered with monthly values that exceed 100 percent, and the
  resultant budget dollars will now compound correctly (mathematically), even
  though our programmers have serious questions why anyone would want to do
  this!  We suggest that even in businesses where the total sales in a given
  month exceed the total for the year (eg. lots of sales in December, many
  returns in January, and no sales for the rest of the year), users should
  take care to ensure that these large percentages are what they really mean!

                         --- end ---
