Versions Compared

Version Old Version 74 New Version 75
Changes made by

Documentation Reviewer

Documentation Reviewer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

New Features

Service Management

Case #Description
SMS-1971

Refrigerant Tracking leak rate calculation has been updated to use the refrigerant released value entered in the Accidentally Released field. Previously, the calculation used the Refrigerant Added value. See Refrigerant Tracking and Choosing Service Options.

New calculations for the Refrigerant Tracking Leak Rate Analysis Methods in the Service Options Setup window:

  • Annualized
    The annualizing leak rate calculation method is as follows: Leak Rate (%) = (pounds of refrigerant released / pounds of refrigerant in full charge) x (365 days/year / short of #days since refrigerant added OR 365 days) x 100% If the owner/operator selects to use the annualizing method, for the first refrigerant released in the calendar year 2019 the second term would be 365 / 365 (or "1"). For subsequent additions, the second term would be 365 divided by the shorter of the number days since refrigerant was last released or 365.
  • Rolling Average
    The rolling average method is as follows: Leak Rate (%) = (pounds of refrigerant released over past 365 days / pounds of refrigerant in full charge) x 100% If the owner/operator selects to use the rolling average method for refrigerant releases in the calendar year 2018 the numerator would be the pounds of refrigerant released since the shorter of January 1, 2019, or the last successful follow-up verification test, if one was conducted in 2019. For releases in 2020 and beyond, the numerator would be the pounds of refrigerant released since the shorter of 365 days or the last successful follow-up verification test.
SMS-1975

When importing a service call in SmartConnect, if you do not pass in a Bill To customer ID and Bill To address code we are now filling the information in this order:

  1. If the call type is MC or MCC and you pass in a contract number, the bill to information will come from SV00500.
  2. If those are empty or if it is not a contract call, then we will get the bill to information from SV00200.
  3. If they are still empty, the primary bill to address code comes from RM00101 and the customer will be the one passed into the procedure.
  4. If these are still empty, it will default the bill to information based on the customer and address code passed into the procedure.

Job Cost

Case #Description

JC-458

We've updated the Signature Credit Apply window regarding applying project credit memos to project invoices.

  • When you select the checkbox, if the job on the invoice matches the job on the credit memo, it will default in the amount from the credit memo. If the Remaining Amount is less, then it would use the Remaining Amount.
  • You can override the default up to the Remaining Amount as long as the total is not more than the unapplied amount on the credit memo.
Note
The window no longer displays the Credit Memo Amount and CM Unapplied Amount columns as these columns were causing display issues if amounts were applied and then unapplied.


JC-460

The .NET Close Jobs window has the following functional changes. See Closing a Job, Additional Job Close Setup, and Signature Action Lists for JC.

  • The process timeout has been increased to 120 seconds when redisplaying or filtering jobs available to close.
  • Marking/unmarking jobs in the Available to Close grid will insert/delete from the k2aAddInJobCloseSchedule table immediately.
    • If the Save Schedule option is NOT ON, the marked jobs will stay in that table until you run close, unmark the jobs, or close the window.
    • If the Save Schedule option is ON, the marked jobs will stay in that table until you run close or unmark the jobs. The jobs lines are automatically saved since they are in the table already.
    • A user could have multiple jobs marked for different schedule/posting dates in table k2aAddInJobCloseCloseSchedule.
  • All jobs that display in the window are no longer temporarily made inactive. This provides an enhanced performance boost for users who also are using MobileTech.
  • Selecting the Redisplay button will reload the list, keep the marked jobs, and those marked will appear first in the list. A user can mark jobs they find and then filter differently to find others. Each time the user clicks Redisplay the list will rebuild and show all marked at the top along with other unmarked available jobs that fit the filters on the window. A user will not lose the jobs that they have marked if they filter differently. To discard wrongly marked jobs they have to unmark them or use Unmark All.
  • If using the Save Schedule setup option, the Existing Schedule button now functions the same as Redisplay.  See Additional Job Close Setup.
  • The Existing Schedule button only displays when the Save Schedule option is on.
  • Updates to the Available or Not Available Reports:
    • Filter fields have been added as parameters to the report.
    • When printing, the filters selected in the Close Job window are displayed at the top of the report window.
    • The Available to Close report will show marked jobs regardless if they fit the filter criteria passed from the window.
  • Updates when opening the .NET Close Job window from the Job List (see Signature Action Lists for JC and Additional Job Close Setup):
    • If Saved Schedule option OFF - When a user marks a job in the Job List and then opens the Close Job window. The window will load with that job marked and other jobs available to close. If the user did not pick a job and clicked to open the Close Job window, the window will open with nothing displayed, which is the current functionality. Select Redisplay to populate the window.
    • If Saved Schedule option ON - When a user marks a job in the Job List window, the job will be added to the table, and display as marked in the Close Jobs window. The marked jobs will remain marked. The user will not receive a dialog to delete the already saved schedule. If the user doesn’t pick any additional jobs, the window opens with what the user saved before or just all available jobs (even if not marked).
  • Removed the Save Schedule button from the Close Jobs window since records are stored differently and directly to the k2aAddInJobCloseSchedule table when a job is marked.
  • Column sorting has been added to the Jobs Available to Close section. Select the column header to sort ascending, and select again to sort descending.
JC-463We've enhanced the speed performance for closing jobs which will also improve closing months and running the recreate summary process.

Signature Fixes

Service Management

Case #Description
SMS-1961The alternate Customer Maintenance window is now compatible with the Dynamics GP 2022 Mid-Year Canadian Payroll Tax Update.
SMS-1964The Unit of Measure field in SV000810 is now being filled in when processing an SOP inventory transaction from MobileTech. 
SMS-1966We’ve fixed an issue where SMS_Pricing_Matrix or SMS_Pricing_Matrix_Markup was not using the default Address Code that was selected in Invoice Options (Bill To or Service Location).

SMS-1967

In the Mobile Inventory window, users can now view the error and/or delete the line when the transaction has an eConnect error.
SMS-1968We've fixed an issue that occurred when posting payroll to Service Management and there are already transactions in the SV000810 table that are not labor. Users were receiving a “Conversion failed when converting the varchar value xxx to data type int”. (The xxx value depends on the existing transaction number on the service call.)
SMS-1969We've updated the k2aSigPostToService SQL procedure to include additional fields including SV_Language_ID, Time_Zone, and all the WS_Reserved checkbox fields. Users will no longer receive the error message "An error occurred during the execution of SQL procedure k2aSigPostToService".
SMS-1970We've fixed a registration issue when using the GP Web Client to access Signature windows.
SMS-1972We've fixed an issue where reconciling Billing MC contracts was not setting the TTD field correctly with billing in multiple years. The Revenue/Costs and Contract Cost Life to Date windows now display the correct billed amount.
SMS-1973

When creating maintenance invoices on master contracts where the credit memo is in the same period as a posted invoice and the invoice amount is more than the credit memo, credit memo numbering is now used as expected. 

SMS-1974We've increased the MCC Call Creation process performance to significantly decrease the processing time. 
SMS-1976The Billing_Amount is now filled as expected in the SV000810 table for mobile purchase orders (originating from MobileTech) when using Extended Pricing with a 0% markup.
SMS-1977The SSRS-Maintenance Contract Profitability pull through report is now defaulting the starting date as 2022.

Job Cost

Case #Description
JC-459SOP transactions with the item type of SERVICES going to a Cost Plus job with the Billing Type as Project Trx Level and a profit type of Flat Rate on the cost code are now showing a billing amount in the Project Transaction Level Billing window.
JC-464You can now use the last day of year 12/31/xxxx as a schedule date when the period is OPEN. Users had experienced an error message when selecting this date and attempting to close jobs.

TimeTrack

Case #Description

TT-145

The Fixed Asset batches are now created as expected when committing fixed asset transactions when Reimburse Expenses Through Accounts Payable is selected for expense/travel transactions as well as Integrate to FA Management in TimeTrack Setup Options.

TT-147

When a labor transaction is created in MobileTech and synced, the performance has been enhanced, and all fields are filled as expected.

TT-148

When a travel transaction is created in MobileTech and synced back to TimeTrack, the billing amount is now calculated as expected. This affected users with no billing rate set up in the Invoice Travel Setup window and using standard pricing.

TT-149

If you have TimeTrack setup to allow the modification of pay rates and Use Average Salary Labor Rate is marked in setup, when you create a TimeTrack transaction with a $0 pay rate, the Edit Pay Rate window will no longer attempt to open so that the transaction may now be saved.

TT-150

When a labor transaction is created in MobileTech and synced back to TimeTrack, the Local Tax field is now filled in the WS10702 table as expected.

TT-152

A transaction note created in Excel TimeTrack will now be saved to the JC00501 table when the transaction is committed in TimeTrack.

TT-153

In the TimeTrack Setup Options window, if you’ve marked both:

• Create a GL Journal Entry for Unbilled Transactions
• Create Expense/Travel Transactions Reimburse Through Accounts Payable

The labor unbilled (UN) batches and associated GL transactions are now created as expected. The naming convention is "UN" and then the TimeTrack batch name. The associated GL unbilled transactions are also created.