/
Issues Fixed
Issues Fixed
- Documentation Reviewer
Owned by Documentation Reviewer
The following issues have been fixed:
Service Management
| Case # | Description |
|---|---|
| SMS-154 | When filtering by Billing Customer in the Service Batch Invoicing window, if service call was saved without a Bill Customer, the filter using the Customer on the service call. |
| SMS-158 | The system no longer freezes up when posting Receivables batches from Receivables Transaction Entry and then closing the window. |
| SMS-243, SMS-518 | If you change the Call Type from T&M to MC, stranded journal entries based on overhead on Labor transactions are no longer created if the Invoice Options are not marked in setup. |
| SMS-261 | The Sales Transaction Entry window now displays the credit limit warning if a second SOP transaction line is added to an SOP billing type job. It was reported that a user updated a customer's credit limit prior to creating the transaction and the exceeded credit limit warning was not displayed. |
| SMS-385 | After clearing the Contract Maintenance window that was accessed by zooming on the Contract field, the Contract Number lookup now displays the open contracts available for the customer. |
| SMS-434 | The Billable and Taxable checkboxes now display as expected in the Adjustments to Costs window when Enable Task-Based Expense Entry is marked in the Service Options window. Additionally, if the Billable field is unmarked, the Billing Amount field is disabled. If Billable is marked, the Billing Amount field displays based on your settings. |
| SMS-457 | When a maintenance contract (MC) call is created, the Bill To customer and location from the contract now default on the call. |
| SMS-466 | We've made the Master Contract ID column wider in the Escalation Posting window so that the entire ID displays. |
| SMS-478 | The default GP account or changed account remains when transferring to a shipment or shipment/invoice. Users were experiencing the defaulting account number changing to a service account number when transferring to a shipment or shipment/invoice. This occurs only with the following setup options:
|
| SMS-482 | When assigning an equipment type to a new equipment record, the information now defaults from the equipment type as expected. |
| SMS-483 | When generating MCC calls, the bill to customer and address now default to the bill to customer and bill to address from the contract. |
| SMS-515 | When an inventory item and a non-inventory item are submitted from MobileTech on the same service call, if the general entry batch is deleted before the SOP batch is processed, the line item in the SV000805 is no longer deleted. |
| SMS-531 | When using Signature Utilities to import the Contract Task Master, equipment now displays correctly in the Contract Coverage window. |
| SMS-561 | The Bill To information now auto-populates when the Call Type is changed when creating a service call. For example, if an existing call type is changed from MC to another call type like T&M, the Bill To values are updated to reflect the default Bill To values from the Location (if this exists). If those are empty, the Bill To information on the Customer record is used. If that is empty, then the Customer/Location values default to those on the Service Call. |
| SMS-565 | We've fixed an issue that occurred with users who use the MANUAL Revenue Recognition method and attempting to build checks. Users will no longer be prompted to set up maintenance accounts. |
| SMS-571 | When editing a document attachment in the Document Maintenance window after using the Move Location Utility or Move Service Call Utility to move to a different customer, you are able to edit the document attachment description and the file section is disabled as expected. |
| SMS-574 | An employee ID can now only be associated with one Technician ID. |
| SMS-649 | When a maintenance contract is generated, and the contract is assigned to a master contract without billing control marked, the invoice now has the bill to customer and address code from the contract as expected. |
| SMS-659 | The Time Stamp Inquiry window was updated to gray out all the fields as the data is display-only for all the fields in the window. |
| SMS-666 | When using Allow Editing of the SMS GL Account on PO Line Item, the correct ACTNDX_DR is now used. |
| SMS-668 | Backing out a journal entry is now reversing the Billing Amount field sign and the transaction quantity as expected. |
| SMS-680 | When printing a maintenance contract invoice, the footer now correctly displays the page number. |
| SMS-683 | Tax calculations are now correct when creating a master contract invoice to Receivables with a combination of invoice and credit billings. |
| SMS-705, SMS-708, SMS-761 | When opening the Revenue/Cost window, a comparison of current Forecast Costs/Hours to Actual Costs/Hours is performed and if the Current Cost exceeds the Current Forecast, the Forecast is adjusted. An indicator displays when the Forecast is adjusted. Additionally, if the Current and Original Forecast is currently $0.00 and you set a value, then both the Original and the Current Forecast amounts are set to that value. If the Original Forecast is <> $0.00 then no future updates to the Forecast will update the original Forecast values. |
| SMS-720 | When creating a correcting journal entry when using multicurrency, the Product Indicator, Service Call/Job ID, and Cost Code fields are filled as expected on the correcting entry. |
| SMS-741 | Updated customer logos now display as expected on SSRS reports. |
| SMS-748 | The Billable checkbox is now marked as expected when a Signature Transaction Entry with a billing amount in the Adjustments to Cost window and the Billable_Check_Box field in table SV000810 has a status of 1. |
| SMS-762 | When doing a PO return to a purchase order that went against a service call (or a job) and the inventory item on the purchase order uses bins, the inventory and bins are unaffected with the return. (The Bin Quantity Entry window no longer opens.) |
| SMS-770 | The calculated fields in the Master Contract Revenue/Cost window now update as expected when the window is opened. |
| SMS-771 | Invoicing a service call or MCC call now only adds an equipment ID to the SV00815 table if the equipment ID was added to the initial transaction. |
| SMS-773, SMS-774 | The year drop-down lists for MCC Calls and Recognized Revenue now display the current year for users who have fiscal years that are not based on the calendar year when the fiscal year containing the current year is closed. |
| SMS-780 | The billing amount is now correct if you edit the transaction hours in the Service Transactions window. |
| SMS-785 | The Move Utility cannot be used if the location is on a maintenance contract. |
| SMS-787 | Users can now select a different Bill To Customer location as expected when creating a new maintenance contract. |
| SMS-788 | When Global Filtering is turned off, when the Bill To customer is selected on the new service call, the Bill To lookup window now displays all the Bill To customer's locations as expected. |
| SMS-792 | When the date is cleared in the Task Schedule window, the "Invalid month '0' in date function. Script terminated." error message no longer displays. |
| SMS-798 | When renewing a multi-year contract after a scheduled task date was updated, all scheduled tasks are now added as expected to the renewed multi-year contract. |
| SMS-801 | The Master Contract Revenue Cost window now displays the Contract Revenue percentages as expected. |
| SMS-810 | On the Inventory Transaction Inquiry window, the Transaction Type radio button was added and the Unbilled checkbox label now displays. |
| SMS-812 | On the Transaction Entry Zoom window, the Back Out By JE field label now displays next to the field. |
| SMS-826 | If a primary Bill To Address is set up in the customer RM record but is NOT set up as a service location, the Bill To address cannot be added to a service call. |
Job Cost
| Case # | Description |
|---|---|
| JC-021 | We've updated the performance of selecting the Product Indicator in the Payables Transaction Entry Distribution window. Originally an Offset Account check was performed when the window was opened. This check has been updated to validate after the job number is entered so that the check only runs on that job's division. |
| JC-052 | The amount remaining is now reflected correctly on the job when a credit memo is applied as payment. |
| JC-097 | The job import process was updated to reduce the import process time. |
| JC-118 | We've fixed an issue that allowed a Drop Ship Purchase Order on a Purchase Order Invoice to be posted against a closed Job Cost period. This caused the JC_Job_MSTR to not be updated properly and the summary transaction was not created. |
| JC-123 | A Job Cost User Defined Bill Code invoice now logs total sales amount when the bill code is excluded from sales tax and when only the non-taxable portion is invoiced. |
| JC-130 | Project Invoice Entry invoice that uses a billing type of Project Bill Code now logs the total sales amount when the bill code is excluded from sales tax, regardless if only the non-taxable portion is invoiced or if it is included with another element. |
| JC-132 | We've fixed an issue that allowed a user to create a return on a closed Job. |
| JC-133 | The Job Cost Audit report has been updated to display any changes to the cost code description. |
| JC-143 | We've updated the RPO Revenue Entry window to prompt users to either post the RPO Revenue Entry build or to remove the build when closing the window without posting. |
| JC-178 | The Rate_Per_Unit is now calculated and filled and the Expected Contract, Anticipated Margin, and Margin Percent are now correct after changing the profit type to 9 or from 9 to another code in Job Maintenance and posting the GL batch. |
| JC-183 | When using the Move Location Utility, if the related GP Address ID associated to the Service Location you are attempting to move is assigned as the Job Address for any open or closed Job, the address is not removed from RM00102. |
| JC-184 | The Job Cash Receipts inquiry window now only displays the cash receipt payment transactions. |
| JC-187 | We've fixed an issue where users were receiving an “Unhandled script exception. Illegal address…” message that occurred when using Lockbox and applying payments to Job Cost invoices. This fix will pull the Original Amount information from the Apply Sales Documents window if the window is open, otherwise, the Original Transaction Amount will be pulled from the RM_Cash_WORK (RM10201) table. |
| JC-190 | If you are not utilizing all cost code segments, you have Update If Exists marked, and you import data updates to records that already exist, the primary key violation error message no displays. |
| JC-197 | The Unit Bill Rate is now calculated as expected on the Unbilled Cost report for Jobs with transaction-level billing after the Profit Type is changed. |
| JC-199 | The Percentage-of-Completion (POC) Journal Number is now auto-generated to prevent the possibility of a user entering the same transaction number in the same month/year. |
| JC-206 | Users can now apply an unposted project-level credit memo to a posted project invoice. |
| JC-207 | The Billing Transaction Inquiry window correctly displays the remaining amount after applying a Sales Order Processing return. |
| JC-209 | For users who import using the wsiJCChangeOrdersDetailMSTR, the following fixes have been made:
|
| JC-212 | The Project Billing Inquiry window now displays chronologically with the oldest date at the top. |
| JC-213, JC-231 | The AIA report now correctly reports the work completed amount if more than one job was on the same project with a bill type of Project Bill Code; and each job had the same bill codes but with different descriptions and Total Billable Amounts. |
| JC-221 | After deleting a Project Cost Plus Billing Invoice batch, the JC20002 table is updated as expected. The Billed Transaction field is set to 0 and the deleted invoice is removed. |
| JC-222 | When more than one payment is received on a contract agreement, the Subcontractor Transaction Detail SSRS report no longer duplicates the contract lines. |
| JC-229 | The AIA report now correctly reports the Retention on Continuation amount after the retention had been paid. The AIA report displays the total retainage on page 2 and this matches the amount on page 1. (Provided that no retention is paid against a job until the end of the job, the retainage per bill code will display appropriately. After the retention is paid, the retention is split between the bill codes.) |
| JC-230 | Tax is now calculating correctly for retention on Contract Agreement Payments when part of the payment is allocated to a negative balance change order. |
| JC-234 | The Open Closed Jobs window threshold has been increased to 100,000 jobs. |
| JC-243 | For Job transaction-level invoices, the Show Credited Transaction checkbox is now functioning as expected. When marked, the transactions with a billed invoice and credit memo number display. |
| JC-244 | When creating a shipment/invoice in the Receivings Transaction Entry window that only has freight and taxes added, and this is saved to a batch and then Series Posted, the posting no longer hangs at 100%. If a transaction level posting is attempted, a “division by zero” error is no longer displayed. |
| JC-250 | When creating a payables transaction, when re-entering the Distributions window, the Job Number field no longer clears out. |
| JC-254 | When posting a payables transaction batch in the Payables Batch Entry window, users no longer experience an erroneous message indicating there are no transactions in a batch, yet the batch posts as expected. This message only occurred for users using workflow to approve payables transactions. |
| JC-255 | In the Job Status window, actual hours on the job are no longer doubling when multiple change orders are posted using the same cost code. |
| JC-257 | Users can no longer reprint a PAR invoice as the amounts are based on when the invoice is reprinted. |
| JC-265 | Users who save transactions to a batch in the Job Invoice Transaction Entry window, change to a different batch, and then delete the original batch - the transactions are no longer removed from the JC10504 table. |
| JC-269 | The Job Original Contract and Expected Contract Amounts are now correct when a fixed change order is created for a Cost Plus/NTE job. |
| JC-272 | The SQL Stored procedure wsiJCInventoryWork has been updated to include a SmartConnect node so that the IVIVOFIX field in table IV10001 with the @I_vAccountIndexArray21 parameter value. |
| JC-274 | When creating a credit memo for a PAR project, the duplicate key values error message no longer displays. |
TimeTrack
| Case # | Description |
|---|---|
| TT-013 | In the Manager Approval window, the lookups for disabled fields have been removed as changes for the disabled fields are not allowed. |
| TT-033 | Users who edit a MobileTech time entry and then create a manual entry for the same employee no longer experience the MobileTech time entry's appointment number to display on the new manual entry. |
| TT-036 | If a transaction number has already been used in WS30702, an error message now displays and the transaction will not be committed. |
| TT-038 | The Act Labor Cost TTD + Markup amount is now rounding as expected to two decimal places for profit types 3, 4, 5, 8, and 9. |
| TT-039 | Payroll transactions are committed as expected if linked to a service call. |
| TT-061 | After committing a batch with fixed asset transactions, the batch can now be deleted from payroll. |
| TT-062 | Batch names with apostrophes can now be committed as expected. |