March 31, 2003
The AccountMate 6.0 for SQL MS602a CD contains the following components:
· AccountMate 6.0 for SQL Program Files
· Report Utility Files (For details, refer to the Readme file under the “Crystal Utilities” folder.)
· Stored Procedure and Trigger Update Program (For details, refer to amspmain.pdf file under the “Other Utilities” folder.)
· Microsoft Visual FoxPro 6.0 (Service Pack 5) Runtime Files
· Seagate Crystal Reports 8.5 Runtime Files
Refer to the MS602a Maintenance Release Summary under the Technical Support section of the AccountMate Business Partner Home Page.
There are 2 sets of Maintenance Release Summary for this build release. The following are:
1. Issues verified as existing in VAM/SQL 5
· Sort by Control Number
/download/bugnotes/Fix_Summary_MS602a_from_MS5_byControl.htm
· Sort by Module
/download/bugnotes/Fix_Summary_MS602a_from_MS5_byModule.htm
2. Issues verified in AM 6.0 only
· Sort by Control Number
/download/bugnotes/Fix_Summary_MS602a_byControl.htm
· Sort by Module
/download/bugnotes/Fix_Summary_MS602a_byModule.htm
In the previous build, recalculation of the YTD amounts for the customer and vendor record can only be performed one record at a time through the Customer and Vendor Maintenance. Now, we have added the capability to recalculate YTD amounts for multiple customer and vendor records at a time. The features Update Customer YTD Sales Amount and Update Vendor YTD Purchase Amount will allow the user to pick a range of records to process and assign a separate Start Date value to each customer/vendor record which the system will use for the computation. These features are available through the Utilities > Data Manager function.
The AR Void Payment function has been enhanced to more properly take into account its effect on the users’ ability to take up any associated deposit records through the Record Bank Deposit function, by taking the following scenarios into consideration:
When a user tries to void a payment, he/she will first be asked, "Is this payment included as part of a deposit that has actually reached the bank?” A 'Yes' answer means the payment has been physically deposited to the bank. In this case the user will be able to void the payment regardless of whether it has been recorded as part of a deposit in the system or not. The voided payment can later be included in a deposit posted in the system through the Record Bank Deposit function.
If a payment has not yet reached the bank but has been recorded in the system as part of a deposit, the user will not be able to void the payment unless the payment is first removed from the deposit record on which it was posted. Under this circumstance, AccountMate will display this message, “This payment is included in deposit # [XXX]. Please use the Amend Bank Deposit function to remove it from the deposit, and then return to this function to continue to void the payment."
If a payment has neither been physically deposited in the bank nor has been recorded as part of a deposit in the system, AccountMate will show this message, "You will not be able to record this payment as part of a deposit. Do you want to continue?” A 'Yes' answer to this question will prevent the user from accessing the voided payment record in the Record Bank Deposit function. A "No" answer will stop the void transaction. The purpose of this message is to remind the user that once the payment is voided, it cannot be included in a deposit in the system. The user therefore has to use caution and ensure that the payment that he/she wants to void is actually a wrong or invalid payment which was never part of a real bank deposit.
The Cancel Received Goods function has been enhanced to allow the canceling of received goods which have been invoiced in the Accounts Payable module. Users no longer need to void the AP invoice before canceling the goods received.
This new build allows the users to reverse both the received goods and cancelled received goods. When the user matches the received goods during the AP Invoice function, the Accrued Purchase Order window now shows the cancelled received goods with a negative quantity.
The system also changes the way it handles the rounding of sales tax calculation. It no longer leaves a small sales amount (due to rounding) when all the received goods are matched (i.e., invoiced).
A new report has been added in the Accounts Payable Module. The Reversed Accrued Received Goods Report shows pertinent information related to reversal of the accrued received goods. This report is accessible through the Reports > Invoice Reports menu. The data can be sorted by Vendor # + Invoice #, by PO #, or by Invoice Date.
The SUTA calculation has been changed to base on the defined SUTA rate in the PR Module Setup. The default SUTA rate in the State Tax Table will no longer be used in the calculation.
In the previous builds, our system used the SUTA rate in the PR Module Setup only if the value defined is not zero. If the SUTA rate in the PR Module Setup was zero, our system took the default SUTA Rate in the State Tax Table. In this new build, the system will always use the SUTA rate defined in the PR Module Setup regardless of whether it is a non-zero rate or not.
Before using your Payroll system, validate the SUTA rate in the PR Module Setup. Enter zero on the SUTA rate field if there is no SUTA due/collectible.
A validation process in the Create Sales Return with Invoice function has been added to prevent over-posting of sales returns. With this validation, the system ensures that quantities to be returned do not exceed the “non-returned” quantities (shipped quantity less accumulated returns) for a given invoice.
A new option "Allow Exceed Credit Limit" has been added to both the Import Invoice and Import Sales Order functions as part of the validation of customers’ credit limit during the data import process. The default value of this option is retrieved from the AR/SO Module Setup. If the "Allow to Exceed Credit Limit" option in the Module Setup is unmarked, this new option in the import function will be disabled and the system will automatically validate all invoices/sales orders from the text file to be imported against the available credit limit of the corresponding customer. If the "Allow to Exceed Credit Limit" option in the AR/SO Module Setup is marked, the user can choose to either have AccountMate validate or not validate customers’ credit limits during the import process.
Enhanced user access rights validation against the Amend Quote function has been accomplished by adding two new entries in the User Access Rights Setup list:
"Supervisor" must now assign explicit user rights to allow or restrict them from accessing the Amend Sales Quote and/or the Amend Purchase Quote functions.
The Print Customer Statement function has been enhanced to prevent erroneous Open Credit amounts from showing up in an upgraded system due to corrupted data prior to conversion. A new option “Excl History Cash Rcpts before" is added to the Print Customer Statement function. The date entered for this option must not be later than the specified “Last Statement Date”. AccountMate will now compute the Open Credit amounts based on Cash Receipts that fall within the date range defined by the “Excl History Cash Rcpts before” date and the “Statement Cut-off Date”.
the Consolidate All Segments option in the GL Reports has been added to generate the GL Report by individual segments into one consolidated report.
When the Consolidate All Segments option is marked, the system will generate one GL Report but each GL Segment is started on a new page. This option will bypass the prompts for “Next GL Segment [XXX]” when viewing Individual Segment without consolidation.
The Bank Reconciliation Report has been enhanced to exclude zero amount AP and PR checks during preview or printing. This change is intended to match the Reconcile Bank Account function where zero amount checks are not shown during reconciliation.
We have corrected our system to generate the computer check based on the layout selected in the AP Module Setup. In the previous build, the check output does not conform to the check version and layout selected in the module setup.
Verify the check version and layout settings in the AP Module Setup before using the Print Computer Check function.
an ambiguity regarding voiding Credit Invoices generated from RMA has been clarified in this buld. Unlike voiding a Sales Return Invoice, Voiding a RMA Credit Invoice will not affect inventory quantity. Inventory will only be updated during the Cancel Receive RMA process. The message, “Voiding the credit invoice will not update the on-hand quantity. The on-hand quantity will be updated when you perform Cancel Receive RMA." will be displayed to remind users of this change.
Invoices in the AR Apply Payment function are now sorted and displayed in the order of Invoice# + Invoice Date, instead of just by Invoice Date.
The MI report option "Inventory Quantity Listing" under the Inventory Reports group has been changed to "Warehouse Quantity Listing" to be consistent with the report header.
The MI module has been enhanced to use the inventory’s master bin (set up as first bin) as the default bin for the Create Work Order, Post Work-In-Process, and Post Finished Goods functions. Before the change, the system used the warehouse master bin as default bin.
The Inventory Serial Number Report has been enhanced to show the Transaction Number information, if available, alongside the Transaction Type field. The user will be able to tell the actual transaction that affected the Inventory Serial Number.
A new parameter has been added to the Tfrmtbr.dbfrevert() method. This parameter will indicate whether the message “A conflict occurred during the “Save” operation” should be displayed. The new parameter has a logical data type with the default value set to FALSE – not to suppress the message.
If you overwrite the class code by adding code in the dbfrevert() method, make sure to update your program code by adding the new parameter (.f.).
|
CPU |
Intel-based Pentium III 700MHz |
|
Memory |
256MB |
|
Hard Disk |
1GB Free Space |
|
Operating System |
Windows 2000 Server or Advanced Server (SP2) or Windows NT Server 4.0 (SP6) |
|
Database |
MS SQL Server 2002 (SP2) or MS SQL Server 7.0 (SP2 or later) |
|
CPU |
Intel-based Pentium III 700MHz |
|
Memory |
256MB |
|
Hard Disk |
500MB Free Space |
|
Operating System |
Windows 2000 Server or Advanced Server (SP2) or Windows 2000 Professional (SP2) or Windows NT 4.0 Server (SP6) or Windows NT 4.0 Workstation (SP6) |
|
CPU |
Intel-based Pentium II |
|
Memory |
128MB |
|
Hard Drive |
200MB Free Space |
|
Operating System |
Windows XP Professional or Windows 2000 Professional (SP2) or Windows NT Workstation 4.0 (SP6) or Windows 98 (Second Edition) (not recommended) |
Visual FoxPro 6.0 (SP5)
Crystal Reports 8.5
MS SQL Server 7.0 or 2000 Utilities
There is no installation interface for the Report Utility Files (Rptsetup.exe). When the files are needed, the users are required to copy them manually from the CD. The same applies for the Stored Procedure/Trigger Maintenance Utility (Amspmain.exe).
Microsoft SQL Server is not included in the CD. If SQL Server has not been installed on the database server, the user is required to install Microsoft SQL Server before installing AccountMate 6.0. Refer to the Hardware/Software Requirements above regarding the versions of SQL Server that AccountMate 6.0 supports.
Do not forget to install the Microsoft Data Access Component (MDAC), if it has not been installed on each workstation that will be running AccountMate 6.0.
The following Setup Types are available during the installation process.
This option will install AccountMate 6.0 Program Files, Visual FoxPro 6.0 Runtime Library and other drivers for Crystal Reports 8.5.
· Choose this option if you do not use a file server to load AM 6.0 or you want to run the AM 6.0 application from the workstation.
This option will install Visual FoxPro 6.0 Runtime Library and other drivers for Crystal Reports 8.5.
· Choose this option if AM 6.0 has been installed on a file server and you only want to install the minimum files required on the workstation in order to run AM 6.0 from the file server.
This option will check all three components included with the Custom option as default and allow the user to pick and choose the specific component(s) desired during the installation. Available components are AccountMate 6.0 Program Files, AccountMate 6.0 Administrator Program, and Runtime Files (i.e., Visual FoxPro 6.0 Runtime Library, and drivers for Crystal Reports 8.5).
· Choose this option to install any components that you forgot to install or choose specific components to fit your needs.