Version 9.2.0.1 Teal - August 29, 2014

ACCUBUILD USER LOGIN  

•CORRECTION - If a user was in the middle of coding a payable invoice from the Document Routing screen, and a different user was trying to log into the same company in AccuBuild, an exception error would be displayed as follows: “Exception Error opening table NEXTAPNO”. The user trying to log into the system would be denied access until the payable invoice screen was closed by the first user.  This problem has been corrected.

ACCUBUILD MOBILE  

•ENHANCEMENT -The Mobile Procedures for accessing the Customer List and the Vendor List from the AccuBuild Mobile application was not working if there were blank customer or vendor names on the list. The stored procedures were updated to ignore any blank names so that these functions work correctly now.

•ENHANCEMENT -The AccuBuild Mobile Stored Procedures will now be updated automatically whenever new changes are made to the AccuBuild Mobile Product. Previously whenever new changes were made to the mobile procedures, the user had to manually update the Mobile Stored Procedures from the Mobile Configuration Screen. This process will now be handled automatically and if the procedures are updated during the company open process, the user will be notified of the update.

•CORRECTION - The MAR Report Script had a bug on selected Job Cost Reports that were accessed via the AccuBuild Mobile product. The new Ignore Job Links option which is now available in the AccuBuild Program is NOT available for mobile reports and so the SQL Scripts on selected job cost reports were failing on the Mobile Reporting side. This issue has been corrected.

ACCUBUILD JOB SITE TIME CLOCK  

•New Procedures were added to the Mobile Stored Procedures which will now record both the actual clock in/out time and a rounded clock in/out time and include both of these times when the clock in pictures and time clock date are uploaded from the field. The original stored procedures will remain intact for backwards compatibility with current versions of the Mobile Time Clock Application, and the new procedures will be in place as soon as the final changes and testing on the Time Clock Application are completed:

•abm_ADMSRecord_Write

•abm_DailyReportADMSEmployeePicture_Upload

New Stored Procedures that will record both the exact clock time and a rounded clock time. The rounded clock time will now be stored in the “FileDateTimeStamp” field of the “DMMaster” table, and the actual clock time will be stored in the “DateTime2” field of the “DMMaster” table. It was necessary to store the actual time for audit and testing purposes to prove that the new clocking rounding rules are working correctly.

•abm_ADMSRecord_Write2

•abm_DailyReportADMSEmployeePicture_Upload2

•Support for a new rounding rule type has been added for the next release of the Time Clock Application which will be handled in the MOBILETIMERULES configuration table which is located in the Company Folder.  A new rounding rule “method 2” will be incorporated for rounding the clock in / out time. This new rule allows you to set a StartTime, EndTime, and the desired RoundedTime for any set of time ranges within an hour. The settings are entered using a time range of 12:00 AM through 12:59 AM but will applied to ALL clock in times. There must be no gaps in the time range as shown in the following example:

Example for “Clock Time Rounding ” Records

Clock Time Rounding actually changes the punch in / punch out time based on the rounding rules. The actual punch in and punch out times will be preserved, however, the working hours will be based on the rounded clock times. The following example sets the Rounding rules for the time clock to actually adjust the time instead of rounding the elapsed time. This example rounds to the nearest 15 minutes using the 7/8 rule where any time up to 7 minutes and 59 seconds between the quarter hour is rolled back and any time from 8 minutes and above would be rolled forward.

To use this rounding method, you will need to set up the required number of time range fields where any time that is greater than or equal to the starting time AND less than the ending time will be set to the rounded time as outlined in the following 7/8 Rule example:

Start Time End Time Rounded Time Comments on Rounding Rules

12:53:00 AM 12:08:00 AM 12:00:00 AM >= 53 minutes AND < 8 minutes round to 0 minutes.

12:08:00 AM 12:23:00 AM 12:15:00 AM >= 8 minutes AND < 23 minutes round to 15 minutes.

12:23:00 AM 12:38:00 AM 12:30:00 AM >= 23 minutes AND < 38 minutes round to 30 minutes.

12:38:00 AM 12:53:00 AM 12:45:00 AM >= 38 minutes AND < 53 minutes round to 45 minutes.

NOTE: The Samples Folder under the AccuBuild Program contains a sample of the above configuration settings titled “mobiletimerules_15MinuteRounding_78Rule.ADT”. If you would like to use the above settings, you can copy this table to your company directory and then rename as “MOBILETIMERULES.ADT” replacing the existing copy of the table.

GENERAL LEDGER

•CORRECTION -  The Direct Deposit Transactions were not being flagged correctly with the “[DD]” designation on the Bank Reconciliations for any processed NACHA Batches. Only the unprocessed batches were being reflected in the bank reconciliation records. This problem has been corrected and both the processed and non-processed direct deposit records will be flagged correctly.

JOB COST

•ENHANCEMENT - A new property setting was added on the Settings Tab entitled “Disable Audit Trail for Estimate Import and Job Template Postings”. This option will allow the audit trail tracking for the ESTDETL table to be turned off when importing job estimates and processing job templates. When the audit trail is turned off, the posting process is much faster but you will not have a record of the newly posted detail items in the audit trail.  

•ENHANCEMENT - The posting process for posting spreadsheet imports was updated with new SQL processes in order to improve speed performance during posting. These import postings will now be done within a few seconds if the Audit Trail is disabled. Please refer to the new Job Cost Property setting titled “Disable Audit Trail for Estimate Import and Job Template Postings” for more information on disabling the audit trail.

•ENHANCEMENTS - Job Templates

•The G/L Expense Account field associated to a job estimate has been added to the Job Templates screen.

•A new message is displayed to all the current batch of template entries to be deleted automatically instead of requiring the records to be deleted manually in the grid.

•The User Activity Log will be updated with new text during the posting process to indicate if the Audit Trail was enabled during the posting.

MY ACCUBUILD REPORTS

•CORRECTION - The new MAR Payroll reports that reconcile the time card entries in the TIMECARD table to the payroll check totals in the PRCHECK table for other pays, other deductions, and local deductions were showing invalid Yellow Warning messages for miscellaneous flat amount deductions that were NOT tied to a local deduction code. While there was NO problem with the underlying data in these situations, the report was indicating a problem. The SQL Script was correct for these reports to remove the false warnings which include the following MAR Reports:

•PRREPCK1.632 - Pre Check Tax Register Report - IMPORTANT NOTE:  This report should only be printed AFTER payroll taxes have been calculated to insure all of the deduction and pay accumulators are in sync between the time card records and the check records.  If this report is printed prior to calculating payroll taxes, then you will receive invalid results.

•PRREP14D.644 - Payroll Check Detail Reconciliation Report - Trans Date

PAYROLL

•CORRECTION - In the Time Card Entry Screen, when a filter was enabled for one or more columns and a pending (un-posted) record change existed on the grid, clicking the Refresh button was causing the following error: MainProgram.AppException: query Mobile Time Cards: Cannot perform this operation on an open dataset. The screen would then lock up and you could not exit and had to force an End Task in the AccuBuild Program. This problem has been corrected in this release.