 | Many changes have been made to improve
file and record locking on multi-
user versions of Shop Trac. Some of these changes will be
reflected in
single user versions as well.
a) All edit menus now have "Abort" as the default option.
This may
cause some initial frustration for those of you who were
so used to
this system where the "Save" option was the default. To
help with
this problem, the 'Abort' option does allow the chance to
abandon the
abort operation with a Yes/No prompt rather than the
normal ok prompt.
This eliminates almost all unneeded single record locks by
only saving
or processing data when explicitly requested to do so, and
only locking
records during the short duration of the Save/Update
operation.
b) Multiple record locks are only in effect during the
actual
transaction processing, and they take precedence over any
single record
locks, unless the single record was already locked when
the transaction
takes place. Since single record locks are now only for a
split second
(during a Save/Update operation) this should not have any
noticeable
effects.
c) Lock error messages are much the same, although a new
one that
indicates a "Lock Conflict has Occurred" has been added.
This would
only happen when updating a single record that conflicts
with another
single record lock on another station. When this does
happen (rare)
the data will NOT be saved as expected. The only option is
to make
the changes again.
d) Due to these changes it is very important that you do
NOT attempt
to operate a single user version of Shop Trac in a
multi-user environment. Previous safeguards that eliminated this from
happening
are no longer in place. If you have been doing this please
call us
for a multi-user upgrade since doing this WILL corrupt
your data
files. |
| The 'Manufacture Code' database will be
converted to a new format to
support the new Report | Inventory | Manufacture Codes
option. This
report (it takes some extra processing time) will provide
statistics
by manufacture code. A new database will be created using
a new name
and the existing data will be copied into it. This happens
the first
time Shop Trac is loaded after installing this update. |
| Some problems with the 'Optional'
suggested order report that resulted
from the 11/30/2002 update have been fixed. A new 'Vendor'
field has
also been added to this report when this report has been
issued for a
specific vendor. This is because the "Pkg. Qty" may be
unique to that
vendor. |
| A new option called 'Reset Vendor Pkg'
has been added to the Utility |
Supervisor menu. The 11/30/2002 update added the Package
Qty field to
the vendor price database. It seems that some existing
records already
had erroneous data, and this has resulted in some
unreliable package
quantity fields. This option will reset these fields to
the default
package quantity. Any vendor unique package quantities
will need to be
re-input after using this feature. |
| When importing a price list and adding
a prefix to a part number, the
prefix will also be added to superceded part numbers. |
| The 'Journal' reports for all modules
on the 'Transaction' menu now allow
access to previous years data. Please note that this data
may become
erroneous if GL accounts and/or Customer/Vendor accounts
are reassigned,
deleted and/or altered in meaning. |
| The Reports | General | Income
Statement option now accessed another
menu. This menu will produce 2 styles of 'Income
Statements'. 'Normal'
is the same as before, while 'Comparative' creates a
statement that will
also include information from the previous years income as
a comparison. The Reports | General | Income
Statement option now accessed another
menu. This menu will produce 2 styles of 'Income
Statements'. 'Normal'
is the same as before, while 'Comparative' creates a
statement that will
also include information from the previous years income as
a comparison. |
| The parts data export routines have
been changed to allow exclusion of superceded numbers.
Annual sales data, as well as the total of the last 4
years of sales has been added to the exported data. |
| Invoice comments/messages were only
printing on the first page for users with PCL forms. This
has been corrected. |
| Support for a custom PCL purchase order
has been added, as well as the option to change the
existing purchase order format. |
| Postal codes that were not printing
properly on purchase orders should now print ok. |
| Two new fields have been added to Setup
| Defaults. These fields called 'Console Width' and
'Console Height' determine the default window size when
viewing console reports. |
| The 'Terms' field on the invoice has a
new option called 'If Paid By'. The invoice screen
also has a new 'Due Date' field. If the 'Terms' are set to
'If Paid By', then any discount offered (only on the page
1 'Discount' field) will not actually be calculated on the
invoice, but will be offered in a message if the invoice
is paid by the specified due date. The offered
discount amount will be transferred to a previously unused
'Discount' field on the receivable ledger entry. |
| A new field on the invoice called 'Due
Date' allows you to specify the date an invoice is due.
This date defaults to 30 days from the invoice date. This
date is used to determine when a receivable entry is past
due. This field is also used by the new 'If Paid By'
option. |
| A new option called 'Reset GLs' has
been added to the Utility | Supervisor menu. This option
will reset ALL GL accounts for a given parts line to those
as specified by the 'Manufacture' code for that line. If
no 'Manufacture Code' is specified, then all part numbers
will be processed. Please note that this routine when used
may affect your GL balances if you are changing the
'Inventory Asset' account. Changes to GL values are NOT
made by this routine, and these will have to be done
manually. This routine will also allow you to replace a
specified manufacture code with another valid manufacturer
code. Any part numbers encountered with invalid
'Manufacture Codes' will have these codes set to 'UA'. For
this reason it is a good idea to create a 'Manufacture
Code' called 'UA - Unallocated' using the Edit |
Manufactures | Add/Edit option. |
| A new option called 'Price Purge' has
been added to the Utility | Supervisor menu. This option
will purge ALL prices for a given vendor from the vendor
price database. |
| The Edit | Inventory | Price Lists
option has been changed to handle superceded numbers in
the same manner as other areas of Shop Trac. When a
superceded part number is input, the part number
field will be completed with the replacement part number. |
| You will now be able to assign a
different package quantity to different vendors using the
Edit | Inventory | Add/Edit option in the same manner as
you would assign a different part number. If NO package
quantity is defined here, then the package quantity as
assigned for the master part number is assumed. Please
note that when importing suggested orders using the
purchasing routines that vendor information MUST be
supplied if you wish to calculate order points based on
vendor package quantities. The 'Suggested Order' report
will provide proper order points for all vendors based on
package quantities. |
| Customer sales history will now show
the final customer price after all
discounts have been applied. This information should be
more useful then the current 'List Price' that was
displayed. |
| A new field called 'Average Sell' has
been added to the Edit | Inventory | Add/Edit SED. This
field will maintain an average sell price for each part
number. This value is calculated taking all discounts into
account. The previously unused 'Allocated' field has been
removed to make room for this new field. |
| It is now possible to print
Receivable/Payable history reports by 'Account ABC Code'
selection. |
| New features have been added to Shop
Trac that will allow limited data sharing between Shop
Trac users. This would be useful for those users with
multiple branches. The Edit | Inventory | Price Lists menu
has a new option called 'Branch Lists'. This option works
just like an online price list, with the exception that
the data includes a 'Balance' field rather than a 'Last
Updated' field. The 'Branch Lists' data files are created
using the new 'Branch List' option on the Utility | Export
menu. In practice, you would export your data to some type
of removable media, provide this data to a branch
operation. They would be able to check your stock and
prices from within their own Shop Trac system. These
'Branch List' files have a .BRA extension and should be
copied to the \TRAC\DATA1\USER directory (assuming a
default Shop Trac installation). These files would need to
be updated on a regular basis. Branch files only export
the 'Retail Price' to also allow sharing for other than
purposes. |
| The online text editing features (such
as user help accessed with the ALT-F1 key) have been
modified in the way files are saved. Once a file name has
been chosen for editing, the 'Save' command will use this
file name. This will eliminate problems with over writing
other files by mistake. |
| The Inventory | Assembly routines have
a new 'Summary' option added to the edit menu. This
feature works in the same manner as the same option that
is available using the 'Invoicing' option. |
| When adding/superceding a part number,
the new part number is now converted to uppercase just as
in other areas of Shop Trac. |
| The Reports | Inventory | Suggested
Order has a new option available under 'Report Styles'
called 'Emergency'. This option will generate a suggested
order only for items where the balance is zero.
|
| When importing a suggested order into a
'Purchase Order' a 'Report Styles' option is now
available. This offers the same features as the 'Almost
Order' and the 'Emergency' options available on a printed
'Suggested Order' report. |
| When importing a suggested order into a
'Purchase Order', the 'Vendor Account Number' is carried
over into the import window. |
| Both 'Account Number' and 'ABC Code'
selection is now available for all the Journal Reports. If
these fields are not completed then the journals will
simply be printed to include ALL records. This can be a
very useful tool to determine sales by customer or
purchases by vendor for any given period. |
<%=Session("UserName")%> 
