Version 9.3.0.2

•ENHANCEMENT - The AccuBuild Stored Procedures that are used for producing MAR reports for the AccuBuild Mobile product now support the tailored script feature that is available with MAR in the main AccuBuild Program. This now allows tailored SQL Script solutions for MAR Reports to be extended to the AccuBuild Mobile Platform.

NOTE: The MAR Reports that are run from the AccuBuild Mobile product will require that the user’s working directory exists in the Main AccuBuild Program. The user directory is created the first time the user logs into the AccuBuild Main Program. The Mobile Report procedures will use the user’s working directory for all temporary report tables and tracking text files for debugging purposes. Currently, the following files are created in the user’s directory whenever a report is generated from AccuBuild Mobile:

 ABAEP_RunMARReport.txt – This is a debug process file that tracks the steps involved in producing the mobile report and can be helpful for debugging purposes when a report is not working.

 userSQLScriptTableListnnn.txt – This is a list of all of the temporary tables that were created for the mobile report where “nnn” represents the report class number.

 userSQLScriptClassNonnn.txt – This is the SQL Script benchmark tracking log that tracks all of the SQL Script that is used to generate the report, where “nnn” represents the report class number. You can use this file to determine if any of the SQL commands failed during the report generation. In addition, this file is very useful to identify any SQL Bottlenecks for slow performing reports.

 userFIXVarCharFields.txt – This is a list of the SQL Commands that were issued to convert fields with Variable Character Length field types to regular character field types. This script is run after the report SQL Script is run but before the report is previewed in order to keep the temporary data compatible with the database DLLs distributed with the Mobile Application.

 Since Mobile Reports share the same working folder as the AccuBuild Main Program, it can be very useful to have a separate user name and working directory for Mobile users who also will be accessing the Main AccuBuild Program.

 The list of Reports that are run for Mobile need to be tested before allowing access to end users as some reports will not run properly in a mobile environment. Any report that requires any type of user interface other than the default report dialog should never be run on the Mobile Application. For example, if an inlist prompt is added to a report where a pop up partial list is displayed, this will never be displayed on the mobile device and the report will be left hanging since there is no way to communicate with the pop up list from the mobile app.

 Since mobile reports are returned without the user interface capability, any reports where the drill down data is required will need to be copied as custom reports and the drill down option removed from the drill down sub-report so that the drill down sections are always included in the mobile report.

•CORRECTION - AP Invoice Routing - The Proposed Pay Date was not being copied to second and subsequent invoice records when the vendor was not set up for payment terms. This issue has been corrected.

•The Posting Process for A/P Invoices has been changed to only post the approved invoices that are “in the hands of” the current logged in user. Previously, the posting operation was a global function and posted all approved invoices regardless of which user the invoices were assigned to.

•A new “Re-Route” button has been added to the document routing screen which will allow for one or more selected documents to be routed to another user without the need to use the “Approval Settings” button. This feature is very useful for assigning a large number of invoices to another user for processing purposes. For example, if only one person has the security rights for posting invoices and several others in the company have invoice entry rights, approved invoices can be forwarded to the person with the posting rights, once the invoices have been entered and approved by all parties involved. This new option can be used as outlined below:

o Select one or more invoices in the grid to be re-routed by clicking on the first document, and then using the Shift-Click combination or Shift-Up/Down Arrow combination to select multiple invoices.

o Once the invoices have been selected, click on the “Re-Route” Button located at the bottom of the screen.

o Choose the new user name to route the documents to from the drop down list of users, and

click the re-route speed button located to the right of the user name drop down list.

o A confirmation screen will be displayed before the documents are routed to the new user.

NOTE: All of the selected documents will be re-routed once confirmed by the user and the documents in the grid will reflect the new user name under the “In Hands Of” column. In addition, document transaction records will be created for each re-routed document with a transaction description of “re-route document”.

•ENHANCEMENT - The unit pricing for Inventory and Purchasing have been updated with 3 new units of measure:

•ENHANCEMENT - The Stock Request / Fulfillment process now handles stock requests for equipment costs and can be used as a vehicle to transfer inventory stock to a piece of equipment for equipment expenses. Any line item on a Stock Request that is linked to a piece of equipment, will now generate a equipment cost transaction during the posting process of the Stock Fulfillment. In addition, any related job cost transactions and general ledger transactions will be updated with the Equipment number as well.

•ENHANCEMENT - New Business Rules for Posting: During the posting process, each stock fulfillment record will be compared to the Stock Request Detail Item to see if the item contains an Equipment Number, if an item on the Stock Request (Order) contains an equipment number, then a transaction will be created in the EQTRANS table as a record type 10 – Equipment Expense. The equipment number will also be included in the general ledger transaction record associated with the fulfillment and in the associated job cost transaction record if applicable.

•NEW REPORT - A new Purchase Order Report has been added to the MAR Report Library that is a troubleshooting error report to verify that the total invoice amount on each order line is in balance with the 3 individual field amounts which include the extended amount (units * unit price on the order) + paid sales tax amount + paid shipping amount. During the posting process, the paid sales tax and paid shipping amounts are pro-rated against each line item which nets out a total invoice amount for each line. This report will check to make sure these amounts are in balance and will display any problem entries. If no errors are found, then a single line will be printed on the report indicating “*** No Errors ***”.

•ENHANCEMENT - A new Framework has been added to the posting process for job cost estimate imports so that the business rules can be tailored for additional functionality. The new framework provides script class that can be invoked at the start of the posting process and at the end of the posting process and are defined by the following class codes:

Sequence 102012 – Sequence No. 15 - Start of Estimate Import Posting Process

Sequence 102013 – Sequence No. 15 - End of Estimate Import Posting Process

•NEW REPORT - A new job cost report for production units has been added to the MAR Library which contains groupings at the G/L Expense Account level for each cost phase. This allows the report to be filtered for specific cost accounts when needed. The report requires a new class number 519:

•CORRECTION - The accrued State Unemployment Tax was being accrued to the wrong General Ledger Account for employees that have the state withholding going to one state and their state unemployment going to another state (home state in most cases). These amounts were following the account set up for the state based on the State Withholding state code (STATE_CODE) instead of the State Unemployment state code (SUIStateCode) in the PRCHECKS table. This problem has been corrected.

•CORRECTION - The tax burden pro-rate routine which applies employer paid payroll taxes to individual time card pay transactions had a problem when the routine was applying any leftover “rounding” amounts (usually a penny) to the last time card record in the batch. If the last record for the employee was a miscellaneous pay (1-6) but the pay was NOT marked for W-2 Wages, the rounding amount was still being applied. When this occurs, then depending on the department code that was associated with the other pay, it could trigger a violation of the “Direct Cost” business rules and cause the posting routine to be cancelled. This problem has been resolved in this release.

•ENHANCEMENT - The time card worksheet screen has been updated to save the custom grid settings for grouping and field names and field order so that these settings are restored each time the screen is opened.

•The employee list for time card entry has been updated to only include “ACTIVE” employees instead of the entire employee list.

•The Personnel/Visitors Tab on the Daily Report has been expanded to allow time card entries to include all the same fields and business rules as the Time Card Worksheet and AccuBuild Mobile. This Personnel Grid now contains the following fields and features:

•The grid has been expanded to support field grouping with automatic subtotals for hours worked for each field group.

•The layout of the grid is now stored in a user INI file so that a user’s grid layout will be saved and remembered each time the screen is opened.

•A new right-click pop-up menu option has been added to reset the grid defaults.

•The employee default fields will now be updated automatically when new entries are made.

•The Labor Distribution Codes (LDCs) are now supported and will be updated whenever the job cost phase is changed to a phase that has been assigned LDCs.

•A new feature was added to the Date Field (Date of Daily Report) on the General Tab to check the date of the Daily Report against any time card records associated with the Daily Report to make sure the Work Date on each time card record matches the Daily Report Date. If differences are found between the dates, the user will be prompted to change the work dates on the time card entries to match the Daily Report Work Date. Previously, if the date of the Daily Report was changed, there was no way to change any associated time card record work dates using the Daily Report Screen.

NOTE: If the time card records associated with the Daily Report have already been processed for Payroll, then you will NOT be able to change the date on the time card entry.

It is IMPORTANT to note that the Work Date field for the time card records on the Personnel tab will not immediately reflect the new date if the date is changed on the Daily Report until these records are refreshed by closing and reopening the Daily Report OR by clicking on the refresh button at the bottom of the time card grid.

•When the Daily Report screen is closed, the system will check to make sure all the time card entries (if any) have the same work date as the Daily Report Date and if there are records that do not match, a warning will be issued to the user.

•The DELETE option for a Daily Report (pressing Delete Key on Daily Report Record on PM Log) has been updated to run a test for any time card entries that are related to the Daily Report. If the time card entries have been processed for payroll, then you will NOT be able to delete the daily report.

If the Daily Report is deleted, all of the related records associated with the Daily Report will be deleted as well from the following tables:

 PMPersonnel – Payroll Time Card and Jobsite Visitor records related to the Daily Report

•CORRECTION - Restore Data - The AccuBuild Test Data TESTDATA.ZIP was missing the property settings after the 9.3 Release. The global settings have been restored to the test data.

•ENHANCEMENT - The Batch Log Lookup Process has been updated to include the EQTRANS table for Stock Fulfillment batches for any Stock Fulfillment records that are linked to a piece of equipment.

•ENHANCEMENT - The AccuBuild Import Utility Program (accuimport.exe) which is used to import spreadsheet data into AccuBuild user batches has been updated to now support equipment journal entries which includes depreciation expenses, equipment costs etc. The import utility now supports the following types of batch records:

Refer to the System Administrator FAQs for more information on the AccuImport Utility.

Version 9.3.0.2 - June 17, 2015