Click to go to Recent Updates.
Due to the need to maintain certain Registry records in a specific order the Registry's lower pane is no longer sorted automatically when it is saved. Instead, the new Sort Lines button allows the user to resort individual registry entries alphabetically.
To do so:
1. Complete any needed changes to the Registry record.
2. Save (or Add) the Registry record.
3. Click the Sort Lines button.
4. Save the record again to retain the new Sort Order.
Important: The Registry viewer does NOT warn the user about losing unsaved changes if all the user did to a record is push the new SortLines button.
By default, all SAMPro Users are warned if their software is close to expiration. This registry changes the expiration warning so that only the specified Users or members of the specified User Groups are warned. If this registry is not present, all Users will continue to get the expiration warning on login.
Id: sys-expiration-notification
Setting Key: GroupId Setting Value: comma delimited list of User Group Id's
This registry specifies the User Group(s) to be receive the expiration warning. The system will evaluate the User Groups on the User's Main and Additional Groups tabs.
Setting Key: UserId Setting Value: comma delimited list of User Id's
This registry specifies the User or Users who should receive the expiration warning. The system will evaluate the User Groups on the User's Main and Additional Groups tabs.
TIP:
Include the support user login in the list of UserId's to be alerted.
Example:
Id: sys-expiration-notification
Setting Key: GroupId Setting Value: IT,Executive
Setting Key: UserId Setting Value: OfficeMgr,dbasics
In this example, member of the IT and Executive User groups as well as User OfficeMgr and dbasics support user would receive the expiration warning.
When most SAMPro journals are edited, the revised entry's id is appended with a 'tack' number. The original journal entry cannot be edited if it has been replaced with a new entry (with a 'tack' number). In this release, user are warned if they access a journal entry which has been replaced. For example:
WARNING: Purchase Order 123456 has been replaced by 123456-01.
This record cannot be changed.
This warning is designed to prevent the user from wasting time by attempting to make changes to a journal entry record which cannot be saved because it has already been replaced. This new default behavior may be disabled globally or by individual viewer:
Registry Id: sys-ffv-global-settings (or by individual viewer)
Setting Key: DisableCase6552 Setting Value: true
Previously, there was no check to make sure that the path in dbreportfiles directory entry referenced a valid file system directory. In this release:
- If a directory path is found in the Registry, but that path does not exist, an attempt will be made to create that directory.
- If that directory creation fails (or no Registry entry is found) a default path referencing the 'Reports' sub-directory within the SAMPro directory will be used. That directory will be automatically created if needed.
- If all else fails, the path to the SAMPro directory itself will be used. This is what previously happened if the Registry entry was absent.
For installations not running with Intercompany enabled, 'sticky' GL Entity fields in many Journals provided for the setting of the default balance sheet entity.
However, if Intercompany enabled, the 'sticky' behavior is turned off. The following registries have been created to support a global registry key for Default Balance Sheet Entity setting as well as journal-specific override/exception registry keys. These registries are particularly useful for single-company Intercompany new installations.
The following journals are impacted by this registry:
AR Cash Receipts
AR Sales (for manual journal entries)
AP Journal
Bank Deposit Journal
Bank Transfer Journal
Bank Reconciliation Journal
This registry can be set globally in sys-ffv-global-settings or on a journal by journal basis:
Registry Id: sys-ffv-global-settings
OR
Registry Id: sys-viewer-afunctionid (where afunction is replaced by the journal's function Id as listing below).
AR Cash Receipts: sys-viewer-varrcptslst
AR Sales (for manual journal entries): sys-viewer-varslslst
AP Journal: sys-viewer-vapjrnl
Bank Deposit Journal: sys-viewer-vbnkdpstjrnl
Bank Transfer Journal: sys-viewer-vbnktrnsfrjrnl
Bank Reconciliation Journal: sys-viewer-vbnkrcncltnjrnl
Setting Key: UseDefaultBalanceSheetEntity Setting Value: true (default is false)
If this registry is enabled, there are two ways to specify the Default Balance Sheet GL Entity Id:
1. Use the following registry setting that explicitly provides the Id.
2. Derive the GL Entity from the Company record if possible and default that. If the default has been explicitly defined in the following option, it overrules this option.
This registry can be set globally in sys-ffv-global-settings or on a journal by journal basis:
Registry Id: sys-ffv-global-settings (to set globally)
OR
Registry: sys-viewer-afunctionid (where afunction is replaced by the journal's function Id as listed below)
AR Cash Receipts: sys-viewer-varrcptslst
AR Sales (for manual journal entries): sys-viewer-varslslst
AP Journal: sys-viewer-vapjrnl
Bank Deposit Journal: sys-viewer-vbnkdpstjrnl
Bank Transfer Journal: sys-viewer-vbnktrnsfrjrnl
Bank Reconciliation Journal: sys-viewer-vbnkrcncltnjrnl
Setting Key: DefaultBalanceSheetEntity Setting Value: GLEntityId
The Setting Value should be replaced by an appropriate balance sheet GL Entity. If this registry is present it will be used and the system will not attempt to derive is from the Company record.
Extremely large error logs are difficult for programmers to research and time-consuming for support to download. In this release, after a successful logon if the error.log size is more than the maximum size of 1 gigabyte, then the error.log will be renamed as 'error [date/time stamp].log'. Next, the system will send a new 'error' message to the log stating 'error.log archived as whatever the renamed file name is'. This will force creation of a new error.log file. It will also document who did it and what the archived file name is.
The following registry allows the user to override the maximum size for archiving the Error Log.
Id: sys-ffv-global-settings of the registry
Setting Key: ErrorLogMaxSize Setting Value: size in bytes
The default is currently 1 Gigabyte (1073741824 bytes).
Example: Set maximum size of error.log to 250 Meg (a quarter of a gig).
Id: sys-ffv-global-settings of the registry
Setting Key: ErrorLogMaxSize Setting Value: 262144000
User Security 1-3:
These fields are designed for use with certain custom analytics. They are not currently referenced by the SAMPro code.
App Name: Last Session Id:
Reserved for Future Use.
Import / Export Profile Buttons
This release corrects a Key Is Missing error when importing certain older analytics with a missing query name.
When a new report is added to your database, the system automatically creates a new User Defined Function for it so that it can be assigned to the appropriate User Groups. This process was not always reliable in previous versions.
Id: sys-ffv-global-settings
Setting Key: OldPrinterDialog Setting Value: true (default false)
Enabling this setting will display the Windows (OldPrinterDialog screen instead of SAMPro's Printer List when printing a report. This allows the use to select a different paper tray and other functions not supported on the SAMPro printer list.
This may be disabled on a function by function basis by the following:
Id: sys-printer-dialog-funtionid
Setting Key: olddialog Setting Value: false
The system handles existing local report registry oldDialog='' as oldDialog = true to preserve old-style registry settings turning on this functionality.
Note:
When OldPrinterDialog/Olddialog is enabled, the From - To Pages settings in the Report viewer are NOT carried to the Second Windows printer box where it must be set. To print only a few pages of a report, the page number must be entered in the Windows Dialog.
Some users 'print' to a generic text printer; this may generate a file with NO FILENAME EXTENSION instead of paper. In some cases, the file is written to the directory containing the SAMPro executable which clutters up the folder. In this function, 'generic document' refers to these files, not SAMPro Document records. In this function, 'generic document' refers to these files, not SAMPro Document records.
If the following registry entry exists, this new function will move all files with no filename extension from the SAMPro base directory to the Destination Directory specified in the registry. If this registry does not exist, running the function will have no impact on your files. This function designed to be run 'headless' so that it can be scheduled to run as a scheduled event.
If there is an exception list of files in the registry these files will not be moved. If the file already exists in the Destination Directory then a count will be added to the file name before it is stored. Special Characters in File names will be replaced by Underscore before file is moved.
Id: sys-start-smvegnrcdcmnts
Setting Key: DestinationDirectory Setting Value: PathToDestinationDirectory
The Setting Value should provide the full path an existing directory. Start Move Generic Documents will move files with no Filename Extension from the base SAMPro directory to the folder define in this option.
Setting Key: FileExceptions Setting Value: ListOfFilesToIgnore
Some files with no filename extension are used by SAMPro and should be excluded from the move. At this point, LabelRemap and inetlog should be excluded. It is possible that other should also be excluded.
Example:
Setting Key: FileExceptions Setting Value: LabelRemap,inetlog
In previous releases, there was not a way to edit the settings made when you schedule a Report Anywhere report. You have to delete the scheduled report and then re-schedule it from scratch. In this release, the system allows you to easily update, copy or cancel a scheduled report. To do so:
Assess the scheduled report that you wish to change and select the Schedule Report option in the upper left-hand pane. The following new fields will be displayed:
Event Id:
Double-click on the Event Id. This field allows you to select from the list of existing Scheduled Events for this report. Select the Schedule Event for this report that you wish to change.
Process Type:
This field allows you to select what you want done to the selected Event when the OK button is pressed. The 3 choices are:
Create Only - this will create a new Scheduled Event; the currently selected Event will not be modified.
Create/Cancel - this will create a new Scheduled Event and remove the selected Schedule Event selected in the Event Id field.
Update - this option will update the selected Scheduled Event.
When OK is pressed on the Scheduled Report screen, the fields on the Scheduled Event screen will be validated and the Report Range screen displayed. Make any needed changes to any of the Range or other input field. When the report options correctly configured for the new/revised event, click the GO button. Doing so will create/remove/update the scheduled event table based on the process type.
This release refines the functionality used to reprint a DBR report where the server with the original bitmaps was changed (a problem if mapped drivers were NOT specified). In this release, when the original bitmap location no longer exists and the system checks the \bitmaps folder of the SAMPro base directory, and supports bitmap overrides (BitmapOverrideBasedOn=branch) as long as a bitmap= option is NOT in the report registry. However, if the bitmap= option is active, it overrides the override.
Corrects a problem which prevented this function from running in recent versions.
This release corrects a timing issue where SAMPro would attempt to create an archive before the original document is done being scanned / saved. This could result in a 0KB archive file being created.
This release corrects a sporadic 'Runtime error: index: 1 is outside of collection bounds' which showed up in Windows 10 (fresh install) when trying to show an image in a Document record.
Using Attach>Scan now logs the User Id in addition to the date and time.
Start Document Archive Maintenance's option to convert DBR's to PDF's generated PDF'd PO's as portrait instead of landscape in previous releases. The correct orientation is now maintained when a report is converted to PDF.
When Force Archive and Convert to PDF are both flagged, the archived .dbr file is now converted to a PDF. Previously, the file extension was changed but the file remained in .dbr format.
The DBR to PDF function now uses the report's internal bitmap path to set the pdf graphics if available.
This function now puts convertedDBRs in the root of the document\archive\convertedDBRs with subfoldering (YYYY-MM) if it is enabled.
New Field: Days Past to Check PDF Archives
This field controls a new purchase which has been added to this function to look for documents which failed to be converted from XML to PDF's; if any are found, the system will convert them to PDF's.
When this function is run, the system subtracts the NumberOfPastDaysToCheckPDFArchives in the registry from today's date to check all documents created after that date; if the archive file is a PDF file then it checks if it exists. If it doesn't then it checks if there is an XML document for that archive, and if there is it converts it to the PDF Archive.
By default, this field is set to 7: documents created within the last 7 days will be checked to see if they need to be converted to PDF's. If this field is set to 0, no Documents will be checked to set if they are XML files which need to be converted to PDF. The following registry allows the default value of the Days Past to Check PDF Archives field to be adjusted.
Id: sys-start-sdcmntarchvemntnnce
Setting Key: NumberOfPastDaysToCheckPDFArchives Setting Value: numberofdays (default is 7)
This registry entry provides the default value for this field for the manual Start Document Archive Maintenance function and the Start Document Archive Maintenance (Automated) function.
Multi-file Document records allow the user to view the files combined into a single PDF, generating a UserId_ViewDocument.pdf in SAMPro's base directory. This file is deleted when the user logs off for security reasons and to cleanup these extraneous files.
File Location:
Some users employ the Document Viewer to store web addresses instead of actual files. The File Location validation applied in earlier releases now ignores the location validation if the Location field begins with 'http://', 'https://' or "www.'.
If a web address is stored in the File Location field, clicking the View Document button launches a web browser pointing to the web address.
In previous releases, if the global registry option UseConvertedDBRs was set to true, landscape PO's that were archived as PDF's using this functionality were erroneously generated in portrait format. This release corrects this problem.
To correct previously auto-saved PO PDF's
Access the Purchase Order or Print PO Form
Start the Print PO process to display the report (but do not actually print it),
If your PO's are set to autosave, this procedure will resave the PO DBReport and regenerate the PDF correctly.
Quick Attach documents may now be attached to 'locked' journal entries (both the Add and Save button disabled). QA documents are attached immediately when the record is NOT in Add mode.
This release provides a performance enhancement that will be especially noticeable if the save path has many files. In addition, the user will be warned if the Quick Attach Save path does not exists, and will not be allowed to continue. If the Quick Attach New path does not exist, the browser windows will be opened to the SAMPro root directory, and the user will be allowed to continue.
SAMPro's Email form supports an expanded Message field of 1200 characters to allow the entire contents of a Common phase to be included in the Message.
When UseOutlook is enabled in the sys-email registry, this release handles setting the 'To' field for multiple addresses. For example, when emailing from the Collection viewer, the Client's Collections Email containing 0, 1 or 2 addresses (delimited with a comma or a semi-colon) will be inserted in the Outlook form's Email To field.
This release also supports setting Outlook's email 'To' field as well as defaulting pdf'd attachments The revised xmlToPdf.jar file (dated 12017/12/29 or later) is also required.
This release corrects an issue where using the CopyAll registry setting in sys-email resulted in a duplicate email if the email came from escalation event.
New file: XmlToPdf[2019-01-16 Java8-11].jar
This file must be renamed as XmlToPdf.jar in order to be used. This version of the XmlToPdf.jar file supports Java 8-11. It should NOT be installed if Java 7 users will be sending emails from SAMPro. It also creates Monthly folders in the XmlToPDFSent folder (YYYY-MM format) to store all the sent pdfs (and xml and log files, if enabled via registry) from a particular month.
This version of the file also corrects the following which existed in the previous Java 8-11 files:
Email Retry files would fail to include the pdf and leave it in the retry folder.
Single report (no attachments, one section) Password protected pdf's were not properly applying a password.
The functionality of the -d and -v flags (enabled via the global appflagsxmltopdf) has been altered for XmlToPdf[2019-01-03 Java8-11] and above. Previously, the -d flag just deleted the log and xml file. That was changed to include the pdf also at some point. This version makes the -d flag only delete the XML file. The PDF file is now always preserved. The log file is now deleted by default. Adding the -v flag will preserve the log.
Registry Id: sys-ffv-global-settings
Setting Key: appflagsxmltopdf
Setting Value: -d
This value retains the pdf files only. This is the default setting if this registry option appflagsxmltopdf is NOT enabled.
Setting Value:-v
If the Setting Value is set to -v the log, xml and pdf files (if present) will be retained in the base XmlToPDF_Sent folder.
If the MailerMethod is set to Java in the sys-email registry, running with the -v flag set also retain the xml and log files of emails sent without an attachment. This allows the Xml record of scheduled event emails to be retained.
Note that the log files of emails of emails with pdf attaches can be quite large, so the monthly folders should be cleared out on a regular basis.
Setting Value: -d -v
This retains the pdf and log files but not the xml files. If the MailerMethod is set to Java in the sys-email registry, running with the -v and -v flags set also retains the log files of emails sent without an attachment. This allows a log of scheduled event emails and emailed reports to be retained.
Installations with some Java 7 users should rename the XmlToPdf[2017-12-27].jar XmlToPdf.jar in order for it to be used. This file supports the revised W-2 reporting format. It also corrects a file 'cannot find this file' error with UseOutlook enabled for Outlook 2013 and below. This version support Java 7 and 8.
Switching Security from the File>Switch Security Id menu no longer terminates the User's Web sessions.
For SQL Server database users, SAMPro will check for database table change rights and uncommitted transactions to ensure a successful database conversion.
Corrects a 'failed to set read permissions for user' error logging into SAMPro with an SQL 2008 database.
See Customer Note 1.1.1 for a registry to limit software expiration warnings to specific Users/User Groups.
The Dashboard, Point Of Sale, Reports, Scheduled Events and TechAnywhere Events Managers have been refined to better handle recurring events that have been interrupted and need re-scheduled.
This release revises the Warning message that when you leave a record that has changes that have not yet been saved:
WARNING: you have not saved all the changes you made to record ''xxx'',
Click ''Yes'' to return to record ''xxx'' so you can save the changes.
Click ''No'' to continue without saving the changes.
This release corrects sporadic errors encountered when clicking the End key and then editing an Id field that already contains the maximum number of characters.
This release provides improved performance when an Id-lookup list is initially opened (by double-clicking on an Id field or clicking the Lookup button 
) and also when the user selects a different sort order in an Id-lookup list.
The Status Pane (the bar at the bottom of SAMPro record windows) now displays the value of the field that the mouse is hovering over. This enhancement enables the user to view the contents of fields (such as the Job Cost Code Id) which are not fully displayed in the data-entry screen. Note that when the Status Pane displays the 'in focus' field that changes to that field will not be displayed on the Status Pane until the user has tabbed out of it.
On list panes, you can now right click on column titles to apply filters to the column. This includes both record lists and lists displayed via child and parent tabs. On record lists, this saves you the trouble of going back and forth to the range screen to do your filtering.
* To filter a column, right click on the column title and enter the filter on the subsequent popup.
* The list will be redisplayed with the filter applied. The column title will be displayed with the column title and text colors reverses o indicate that a filter on the column is being applied.
The new list pane filtering functionality is very similar to filtering you are used to in range screens and DBAnalytics. The following documentation provides details and examples on using the list pane filtering.
* Filters may be applied to multiple columns.
* To remove a filter, enter a blank filter in the popup.
* To apply a blank filter, enter a filter value of ‘=’ in the popup.
* After a filter is applied, the list will always revert to its original sort order.
* Filters on numeric columns will use numeric comparison operators. Case insensitive String comparison operators will be used on all other columns. This means that for numeric column (but not a String column), a filter of ‘5000’ will match a column value of ‘5,000.00’. A column is deemed numeric if
o All its contents in the list are numeric
o And the entered filter is also numeric.
The filter format is similar to that used by the ‘Find Data’ button The filter consists of one or more ‘or clauses’ separated by commas.
Each ‘or clause’ can be in one of these two formats:
? <not><operator>value
<not> is the optional ‘not operator’ (‘!’)
Valid <operator>s are
‘=’
‘<>’
‘>’
‘>=’
‘<’
‘<=’
If no operator is present, ’=’ is assumed.
Examples:
50 (and the equivalent ‘=50’)
<50
!<50 (equivalent to ‘>=50)
>=2017-01-01
<not><firstValue>_<lastValue>
<not> is the optional ‘not operator’ (‘!’)
The values represent an inclusive range
Example: 2017-01-01_2017-12-31
The list of ‘or clauses’ can be proceeded with a ’global not’ operator ( ‘~’). So while
50,60
will include all lines having a value of 50 or 60 in the column,
~50,60
will include all lines NOT having a value of 50 or 60 in the column.
‘Wild Card’ filters may be used with the actual or implied ‘=’ operators on non-numeric columns. either ‘%’ or ‘*’ may be used as the Wild Card character.
If you enter a column filter that would result in no lines being displayed:
An Error Message will be displayed.
The list will not be updated.
The filter will be restored to its previous value.
When you hover the mouse over a title column, the status pane will now display the following:
A reminder that you can left click on a column to sort the list by that column.
A reminder that you can right click on a column to apply a filter to that column.
In addition, the current value of the filter (if there is one) will be displayed.
The user may now toggle between the Magnify and Line views of the selected child tab line with the key board equivalent Ctrl+Q or Ctrl+q.
When most SAMPro journals are edited, the revised entry's id is usually appended with a 'tack' number. The original journal entry cannot be edited if it has been replaced with a new entry (with a higher 'tack' number). In this release, the user is warned if they access a journal entry which has been replaced. For example, if Purchase Orders are used as controlled documents, the following warning would appear:
WARNING: Purchase Order 123456 has been replaced by 123456-01.
This record cannot be changed.
This warning is designed to prevent the user from wasting time by attempting to make changes to a journal entry record which cannot be saved because it has already been replaced. See Customer Note 1.1.2 for a registry to disable this warning globally or by individual viewer.
This release closes a loophole which allowed more Full User and TechAnywhere (Technician) records to be created than allowed by the Data-Basics license. If the maximum has been exceeded, the User/Technician records cannot be edited except to disable them. If this occurs:
User Record: Flag the Disabled flag on any Full User record not in service.
Technician Record: Active Techs not currently using TechAnywhere should have the Remote Device Type set to None so they will not be included in the TechAnywhere license count. These Technicians will not have access to TechAnywhere.
If additional Full User and/or Technician licenses are still required after disabling unused records, contact your SAMPro account manager.
This release supports Bank Of America Positive Pay Reporting w/ Payee Information. This functionality is enabled via the following registry:
Id: sys-positive-pay
Setting Key: Format Setting Value: BankOfAmericaPayee
The AccountNo and BatchId registry options are also required when this Format is specified.
This release adds Positive Pay reporting for RBC (Royal Bank of Canada). The Check Reference Name is included in the Positive Pay file. The following registry entries are required:
Id: sys-positive-pay-glaccount-glentity
If more than one report will be produced, the Id must include the GL Account (and, optionally, the GL Entity combination) this file will be created for. Note that even if you do not specify an entity, a dash must follow the GL Account Id.
Setting Key: Format Setting Value: RBC
This registry is required for RBC positive pay. The following additional registry options are required for positive pay reporting with Royal Bank of Canada.
Setting Key: RID Setting Value: TransitBatchNo
Enter the Transit/Batch Numbers as specified by your bank. This field defines the Transit/Batch Number (Referenced in Batch Header Record, Transaction Record, Batch Trailer Record).
Setting Key: BatchId Setting Value: ClientNumber
Your Client Number as specified by RBC (Referenced in File Header Record).
Setting Key: AccountNo Setting Value: AccountNumber
Where AccountNumber is replaced by the number of the bank account at your financial institution. This field is referenced in the Batch Header Record, Transaction Record and Batch Trailer Record.
Setting Key: TestFileHeader Setting Value: StringForTestHeader
Enter the StringForTestHeader exactly as specified by RBC in the Setting Value. The system will use the TestFileHeader if the Test box on Report Positive Pay is checked.
Setting Key: ProdFileHeader Setting Value: StringForProdHeader
Enter the StringForProdHeader exactly as specified by RBC in the Setting Value. The system will use the ProdFileHeader setting if the Test box on Report Positive Pay is clear.
The following registry options are required:
Id: sys-positive-pay
Setting Key: Format Setting Value: BBT
Setting Key: AccountNo Setting Value: as provided by the bank
The filename registry is optional. If you do not use this option, file will be system will prompt you to select a name and directory for this file.
This registry supports a custom layout requested by a specific SAMPro user.
Id: sys-positive-pay
Setting Key: Format Setting Value: WellsFargo2
Setting Key: AccountNo Setting Value: as provided by the bank
Setting Key: BatchId Setting Value: format as provided by the bank
Setting Key: filename Setting Value: yourfilename^date^^time^.cvs
The filename format should be used if multiple branches are running this report. The filename should be set to .csv for Wells Fargo2. The file will be created in the working directory where the SAM Pro executable v.exe is running. If you do not use this option, the system will prompt you to select a name and directory for this file.
The ^date^ and ^time^ tokens enable you to automatically imbed the date and time the file is run. This will prevent existing reports from being overwritten.
Corrects a problem where 'cloning' a User Group cleared all selected lines. The settings from the original record are now retained in the newly created one.
The default XmlToPdf.jar file included in this release will support both Java 7 and 8; it is dated 2017-12-29. It supports the revised W-2 reporting format and corrects a file 'cannot find this file' error when running with UseOutlook enabled.
Enhanced Java 8 Functionality: The newest XmlToPdf.jar file (included as XmlToPdf [2018-06-29].jar) requires Java 8. Java 8 must be installed on ALL machines that will do emailing, including one that runs scheduled events. This file supports enhanced error handling to give a number of different status codes based on where the error was encountered and what type of error it was. It logs the error to a new XmlToPdf.log file in the root SAMPro directory. To use this functionality:
Change the name of the default XmlToPdf.jar file to XmlToPdfOUT.jar and then
Copy the XmlToPdf [2018-06-29].jar and change the name of the copy to XmlToPdf.jar
A ‘Comm Link Failure’ (CLF) occurs when SAMPro attempts to access a database on a network connected server and the communication link to that server is inoperable (e.g., ethernet or wireless issues). This release intercepts CLFs on database queries and enters a ‘Recovery Loop’. which tries to re-establish the connection to the database server. When the connection is successfully re-established, SAMPro continues as if nothing has happened. Registry entries are available from Support if this functionality needs to be adjusted.
The revised PDFJoiner.jar file dated 2018-03-14 supports joining secured pdf's, such as invoices received from Vendors. When the Make PDF button is clicked (or other functionality involving a PDF merge is invoked), pdf's that do not require a password to open will be merged. PDF's that do require a password to open will be skipped.
In previous releases, the Custom Fields functionality was label-specific. In other words, if you changed a common label such as "Email Address:" in one viewer (say, the Client record) to "Client Email:" it would appear in all Viewers (e.g, Job, Client Site, etc.) as "Client Email".
In this release the Custom Fields functionality has been enhanced to be viewer-specific with the following exceptions:
Id Field Labels:
Custom Field Labels for record Id's are used wherever that record is reference. For example, if you change the label "Client Id:" to "Customer#" the label Customer# will appear in the Client viewer as well as in the Job viewer.
Labels to the right of the field:
This release does not support the customization of labels that appear to the right of the fields, as is the case with most Checkbox (boolean) fields.
Fields without Standard Labels:
Some fields do not have a standard label defined; these may not be customized.
Address Fields:
Address fields may not be changed via Custom Fields but may be changed for all instances via Start Field Label Remap.
A new v.cus field is required to see this new functionality: contact your Support Representative if needed.
The Equipment Type Id is no longer cleared when the PCR Table Id is updated. This corrects a problem in TechAnywhere and in manual changes to the Site Equipment record.
New Field: Deny TA Edit
This field should be flagged if TechAnywhere Techs should be allowed to see and add charges to this Equipment, but NOT to edit the equipment details. This would typically be used to prevent technicians from filling in important details into the wrong/generic equipment record.
This version supports multiple Certifications per Equipment and Site.
This new tab allows users to list Certifications required to work on the selected Equipment in addition to the Certification listed on the Equipment's Main tab.
When TechFinder is launched from the Dispatch Board or Work Order, all Certifications for the Site and the first piece of Equipment on the Work Order will be listed. When TechFinder is launched from New Call, all Certifications for the selected and Equipment will be listed. This list is prepended with an ampersand & so that only those Techs with all the Certifications listed appear in TechFinder.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
Service Tasks Id:
This field is now used to provide a default for PM's generated from the Master Contract. In previous releases, if a Service Task Id wasn't specified on the Schedule tab of the Master Contract then no Task List was attached to the PM Work Order generated from that line. In this release, if the Service Task Id is blank on the Master Contract, the system now looks to this field instead. This enhancement allows for different Task Lists to be assigned by the Equipment scheduled. If a Service Task List is specified on the Master Contract's Schedule line, it will continue to be used for all Equipment scheduled for from that line.
New Fields: Replacement Equipment Id: Replacement (Date):
These display fields will be completed if the currently selected Equipment Id was replaced by the Replacement Equipment Id on the Replacement date listed from TechAnywhere. If the selected Equipment has NOT been tagged as replaced, these fields well be blank. See Customer Note 19.7 for additional details.
A new Sort Order has been added: ClientSiteEquipmentByIdByBarcode.
New Range Field: Bar Code
This version supports multiple Certifications per Equipment and Site.
This new child tab allows users to list Certifications required to work at the selected Site. It will apply to all Equipment associated with this Site. Certifications which are only applicable to certain Equipment at a site should be added to the Site Equipment's Certifications tab.
When TechFinder is launched from the Dispatch Board or Work Order, all Certifications for the Site and the first piece of Equipment on the Work Order will be listed. When TechFinder is launched from New Call, all Certifications for the selected and Equipment will be listed. This list is prepended with an ampersand & so that only those Techs with all the Certifications listed appear in TechFinder.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
New Fields - Client Site User 6-10:
Five new User fields have been added for use with custom reporting, analytics, etc.
The new Sort Order ClientSitesByIdByRn lets the user sort by the Client Site Rn column. This allows the list to be sort by the newest/oldest record added.
New Field: IVR Instructions
This field is designed for the purpose of IVR instructions for the technician. This field is available for use in escalation emails (using the token ^clntste_ivr^). It is also designed for future use in TechAnywhere.
New Field: Tax Exempt Expiration:
The date the Client's Tax Exempt Certification expires. This field is currently for informational purposes only.
This release corrects a display error in the High Balance Date field on the Client Collections screen. Previously, the most current invoice date always appeared in the High Balance Date field.
The first column of the Past Due summary box has been re-titled '1-30 Days' for clarity. It was previously titled 'Current'.
The "Invoice Date" field in the summary pane has been relabeled as 'High Balance Date' to better describe its meaning.
When this new button is clicked, a customer statement report will be launched with the Client Id completed. By default, Report Customer Statements (RCUSTSTMNT) will be launched, but the following registry option allows a different report to be launched instead.
Id: sys-viewer-vclnt
Setting Key: StatementReportId Setting Value: report function id
Notes List New Field: Obsoleted
In previous releases, the user was unable to access obsoleted Collection notes. In this release, the Collection Notes List displays these notes so they can be accessed if needed.
The Email button has been added to the Collection Notes viewer to allow these Notes to be emailed directly. If any changes have been made to the note, it must be saved and reopened before it can be sent.
Street Address:
This new range allows the user to filter on the first street address line of the Client Mailing Address.
City: State: Zip:
These new ranges allow the user to filter on the City, State and Zip Code fields in the Client Mailing Address.
A new Sort Order has been added, ClientsByClientMailingAddress. The new List displays the Client's City, State, Zip, Street Address and Client Name.
The new Customer PO column has been added to the right-hand side of the list. It references the customer's purchase order associated with the invoice.
The Client Collections Screen's center pane can also be used to view paid invoices by clicking the All/Open Invoices button and then using the right-click list pane filtering to filter on 0.00 in the Amount Due column.
One or both of the following registry entries may be set.
If a AP Journal Entry would be set to Requires Approval via these registries, the system will display the warning that the A/P invoice will require approval. The User will be warned if the invoice amount or PO amount variance exceeds the registry-set limit. If the user has access to AP Approve Held Invoices (Start AP Payment Approved List), the message will also ask the user "Would you like to approve invoice now?"
If the User clicks Yes, they will be prompted to enter 40 characters of text describing the reason for the approval. This text will be written to the Vendor Invoice record's change log.
If the User clicks No, the AP Journal entry will be saved as Requires Approved; it may be approved for payment via the standard Start AP Payment Approved List.
Id: sys-viewer-vapjrnl
Setting Key: RequiresApprovalInvoiceAmount Setting Value: dollarvalue
For example, to require approval for invoices of $10,000 or above:
Setting Key: RequiresApprovalInvoiceAmount Setting Value: 10000
Id: sys-viewer-vapjrnl
Setting Key: RequiresApprovalPOVariance Setting Value: percentvalue
This registry enables an invoice be flagged as Requires Approval if the Invoice Total entered in the AP Journal exceeds the PO Total by the specified percent. Note that previous receipts against the PO are taken into account during this calculation.
For example, to require approval if the AP Journal amount exceeds the PO total by at least 8 percent:
Setting Key: RequiresApprovalPOVariance Setting Value: 8
A new registry setting is available for defaulting the Date Closed range field to the appropriate 'sql=' string so that only open PO's will be considered.
Id: sys-start-seomunvchrdap
Setting Key: OpenPOsOnly Setting Value: true
For example, if this registry is enabled, the following SQL statement will generated in the Closed range when the User selects the October 31, 2016 accounting period:
sql=(prchseordr_dte_clsd = '1900-01-01' or prchseordr_dte_clsd > '2016-10-31')
When IntercompanyEnabled = true, then Balance Sheet GL Entities are universally required. Previously, Start Create EOM Unvouchered AP GL Entries required the following registry to determine a "credit-side" GL Entity. In this release, Credit Side Entities will be specified if EITHER of the following registries is enabled:
Id: sys-start-seomunvchrdap
Setting Key: CreditsByEntity Setting Value: true
-or-
Id: sys-ffv-global-settings
Setting Key: IntercompanyEnabled Setting Value: true
When implemented, this registry allows AP Journal entries to be recorded for Subcontractor PO's when the sub amount vouchered exceeds the amount earned/approved. The user will be warned if the vouchered amount exceeds the approved/earned amount, but will be allowed to created the AP Journal entry.
Id: sys-viewer-vapjrnl
Setting Key: AllowSUBAmountToExceedAmountEarned Setting Value: true (default false)
New Button: 
In previous releases, the user was allowed to change the Tax Group in the AP Journal. However, a warning was displayed user that the tax groups on the detail lines have to be reviewed and manually changed if needed.
In this release, the new Reset Tax On Lines button (if enabled via registry) automates the process of changing the Tax Group on all of the Inventory, General and Subcontractor lines, and automatically adjusting the necessary tax amount on such lines. This eliminates the need to touch every line on the AP Journal. Lines with Copied For Edit checked will be skipped.
Note that this functionality does NOT pertain to the AP Journal Taxes tab; entries on this tab must be deleted priority to clicked the Reset Tax On Lines button. The user will be alerted if any lines appear on the Taxes tab when the button is clicked; these lines must be deleted before proceeding.
A registry is required to enable usage of the Reset Tax On Lines button. This setting should be discussed with your support representative before it is enabled.
Registry Id: sys-viewer-vapjrnl
Setting Key: AllowResetTaxOnLines Setting Value: true (default false)
When enabled, when the AP Journal parent Tax Group Id is changed the user will be alerted that the Reset Tax On Lines button should be pressed to go thru the Inventory, General and Subcontractor lines that have a Tax Group Id and emulate changing that field and updating the tax amount. If any errors occurs during the changing of the tax lines an Error Log will display at the end of the process to tell the user what to fix.
A new registry entry has been added which can be used to control the sort order for the function. For example, this can be used to sort invoices by due date rather than invoice number.
Id: sys-viewer-sapdtetopylst
Setting Key: OrderBy Setting Value: field1,field2,...
Any columns in the Vendor or Vendor Invoice tables should be eligible to be included in the registry entry. (NOTE: default Order By is vndr_alpha, vndr_id, vndrinvce_invce_nmbr)
Example: Sort checklist by Vendor Alpha, Id and Vendor Invoice Payment Date
Id: sys-viewer-sapdtetopylst
Setting Key: OrderBy Setting Value: vndr_alpha,vndr_id,vndrinvce_nxt_pymnt_dte
This release adds support for the following registry options to the AP Manual Check
Id: sys-report-rapchckmnl
Setting Key: DefaultGLBankAccount Setting Value: GLAccountId or
Setting Key: GLBankAccount Setting Value: GLAccountId
Setting Key: DefaultGLBankEntity Setting Value: GLEntityId or
Setting Key: GLBankEntity Setting Value: GLEntityId
The GLBankAccount and DefaultGLBankAccount options provide a means of defaulting the bank account. Use of GLBankAccount and DefaultGLBankAccount should be thought of as mutually exclusive even though the Registry viewer won't prevent it. Do not use both!
Intercompany Note: If the DefaultGLBankAccount option is set, the GL Bank Account specified in the registry defaults when the user selects the Company (or it defaults if only one Company is specified in the database). The Account is cleared if the user selects a different Company for which the registry is not set.
The rules for Entity defaulting and validation are similar to the above description for GL Accounts.
Setting Key: disabledFieldsParent Setting Value: glentty.id
This option is designed to prevent the GL Entity from being inadvertently entered for non-Intercompany SAMPro installations. It should only be enabled if the GL Entity should NEVER be entered when printing this type of check.
By default, Canadian AP checks are set up to show the check amounts as unprotected (no asterisks preceding the dollar amount). The following registry may be enabled to protect the amount with leading asterisks on both the stub and actual check. This registry entry will only affect Canadian AP checks.
Id: sys-report-rapchck
Setting Key: ShowCACheckAmountProtected Setting Value: true
Important: The registry setting PrintDollarSign should be disabled if the registry setting ShowCACheckAmountProtected is invoked.
Some recent versions of Troy printer drivers (and other drivers used to print MICR checks) require that a specific MICR font is specified in the SAMPro check reports. In previous versions this required a customization file to specify the font and font size. In this release, the MICR font may be specified in the registries for Payroll, Accounts Payable and PR Miscellaneous Deductions checks. The true type GnuMICR font is currently recommended for most applications.
Important: The MICR font must be installed in Windows on all computers checks will be run from.
Id: sys-report-apchck
Setting Key: FontForMICR Setting Value: GnuMICR
The Setting Value is case sensitive - be sure that matches the filename of the true type font file. Note that the file extension is NOT included in the Setting Value.
Setting Key: PointSizeForMICR Setting Value: 10 (point size for font default is 10)
Additional registry entries are required for MICR printing: see Help for additional settings for check printing.
This release supports AFT/AP Link Reporting For RBC (Royal Bank of Canada).
Registry to Enable:
Id: sys-aftap-glbankaccountid-
Setting Key: Format Setting Value: RBCAPLink
Setting Key: eol Setting Value: crlf
Note: See Help for Registry AFT AP (Canadian) for additional required entries.
This registry may be enabled to prevent or warn the user if the PO's Voucher Effective dates would precede the PO Receipt date. This registry impact AP Journal entries for Purchase Orders with Inventory or General lines. Credit PO's and dollar-based PO's (with detail added on the Subcontractor tab) are not impacted.
Id: sys-viewer-vapjrnl
Setting Key: EvaluatePOReceiptDates Setting Value: warning or error
If this registry is not present, the user will not be notified if the Last PO Receipt Date precedes the AP Journal's Effective Date.
If a Setting Value of warning is specified, the user will be Warned on adding/saving the entry if the AP Journal's Effective Date precedes the Last PO Receipt date. If the entry is in Add mode, the user will be given the opportunity to change the Effective Date before adding the entry:
WARNING: Effective Date should not precede PO Last Receipt Date
Select YES to use the date or
Select No to correct the date before saving.
If a Setting Value of error is specified, the user will be not be allowed to add the entry until the Effective Date is corrected. If the entry was previously saved, the user will be allowed to edit it as long as the Effective Date is not changed to a value preceding the Last PO Receipt.
Note: AP Journal's Last PO Receipt Date
This display field displays the most recent receipt date of the selected PO.
If the AP Journal is in Add mode and the User has selected from a list of IRJ transactions, this field displays the IRJ's Date Received. NOTE: this refinement ONLY applies during ADD mode because the selected IRJ is not saved with the APJ entry. For edits of existing transactions, the overall last Date Received of all Inventory Receipts will be used.
If items were received on the PO itself, the PO's Release Date will be displayed.
Registry Id: sys-viewer-vapjrnl
Setting Key: DefaultJobByEquipmentId Setting Value: true
By default, the system uses the Job in the Work Order header as the default job for entering WO-related detail in the AP Journal. This release supports the above registry setting to alter this behavior. If this registry entry is enabled (and the referenced WO is NOT preventative maintenance), the system will check to see if there is a default service job in the Equipment header. If so, the Job, Cost Code and Billing item to the from the Equipment will be defaulted instead of from the WO header. If the job info is blank in the equipment record, the system uses the job info in the work order header.
For Preventive Maintenance Work Orders, Job information defaults from the WO header, regardless of whether or not this registry entry is enabled.
If Intercompany is enabled, the balance sheet GL Entity is not 'sticky'. Customer Note 1.14 details the new registries for setting the Default Balance Sheet Entity for this journal or globally.
When entering in invoices in the AP Journal, if the Effective Date and the Period ID are changed, they remain the same for the next journal if there is no PO entered. But if you do enter a PO ID, then the period goes back to the default. The effective date does not change. With the following registry enabled, the Accounting Period and Date will not change from the first journal entry in the session, even if a PO Id is specified.
Registry Id: sys-viewer-vapjrnl
Setting Key: retainDateAndPeriodWhileInSession Setting Value: true (default false)
This release supports the auto-sequencing of the Vendor Id via the following registry. The sequencing will start at 10001 and will automatically skip ahead if a collision is detected. This registry should be discussed with your support representative before it is implemented.
Registry Id: sys-ffv-global-settings
Setting Key: autosequenceVendorid Setting Value: true (default false)
If the registry is true users may not specify the Vendor Id when adding a new record. The Id may be changed once the Vendor record has been added.
This release prevents users from printing AP Checks that are currently being updated by the AP Date to Pay function, preventing possible double-payment of the Vendor Invoice.
The check total amount has been added to the lower right-hand position of the stub(s) of live and EFT checks.
This release corrects sporadic locking issues when various users attempted to print AP Checks for different securities at the same time.
New Field
Check Print: All Checks - Physical Checks - EFT Checks
This field may be used to separate EFT and Physical Checks. The All Checks option prints both Physical and EFT checks. Select Physical Checks to only print live checks, or EFT Checks to live the run to EFT's.
This new report, dated 2015-08-19, excludes PR checks. Only AP and PRMD checks will be listed.
The report revised 2016-06-15 adds ending date header and corrections to page header.
The Report Vendor Payment History (VNDRPYMNTS.rpt) dated 2017-01-26 was revised to display the 1099 Category of each Vendor. You may also filter on the 1099 Category in this report.
This release corrects the landscape formatting of the printed Electronic Payment Register report generated when Report EFT Accounts Payable is run to produce the electronic file for direct deposit.
This release corrects the landscape formatting of the printed Electronic Payment Register report generated when Report AFT Accounts Payable is run to produce the electronic file for direct deposit.
This new function creates the files that is used to submit the T5018s electronically to the CRA (Canadian Revenue Agency).
Important Vendor Record Notes:
The following fields must be set correctly in order to ensure that the T5018s are generated correctly for your individual and corporate Vendors.
Vendor T5018 Tab (may be labeled 1099)
Federal Tax Id:
If this field is set to 9 digits (the Vendor's SIN) the Vendor will be handled as an individual for the report. If this field is 10 digits or more, the Vendor will be handled as a corporation for the report.
T5018 Name(s) (may be labeled 1099 Name(s))
For Vendors who are individuals, the first Name field should be the last name. The second Name field should be the individual's first name.
For Vendors who are corporations, the first Name field should be the legal corporation name. The Name field should be the corporation's DBA name.
Start Date: End Date:
Defines the range of the effective (check) dates of payments to include on this report.
T5018 Limit:
Enter a dollar value to limit the T5018’s to only those Vendors you have paid at least in the time period specified by the Start and End Dates.
Report Type Code:
Enter O for Original or A for Amended.
Submission Reference Id:
This field is user-defined. For example, the submission date may be specified.
When you click Go, the system will display an Audit Report which may be printed for review. Leave the report viewer open.
If all is in order, click the Save button. When you do so, the electronic file to be submitted, T5018E.xml, will be written to the directory defined by the dbreportfiles registry's directory option.
Registry Id: sys-report-rT5018E
Registry Name: Report AP Canadian Electronic T5018s
The following settings define the contact information to be included in the electronic file.
Setting Key: T5018AreaCode Setting Value: 3 digit code
Setting Key: T5018Telephone Setting Value: nnn-nnnn
Setting Key: T5018Extension Setting Value: up to 5 digit extension
The Extension registry may be omitted if it is not needed.
Setting Key: T5018ContactEmail Setting Value: valid email address
Setting Key: T5018ContactPerson Setting Value: Firstname Lastname
The following settings specify your company information which will be included in the electronic file.
Setting Key: T5018PayerAddress1 Setting Value: street address
Setting Key: T5018PayerAddress2 Setting Value: suite number
The Address2 setting may be omitted if it is not needed.
Setting Key: T5018PayerCity Setting Value: city
Setting Key: T5018PayerPostalCode Setting Value: postal code
Setting Key: T5018PayerProvince Setting Value: 2 character province code
Setting Key: T5018TransmitterNumber Setting Value: as specified by the CRA
The revised report (RAPCHEKv72b001.rpt) dated 2017-08-15 includes a new range filter, Check Number to enable printing for a specific check or range of check/eft numbers.
The revised Report AP 1099 (rap1099.rpt) dated 2018-01-09 supports a new registry entry which will set the State EIN. Note that this report may also be titled Report Vendor 1099's.
Id: sys-report-rap1099
Setting Key: EINState Setting Value: company's state ein
This new report function creates the files that is used to submit 1099 files electronically. The report RAP1099EF.rpt must be imported into your data and assigned to the appropriate User Groups and the required registry entries (listed below) implemented.
The following potential issues existing when running the electronic 1099’s:
There is currently no way to process multiple Payer Type ‘A’ records
There is a TIN type field in the Payee Type ‘B’ records which should be set to ‘1’ for an EIN number and ‘2’ for a SSN. This is currently handled by checking the Federal Tax Id field on Vendor's 1099 tab. If the Id has a dash in the 3rd position it is processed as an EIN; otherwise it is considered to be an SSN.
1099 Year:
Defines the year of the effective (check) dates of payments to include on this report.
Prior Year:
Check this box if this report is for the Prior Year.
Test File:
Check this box if this is a Test file.
1099 Limit:
Enter a dollar value to limit the 1099’s to only those Vendors you have paid at least in the time period specified by 1099 Year. This field is also used for prior year reporting.
When you click Go, the system will display a raw dump of the report Leave the report viewer open.
If all is in order, click the Save button and save the report as a Text file. When you do so, the electronic file to be submitted will be written to the directory defined by the dbreportfiles registry's directory option.
Registry Id: sys-report-rap1099ef
Name: Report AP 1099 Electronic File
Setting Key: TextFileFixedWidth Setting Value: 750
This registry defines the width of the output file. It is required.
Registry Id: sys-1099-ef
Name: 1099 Electronic Filing
The following settings define the contact information to be included in the electronic file.
Setting Key: TransmitterName Setting Value: Firstname Lastname
Setting Key: CompanyName Setting Value: Your Company's Name
Setting Key: CompanyAddress Setting Value: Street Address
Setting Key: CompanyCity Setting Value: City
Setting Key: CompanyState Setting Value: 2 Character State
Setting Key: CompanyZip Setting Value: 5 digit zip
Setting Key: CompanyPhone Setting Value: 10 numeric digits, no spaces
Setting Key: ContactName Setting Value: Firstname Lastname
Setting Key: ContactPhone Setting Value: 10 numeric digits, no spaces
Setting Key: ContactEmail Setting Value: Contact's Email
The following entries specify the software vendor generating the electronic file and should be entered as shown below:
Setting Key: VendorName Setting Value: Data-Basics Inc
Setting Key: VendorAddress Setting Value: 600 Broadway Avenue
Setting Key: VendorCity Setting Value: Bedford
Setting Key: VendorState Setting Value: OH
Setting Key: VendorZip Setting Value: 44146
Setting Key: VendorContactName Setting Value: Support
Setting Key: VendorContactPhone Setting Value: 2166635600
The following IRS codes are also required:
Setting Key: TCC Setting Value: Transmitter Control Code Assigned by IRS
Setting Key: AmountCodes Setting Value: 12345678ABCDE
Enter the Setting Value for the AmountCodes exactly as shown above.
The new Report AP Vendor Payment history (RVNDRPYMNTHSTRY.rpt dated 2/15/2018) will show the total amount paid by select vendors based on a beginning and ending date range that is specified by the user when running the report. These two dates correlate with the AP history effective date. The report detail includes the vendor ID, vendor name, city, state, and total amount paid to that vendor.
The Expired Insurance Notice Report (REXPIRDINSRNCE.rpt) dated 2018-05-08 has been updated to provide for bitmap placement (by specifying the new Lines adjustment field on the report range) as well as cosmetic work on the font and alignment. This report also has the functionality to automatically email vendors when their insurance on file has expired.
This release corrects incorrect validation that allowed you to create an AP Journal Entry towards a Cancelled Credit PO. Note that PO's are considered to be Cancelled if the status is 'Cancelled' on the Status tab.
When Intercompany is enabled and a detail line contains a Job Id, any changes to the line's GL Entity are validated to ensure that the new GL Entity belongs to the same company as the Job.
The AP Journal posting logic has been corrected to reverse the sign on JCH Committed Cost $ when posting a PO-SUB line for a Credit Memo.
This release corrects a currency conversion rounding error between the cost written to the Subcontractor, General and CM tabs and the cost being posted to JCH. This resulted in entries being off by pennies preventing them being vouchered. APJ line amounts are now rounded to 2 decimals before summing to be comparable to JCH postings.
This release refines the Manual Check # validation tests so that it ignores check #'s for Check records of type 'EFT'.
Corrects an error -143 from the previous release when a Credit Purchase Order is selected.
Job Cost Categories are not needed if a Job/Work Order is not specified. When loading an APJ entry into the viewer, the Job Cost Category will be cleared if a Job is NOT specified on a detail line.
Postings to the Bank Account specified in the AP Manual Check section ONLY use the GL Entity on the Main tab when InterCompany is enabled via registry. If InterCompany is NOT enabled, the GL Entity is not used for Manual Check / EFT / CC posting and Check records.
A warning is now displayed if a user accesses a journal entry which has been replaced by one with a higher 'tack' number. This warning is designed to prevent the user from wasting time by attempting to make changes to a journal entry record which cannot be saved because it has already been replaced. See Customer Note 1.1.2 for a registry to disable this warning globally or by individual viewer.
This release corrects the calculation of Tax Cost on subsequent AP entries where the PO had previously been partially vouchered.
This release refines the allocation of line item Tax Cost credit amounts to Tax Authorities. A Tax Authority only qualifies for inclusion in the allocation when EITHER of the following is true:
1. The APJ line's Tax Type is Use.
2. The Group Tax Authority line's Job Cost flag is True.
The rules regarding allowed Cost Category Types have changed as follows:
|
AP Journal |
Revised Cost Category Rules |
Old Cost Category Rules |
|
Inventory Tab |
ok: mat, oth, sub, eqp |
ok: mat, oth, sub |
|
General Tab |
ok: mat, oth, sub, eqp |
ok: mat, oth, sub |
|
Subcontractor Tab |
ok: sub, eqp |
ok: sub |
|
Material Returns Tab |
ok: mat, eqp |
ok: mat |
This release corrects a General tab defaulting issue where the Equipment did not default from the Work Order if a PO was NOT specified on the AP Journal header.
The Other Rate Id AND Cost Category Id fields have both been moved to the right of the Job and Job Cost Code. This was done to prevent issues entering manually created lines that need Job Cost info when Cost Category usage restrictions are in place. This change applies to WinII and WinII derived customizations; a new customization file is needed to see the change.
Reversing General lines are now flagged as No Discount to avoid discount calculation issues when the Date Effective is edited.
General items entered on a PO now post the AP General Unit Cost to Inventory History if the cost is changed in AP.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
Changed Field: Revenue
When a subcontractor PO is partially vouchered and the Amount is changed, the Revenue is now correctly recalculated based on the new Amount.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
Changed Field: Invoice #: By default, the system now prevents the same Vendor Invoice from being vouchered multiple times; previously a registry was required for this validation.
New Button:
The new Reset Tax On Lines button (if enabled via registry in Customer Note 3.1.3a) automates the process of changing the Tax Group on all of the Inventory, General and Subcontractor lines, and automatically adjusting the necessary tax amount on such lines.
New Field: Last PO Receipt
This display field displays the most recent receipt date of the selected PO.
If the AP Journal is in Add mode and the User has selected from a list of IRJ transactions, this field will be displayed based on the IRJ's Date Received. WARNING: this refinement ONLY applies during ADD mode because the selected IRJ is not saved with the APJ entry. For edits of existing transactions, the overall last Date Received of all Inventory Receipts will be used.
If items were received on the PO itself, the PO's Release Date will be displayed.
See Customer Note 3.1.8 for a registry to display an Error or Warning when selecting a PO whose Last PO Receipt date precedes the AP Journal's Effecting Date.
Branch Id:
Corrects setting the Branch Id when the global setting BranchOverrideFrom=job is enabled and the Work Order is completed before the Vendor is selected.
New Field - New Line JC Defaults:
Job Id: Job Code: Cost Category:
When the Purchase Order Id is entered, the system will attempt to determine the Purchase Order can be used to provide default values for any new General lines the user might enter. If all detail (Inventory, General and Subcontract) lines on the PO match, the result will be displayed and General line defaulting will be as follows:
If the Job - Cost Code - Cost Category all match - all values default when adding General lines.
If the Job and Cost Code match but the Cost Category doesn't, only the Job and Cost Code default when adding new General lines.
If the Jobs match but the Costs Codes don't, the Job is not defaulted.
If only the Cost Categories match, the Cost Category will be used for defaulting General line.
If a AP Journal Entry would be set to Requires Approval via the registries in Customer Note 3.1.1, the system will display the warning that the A/P invoice will require approval. The User will be warned if the invoice amount or PO amount variance exceeds the registry-set limit. If the user has access to AP Approve Held Invoices (Start AP Payment Approved List), the message will also ask the user "Would you like to approve invoice now?"
If the User clicks Yes, they will be prompted to enter 40 characters of text describing the reason for the approval. This text will be written to the Vendor Invoice record's change log.
If the User clicks No, the AP Journal entry will be saved as Requires Approved; it may be approved for payment via the standard Start AP Payment Approved List.
This new Viewer lists ONLY Vendor (AP and PRMD) checks.
User Group: Since this is a new viewer, access must be assigned to the appropriate User Group(s). Unless the User Group also need access to PR Checks, we recommend turning off access to View Checks.
Unless Checks are being entered as part of the startup process, edits to View Checks (Vendor) should be disabled. We recommend the following settings for the new View Checks (Vendor) viewer.
Id: sys-viewer-vchcklstap
Setting Key: DisabledFieldsParent
Setting Value: gl-bnk: glaccnt.id,glentty.id,chck.nmbr,chck.amnt,chck.rfrnce-nme,chck.dte-chck,chck.type,chck.dscrptn
Setting Key: disabledFieldschild
Setting Value: chcklst.amnt-grss
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
The rules regarding allowed Cost Category Selection Cost Types have changed as follow:
|
Recurring AP Journal |
Revised Cost Category Rules |
Old Cost Category Rules |
|
Recurring Lines Tab |
ok: mat, oth, sub, eqp |
ok: mat, oth, sub |
SAMPro now supports Partial and Final Lien Waiver Processing. This expended functionality supports the generation of Partial and Final Lien Waiver documents for subcontractors following the generation of AP Checks. Both the Job and Vendor must be flagged as Lien Waiver Required before a Purchase Order is generated to implement this enhancement so that the PO's Lien Waiver flag will carry through to the individual Vendor Invoices and AP Checks.
The Lien Waiver Documents generated by the new reports would then be sent to the Contractors for their signatures/notarization.
Vendor - New Field
Lien Waiver Req'd?
This field should be checked if Lien Waivers are required for this Vendor for a Job that also requires Lien Waivers. Lien Waiver Processing is only enabled if both the Vendor and Job require Lien Waivers.
Job - Changed Field
Lien Waiver Req'd?
This field should be checked if Lien Waivers are required for this Job. Note that Lien Waiver Processing will only be enabled if both the Vendor and Job require Lien Waivers. In version 9.0, only the Job's Lien Waiver status was considered.
Purchase Order - Changed Field
Lien Waiver Req'd (below Vendor Id)
This field is displayed from the Vendor record.
Lien Waiver Req'd (to the right of the Job Id)
When BOTH the Job Record's Lien Waiver Required and the Vendor's Lien Waiver Required fields are checked, Purchase Orders for this Job and Vendor will also be flagged as Lien Waiver Required when they are created. If a Work Order referenced in the PO header, the Lien Waiver flag will also be checked if BOTH the Work Order's header Job and the Vendor require Lien Waivers.
The PO's Lien Waiver flag will carry through to individual Vendor Invoices and AP Checks.
AP Journal - Changed Field
Lien Waiver Req'd?
This field will be checked if the PO used to generate it required Lien Waivers.
Vendor Invoice (Internal)
Lien Waiver Req'd?
This field will be checked if the AP Journal used to generate it required Lien Waivers.
AP Check Record (Internal)
Lien Waiver Req'd?
This field will be checked if the AP Journal / Vendor Invoice used to generate it required Lien Waivers.
This report lists Partial Lien Waivers based on the AP Checks which were printed for Lien Waiver Required Vendor Invoices. The Job Name, Site Address, and Client Name will be printed in the left-name Project/Owner section. The Vendor Name, Address, Check Date and the lien waiver Amount will be printed in the right-hand Contractor section.
If this report is set to autosave via registry, it will be attached to the applicable Job, Vendor and Check records.
Beginning Date: Ending Date:
These required fields define the AP Check date range to include when printing the Partial Waivers.
The following ranges may be use to further limit the Partial Lien Waiver report:
Vendor Id:
Enter a Vendor Id to only print Waivers for the specified Lien Waiver Vendor.
Job Id:
Enter a Job Id to only print Waivers for the specified Lien Waiver Job.
Purchase Order Id:
If this field remains blank, the Lien Waiver Amount will reflect all Lien Waiver PO's processed each AP Check. Entering a PO Id (or list of Id's) in this range will limit the Amount listed on the Waiver to that allocated for the specified PO(s).
Vendor Invoice Number:
If this field remains blank, the Lien Waiver's Amount will reflect all Lien Waiver Vendor Invoices processed on each AP Check. Entering a Vendor Invoice Number (or list of numbers) in this range will limit the Amount listed on the Waiver to that allocated for the specified Vendor Invoice(s).
Check Number:
Enter an AP Check Number to only print the Waiver for the specified Check.
Id: sys-report-RLNWVRPRTL
The following settings are recommended for this report. If this report is set to autosave via registry, it will be attached to the applicable Job, Vendor and Check records.
Setting Key: autosave Setting Value: true
Setting Key: autosavefiletype Setting Value: pdf
Setting Key: autosavebysection Setting Value: true
Setting Key: autosavefilename Setting Value: ^sectionkeyvalue^,Partial
When the report is saved, the ^sectionkeyvalue^ token will generate the Job Id followed by the Check Number. The literal Partial will distinguish Partial from Final Waivers.
Setting Key: autosavedirectory Setting Value: full path to directory for Partial Lien Waivers
Setting Key: bitmap Setting Value: full path to bitmap for partial waivers
The Final lien waiver should be printed when it is determined that the check being sent to the Vendor is the last payment being made for work performed on a specific Job.
This report lists Final Lien Waivers based on AP Checks which were printed for Lien Waiver Required Vendor Invoices. The Job Name, Site Address, and Client Name will be printed in the left-name Project/Owner section. The Vendor Name, Address, Check Date and Amount will be printed in the right-hand Contractor section.
If this report is set to autosave via registry, it will be attached to the applicable Job, Vendor and Check records.
Beginning Date: Ending Date:
These fields define the AP Check date range to include when printing the Final Waivers.
The following ranges may be use to further limit the Partial Lien Waiver report:
Vendor Id:
Enter a Vendor Id only print Waivers for the specified Vendor.
Job Id:
Enter a Job Id to only print Waivers for the specified Job.
Purchase Order Id:
If this field remains blank, the Lien Waiver's Amount will reflect all PO's processed on the AP Check. Entering a PO Id (or list of Id's) in this range will limit the Amount listed on the Waiver to that allocated for the specified PO(s).
Vendor Invoice Number:
If this field remains blank, the Lien Waiver's Amount will reflect all Vendor Invoices processed on the AP Check. Entering a Vendor Invoice Number (or list of numbers) in this range will limit the Amount listed on the Waiver to that allocated for the specified Vendor Invoice(s).
Check Number:
Enter an AP Check Number to only print the Waiver for the specified Check.
Id: sys-report-RLNWVRFNL
The following settings are recommended for this report. If this report is set to autosave via registry, it will be attached to the applicable Job, Vendor and Check records.
Setting Key: autosave Setting Value: true
Setting Key: autosavefiletype Setting Value: pdf
Setting Key: autosavebysection Setting Value: true
Setting Key: autosavefilename Setting Value: ^sectionkeyvalue^,Final
When the report is saved, the ^sectionkeyvalue^ token will generate the Job Id followed by the Check Number. The literal Final will distinguish Final from Partial Waivers.
Setting Key: autosavedirectory Setting Value: full path to directory for Lien Waivers
Setting Key: bitmap Setting Value: full path to bitmap for final waivers
New Field - Obsolete?
If this field is checked, the record is considered Obsolete, and it may not be directly specified during data-entry (either by entering the Id or selecting it from a list). Obsoleted records can be edited and the Obsolete option can be cleared when necessary.
New Field: 1 Invoice Per Check?
If this field is flagged, when AP Checks/EFT's are generated for this Vendor, one Check will be printed for each Vendor Invoice.
Important Note on Credit Memos:
Vendor credit memos are separate invoices and an AP Check can't be negative. To process a Credit Memo, temporarily uncheck the I Invoice Per Check field and apply the credit memo to an outstanding invoice or 2, or 3.
This tab is now automatically sorted in descending order by the End Date when the Vendor record is saved. The most recently dated Insurance Entries will appear at the top of the tab so they are easier to review.
A new Sort Order, VendorByNameByAccountNumber has been added. The list displays the Vendor Name and Id, City, State, Address and Account Number (from the Vendor Default tab).
The Vendor's Account Number has been added as a Range field.
New Field: Overhead Jobs Only?
When this box is flagged, direct jobs are excluded and this function will be limited to:
AP entries with no PO
AP entries for PO's with no header Job/WO
AP entries for PO's with an Overhead job in the header
New Range - Job Id:
This range allows you to limit this function to the Job (from the PO header) with which this payment is associated. If you leave this range blank, all eligible entries (subject to other range restrictions) will be selected.
This release prevents users from printing AP Checks that are currently being updated by the AP Date to Pay function, preventing possible double-payment of the Vendor Invoice.
Previously, overpaid invoices appeared on the AP Date-to-Pay list with the amount overpaid erroneously defaulted into the Discount to Take and Retainage to Pay fields. If the user failed to manually correct this, the credit would not happen and there will be inconsistent history postings. This release implements special handling for 'over paid' invoices so that the overpayment is NOT defaulted to the Discount and Retainage fields.
In this release, the Next Pay Amount field will be completed appropriately when the Next Pay Day field is blank (01/01/1900).
In previous releases, cost entered to a Service Compute Job without a work order being referenced "marooned" the cost as unbilled, having never had the opportunity (lacking a WO) to get included and billed on an invoice. The PWP Billing List has been enhanced to include UNBILLED JCH lines for Service Compute Jobs lacking a Work Order reference.
New Field: Check Description:
This field defaults from the Check record. It may be edited by the user to note the reason for the void. If the Check Description field was blank when the Check is voided, the system will continue to default in the Description using the following format: Voided 07/09/2018 01:36:39 PM UserId.
By default, if a Subcontractor PO is auto-generated in New Call, there is no validation as to the Release Date and the Accounting period; today's date and the default Accounting Period are always used on the auto-generated PO unless trumped by the sys-newcall registry option AutoPOPeriodID.
In this release, the following registry entry allows either the Date or Accounting Period to be adjusted to keep them in sync for Purchase Orders generated from New Call only. If this registry is not enabled, the default Accounting Period and today's date will continue to be used. Note: this setting will also be trumped by the sys-newcall registry option AutoPOPeriodID if enabled.
Id: sys-viewer-vprchseordrlst
When the defaulted Release Date and Accounting Period are NOT out-of-sync, NO adjustments are made to the defaulted values when a PO is generated from New Call. The rules noted below are used only when an adjustment is necessary.
Setting Key: AdjustDefaultDateOrPeriod
Setting Value: period
The Accounting Period table is queried for eligible Accounting Periods. To qualify, the period must be Active and its date range must include the defaulted Release Date. When multiple periods are eligible, the one with the smallest Period Id is chosen to become the new Accounting Period for the current transaction. If no eligible period is found, nothing is changed.
Setting Value: date
The Release Date is adjusted to be either the Start Date or the End Date of the defaulted Accounting Period. The Start Date is chosen when the current date is less than the Start Date. The End Date is chosen when the current date is greater than the End Date.
Registry Id: sys-viewer-vprchseordrlst
Setting Key: DefaultJobByEquipmentId Setting Value: true
By default, the system uses the Job in the Work Order header as the default job for entering WO-related detail in the Labor, Purchase Order and AP Journal. This release supports the above registry settings to alter this behavior. If this registry entry is enabled (and the referenced WO is NOT preventative maintenance), the system will check to see if there is a default service job in the equipment header. If so, the Job, Cost Code and Billing item to the from the Equipment will be defaulted instead of from the WO header. If the job info is blank in the equipment record, the system uses the job info in the work order header.
For Preventive Maintenance Work Orders, Job information defaults from the WO header, regardless of whether or not this registry entry is enabled.
Note: a registry option to provide this functionality in the Work Order itself is already supported in sys-viewer-vwrkordr.
Note: registry options to provide this functionality are also available in the Work Order, AP Journal and Labor Journal registries.
When PO's are handled as controlled, the PO number (Id) will be appended with a 'tack' number when it is saved as Changed. At this point, the original PO record cannot be edited since it has been replaced with a new entry (with a 'tack' number). In this release, users are warned if they access a PO entry which has been replaced. For example, if Purchase Orders are used as controlled documents, the following warning would appear:
WARNING: Purchase Order 123456 has been replaced by 123456-01.
This record cannot be changed.
This warning is designed to prevent the user from wasting time by attempting to make changes to a journal entry record which cannot be saved because it has already been replaced. This new default behavior may be disabled globally (sys-ffv-global-settings) or by individual viewer. :
Registry Id: sys-viewer-vprchseordrlst
Setting Key: DisableCase6552 Setting Value: true
The registry that controls how TechAnywhere Purchase Orders are handled has been charged so that the default value is now 'standard'. The standard SAMPro posting method (where job history is written) will now be used by default for PO's generated from TechAnywhere.
In previous releases, the standard method could only be used if COD work orders were NEVER used. In this version, COD and (and other PO changes) are successfully handled since the Billable Quantity and Price updates are posted to the Purchase Order so the standard posting method is now the default.
Registry Id: sys-viewer-vprchseordrlst
Setting Key: TechAnywherePostingStyle Setting Value: standard (default standard)
To return to the old style (where PO's were NOT created with job history) the Setting Value would be set to nonstandard. This is NOT recommended, and should be discussed with your TechAnywhere Support Rep.
The following registry setting for the Purchase Order viewer should be used to provide control over changes to POs that were generated in the field via TechAnywhere. In the absence of this setting, changes are allowed and the user is not alerted.
TechAnywhere Purchase Orders should not be changed while the technician still has control of the work order. It isn’t until the Technician has completed the Work Order that every update is committed to the purchased items (job quantity. Changing a TechAnywhere Purchase Order may have adverse effects during TechAnywhere message posting.
Setting Key: EditTechAnywherePOs Setting Values: warning OR error
Warning Message: "WARNING: This PO was created from TechAnywhere."
Error Message: "This PO was created from TechAnywhere. Changes are not allowed."
The following Ranges have been added to the Purchase Order Report: Vendor Id, WO Id and PO Date Entered.
This release corrects a spurious 'trim blanks' error when the Windows Printer Dialog box is enabled and the 'PrintConfirmationDisabled' registry entry was not enabled.
This release corrects the spurious error "You cannot change this Purchase Order because it was spooled to the printer, but it was not marked as being successfully printed" which could occur if the Print Confirmation was disabled by registry entry.
By default, the PO prints in landscape mode. This option will allow it to print in portrait orientation, and will fit in most typical window envelopes when folded. The following registry option enables the portrait format:
Registry Id: sys-printer-dialog-rpofrm
Setting Key: orientation Setting Value: 1
Important Note on Graphics:
If your company changes to the portrait format from landscape you will need to have new graphics supporting the change in place. The existing landscape graphics should NOT be removed (to supported previously archived reports). The new portrait graphics should have a different name, and the bitmaps option of the sys-report-rpofrm registry should be updated with the new graphics name at the same time when the registry enabling the portrait format is enabled.
This report now gets Security from Location/GL Entity/Company/Security links if Intercompany is enabled. Previously the report would always try to pull the Security from the Location. This system report does not need to be imported.
This release eliminates a sporadic error when saving a PO when Unvouchered A/P box is flagged in the Accounting Period and receipts are made directly on the PO.
When a PO record is loaded or saved, the Job Cost Category will be cleared if a Job is NOT specified on a detail line. This release also tightens Job Cost Category / Job validation.
New Button: Receive
When this button is clicked in a saved PO, the system will open the Inventory Receipts Journal. A new transaction will automatically be started with the PO Id entered. If the PO has unsaved changes, the user will be alerted that the changes must be saved before clicking the Receive button.
This release corrects sporadic Tab Mismatch errors encountered when a PO was created or edited for a foreign currency Vendor (e.g., Currency Id set in the Vendor record).
The user is now warned when the user first accesses a Purchase Order which has been replaced by one with a higher 'tack' number. This warning is designed to prevent the user from wasting time by attempting to make changes to a journal entry record which cannot be saved because it has already been replaced. For example, if Purchase Orders are used as controlled documents, the following warning would appear:
WARNING: Purchase Order 123456 has been replaced by 123456-01.
This record cannot be changed.
See Customer Note 4.1.2 for a registry to disable this warning globally or by individual viewer.
New Field Magnify View: Billable Quantity
This field supports the scenario where a TechAnywhere technician changes the Billable Quantity of an item so that it will be correctly imported into the Work Order. By default this field is set from the Job Quantity Ordered. Previously, the Billable Quantity always defaulted from the Job Quantity Ordered when the Work Order's Import Costs button was clicked.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
The rules regarding allowed Cost Category Selection Types have been changed as follows on this tab:
|
Purchase Order |
Revised Cost Category Rules |
Old Cost Category Rules |
|
Inventory Tab |
ok: mat, oth, eqp |
ok: mat, oth |
New Field Magnify View: Billable Quantity
This field supports the scenario where a TechAnywhere technician changes the Billable Quantity of an item so that it will be correctly imported into the Work Order. By default this field is set from the Job Quantity Ordered. Previously, the Billable Quantity always defaulted from the Job Quantity Ordered when the Work Order's Import Costs button was clicked.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
The rules regarding allowed Cost Category Selection Types have been changed as follows on this tab:
|
Purchase Order |
Revised Cost Category Rules |
Old Cost Category Rules |
|
General Tab |
ok: mat, oth, sub, eqp |
ok: mat, oth, sub |
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
Changing the Job Cost Category Id now defaults the correct GL Account (from the Cost Category's GL Expense Account) into the line. Previously, the GL Account was only set from the Cost Category when it was first selected.
The Job Cost Category validation now allows Equipment types:
|
Purchase Order |
Revised Cost Category Rules |
Old Cost Category Rules |
|
Subcontractor Tab |
ok: oth, sub, eqp |
ok: oth, sub |
New Field (click Magnify) - Order Details:
This display-only field shows data retrieved from the PO Details table generated by a custom PO Analytic. Validation prevents changes to PO-SUB lines that originated in the PO Analytic and have details stored in the PO Detail table.
In this release, the Tax Cost (if applicable) is successfully recomputed when the C.O. Amount is changed on an existing line.
Changed Fields: Tax Cost - Tax Group Id
If a Tax Group flagged as Job Cost is specified on the Purchase Order header, it will now be used to calculate the Tax Cost on the Subcontractor tab: the committed cost will include the tax. When the AP journal is recorded, the tax shown in the Subcontractor will be job costed on top of the value, and would debit the expense account and credit the tax payable account. In previous releases, this functionality was only supported on the Inventory and General tabs, and the PO header Job's (or Work Order's Job) Tax Group was incorrectly referenced on the Subcontractor tab.
The PO's "ordered by" field has been added to the sort option PurchaseOrderByVendorAlphaByIdByDescription after the status column.
In previous releases, If the Work Order's Sub NTE field was completed, a warning was displayed if any of the actual / committed costs on the WO exceeded the Sub NTE. In this release, the message will only be displayed if actual and committed costs associated with PO's (of any kind) exceed the Work Order's Sub/PO NTE value. The message itself has been changed to reflect this:
WARNING: Work Order has a Sub/PO NTE amount of $ #####
This limit is exceeded by its to-date PO costs (actual+committments) of $ #####
This release corrects a problem where this function did not always apply Security to the history reversals lines generated by this function.
This function currently does not support scenarios where a PO has receipts entered in the Inventory Receipts Journal viewer; do so resulted in data being incorrectly updated. In this release, this function now automatically excludes POs that have one or more lines with net IRJ receipts <> zero in case it is inadvertently run where receipts are not exclusively made on the PO.
SAMPro now provides for an option job cost burden to be applied to inventory costs when Inventory Adjustment Journal transactions are generated. To do so, the Burden Rate % field would be completed in one or both of the following places:
In the Inventory Item record
In the Location Rate record (the Apply Location Burden field must be flagged in the applicable Inventory Item Groups)
In addition, the following registry entry is required to specify the income account to be credited with the burden.
Registry Id: sys-viewer-vinvntryadjstmnt
Setting Key: AppliedBurdenGLAccountId Setting Value: gl account id
where the Setting Value specifies the GL Income Account that will be credited with the applied burden.
Registry Id: sys-viewer-vinvntryitm
Setting Key: AllowPriceChangesOnlyByPurchaseAgents
Setting Value: true (default false)
When the above registry is enabled, the following changes to default behavior will be in effect:
Inventory Item Viewer Vendors Tab
Only Users flagged as Purchasing Agents are allowed to directly alter the Price field. When a change is made, a secure note will be created, and the Change Date and User Id on the Detail view will be update
Users NOT flagged as Purchasing Agents are not allowed to delete lines, add lines, or insert with copy. They are allowed to update the Description filed.
Purchase Order Viewer
When this registry is enabled, the Purchase Order will no longer update the Price field on existing line on the Inventory Item's Vendors Tab. When buying an Item from a Vendor for the first time, the PO viewer allows the creation of a new line on the Inventory Item Vendor tab, including the Price field.
This functionality is supported for PO's created from the Purchase Order viewer, QuoteMaster / Quote Manager, Start Generate Purchase Orders, and TechAnywhere.
AP Journal Viewer
When this registry is enabled, the AP Journal will no longer update the Price field on the Inventory Item's Vendors Tab.
The following registry may be used to refine the Compute Corporate Metrics logic so that so that if an item’s on-hand quantity is <=0 AND the transaction will reduce the quantity on hand further, the transaction is NOT used in the turns calculation. This change is incorporated in both the Inventory and Inventory By Location computations.
Id: sys-corporate-metrics
Setting Key: Turns-IncludePositiveOnHandOnly Setting Value: Yes (default No)
Any value beginning with 'Y' or 'T' (upper or lower case) will turn this option on.
The over-receiving 'feature' for items purchased to Stock was added expressly to eliminate the requirement that the PO line had to be changed to match the over-receipt before the IRJ could be recorded. The IRJ posting was made smart enough to make the Qty On Order equal zero in this circumstance. Thus, the user had no reason to go back and sync the PO Qty Ordered with the IRJ Qty Received. Note that over-receiving it NOT allowed on items purchased to jobs.
However, some users may prefer to not allow the over-receipt of stock items. The following registry may be implemented to allow the current warning on the over-receipt to be changed to an error.
Registry Id: sys-viewer-vinvntryrcpt
Setting Key: AllowOverReceiving Setting Value: false (true is default)
Id: sys-viewer-vinvntryadjstmnt
Setting Key: QuantityNotToExceed Setting Value: threshold quantity
When this option is set and the quantity entered exceeds the value, a warning will display: 'Warning: Quantity entered exceeds limit entered in Registry'
Setting Key: UnitCostNotToExceed Setting Value: threshold cost
When this option is set and the unit cost manually entered exceeds the threshold cost value a warning will display: 'Warning: Unit Cost entered exceeds limit entered in Registry.'
New Button: 
This button calls a new report, Report Purchasing Packing Slip (RPOPCKNGSLP.rpt). Note that this report must be installed and assigned to the appropriate user groups.
The report shows received items from the purchase order deriving it's data from the inventory receipts journal. If the report is launched from the Inventory Receipt Journal, the input fields Beginning Date / Ending Date and Inventory Receipt Id be automatically completed by the system. This portrait-style report includes space for a company bitmap (1.25" high by 5.25" wide_. The report includes details such as the Purchase Order Id, Work Order or Job Id (from the PO Main tab Site Name/Address, Date Received. All items received are listed with their quantities received and item description.
In previous releases, the Report Stock Status excluded entries for locations that have a zero on hand amount (imhstry_qntty_on_hnd - imhstry_qntty_rcvd_jb). As an example, if 0 were on hand but 2 on order for stock, it did not show on the report. In this release, if any of the following columns that are on the report have values that could affect the On Hand amount, then the Location should be shown: On-Hand, Allocated, Cust BO, Shop BO, Reorder and On-Order. Note that this is a system report and does not need to be installed in the system.
This release corrects a minor rounding problem resulting in the sum of individual Location Totals not adding up to All Reported Locations Total. This system report does not need to be imported.
When Intercompany is enabled, changes to a To or From line's GL Entity are validated to ensure that the new GL Entity belongs to the same Company as the Job or Location on that same line.
This release properly validates that the From GL Entity is required for Intercompany installations. This corrects an issue where the Security was not always written to IM History on Inventory Adjustments.
This release corrects issues with unbalanced GL entries: extended costs are now correctly rounded instead of being truncated.
When Location adjustments are edited, the GL Account and Entity from the Inventory Item's Group are updated if needed when the Inventory Item is changed.
SAMPro now provides for an option job cost burden to be applied to inventory costs when Inventory Adjustment Journal transactions are generated. A registry entry (see Customer Note 5.1.1) as required to specify the income account to be credited with the burden.
This functionality is currently supported by the following functions and processes that emulate the journal:
Fill Lines Wizard (button in IM Adjustments Journal parent)
Start Work Order Material Pickup
Start Import Inventory Adjustments (custom)
This functionality will be extended to other records/functions in a future release.
New Field: Material Burden Unit Cost
This display-only field will be calculated by the system when the adjustment involves a Job transfer and
The Inventory Item and/or Location has the Burden Rate % field set
The Inventory Item's Inventory Group has the Apply Location Burden? field checked (and the Location's Burden Rate % field is set)
The calculated unit burden is added to the inventory unit cost for Job History, debits COS and credits the registry set income account (see registry below) when the Inventory Adjustment Journal entry is recorded.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
Cost Categories with a Selection Cost Type of Equipment or Material are now supported.
|
Inventory Adjustment Journal |
Revised Cost Category Rules |
Old Cost Category Rules |
|
lnventory Tab |
ok: mat, eqp |
ok: lab, mat, oth, sub |
New Field: Burden Rate %
If this field is completed, it will be will be used to calculate the Unit Burden Cost in Job History when an Inventory Adjustment Journal entry is created which involves a Job / WO transfer. If a Burden Rate % is specified in both the Inventory Item and Location Record, the cumulative Burden Rate total will be applied. A registry entry (Customer Note 5.1.1) specifies the income account to be credited.
New Field - Obsolete:
Obsolete Locations are now displayed at the bottom of the Inventory Item Location tab. The Obsolete flag has been added as a column on the far right of the tab.
The Inventory Item's Extended Description columns have been added to the InventoryItemByGroupByIDByExtendedName Inventory Item list.
A saved range can be added to enable the user to search on the first Extended Description column: sql=(invntryitm_dscrptn_extndd like '%text%')
A CVS file is generated by the BOM-CVS button. The column heading for the Master Inventory Item Description has been changed from "Description" to "MasterDescription" to avoid conflict with the Component Inventory Item Descriptions which also has a column heading of "Description".
New Field: Apply Location Burden?
If this field is checked, the Burden Rate % in the Location record will be used to calculate the Unit Burden Cost in Job History when an Inventory Adjustment Journal entry is created which involves a Job / WO transfer. Note that if a Burden Rate % is specified in both the Inventory Item and Location Record, the cumulative Burden Rate total will be applied. A registry entry (Customer Note 5.1.1) specifies the income account to be credited.
A Cost Category with the Selection Cost Type of Equipment is now supported.
|
Inventory Group |
Revised Cost Category Rules |
Old Cost Category Rules |
|
ok: mat, eqp |
ok: mat |
Import Stock Levels:
When the Import Stock Levels button is clicked, the system validates that a valid Location Id is selected. The user may double-click on the field to select an Id.
New Field: Burden Rate %
If this field is completed AND the Apply Location Burden flag is checked in the Inventory Group, it will be will be used to calculate the Unit Burden Cost in Job History when an Inventory Adjustment Journal entry is created which involves a Job / WO transfer. Note that if a Burden Rate % is specified in both the Inventory Item and Location Record, the cumulative Burden Rate total will be applied. A registry entry (Customer Note 5.1.1) specifies the income account to be credited.
Changed Field - Obsolete?
In addition to the standard references checking, when a user flags the Obsolete field and saves the record, the system will also check to see if there are any references to this Location exist on the Inventory Item's Locations tab. If Inventory Item Tab entries for this Location are found with 0 quantities (On Hand, On Order, Cust BO, Shop BO, Pick and Rejected) the system will ask if you wish to remove these entries:
'Would you like to remove ** items with zero quantities for this Location from the Inventory Item''s Locations tab?'
If you click Yes these lines will be removed; clicking No retains the Inventory Location lines.
This release corrects an issue where some general items not referencing an Other Rate wrote to Job History with Labor as the jchstry_type if the Auto Set Quantity Received button was used.
This release refines the precision in used in cost calculations to correct a problem where received POs could not close at AP voucher due to pennies left committed.
Important: Un-receipted lines are no longer displayed to enforce the requirement that a new Inventory Receipt entry must be created to re-receipt items.
This release corrects a sporadic Tab Mismatch error receiving quantities via the Auto Set Qty Rec'd button.
A warning is now displayed when the user first accesses a Journal entry which has been replaced by one with a higher 'tack' number. This warning is designed to prevent the user from wasting time by attempting to make changes to a journal entry record which cannot be saved because it has already been replaced. See Customer Note 1.1.2 for a registry to disable this warning globally or by individual viewer.
Changed Field: Cost Category
The Job Cost Category validation now allows Equipment Selection Cost Types. The Cost Category field is display-only and is set from the Purchase Order.
|
Inventory Receipts Journal |
Revised Cost Category Rules |
Old Cost Category Rules |
|
Receipts Tab |
ok: mat, oth, sub, eqp |
ok: mat, oth, sub |
PO Id: Vendor Id: Tax Group Id:
These display-only fields default from the Purchase Order's Main tab. Note that the Tax Group Id will only be completed if it is completed in the Purchase Order's Main tab.
Subtotal:
This field displays the expected Vendor Invoice cost total based on this Inventory Receipt.
Tax:
This field displays the tax anticipated to be assessed on vendor's invoice from this Inventory Receipt. This field will ONLY be completed if a Sales Tax Group with "job costed" authorities exists on the Purchase Order Main Tab. If a Tax Group is not specified on the PO Main Tab, or if one is specified but it is NOT "job costed", this field will NOT display the calculated tax.
Total:
Displays the Subtotal + anticipate Tax (if calculated),
This tab may be disabled via the following registry if the cost summary should not be displayed for security reasons. When this registry is in place, the Main tab will be displayed, but the Summary tab will not.
Id: sys-viewer-vinvntryrcpt
Setting Key: ParentTabs Setting Value: Main
In previous releases, if a serialized item was received and then unreceived, its serial number could not be reused. In this release, the following procedure may be employed to re-receive a serialized item:
1. Access the View Lot Master record for the serialized item to be re-received.
Verify that the Quantity on Hand = 0.
Change the Lot Status to Reuse S/N.
Save the record.
2. Create a new Inventory Receipt entry to re-receive the item. You will be warned that the serial number already existed but you will be allowed to save the Inventory Receipt.
Used to import Inventory Adjustment entries from a Database table or a csv file. The import file can be created by a custom barcode program that writes to a database table or manually entered in a spreadsheet.
When this function is run, the date effective (from the .cvs file or database table) is used to get a valid Accounting Period which includes that date. If no valid Accounting Period is found, an error message 'Effective date has no valid Accounting Period' is displayed and the adjustment will be rejected.
Import From: Database - Text CSV File
Choose whether you will be importing from a database table or a csv file.
If you choose to import from a table, the checklist will appear with available (unposted) transactions.
If you choose to import from a csv file, you will browse and choose the file and the checklist will appear.
Select the transactions to be posted and hit Go.
A message will display when the import is complete.
If there are failed transactions, a file containing those transactions will be created and the location of the file will be displayed in a message box. The Email-to address define in the registry will also receive an email. A user needs to go to that file and fix the errors which will be noted in the file.
The user should then run the manual function selecting the csv file, and browse to and choose the fixed file.
Start Import IM Adjustments (Automated) may be used to run this function as a scheduled event:
The import expects a header row; the file must be comma delimited. The specifications are as follows:
Date - date(10) (if blank today's date) format (YYYY-MM-DD)
Transaction Type - char(10) values Loc-to-Loc, Loc-to-Job, Job-to-Job, Job-to-Loc
Inventory Item - char(30)
Serial Number - char(30) (If the use serialized inventory)
Quantity - decimal (12,6)
Unit Cost - decimal (10,3) (ill default from SAMPro if empty
From-Workorder - char(10)
From-Job - char(15)
From-JobCostCode - char(30)
From-JobBillItem - char(15)
From-CostCategory - char(15)
From-Location - char(10)
To-Workorder - char(10)
To-Job - char(15)
To-JobCostCode - char(30)
To-JobBillItem - char(15)
To-CostCategory - char(15)
To-Location - char(10)
If the import is from a database table, see your Support Rep for assistance.
Id: sys-start-simprtimadjstmnt
This registry is used by both Start Import IM Adjustments and Start Import IM Adjustments (Automated).
Importing from a Database Table:
Setting Key: UseDataBase Setting Value: true (default is false)
Use this if you will be importing the entries from a database table.
Importing from a Spreadsheet:
Setting Key: csvfile Setting Value: filename
Specifies the filename to import. This option is required for Start Import IM Adjustments (Automated).
Setting Key: importDirectory Setting Value: directory with import file
Specifies the default directory containing the import file. If an import fails, the system will also use this directory to deposit the failed entry information. This option is required for Start Import IM Adjustments (Automated) and recommended for Start Import IM Adjustments.
Email Failed Records:
Setting Key: email-to Setting Value: email address
Setting Value: email-from Setting Value: email address
The system will automatically email failed record information to the email-to address if the above options are set. Note that both the email-to and email-from entries must be set.
This function now sets the Inventory History Security for Intercompany databases. It also prevents selecting the To and From Locations from different Companies.
Restock Pick List Report: This report is now ordered by the Bin/Location and then the Inventory Id. The Transaction Id and Date Printed has been added to the report.
New Fields
Stocked:
This display field will be checked if the Item is flagged as a Stocked Item.
Reorder Level: Order Up To:
These fields display the current Reorder Level and Order Up To quantities in the Restock To Location.
Inventory Item Name:
This display-only field has been added to help users confirm their stocking list.
When a line is copied and the Inventory Id is changed, the Tax Cost will be re-evaluated for Use Tax jobs. Previously, the Tax Cost was not recomputed from the line it was copied from.
This release corrects a rounding issue that caused the amount expensed/relieved from inventory to differ from Intercompany transactions.
This function now supports the 'creation' of serialized item records (via an Adjustment entry) for Intercompany users.
This release corrects posting to GLH if single company Intercompany is enabled. Previously, this posting was only correct if the AppliedBurdenGLAccountId was enabled.
This release corrects the validation so that Serial Numbers can be added from an Adjustment both for Intercompany (where the "To" line's GL Entity is completed) and non-Intercompany (where the GL Entity should be blank).
Note that the following registry (first implemented in V8.2) must be enabled to allowed the addition of serial items:
Id: sys-viewer-vinvntryadjstmnt
Setting Key: CreateNewSerialNumber Setting Value: true
When this registry is enabled, the adjustment would be made with the Location on the 'To' line completed. The GL Entity would be required on the 'To' line if Intercompany was enabled.
The Inventory module must be enabled in order to access this function.
This viewer now supports Intercompany Security; the Company's Security is correctly written to inventory history.
If Intercompany is enabled, the balance sheet GL Entity is not 'sticky'. Customer Note 1.14 details the new registries for setting the Default Balance Sheet Entity for this journal or globally.
If Intercompany is enabled, the balance sheet GL Entity is not 'sticky'. Customer Note 1.14 details the new registries for setting the Default Balance Sheet Entity for manual entries in this journal or globally.
The DARAGE report (drill down aging) currently uses the Branch specified in the Client Site (of the COP order) for filtering COP orders. The revised report date 2017-09-19 uses the branch specified in the COP order itself and if blank steps defers to the Branch specified in the Site.
The revised report dated 2017-09-18 now includes logic to get the customer's PO# from the Job if PO is blank in Invoice Master or on the Work Order. This corrects a problem where the PO# was not always shown for RININV3 Invoices.
The revised Report AR Aging (DARAGE.rpt) dated 2016-04-05 now gets the PO from the Work Order if the PO is blank in the invoice. It also supports the following enhancements:
New Option: Show Collection Notes
New Option: Age By - Invoice Date - Date Due
Previously, this report always aged by the Invoice Date. The user may now select the option to age by the Date Due instead.
New Range: GL Entity Id
This range allows the user to filter within AR Control Accounts
New Field: Print Statements With Balance Over
The revised report dated 2017-11-15 replaces the Print Zero Balance Statements option with a Print Statements With Balance Over option. By default, this field is blank (zero) so that only positive balance statements will be generated. If a user wants to include zero balance statements they would enter $.01- in the Print Statements with Balance Order field. If a user wants to include credit balance statements they would enter $99999.99- (or some negative value) in the new input field.
The revised report dated 2017-10-06 prints the consolidated invoice description for consolidated invoices.
Report revised 2016-06-16 adds an option to Omit Invoice Description.
This also supports an option to include the PDF'd invoices referenced on the statement as part the PDF version of the statement report. Both job/service based invoices (document category INVOICE) and COP Invoices (document category COPINVOICE) will be included.
If invoices were not originally saved as PDF's, the Start Document Archive Maintenance function may be used to convert these document types to PDF.
Important: Only the PDF'd Statement Includes the Attachments
The .dbr version of the Customer Statement will not display the attached invoices; it does display a list of attached files. Only the PDF'd version of this report includes the 'package' of invoice attachments.
Required File:
A whitesquare.bmp file (available from support) should be added to the directory where your bitmap graphics are stored.
Required Registry:
Id: sys-report-rcuststmnt
Setting Key: IncludeInvoiceDocuments Setting Value: Y (default N)
This option is required to implement the new ' invoice package' functionality.
Setting Key: sectionbackerbitmap Setting Value: Pathname\whitesquare.bmp
This registry is recommended to prevent the invoice bitmap from 'stepping on' the attached documents. The bitmap may be obtained from support. Note that ONLY the bmp version of this file should be installed.
Additional Registries:
These reports support auto emailing. The appropriate registry entries should be made to implement this functionality if invoice documents are included:
Setting Key: emailbysection Setting Value: true
Setting Key: autoemail Setting Value: true
The revised report (RCUSTSTMNTb80v048.rpt) dated 2016-08-26 includes the following new features:
New Range: Client Status
This field defaults to Active so to limit this reports to Client with an Active status. It is recommended that this range remains set to Active if the Print Zero Balance Statements? field is flagged. Setting the Range to Active,Credit Hold will include both Active Customers and those on Credit Hold on the report.
There is a registry associated with this report that controls the text that appears when a zero balance statement shows on the report. By default, 'Zero Dollar Statement' will appear. The following registry overrides this default.
Id: sys-report-RCUSTSTMNT
Setting Key: ZeroBalanceText
Setting Value: Text to appear on report (100 Character Maximum)
Also adds an option to Omit Invoice Description
The revised report dated 2016-08-15 includes the following new features:
New Field: Print Zero Balance Statements?
Flagging this field enables the user to print a zero balance statement for the selected client or clients on this report. Clients with a total outstanding dollar balance in AR History equal to zero will be included on the report, subject to the setting of the other ranges.
New Range: Client Status
This field defaults to Active so to limit this reports to Client with an Active status. It is recommended that this range remains set to Active if the Print Zero Balance Statements? field is flagged. Setting the Range to Active,Credit Hold will include both Active Customers and those on Credit Hold on the report.
There is a registry associated with this report that controls the text that appears when a zero balance statement shows on the report. By default, 'Zero Dollar Statement' will appear. The following registry overrides this default.
Id: sys-report-RCUSTSTMNT2
Setting Key: ZeroBalanceText
Setting Value: Text to appear on report (100 Character Maximum)
This new report (RCCEXPRTN.rpt) dated 2016-10-10 is designed to alert users to upcoming Credit Card expiration dates in the Client Site for payment processing. The report lists the Site Id and Name, Contact Name and Phone Number, Masked Credit Number and Expiration Date for each Site with an expired Credit Card.
Start Date: End Date:
At least one of this fields must be completed.
If the Credit Card Expiration Date falls on or after the Start Date, the Site will be included on the report.
If the Credit Card Expiration Date falls on or before the End Date, the Site will be included on the report.
Client Site Id: Account Manager:
These ranges permit Sites to be filtered by the Site Id or Account Manager.
This report (RCCEXPRTNMSTR.rpt) is designed to alert users to upcoming Credit Card expiration dates in the Master Contract for payment processing. The report lists the Master Contract Id and Description and the associated Masked Credit Number and Expiration Date for each Master Contract with a Credit Card Payment Alias.
Start Date: End Date:
At least one of these fields must be completed.
If the Credit Card Expiration Date falls on or after the Start Date, the Master Contract will be included on the report.
If the Credit Card Expiration Date falls on or before the End Date, the Master Contract will be included on the report.
Master Contract Id: Account Manager:
These ranges permit Sites to be filtered by the Master Contract Id or Account Manager.
This release tightens Job Cost Category / Job validation.
A warning is now displayed when the user first accesses a journal entry which has been replaced by one with a higher 'tack' number. This warning is designed to prevent the user from wasting time by attempting to make changes to a journal entry record which cannot be saved because it has already been replaced. See Customer Note 1.1.2 for a registry to disable this warning globally or by individual viewer.
The 'Receipts Entered' field is correctly updated when lines on the Other Tab are added or deleted.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field (for example, when entering an Unapplied Deposit). The full relationship is validated again when saving the record.
Credit refunds may now be processed via Open Edge / XCharge in the Cash Receipts Journal. To do so:
1. Select a Credit Memo in the AR Cash Receipts Journal, and enter the Total Receipt as a negative number.
2. Verify that the customer has their credit card ready, and then click the Process Payment button.
3. Click through the usual messages; when the x-web portal opens, enter the customer's credit card number (without spaces or dashes) and expiration date and click Submit.
4. If the card is approved, the web portal will display "Approval" in red and the customer's card will be credited with the refund. If it is not approved, check the number and expiration date and try submitting it again.
When an Unapplied Deposit is entered in the AR Cash Receipts journal, the Invoice Master fields are now set as follows:
Currency Id: Defaults from the Client; this field was previously blank.
Effective Date: Defaults from the Cash Receipt's Effective Date; this field was previously blank.
Entry Type: Now set to Unapplied; it was previously set to Unknown
Status: This is now set to Posted; it was previously set to New,
When a database conversion is triggered, previously entered Unapplied Deposits will have their Effective Date, Entry Type and Status reset to the new values.
Note that when entering an Unapplied Deposit, the user should fill out the Description indicating the Invoice that the overpayment was made to if this is known; this will be displayed in AR Cash Receipts Journal's the new Invoice Description column.
New Field - PO#
This new column appears to the right of the Work Order Id column. It displays the customer's Purchase Order specified on the Work Order's PO# field.
New Field - Invoice Description:
The Invoice Description for each Invoice, CM or Unapplied Payment is displayed in this new column on the right-hand side of the list.
This release employs the new list filtering functionality (see Customer Note 1.9.3) in the AR Cash Receipts Journal so that the user can easily filter on the invoices to be paid. To use this functionality in the Cash Receipts Journal:
Enter the Client Id and tab out of the field.
Right-click on the column title in the Open Invoices list that you wish to filter on.
When the Column Filter popup appears, enter an appropriate filter for the selected column and click OK to apply the filter.
More that one filter may be applied if needed. The Running Balance on the Open Invoice List is updated after column filters are applied to the list.
When Open Invoice list has been filtered to match the customer's payment, click the Auto-Fill Transactions button. Only the invoices in the filtered list will be selected.
In previous releases, if a customer paid the same invoice twice, there was no good way to apply the payment to the original invoice. In this release, a registry entry may be implemented to enable the clone function in the AR Cash Receipts Journal to do so.
Id: sys-viewer-varrcptslst
Setting Key: isOkToCloneRecord Setting Value: true (default is false)
Note that Cloning is NOT allowed if NewReversing is enabled in the AR Cash Receipts Journal.
1. Access the original AR Cash Receipt you wish to copy.
2. On the menu at the top of the viewer, select Record > Clone Record.
3. The system will copy the original receipt, clearing the Check Number and Credit Card fields.
4. Enter the new Check Number, Accounting Period, Effective Date and other fields as needed and Add the new record. AR History will show the additional payment to the specified invoice.
This release tightens Job Cost Category / Job validation.
A warning is now displayed when the user first accesses a journal entry which has been replaced by one with a higher 'tack' number. This warning is designed to prevent the user from wasting time by attempting to make changes to a journal entry record which cannot be saved because it has already been replaced. See Customer Note 1.1.2 for a registry to disable this warning globally or by individual viewer.
This release displays the following warning when the user elects to create a credit memo from an existing Sales Journal transaction that includes sales tax. It is important that users manually update lines if a partial credit will be taken.
WARNING: This transaction includes Sales Tax.
It is your responsibility to view and manually adjust each Tax line if needed. Use the magnified view of each Tax line to make all necessary adjustments to the Tax Base, Invoice Amount, etc.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) when saving the record or tabbing out of the Cost Code field.
Formatting configurations within the Avalara import files for certain states may require manual updates to Sales Tax Authorities/Groups following the update. The following enhancements have been made to manage some of the tax anomalies within the Avalara data, and to alert the user to any potential manual changes that may be required.
1. When the Go button is pressed to import an Avalara tax file, validation has been added to show any anomalies in the data about to be imported. When anomalies are found 2 workspaces and a message box will appear. These workspace reports are provided for the users to review the integrity of the data.
The first workspace report gives the Authority Id, Tax Type, Tax Rate and Count. Count is the number of records found in the Avalara import file for that Authority’s Tax Rate.
The second workspace report lists Authority Id, Authority Name, Tax Rate, Tax Type and Signature. The signature shows the zip code and Authority Id’s found with a 0% tax rate.
2. We suggest printing these workspaces before continuing; this will provide you with the information needed if manual adjustments must be made.
3. When the data is imported, if the system finds a state, county or local tax that changes to a zero rate, the system will attempt to create a new tax authorities with a 'z' added to the Id. This will result in a new Sales Tax Group being generated. These new Sales Tax Groups must be added to Jobs as needed.
This release corrects a problem encountered when Server name includes the backslash character.
This release supports an alternative method of computing sales tax on AR Invoices using the Avalara Web Service Integration instead of SAMPro's internal computations. This functionality is currently supported for Sales Tax and Tax Exempt invoices, but not for Use tax computation. An advantage of using Avalara is that they will provide the tax reporting to supported districts.
After obtaining your license and credentials from Avalara, the following registry must be set to enable the Avalara Web Integration. It is required that testing in a 'sandbox' test system be conducted before running live.
Avalara has a field labeled Reference Code that is the functional equivalent of a SAMPro user-defined field. That field is now used to hold the WO Id, Job Id, SAMPro Version No and Function.
Registry Id: sys-ffv-global-settings
Setting Key: UseExternalTaxService Setting Value: true
This registry is the master switch to enable the use of the Avalara Web Integration for tax computation instead of SAMPro's internal tax is computation. If it is set to false, the Site Address validation may still be conducted provided that the Avalara Account information is properly defined.
Setting Key: TaxServiceProvider Setting Value: Avalara
This registry specifies that the Avalara Web Service Integration is used for the tax computation. I exists to support alternatives to Avalara in the future.
Registry Id: sys-avalara (this registry supports via sys-avalara-securityid entries)
Setting Key: ProductionEnvironment Setting Value: true (default is false)
This option is set to true if actual live is being sent. It should be set to false if this data is being used for 'sandbox' testing.
Setting Key: Account Setting Value: as provided by Avalara
Setting Key: License Setting Value: as provided by Avalara
Setting Key: CompanyCode Setting Value: as provided by Avalara
The Setting Values for the Account, License and CompanyCode keys are created during Avalara setup. The CompanyCode setting supports Intercompany configurations; it is passed with each call to Avalara.
Setting Key: OriginAddressLine1 Setting Value: street address
The origin or ship-from street address.
Setting Key: OriginAddressCity Setting Value: city
The origin or ship-from city.
Setting Key: OriginAddressState Setting Value: 2 character state code
The origin or ship-from state or province two character abbreviation.
Setting Key: OriginAddressPostalCode Setting Value: postal/zip code
The origin or ship-from Postal Code. Use the: five digit ZIP Code (12345), nine digit ZIP+4 Code (12345-6789) or six character Canadian Postal Code (A1B 2C3)
Setting Key: TaxAuthorityGLAccountId Setting Value: A valid GL Account Id
The sales tax liability account to be credited. Double-click on this field to select from a list of GL Accounts. This registry may be overridden on a state by state basis as defined in the following option.
Setting Key: TaxAuthorityGLAccountId~StateCode Setting Value: A valid GL Account Id
Example: To specify a different GL Account for Ohio invoices:
Setting Key: TaxAuthorityGLAccountId~OH Setting Value: 201500
Setting Key: DefaultExemptEntityCode Setting Value: G (or as defined by Avalara)
NOTE: See Customer Note 6.6.3e for a registry to enable Job-Specific Exempt Codes.
Setting Key: FixedFeeTaxableTaxCode Setting Value: Avalara Tax Code
Setting Key: FixedFeeNonTaxableTaxCode Setting Value: Avalara Tax Code
Setting Key: FixedFeeExemptTaxCode Setting Value: Avalara Tax Code
The above registry settings specify the appropriate default Avalara Tax Code to use for Fixed Fee Billing Items. They may be trumped by the Avalara Tax Code in the Job Billing Item.
This enhancement supports the optional specification of Job Billing Item-specific Avalara Tax Codes If the following registry is enabled it is used to switch between the two methods of determining the appropriate Avalara Tax Code:
a) Fixed Fee Avalara Tax Codes referenced in the sys-avalara registry;
b) Avalara Tax Codes in the Job Billing Item User field defined in the registry below.
This information will be referenced in the Record Billing Adjustments function when the user pushes the Compute Taxes button.
Id: sys-avalara
Setting Key: FixedFeeTaxCodeUserField Setting Value: integer from 1 to 5
The Setting Value specifies which Job Billing Item User field should contain the Avalara Tax Code for Fixed Fee Job Billing Items. If entered, it trumps all other Fixed Fee-based Tax Codes from the Avalara registry.
Tip: Job Billing Item User Field Referenced by FixedFeeTaxCodeUserField
It is strongly recommended that the Custom Fields functionality is used to relabel the applicable Job Billing Item User field as "Avalara Tax Code: ". The appropriate Custom Field Values should also be set to the appropriate 8 or 2 character code (as specified by Avalara).
This release offers an option (highly recommended) to disable calls to the external tax service in situations where Use Tax is being calculated. When disabled, Use Tax computations are done with SAMPro and no external call is made.
Id: sys-ffv-global-settings
Setting Key: UseExternalTaxServiceForUseTax Setting Value: false (default is true)
This release supports optional registry settings that enable company-specific settings within a multi-tenant database (Intercompany).
Company-specific settings provide replacement values for any standard Avalara setting found in the sys-avalara registry. It is NOT necessary to completely define all settings in the company-specific registry. You only need to include those that are different from the standard (sys-avalara) settings. This allows different Avalara Account and License numbers to be specified, or for the Avalara Web functionality to be disabled for one or more Companies within the SAMPro database.
Registry Id is formatted as sys-avalara-company:CompanyId
Example: Disable Tax Service for Company 01:
Id: sys-avalara-company:01
Setting Key: TaxServiceDisabled Setting Value: true
Example: Specify Different License and Account Number for Company 02
Note that this registry assumes that the ProductionEnvironment, CompanyCode and OriginAddress options are set in the base sys-avalara registry.
Id: sys-avalara-company:02
Setting Key: Account Setting Value: 123456789
Setting Key: License Setting Value: ABC123456789
In previous releases, all exempt jobs used the sys-avalara registry setting for DefaultExemptEntityCode. In this release, an option allows for job-specific Exempt Entity Codes using the following registry AND by setting the appropriate Job User Field.
Registry Id: sys-avalara
Setting Key: ExemptEntityCodeUserField Setting Value: JobUserFieldNumber
Example: Use Job User field 10 to provide specify the GL Entity Id that overrides the GL Entity specified by the DefaultExemptEntityCode registry option:
Setting Key: ExemptEntityCodeUserField Setting Value: 10
Setting Key: DefaultExemptEntityCode Setting Value: G
User:
A SAMPro Special User must be set up to manage the handshake between SAMPro and the Avalara Web Service Integration. This User Id and Password must both be set to taxservice.
Job Cost Category:
Job Cost Category Group: Avalara
Avalara Tax Code:
Service Invoice Job Cost Categories should have this field completed if the Avalara-defined default value should not be used.
Tip: Avalara Tax Code:
It is strongly recommended that the Custom Fields functionality is used to specify the valid codes (as specified by Avalara).
Job Cost Category Group:
A Job Cost Category Group should be created with the Id of Avalara.
Job:
Client Site Id:
A Job that is not Site-specific is NOT eligible for Avalara tax calculations. This applies to both service and progress billing methodologies. The Tax Group must be specified in the Job when invoicing through Record Billing Adjustment.
Sales Tax Group:
If this Group was created in SAMPro or via the Import Sales Tax (Avalara) SAMPro's internal sales tax processing will be used to generate sales or use tax on invoices for this job. If this field is blank, or it contains a Sales Tax Group generated by a call to the Avatax Web Service, the Sales Tax (or Exempt Amount) will computed via the Avalara Web Integration. The Tax Group must be specified in the Job when invoicing through Record Billing Adjustment.
If the Sales Tax Group is blank and the Avalara Web Integration is enabled, clicking this button will make a call to Avalara to set the correct Sales Tax Group for invoicing this Sales or Exempt Job. Note that the Sales Tax Group is required for Progress billed Jobs since the Sales Tax Group must be completed in order to access Record Billing Adjustments.
Client Site:
If the Avalara Web Integration is enabled, clicking this button will make a call to Avalara to validate that Work Site Address is correctly configured so that the correct Sales Tax Authority Group can be determined when invoicing.
The following files compatible with the v.exe SAMPro image must reside in the same directory:
vdevw.exe.manifest
v.exe.manifest
SamproNetFramework.dll
Newtonsoft.Json.dll
Data-Basics.Avalara.Net (Folder and contents)
This function allows validation without having the UseExternalTaxService setting turned on. This allows authentication of the configuration (sys-avalara) prior to enabling live integration.
When using the Avalara Web Service, a new workspace may pop up before the check list is displayed. It relays to the user any issues reported by Avalara. WO/Jobs with errors will still show in the check list but can't be selected for billing.
1. A Job that is not Site-specific is NOT eligible for Avalara tax calculations. This applies to both service and progress billing methodologies. The Tax Group must be specified in the Job when invoicing through Record Billing Adjustment.
2. Better Avalara-based error handling has been implemented in the service invoicing process. A new workspace pops up before the check list is displayed. It relays to the user any issues reported by Avalara. WO/Jobs with errors will still show in the check list but can't be selected for billing.
3. Avalara has a field labeled Reference Code that is the functional equivalent of a SAMPro user-defined field. That field is now used to hold the WO Id, Job Id, SAMPro Version No and Function.
SAMPro now supports Electronic Payments credit card processing as well as OpenEdge. Data-Basics works with USAePay as the middleman to Electronic Payment (the company that SAMPro users would sign up with).
1. To enable this functionality in SAMPro, you must first set up an account with Electronic Payments. Once you have done an API Key and PIN number must be generated for when you set up your SAMPro registries.
Instructions for generating an API PIN/Key:
Log into EP's customer merchant console (Vault Gateway).
Under Settings, click API Keys (If API Keys option is missing, contact EPI support).
Click Add API Key on upper right.
Name = Databasics
PIN = any random 4 digit key you feel like typing (remember this for registry)
Click Save on lower right. After saving, it will auto-generate an API Key. Use this for the registry.
2. SamproSecureCommunication.war must be installed in Glassfish to enable this functionality. If your firm does not already have a Glassfish server installed (for DBAnalytics or TechAnywhere) contact your support representative to set this up.
3. It is recommended that you create a new Payment Type record with the Id set to EPCreditCard and the GL Bank Account set to the appropriate bank or sweep account for Electronic Payments. This will be used for recurring payment processing.
4. Complete the registry entries listed below.
5. We recommend testing this functionality in your sandbox first. When you go life with this functionality, test with a company credit card before using for customers.
Registry ID: sys-ffv-global-settings
Setting Key: DefaultPaymentProcessor Setting Value: EP
This registry is required to specify Electronic Payments as the payment processor, If this registry is absent, Open Edge (OE) is assumed to be the default processor.
Registry Id: sys-payment-processor-ep
Setting Key: Server Setting Value: FILL IN SERVER NAME HERE
This registry specifies your Glassfish server.
Setting Key: Port Setting Value: FILL IN GLASSFISH PORT
Sandbox:
Setting Key: URL Setting Value: https://sandbox.usaepay.com/api/v2/transactions
Live:
Setting Key: URL Setting Value: https://usaepay.com/api/v2/transactions
Setting Key: APIPin Setting Value: enter pin provided by EP
Enter the API Pin provided specified for your firm in Electronic Payments (see Electronic Payments Setup above).
Setting Key: APIKey Setting Value: enter key provided by EP
Enter the API Key provided for your firm by Electronic Payments .
Setting Key: content-type Setting Value: application/json
This entry is required and must be entered as shown above.
Setting Key: PaymentProcessor Setting Value: SamproSecureCommunication/SSL
This entry is required and must be entered as shown above.
Setting Key: Directory Setting Value: paymentProcessing
This entry specifies a subdirectory the base SAMPro directory that is used to for Electronic Payment logs.
Setting Key: PMPaymentBillingCode Setting Value: enter a valid payment type id
This registry defines the Payment Type to use with EP credit card processing. This Payment Type must specify the G/L Bank Account to use for auto pay PM Billings (e.g, EPCreditCard).
This button establishes a Payment Alias with OpenEdge or Electronic Payments if this functionality is implemented in your system. This Alias will be used when PM Invoices are generated to automatically bill the customer's credit card. The system will post successfully paid billings to the Sales Journal as paid and generate the appropriate AR Cash Receipts Journal Entry. The Alias may be set in the Client Site record or the Master Contract Site List tab.
1.Verify that the customer has their credit card ready, and then click this button to enter the customer's credit card information.
2. SAMPro will open a 'Please Enter Credit Card Information' prompter box. Enter the customer's credit card number (without spaces or dashes), expiration date and CVC security code. The Pre Auth Amount field will be set to $1.00 to ensure that the credit card is valid. Click OK to continue.
3. A progress bar will appear as the pre-authorization is processed. If the card is not approved, an error with the reason will be displayed (e.g, "Credit Card has expired). Check the number and expiration date and try submitting it again.
4. When the card is approved, the system will write the Alias back to the Payment Alias field, and complete the CC Masked Account and Expiration Date fields for future reference. A secure note detailing the transaction will be attached to the Master Contract record.
5. Save the Client Site.
Payment Alias:
This field is completed by the system when a Payment Alias is successfully generated by OpenEdge or Electronic Payments via the Payment Alias button. The Payment Alias may be cleared by manually by blanking the field. This would be done if the client changed their mind and did not wish to have their recurring PM's paid via credit card. Validation also prevents the user from manually changing this field to a non-blank value; this field may only be set via the Payment Alias button.
CC Masked Account (first four and last four digits of the credit card)
CC Expiration Date CC Trx Id:
These display fields are completed when an Alias is successfully generated by the credit card processor. Note that Electronic Payments list the first four and last four digits; Open Edge lists only the last four.
The Payment Alias button in the Magnify view of the Site List tab supports Electronic Payment processing as described in the Client Site above.
If you have established an account with Electronic Payments and enabled the appropriate registries, you may process a credit card payment or refund in the AR Cash Receipts Journal.
1. If you use a different sweep account for Electronic Payments receipts, change the Bank Account on the GL tab.
2. On the Main tab, select Invoice or Invoices that the customer wishes to pay for.
3. Enter the Discount (if any) and Total Receipt; this is the amount that will be processed on the credit card.
4. Verify that the customer has their credit card ready, and then click the Process Payment button.
5. SAMPro will open a 'Please Enter Credit Card Information' prompter box. Enter the customer's credit card number (without spaces or dashes), expiration date and CVC security code and click OK.
6 A progress bar will appear as the payment is processed. If the card is not approved,an error with the reason will be displayed (e.g, "Credit Card has expired). . Check the number and expiration date and try submitting it again.
7. When the payment is approved, the system will write the Approval Code back to the Check Number field, and complete the CC Masked Account field for future reference. A secure note will be added to the journal entry detailing the transaction.
8. When preparing to enter the next Cash Receipt, remember to set the GL Bank Account to the appropriate value.
Note: For Cash Receipt Transactions, SAMPro will also send the SAMPro user ID to column "User ID" of export, and sent the User Def 1 to the Client Id.
Electronic Payment Returns:
By default, Electronic Payments does NOT process returns. In order to do so, the Return option must be enabled in the Merchant Console.
1. Select a Credit Memo in the AR Cash Receipts Journal, and enter the Total Receipt as a negative number.
2. Verify that the customer has their credit card ready, and then click the Process Payment button.
3. When the 'Please Enter Credit Card Information' prompter box appears, enter the customer's credit card number (without spaces or dashes), expiration date and CVC security code and click OK.
4. If the card is approved, the customer's card will be credited with the refund. If it is not approved, check the number and expiration date and try submitting it again.
A Work Breakdown Structure (WBS) provides a means of decomposing a construction project into smaller components that organizes the team's work into manageable sections. In SAMPro, the following records are available for the categorization of time, materials and other expenses of a Job.
This button launches the WBS/Budget import function for construction billing from the Job record's Budget Entry tab. When launched, it imports a file or reads a database table looking for data that hasn’t been previously imported. When found, if budget information for the job exists, the user will be given the option to replace the existing WBS/Budget information or append the new data to the existing WBS/Budget.
The WBS Configurator analytic allows the Project Manager to re-align Cost Codes and Billing Items. When this happens, Job History Billing Item may need to get reset. This functionality has been extended to the Job Viewer's WBS Import button. When this button is clicked, the Compute JCH Unbilled Revenue is automatically run so that when a Job Billing Item is created or updated the Cost Code and Billing Items will be re-aligned if needed.
If no budget exists, the system will create new Job Cost Codes based on the WBS information provided and create job cost budget entries for the associated costs.
If a budget exists and “append” is selected, the system will create any new Job Cost Codes found in the data and create job cost budget entries for the associated costs.
If a budget exists and “replace” is selected, the system will delete all Job Cost Codes (that don’t have actual costs posted in JC History), delete all existing job budget entries, mark the date closed on any “orphaned” (has actual cost) Job Cost Codes and then create new Job Cost Codes based on the WBS information provided and create job cost budget entries for the associated costs.
The Import will clear the Cost Code's Date Completed when the following conditions are true:
1. Cost Code record already exists in SAMPro.
2. The existing Cost Code record has no budget prior to the import.
When the WBS Import creates a new Cost Code, the defaulting of its Work Type is as follows: Set the Cost Code's Work Type to Field only if both the Skill and Discipline both have Work Types of Field. Otherwise, the Cost Code has its Work Type set to Office.
When creating new Cost Codes, the system will set the Certified PR flag to True whenever the Cost Code work type is set to Field. The Cost Category Usage Filter from the Discipline User2 field when creating new Cost Codes.
For new Cost Codes determined to be of type Field:
When the Job's CIP Discount % is not zero, set the Cost Code's CIP Discount flag equal to checked
Set the Cost Code's Certified PR Report flag equal to checked
Set the CIP Discount flag to checked
When the WBS has changed, 'orphaned' Job Cost Codes will have their Date Closed set so then can no longer be used for data entry.
Unique Job Cost Codes Id's defined in the import will specify levels 1-4 of the WBS Structure to ensure data entry consistency. The spreadsheet structure includes a header line. The columns are defined as follows:
Column 1: Cost Code Id
Column 2: Cost Code Name
Column 3: Bld/Floor (Cost Code Level 1)
Column 4: Area (Cost Code Level 2)
Column 5: Discipline
Column 6: Skill
If needed Job Billing Items will also be created during the import using the Standard Schedule of Values (see Customer Note 7.3). If a Billing Item cannot be determined during the import and a combination is not found in the SoV table, the system will create and set the Billing Item Id to a default value “Unassigned”.
When the Job's Contract Type is Lump Sum, set the Billing Item's Fixed Fee Billing flag equal to True.
When the Job's Contract Type is GMP*, set the Billing Item's Include in GMP flag equal to True.
The Billing Item Ok to Bill, Fixed Fee Billing, and Include in GMP flags will be set based on the Job Contract Type as follows:
Unknown: Ok to Bill = blank, Fixed Fee = blank, GMP = blank
Lump Sum: Ok to Bill = checked, Fixed Fee = checked, GMP = blank
T&M: Ok to Bill = checked, Fixed Fee = blank, GMP = blank
GMP Cost Plus: Ok to Bill = checked, Fixed Fee = blank, = checked
GMP Cost Plus: Ok to Bill = checked, Fixed Fee = blank, GMP = checked
This option should ONLY be implemented if the WBS Configurator/Import process is being used to import Job Budget Entry child lines. Without this registry setting, the Budget Entry child posts like other 'journals'. It makes new plus entries and offsets them with reversing entries to achieve the desired 'net effect'. With this registry setting, all Budget Entry Job History is completely replaced (deleted) by new lines posted from the child rows.
Registry Id: sys-viewer-vjb
Setting Key: NoReversing
Setting Value: true {Default is false}
The following registry entries are required.
Registry Id: sys-viewer-vjb
Setting Key: ImportWBSGLAccount Setting Value: GLAccountId
This field should specify the value to be set in the Cost Code's GL Income Account.
Registry Id: sys-viewer-vjbbllngitm
The following default values are needed for constructing new Billing Item records during the WBS Import. Please implement the following:
Setting Key: NewBIReportId Setting Value: Report Id (rprt_id) from Report table
Setting Key: NewBIReportQueryId Setting Value: Report Query Id (rprtqry_id) from Report Query table
These fields specify the Invoice Report and Query (Format) setting for Billing Items created during the import.
Setting Key: NewBIRetainage% Setting Value: Percentage to Retain
Specifies the Retainage percentage (e.g., 10).
Setting Key: NewBIWorksheetReportId Setting Value: Report Id from Report table
Setting Key: NewBIWorksheetReportQueryId Setting Value: Report Query Id from Report Query table
These fields specify the Billing Worksheet Report and Query (Format) setting for Billing Items created during the import.
The Job viewer's WBS Import process also needs to know which of the specific Cost Codes should be marked as the 'Fee Code'. The following registry is used to enable this functionality.
Id: sys-viewer-vjb
Setting Key: ImportWBSFeeCodeCodeId Setting Value: JobCostCodeId
When BOTH this registry and the sys-viewer-vjbprgrss registry's LumpSumUsrFldNmbr options are present, the selected user-definable field will be marked with either a Y or N to indicate which of the cost codes is the 'Fee Code'.
This release modifies the WBS Import function so that when it auto creates WBS Codes (Job Cost Codes) the Hourly Burden will be pre-set based on defaults established in this registry entry (if enabled). The registry allows the setting of default Hourly Burden rates based on a combination of Branch and Discipline. In addition, this release modifies the posting logic used to create job cost labor and associated G/L accrual entries to support positing of the Hourly Burden to the G/L based on rules set in an Earnings Id specified in the new registry. Default Earning Id’s are based on the specified Branch id’s.
Registry Id: sys-behavior-CostCodeLaborBurden
Registry Name: Define Use of Cost Code Labor Burden Rates
Setting Key: ApplyCostCodeHourlyBurden Setting Value: true
Setting Key: AddPayRateFactor Setting Value: true
Setting Key: BranchId~DisciplineId Setting Value: laborburdenrate,EarningId
A separate line for each applicable Branch and Disciple combination should be set up. The Setting Key consists of the Branch Id (from the Job) and the Disciple Id from the Cost Code separated by a tilde (~).
The Setting Values are a combination of the hourly labor burden rate (in dollars) and the special Earnings Id separated by a comma.
Example:
Setting Key: Cleveland~HVAC Setting Value: 35,BurdenHVAC
For every Employee applying time the Cost Code generated with this configuration, a 'virtual' Employee Earnings line is included in the costings calculations. Values from the Earnings record are processed like any other burden-type Earnings line.
Important Notes on Other Registries:
1. The labor rate methodology implemented in the following registry must also be enabled:
Id: sys-ffv-global-settings
Setting Key: LaborRatesAndAccrualMethod Setting Value: 7687
2. Other labor rate calculation methodologies must be explicitly disabled.
When a new Job Cost Code is created in during the WBS Import, the GL Entity is set by default from the Job Entity on the Job's Financial tab. The following registry may be used to specify that the Cost Code's GL Entity instead comes from the Discipline Id specified in the Import.
Id: sys-viewer-vjb
Setting Key: ForWBSGetEntityFromDiscipline Setting Value: true (default is false)
Note that if the WBS import is being used to update existing Job Cost Codes, the GL Entity will be left alone, regardless of whether or not this registry is set.
The records in this viewer are used as a model when importing WBS Budget data to define Job Billing records when necessary for 'standard' jobs.
Each Standard Schedule of Values record defines a unique combination of a Billing Item Id, Discipline Id, and Skill Id. The table specifies the Billing Item Group, Billing Item Id and Billing Item Name that will be used when importing WBS Budget data for which Billing Items and Cost Codes do not yet exist. During the import, if a combination is not found in the table, the system will create and set the Billing Item Id to a default value “Unassigned”.
SoV Id:
This display-only field will be generated by the system when the record is added.
Discipline Id:
Skill Id:
Enter the unique Disciple and Skill records that define this record. The Discipline defines the Trade or the type of personnel needed. Typically, the Discipline is further defined by the Skill. For example, if a Discipline was Pipe Fitting Field Install, the trade Skill would indicate the material of the pipe (e.g., Carbon Steel, Copper, etc.). The Skill may also define the type of material, equipment or subcontractor required.
SoV Bill Item Id: SoV Bill Item Description:
These field provide the text used to generate the Billing Item and Job Cost Code's Id and Description when they are created via the WBS Import.
SoV Billing Item Group:
These field specifies the text written to the Billing Item Group field (on the Billing Item's Invoicing tab) when the Billing Item is generated via the WBS Import.
SoV User 1-5:
These fields are used to update the Job Billing Item User fields 1 thru 5 during the processing of the WBS Import.
Obsolete:
Reserved for future use.
In Version 9.1, the Discipline record is also referenced in the Standard Schedule of Values for use with the WBS Budget Import functionality in the Job record. When used in this fashion, the Discipline may be further defined by the Skill. For example, if a Discipline was Pipe Fitting Field Install, the trade Skill would indicate the material of the pipe (e.g., Carbon Steel, Copper, etc.).
New Field - Work Type: n/a - Office - Field
This new field supports the WBS Budget Import's creation of new Job Cost Codes using the Standard Schedule of Values. When the Import creates a new Cost Code, the defaulting of its Work Type is as follows: Set the Cost Code's Work Type to Field only if both the Skill and Discipline (in the Schedule of Values) both have Work Types of Field. Otherwise, the Cost Codes has its Work Type set to Office.
The n/a option may be used as a placeholder during data conversion.
Changed Field: Discipline User2:
The WBS Import sets the Cost Category Usage Filter from the Discipline User2 field when creating new Cost Codes.
In Version 9.1, the Skill record is also referenced in the Standard Schedule of Values for use with the WBS Budget Import functionality in the Job record. When used in this fashion, the Skill would typically indicate a further breakout of detail applied to the trade Discipline. For example, if a Discipline was Pipe Fitting Field Install, the Skill would indicate the material of the pipe (e.g., Carbon Steel, Copper, etc.).
New Field - Work Type: n/a - Office - Field
This new field supports the WBS Budget Import's creation of new Job Cost Codes using the Standard Schedule of Values. When the Import creates a new Cost Code, the defaulting of its Work Type is as follows: Set the Cost Code's Work Type to Field only if both the Skill and Discipline (in the Schedule of Values) both have Work Types of Field. Otherwise, the Cost Codes has its Work Type set to Office.
This records in this viewer are typically generated when a WBS budget is generated via the Import WBS button in the Job Budget Entry tab.
The WBS Contingency table is used by the WBS Configurator Analytic for validating combinations of Discipline, Skill and Cost Category. It has no use within SAMPro itself. Although a standard SAMPro viewer has been implemented, the data in this table will be imported initially and most likely remain unchanged.
WBS Contingency Id:
This field will be generated by the system when a record is added.
Discipline Id: Skill Name: Cost Category:
These fields define allowable Discipline, Skill and Job Cost Category which may be selected in the WBS Configurator. This combination must be unique within the WBS Contingency table.
This option should ONLY be implemented if the WBS Configurator/Import process is being used to import Job Budget Entry child lines. See Customer Release Note 7.2.1 for details.
The following registry may be used to change the Cost Code ~ Cost Category Validation error into a warning.
Important:
This registry should only be enabled for only special accounting department users so they can make adjustments to previously posted JCH independent of the new rules.
Id: sys-viewer-vjbjrnl
Setting Key: CostCategoryUsageValidationType
Setting Value: warning (default error)
The Job Journal supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record. This registry controls whether a violation of the Cost Category Usage Validations is treated as an error (the default) or a warning (which warns the user but allows the record to be saved.
Id: sys-viewer-vjbjrnl
Setting Key: NetZeroEquipmentCost Setting Value: true (default false)
This registry impacts the Job Journal's Co.Equip tab which is used to charge company equipment assets to a Job or Work Order. When enabled, this registry requires that the costs entered on the Co.Equip tab net to zero. This entry provides a means of controlling job cost transfers.
By default, the user is warned when changing the Overhead? flag on a Job which has non-zero Job History based on the JCH Hours, Quantity, Total Cost and Total Revenue fields. The following registry changes the warning to an error to prevent the user from changing the Overhead? flag for Jobs with non-zero history.
Registry Id: sys-viewer-vjb
Setting Key: ValidateOverheadChange Setting Value: error or warning (default)
By default when Actual + Committed equals or exceeds existing Projected Cost, then the Over/Under adjustment is "forced" to bring the projection in line with Actual (Actual + Committed becomes the projection line IS 100% Complete): the following message will appear when a Job with this criteria is accessed:
One or more lines required adjustments to prevent Actual Costs
from exceeding Projected Costs. If you exit this viewer without
saving, these adjustments will be discarded and will not appear
on subsequently produced job reports.
There may be cases when the Over/Under adjustment should not be forced: for example, assume that a budget line has more actual cost than budgeted, but revising the "projected costs" to the higher value is NOT desired. Perhaps there is material on site that is expected to be returned, vendor credit or rebates expected to be realized in the future, etc. This new registry allows the system to reflect >100% complete with a negative CostToComplete "projection". An additional option allows the user to control the message which appears on the new Messages column on the Job Progress Viewer child tab.
NOTE: The system will NOT automatically calculate the Over/Under Adjustments for you when this registry is in effect!
Id: sys-viewer-vjbprgrss
Setting Key: ActualCanExceedProjected Setting Value: true (default false)
This option enables the option to permit >100% complete.
Setting Key: ActualExceedsProjectedMessage Setting Value: message
This registry allows the default message (Actual > Projected) to be customized.
For example:
Setting Key: ActualExceedsProjectedMessage
Setting Value: WARNING: Actual > Projected
Certain Custom PM Workbench analytics depend on knowing which of a job's Cost Codes is designated as the 'Fee Code'. This analytic uses the following registry to determine which of the Cost Code User fields is being used (typically the User4 field).
Id: sys-viewer-vjbprgrss
Setting Key: LumpSumUsrFldNmbr Setting Value: 4 (1,2 or 3 are also permitted)
In this case, the Job Cost User User4 field should be set to Y if it is designated as the 'Fee Code' record or N if it is not.
See Customer Note 7.2.4 for a related registry.
The Job Viewer's Copy From Client button has been changed so that the Sales Tax Group, Service Zone and Branch will be set from the Zipcode table (if enabled) for the Client's Zipcode. For Commercial / Industrial Jobs, this is not desirable. The following registry changes default behavior so that only Client Address fields are set when Job viewer's Copy From Client button is clicked.
Registry Id: sys-viewer-vjb
Setting Key: JustSetAddressFromClient Setting Value: true (default false)
In previous releases the registry entry (sys-job-eom) setting key GLCOS to specify the Cost of Goods Sold account was only applied as a rule of last resort. For Inventory, the Expense Acct might come from the Inventory Group depending on registry settings and other conditions. Otherwise, the normal progression for all cost types is (1) Cost Category; (2) Cost Code: (3) 'glcos' registry setting; (4) the Vendor record; (5) nothing.
In this release, the following registry settings trump ALL of the above defaulting for the Cost of Goods Sold when this function is run. They allow the Cost Of Goods Sold to be specified by DIRECT assignment of COS GL Account by cost type, to support greater flexibility in configuration.
This is particularly necessary to define a specific rule for COS Labor to circumvent the skew that is inevitable if BURDEN is being carried in Labor Cost.
Id: sys-job-eom
Setting Key: GLCOSLAB Setting Value: glaccountidforlabor
Setting Key: GLCOSMAT Setting Value: glaccountidformaterial
Setting Key: GLCOSOTH Setting Value: glaccountidforother
Setting Key: GLCOSSUB Setting Value: glaccountidfosubs
This release implements a new registry setting which, when set, skips Change Orders that haven't yet been approved. If this entry is not in place, Change Orders are included in the calculation for revenue recognition even if the Change Order was not approved until the next accounting period.
Registry Id: sys-job-eom
Setting Key: SkipUnapprovedCOs Setting Values: true (default false)
The above option is recommended if the following are also in place:
Setting Key: Contract Setting Value: PercentComplete
Setting Key: ContractPercentCompleteLevel Setting Value: job
By default,when a Job is cloned via the Clone Job button in the Job record, the new Job's Branch Id defaults from the Job (or Job Template) it was cloned from. If the following registry is enabled, the new Job's Branch will be derived from the Site selected in the Clone Job wizard.
Registry Id: sys-viewer-vjb
Setting Key: UseCloneSiteBranchForClonedJob Setting Value: true (default false)
This release supports a enhancement to the way Small Jobs processing is handled. Instead of using the Job Date Closed as the trigger date for Small Jobs revenue recognition, the Date Completed will be used instead. The Job's Date Completed field is implemented via the v.cus file as a special, non-database field that is used to update a Job User field (specified via registry), ensuring that the Job User field is set to the correct date format. Note that a revised v.cus file is required to support this functionality.
In addition to the customized v.cus file with the Job Date Completed, the following registry is also required to define the Job User field used to sort the Date Completed.
Registry Id: sys-viewer-vjb
Setting Key: DateCompletedUserField Setting Value: 4
The following validation has been added when changing the new Job Date Completed field:
Change from Original Blank Date To New Non-Blank Date (OK)
Change from Original Non-Blank Date to New Non-Blank Date within same Accounting Period (OK)
If New Job Date Completed NOT in same Accounting Period as Original Date Completed:
If Non-Reversing JC EOM Entries found for Original Accounting Period (ERROR)
If Non-Reversing JC EOM Entries NOT found for Original Accounting Period and New Job Date Completed is blank (OK)
If Non-Reversing JC EOM Entries found for Date >= New Job Date Completed (ERROR)
The revised component report CSERPFT1.rpt dated 2016-09-28 corrects an error when drilling down from the Drilldown Service Profitability report.
The revised report (AKA Report Job Billing Recap) dated 2016-03-31 supports Security Id processing and corrects an issue which caused it to 'hang' in some environments.
The revised report dated 2016-10-19 enhances how the billed costs are calculated for the Labor, Material, Other, and Subcontract columns at the Client, Client Site, and Bill Item Summary levels.
Revised report (RSLSSMMRYSLSRP) dated 2016-12-20 correctly displays the current year's sales amount if more than one Sales Rep is specified on the Commissions tab of the Job by taking the share percentage into consideration.
This new report (RJBDTLDRCT.rpt dated 2016-01-10) resembles the original Report Job Billing Details but skips all overhead jobs in order to prevent typical users from running the report for indirect overhead jobs and seeing confidential data.
The revised report (RJBPRGRSS.rpt) dated 2017-03-10) replaces the Over/Under Billed column heading w/ Total Billed JTD - Cost JTD. For Change Orders (Billing Items with the Change Order? box checked), the report now checks the CO Date Approved when determining whether or not to include the CO Amount in the Total Revised Contract: the CO Date Approved must be less than or equal to the report's Ending Date.
This new report (DWIPSUM2.rpt) dated 2017-03-13 calculates Total Estimated Revenue from the Contract Amounts in the Billing Items. For Change Orders, the Date Change Approved must be less than or equal to the Ending Date for the report.
In Version 9.1, the Discipline record is also referenced in the Standard Schedule of Values for use with the WBS Budget Import functionality in the Job record. When used in this fashion, the Discipline may be further defined by the Skill. For example, if a Discipline was Pipe Fitting Field Install, the Skill would indicate the material of the pipe (e.g., Carbon Steel, Copper, etc.).
New Field - Work Type: n/a - Office - Field
This new field supports the WBS Budget Import's creation of new Job Cost Codes using the Standard Schedule of Values. When the Import creates a new Cost Code, the defaulting of its Work Type is as follows: Set the Cost Code's Work Type to Field only if both the Skill and Discipline (in the Schedule of Values) both have Work Types of Field. Otherwise, the Cost Codes has its Work Type set to Office.
The n/a option may be used as a placeholder during data conversion.
In Version 9.1, the Skill record is also referenced in the Standard Schedule of Values for use with the WBS Budget Import functionality in the Job record. When used in this fashion, the Skill would typically indicate a further breakout of detail applied to the Discipline. For example, if a Discipline was Pipe Fitting Field Install, the Skill would indicate the material of the pipe (e.g., Carbon Steel, Copper, etc.).
New Field - Work Type: n/a - Office - Field
This new field supports the WBS Budget Import's creation of new Job Cost Codes using the Standard Schedule of Values. When the Import creates a new Cost Code, the defaulting of its Work Type is as follows: Set the Cost Code's Work Type to Field only if both the Skill and Discipline (in the Schedule of Values) both have Work Types of Field. Otherwise, the Cost Codes has its Work Type set to Office.
A warning is now displayed when the user first accesses a journal entry which has been replaced by one with a higher 'tack' number. This warning is designed to prevent the user from wasting time by attempting to make changes to a journal entry record which cannot be saved because it has already been replaced. See Customer Note 1.1.2 for a registry to disable this warning globally or by individual viewer.
Changed Field - Total Labor Cost:
Previously, this display field was not promptly updated if the global registry LaborRatesAndAccrualMethod was set to 7687. This field is now correctly updated when the Job Cost Code is entered.
New Field - Supervisor Id:
If completed, this field specifies the Supervisor responsible for work in this entry.
Changed Field - Cost Category:
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
See Customer Note 8.1.2 for a Job Journal Registry to Change the Cost Code ~ Cost Category Validation Error into a Warning.
Changed Field - Cost Category:
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
See Customer Note 8.1.2 for a Job Journal Registry to Change the Cost Code ~ Cost Category Validation Error into a Warning.
Changed Field - Cost Category:
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
See Customer Note 8.1.2 for a Job Journal Registry to Change the Cost Code ~ Cost Category Validation Error into a Warning.
Job Budgets, Job Labor, Job Expense and Projected Cost now have the Security Id set when created in the Inter-Company model. New validation requires Job Journal entries for Inter-Company type clients to include 2 or fewer companies on each child tab. The 'Parent' company is the company whose GL COS account is credited.
This new tab allows Sales Tax Certificates to be recorded for informational and reporting purposes.
Authority Id:
The Sales Tax Authority Id.
Start Date: End Date:
Defines the date range this Certificate is valid for (required).
Certificate Number:
The number provided by the Tax Authority (required).
Certificate On File?
This box should be checked if this Certificate is on file.
Tax Certificate Description:
Briefly describes this Certificate.
In previous releases, manually entering the Job Invoice Address's Zip Code caused the Sales Tax Group to default on Job's Main tab (if the Sales Tax Group was specified in the Zip Code table). In this release, this defaulting has been extended to the use of the Copy Client Address or Copy Site Address icons to populate the Invoice Address's Zip Code.
WARNING: Defaulting the Sales Tax Group from the Client record may lead to undesirable results. For most installations, we strongly recommend disabling the default of the Sales Tax Group via the registry setting in Customer Note 8.1.7 so that only the address fields from the Client default.
Enhanced Field - Invoice Email To:
Double-clicking this field now brings up a list of potential email addresses from the Site and Client records for the user to select from. Note that only email addresses including the @ symbol will be included on the list. Email Groups will not appear on the list, but may be added manually and enclosed by brackets [emailgroupid].
Changed Field - Job Invoice Description:
This field has been expended from 1000 to 3000 characters.
This release corrects a rounding error in computing a negative gross margin.
All currency fields have been expanded to display amounts up to $999,999,999 correctly.
This tab is refreshed correctly when it is selected when the Next - Previous buttons are pushed.
Financial Tab CIP Discount Percent
This release refines the support for OCIP/CCIP discounted insurance job costing. OCIP/CCIP Job Cost Rate Discounts will be implemented only if the CIP Discount? is flagged in the applicable Earnings record AND Job Cost Code record. In the original implementation, all N/A-type earnings were subject to CIP Discounting.
This release corrects the problem of Job Budget entries (made directly to Budget tab of Job) posting to JCH with no security in the Intercompany model. This resulted in inaccurate data on the Job Budget Reports RJBBUDG1, RJBBUDG2 and RJBBUDG3. Now all budget lines on the Job record, as well as Job Journal budget entries are posted to JCH with Security Rn, and all Budget reports pull accurate data when run globally, or by Company.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
New Button:
This button imports a file or reads a database table looking for data that hasn’t been previously imported. When found, if budget information for the job exists, the user will be given the option to replace the existing WBS/Budget information or append the new data to the existing WBS/Budget. If no budget exists, the system will create new Job Cost Codes based on the WBS information provided and create job cost budget entries for the associated costs.
See Customer Note 7.1 for additional details.
The new JobByProjectDescriptionByJobId option on the Job List's Sort Order Pane displays these columns: Project Description - Project Id - Job Id - Job Name - Site Id - Site Name
New Column: CO Request
The CO Request field will be set to Y for Job Billing Item Change Requests.
Contract Total:
This value is zero for Change Requests and for unapproved Change Orders.
Main Tab New Display - Only Field - Client Site Info:
These new fields list the Site's Name and Work/Ship Address. A new v.cus file may be needed to see these fields.
Changed Button: Clone Job
In this release, Change Orders and Change Requests will not be cloned.
See Customer Note 8.1.9 for a registry to default the cloned Job's Branch from the Site instead of the template Job.
The OpenWO tab lists all work orders created for this Job that have a Work Order Status Category of Open. You may double-click on a line to open the corresponding Work Order.
The OtherWO tab lists all work orders created for this Job that have a Work Order Status Category that is not set to Open (e.g., Completed, Billed, Ok to Invoice, etc.). You may double-click on a line to open the corresponding Work Order.
Costs and Revenues are not recognized on a Small Job until the Job Date Closed is set.
Modification to use Date Completed: See Customer Note 8.1.9 for the Registry to Use the Job Date Completed instead of the Date Closed as a trigger in Job EOM for Small Jobs.
If the Job's Contract Type is set to Small Job, Start Job EOM will automatically use a special WIP method that will accrue revenue and costs until the Job Date Closed field is manually set by a user. If costs and or revenues are found for an open Small Job (Job Date Closed is blank) they will be debited/credited in the current accounting period and automatically reversed in the next accounting period.
If the job is closed in the current EOM period (Job Date Closed not blank) the Start Job EOM will attempt to recognize any unbilled revenue for this job (Contract amount from billing items), reversing this transaction in the 1st day of the next accounting period. When the job is billed complete no further Job EOM process takes place.
Note: DB Underbilling - CR Income
The G/L accounts used for the posting are set via the sys-job-eom registry.
In the Job viewer, validation logic prevents a user from changing the Job Date Closed on Small Jobs if it is not blank and the Job EOM function has been executed for the job.
A new range, PO#, has been added to allow the user to filter on the customer's PO# on the Job's Main tab. In addition, the PO# has been added as a column to the JobByClientIdByJobId list view.
Changed Field - Billing Item Id:
See Customer Note 8.1.4 for a Job Cost Code Registry to Warn User / Remove Job Progress Lines when the Billing Item is Changed (for use with custom Job Progress Analytics.
CIP Discount?
This release refines the handling of this field. If the CIP Discount box is flagged in the applicable Earnings record and in this Job Cost Code record, the CIP Discount Percent in the Job record will be applied to discounts the non-wage labor (burden) cost posted to this Job Cost Code. In the original implementation, all N/A-type earnings were subject to CIP Discounting.
New Field - Obsolete?
If this field is checked, the record is considered Obsolete, and it may not be directly specified during data-entry (either by entering the Id or selecting it from a list). Obsoleted records can be edited and the Obsolete option can be cleared when necessary.
New Field: Job Cost Category Usage Filter
This field allows the user to filter which Cost Categories are eligible for selection when this Cost Code is entered in certain journals and records. When the user specifies this Cost Code in a detail line (i.e., for a Job Journal entry), the contents of this Usage Filter will automatically be added to the Cost Cat: range of the Job Cost Category filter preceded by sql=. This special filtering is in addition to any Job Cost Category filtering implemented for that specific journal or record.
Click the Test Filter button to preview the results of the Cost Category Usage field. The Cost Category list will be opened pre-filtered to the contents of the Cost Category Usage field.
This functionality currently extends to the following viewers:
AP Journal, Recurring AP Journal, Cash Receipts Journal, Employee (Recurring Wages/Other), Inventory Adjustment Journal, Job Journal, Purchase Order, Quote / Quote Scope, Work Order, Job, Job Billing Item, Sales Journal, Labor Journal.
TechAnywhere: In this release, these Cost Code ~ Cost Category Usage Validations have been disabled for TechAnywhere Posts. In the labor Journal, cost category restrictions have been refined to tolerate TechAnywhere posts to the Labor Journal.
See Customer Note 8.1.2 for a Job Journal Registry to Change the Cost Code ~ Cost Category Validation Error into a Warning.
The Unit Cost, Unit Price and Revenue Tab fields in Job History have been expanded to support values of up to 10 Million.
JobCostCategorybyGLExpenseAccountById
When this index is selected, the record's GL Expense Account/Name will be displayed on the list.
JobCostCategorybyGLIncomeAccountById
When this index is selected, the record's GL Income Account/Name will be displayed on the list.
New Range - GL Account Id:
This new range is sensitive to the Index selected.
When JobCostCategorybyGLExpenseAccountById is selected, the Cost Category's GL Expense Account/Name will be filtered on.
When JobCostCategorybyGLIncomeAccountById is selected, the Cost Category's GL Income Account/Name will be filtered on.
When one of the other Indices is selected, the system will filter for a match in both the GL Income and GL Expense Account fields.
New Range - GL Account Type Id:
This new range is sensitive to the Index selected.
When JobCostCategorybyGLExpenseAccountById is selected, the Account Type Id associated with the Cost Category's GL Expense Account will be filtered on.
When JobCostCategorybyGLIncomeAccountById is selected, the Account Type Id associated with the Cost Category's GL Income Account will be filtered on.
When one of the other Indices is selected, the system will filter for a match in both the Account Types associated with the GL Income and GL Expense Accounts.
New Field: Discipline Id
This field supports multiple Worker's Comp Categories per Worker's Comp State. When Field time is entered, the system uses the entries on this tab to determine the correct WC Category using the state (from the Job record) and the Discipline (from the Job Cost Code record). It this field is NOT completed, only a single Worker's Comp Category per state is supported.
Note: the following registries must be implemented to apply this methodology to Office hours.
Id: sys-ffv-global-settings
Setting Key: UseCostCategoryWorkersCompForOffice Setting Value: true
If enabled, Worker Comp settings will be pulled from the Job Cost Category for Office time entered in the Labor Journal and Work Order Labor tabs and via TimeAnywhere. If not enabled, the Workers Comp category will continue to pull from the Employee record for Office hours.
Setting Key: useCostCodeWorkType Setting Value: true
If this option is implemented, prevailing wage and/or payroll reciprocity overrides will only be implemented for Job Cost Codes flagged as Field for Hours entered in the Labor Journal, Work Order Labor tab, and from Remote Time Entry. It will override the default settings of the Work Type in the Employee Record and default it with the settings in the Job Cost Code.
New Fields - User3-5:
These fields are designed for use with web-based PO processing if implemented on your system.
Changed Field - Invoice Description:
This field has been expended from 1000 to 3000 characters.
New Field - Obsolete?
If this field is checked, the record is considered Obsolete, and it may not be directly specified during data-entry (either by entering the Id or selecting it from a list). Obsoleted records can be edited and the Obsolete option can be cleared when necessary.
The right-click 'Quick Edit' functionality has been disabled for GMP-type Jobs.
The Cost Code Name has been added to this tab to the right of the Cost Code Id field.
This release expands percentage columns to max out at 999999.9 on the Progress tab. This corrects the handling of lines having a %Used value exceeding 9999.9 so that the Totals display incorrectly.
When changes to a Job are required but not yet approved, Change Requests (CORs) may be created for budgeting / reporting purposes prior to their approval. When a Change Request is approved, it may be converted to or attached to a Change Order for billing and costing; budgets included on the Change Request will be added to the Job's Budget tab during this process.
The Billing Item can have 3 different forms:
A standard Billing Item (typically created when Job was set up)
A Change Order Billing Item that Changes a Original Job. (CO)
A Change Request (COR)
Billing Items marked as Change Requests are used for budgeting, NOT for actual billing or costing. However, when a Change Request is approved, it may be:
Converted to a Change Order via the Convert To CO Button in the Job Billing Item Change Request viewer
Or
Attached to an existing Job Billing Item Change Order via the Attach CO Requests button in the Job Billing Item Change Order viewer
Charge Request Amounts represent the values requested, not necessarily the values approved. It is the user's responsibility to manually enter all appropriate values when converting or attaching to a Change Order!
Budgets entered on the Change Request's BudgetEntry tab will be used to generate corresponding entries to the Job's Budget tab when a Change Request is converted or attached to a Change Order.
Open Change Requests (CORs) are included in Job EOM processing. They are treated as Fixed Fee with the Contract Amount adjusted by Percent Likelihood. Change Requests will be processed by the EOM function if:
Date Approved & Date Declined = 1900-01-01
CO Amount & Percent Likelihood <> 0
Main Tab
Bill Item Id:
This required alphanumeric field must uniquely identify this Change Request for this Job.
Bill Item Description:
Briefly describes this Change Request. Recommended but not required.
Job Id:
The Job this Change Order Request is associated with.
CO Amount: Expected Cost:
In previous releases these fields were display only, and were maintained by the system based on the Change Request's Budget Tab. In this release, these fields may be manually updated if no Budget lines are present in the Change Request. If Budget lines are added, the Budget lines will overwrite the manually entered CO Amount and Expected Cost values on the Change Request's Main Tab. Note that it is necessary to save the record and then refresh the display to see the changes.
% Likelihood:
How likely this Change Order Request is to be approved, entered as a percentage. This field controls how lines from the Budget Tab are written to Job History. If the Likelihood is changed as the Job progresses, the appropriate changes to the Job History budget will be generated.
Example:
% Likelihood = 50 CO Amount: 1000 Expected Cost:550
Budget lines written to Job History for this Change Order Request total a budgeted revenue of $500 and a budgeted cost of $275.
CO Date Requested:
The date this Change Order Request was asked for.
CO Date Approved:
This display-only field will be competed by the system when this Change Request is converted to a Change Order or attached to a Change Order.
CO Date Declined:
This field should only be completed the customer declines this Change Order Request. When a Change Order Request is Declined, any Job History entries generated for this Request will be reversed when this record is saved.
Change Request Description:
This field will be used to generate the Change Order's Invoice Description if this Change Request is approved and converted to a Change Order.
Change Order:
This display field will be completed if this Change Request has been attached the displayed Change Order.
When a Change Request is approved, clicking this button will convert it to a Change Order (CO) Billing Item. You will be asked to enter the Date Approved to be used on the Change Order and then click Yes to continue. When the Change Request has been converted, it will no longer be displayed in this viewer; it must be accessed via the Job Billing Item Change Order viewer.
Budgets entered on the Change Request's BudgetEntry tab will be used to generate corresponding entries to the Job's Budget tab at 100% likelihood. Once the Change Request has been converted it is the user's responsibility to access it from the Job Billing Change Order viewer in order to complete any necessary fields, including the CO Amount and CO Cost, Invoicing Tab fields, etc.
Alternative to Converting: Instead of Converting a Change Request, it may be attached to an existing Change Order (using the Job Billing Change Order viewer's Attach CO Requests button). This allows multiple Change Requests to be combined on the same CO.
Invoice:
Report Id: Report Query Id:
Enter the Id's for the Invoice Report and Report Query formats to be used if this Change Request is converted to a Change Order with the Convert to C.O. button. They are not required if the Change Request will be attached to an existing Change Order. These field must be completed before the Change Request can converted unless a Registry to Set Change Order Invoice Report Fields on Converting COR to CO (see Customer Note 8.13.4).
Billing Worksheet:
Report Id: Report Query Id:
Enter the Id's for the Billing WorkSheet Report and Report Query formats to be used if this Change Request is converted to a Change Order with the Convert to C.O. button.
User Fields Tab
Job Billing Item User1-5:
These optional fields may be used to record additional information required by your company or for reporting purposes.
Budget Entry Tab
Entries made in this tab will be written to Job History with a source journal of JBI Budget. Edits and changes to these lines will also be written to Job History. The Likelihood % field (see above)controls how lines from the Budget Tab are written to Job History. If the Likelihood is changed as the Job progresses, the appropriate changes to the Job History budget will be generated.
Editing Budget Entries:
The BudgetEntry tab functions like the other SAMPro journals. If it is necessary to change a line, simply change it to the desired value and save the record.
Hours: Quantity:
The Hours fields should be used to record labor budgets lines, and the Quantity field should be used to record material or other items. On a single line, fill in either the Hours or Quantity field.
Inventory Item:
This option field would be used if you are budgeting for specific parts. Note that the cost / revenue for this part must be specified by the user; these values will not default from inventory history.
Cost Category:
Enter (or import) an appropriate Job Cost Category for this line. For example, a Cost Category of type Labor should be selected for Hours entries.
This field supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated relative to Cost Codes if this filtering is in place.
Job Cost Code:
The Cost Code this budget is assigned to.
Unit Cost: Extended Cost:
The Unit Cost must be entered by the user. The system will multiply the Hours or Quantity by the Unit Cost to calculate the Extended Cost. The Likelihood % field controls the cost which is written to Job History. If the Likelihood is changed as the Job progresses, the appropriate changes to the Job History budget will be generated.
Billing Type: Revenue Rate: Extended Revenue:
By default, the billing type is set to n/a so that the user can enter the Revenue directly. To have the system calculate the Extended Revenue for you, select a Billing Type and enter a Revenue Rate. The Likelihood % field controls this revenue which is written to Job History. If the Likelihood is changed as the Job progresses, the appropriate changes to the Job History budget will be generated.
Click the Magnify Button to Access the following fields.
Description:
If completed, this field will be used to generate the Job History Description.
Effective Date:
If completed, this field will provide the Effective Date written to the JBI Budget entry in Job History. If this field is blank, the Job Record's BudgetEffectiveDate registry will be used to set the Effective Date in History. If this field is not set the Job registry is not implemented, the Effective Date in Job History will be set to blank (01011900).
Changed Field: CO Amount
Corrects a problem in recent versions which did not allow negative Change Orders. Negative Change Orders allow credits to be accounted for as a project proceeds.
Expected Cost:
If this CO was created from a Change Request, this field will be generated from the Change Request's Budgeted Costs. If Change Requests were attached to this Change Order, this field should be manually updated to include the budgeted cost on the attached Change Requests.
When this new button is clicked, the system will determine if any Change Requests are eligible for attachment to this Change Order. If any are found, a checklist will be displayed, allowing the user to select which ones to attach. Budgets entered on the Change Request's BudgetEntry tab will be used to generate corresponding entries to the Job's Budget tab at 100% likelihood. It is the user's responsibility to manually enter update all appropriate values in the Change Order including the CO Amount and CO Cost when attaching to a Change Order!
Change Order Requests Tab
This tab displays Change Requests which have already been included in this Change Order as well as Change Requests which have not yet been included in any Change Order for the selected Job.
IncludedInCO: CORequestId:
The IncludeInCo field will be set to No if the specified Change Request has yet to be included in any Change Order for the selected Job.
The IncludeInCO field will be set to Yes if the specified Change Request has been include in this Change Order via the Attach CO Requests button. If the Change Request was recently attach
Requested $
This field displays the CO Amount on the Change Request record. This field is based on the Change Request's Budget entries.
Requested Date:
The requested Date from the Change Request.
Approved Date:
The date the Change Request was approved and included in this Change Order.
Description: Extended Description:
These fields default from the corresponding fields in the Change Request record.
When Job Billing Item Change Request (COR) is converted to a Change Order (CO), the Report Id and Report Query Id on the COR default to the CO. If the user neglects to complete these important fields, they will be blank on the CO.
If enabled, the following registry specifies the invoice Report Id and Report Query that will be written to the CO when the COR is converted if these fields are NOT completed in the COR. If the Report Id and the Report Query ARE completed in the COR they will override this registry when the COR is converted to a CO.
Registry Id: sys-viewer-vjbbllngitmcor
Setting Key: AllowDefaultsForInvoiceReporting Setting Value: true (default is false)
Setting Key: DefaultInvoiceReportId Setting Value: invoicereportid
Setting Key: DefaultInvoiceReportQueryId Setting Value: invoicequeryid
Example:
Registry Id: sys-viewer-vjbbllngitmcor
Setting Key: AllowDefaultsForInvoiceReporting Setting Value: true
Setting Key: DefaultInvoiceReportId Setting Value: RININV3
Setting Key: DefaultInvoiceReportQueryId Setting Value: FFDETAILS
A new column at the right of this tab will display a message if the actual cost exceeds the projected cost.
If default behavior is in effect and actual will exceed projected, the message "Projected Adjusted to Match Actual" will be displayed if the line was adjusted when the Job was loaded in the viewer.
If the registry ActualCanExceedProjected is enabled, the message Actual > Projected (or the message defined via the registry discussed in Customer Note 8.1.5) will be displayed if the Actual Cost exceeds the Projected Cost on this line.
This release corrects a sporadic display issue on the Margin %.
This release includes 'open' Job Billing Item Change Requests (CORs) in the processing. They are treated as Fixed Fee with the Contract Amount adjusted by Percent Likelihood. Change Requests will be processed by the EOM function if:
Date Approved & Date Declined = 1900-01-01
CO Amount & Percent Likelihood <> 0
Important: A new v.cus file will be required to see this enhancement; standard customizations are included with this release. Company-specific customization may be requested from your Support representative. Note that View Prevailing Wage Schedule must be enabled for the User Groups that should have access to it.
The Prevailing Wage Schedule (P.W. Schedule record) may be used instead of the Job's Prevailing Wage tab to define a Job's Prevailing Wage structure. In this way, when a particular Prevailing Wage Schedule changes, it is only necessary to change it this new record, instead of changing the Prevailing Wage Tab in each Job record that it impacts.
This feature is ONLY supported if the following registry is enabled:
Id: sys-ffv-global-settings
Setting Key: LaborRatesAndAccrualMethod Setting Value: 7687
If a P.W. Schedule Id is specified on the Job's Main or Financial Tab, the Prevailing Wage Type must be set to Labor Rate for the prevailing wage functionality to be enabled.
If both the P.W. Schedule Id field and the Prevailing Wages Tab are completed on a Job, the P.W. Schedule will have precedence.
P.W. Schedule Id:
A unique Id for this table. This field is required.
P.W. Schedule Name:
A brief description of this table. This field is optional.
P.W. Schedule User 1-2:
These fields may be used for informational and reporting purposes
Obsolete?
If this field is checked, the record is considered Obsolete, and it may not be directly specified during data-entry (either by entering the Id or selecting it from a list). Obsoleted records can be edited and the Obsolete option cleared when necessary.
Start: Date:
These fields default the effective (work) date range the prevailing wage is in effect for.
Labor Rate Id:
All Labor Rates that would be impacted by this job’s prevailing wage functionality should be listed on this tab.
Overtime / Doubletime Pay Rates:
The Pay rate multiplier DOES NOT affect the Prevailing Wage Package Amount. Regular, overtime and any other pays must be all accommodated for each Labor Rate specified.
Base Rate:
This field should be used to enter the base wage rate for this Prevailing Wage. The system will sum the Fringe Rate and the Base Rate when determining whether to use the Prevailing Wage during Compute Payroll.
Standard Calculation:
Example 1: Employee’s Regular Wages + Fringes Exceed P.W. Base + Fringes Amount
Base Rate: $25.00 / hour
Fringe Rate: $0.00
Wage Earnings: $24.00 / hour
Fringe 1: $2.50 / hour
Fringe 2: $1.50 / hour
Since the Employee’s regular Wages + Fringes total $28.00 / hours (greater than the prevailing wage Base + Fringe of $25.00/ hour), they will be used for payroll calculations for this Prevailing Wage job.
Standard Calculation
Example 2: Job Base Rate + Fringes Amount Exceeds Employee’s Regular Wages + Fringes
Base Rate: $40.00 / hour
Fringe Rage: $5.00 / hour
Wage Earnings: $27.00 / hour
Fringe: $1.00 / hour
Since the Employee’s regular Wages + Fringes total $28.00 / hours, the Prevailing Wage methodology will come into effect since the Base Rate + Fringe Rate = 45.00 / hour. The system calculates the Employee’s Wages as follows:
Wage Earnings Calculated Under Prevailing Wage: $44.00 / hour
Fringe: $1.00 / hour
Note that the Employee’s Wages + Fringes package now equals $45 / hour, the Prevailing Wage Job Package rate. The increased difference is added to the Employee wage.
Fringe Rate:
This field enables you to separate Fringes from the Base Rate for prevailing wages. The system will sum the Fringe Rate and the Base Rate when determining whether to use the Prevailing Wage during Compute Payroll.
Note: Excluding Fringes from Workers Compensation
Workers comp 'wages' typically should not include any amounts related to prevailing wage fringes. The Exclude Fringes field in the appropriate Workers Comp State should be flagged to exclude these fringes from workers compensation calculation.
Certified PR Report Label:
The Certified Payroll report has been enhanced so that it uses this field (if completed) instead of the Labor Rate Description. If this field is blank, the Labor Rate Description will be used.
New Field:
P.W. Schedule Id:
If this field is completed AND the Prevailing Wage Type field is set to Labor Rate, the P.W. Schedule will be used for prevailing wage calculations. When completed, this field overrides any entries on the Job's Prevailing Wages Tab.
IMPORTANT: The sys-ffv-global-settings option LaborRatesAndAccrualMethod must be set to 7687 to support this functionality.
See Customer Note 9.2.2 for registries supported in the revised report.
When this registry is enabled, the Service Account Manager from the Client Site will be defaulted to the PM Invoice Work Order. If this registry is not implemented or set to false, the Service Account Manager field will be blank.
Registry Id: sys-start-scrtepmbllng
Setting Key: GetServiceAccountManagerFromClientSite Setting Value: true (default is false)
The revised Report Service Invoice dated 2017-04-14 (SERVICEINVOICEv90b028.rpt) supports a registry option to skip print $0 DUE invoices (e.g., COD Invoices). Note that $0 Dues includes will still be attached as documents when the print in confirmed; they simply will not be physically printed.
Id: sys-start-ssrvcebllngcmpte
Setting Key: SkipPrintZeroDueInvoices Setting Value: true (default false)
This release supports registry entries to clear the default initial values when running Compute Service Invoice. This allows the Billing Agent User Id range to be automatically cleared when running this function. Previously, the User Id of the user running the function would always be written to the Billing Agent User Id range when Compute Service Invoice was run.
Registry Id: sys-start-ssrvcebllngcmpte
Setting Key: initialValueFor~usr.id Setting Value:
Note that the Setting Value is blank in this case.
The following registry automatically restarts Record Billing Adjustments when a record is saved.
Id: sys-viewer-srcrdbllngadjstmt
Setting Key: ReopenViewerWhenRecordWritten Setting Value: true (default is false)
If this option is enabled, clicking the red X on the Job Id input screen closes Record Billing Adjustments so that is does not reopen.
When enabled, this registry denies selection of 'Ready to Post' in Record Billing Adjustments (the Job Invoice Viewer). This registry is strongly recommended to prevent users from posting an invoice without having produced a printed copy. It should always be implemented if autosave or autosavewhenprinted is enabled.
:
Id: sys-viewer-srcrdbllngadjstmts
Setting Key: DenyReadyToPost Setting Value: true (default false)
This release corrects sporadic 'key is missing' errors invoicing COD WOs. Potentially OOB Cash Receipts / AR Sales entries appear on the Checklist but cannot be flagged for processing.
The report revised 2016-04-05 adds the PO Id to AR Summary section.
Previously, if Show Equipment Detail was flagged, only the first 1200 characters of the Equipment Work Requested and Performed were printed. The revised Service Invoice (SERVICEINVOICEv90_b002.rpt revised 2015-12-19) prints the entire 3000 character contents of these fields if applicable.
The revised Service Invoice (SERVICEINVOICEv90_b002.rpt revised 2015-11-02) supports the new "Equipment Work Performed Addendum - Show on Invoices" box on the Work Order. If this box is flagged, the invoice will continue to print the Invoice Description of Work Performed. However, a page break AFTER the Invoice Total/AR Summary will occur and additional (addendum) page(s) will print as necessary to present the COMPLETE – Work Performed text associated to EACH WO Equipment record on the work order. See Customer Note 16.3.3 for additional details.
This release adds the ability to append TechAnywhere receipts or other documents to the PDF'd version of Service Invoices. This allows an Invoice Package to be automatically emailed to customers configured to receive Service Invoices via email. Supported document attachment file types include: .bmp, .jpg, .gif, .png, and .pdf. This functionality is suitable for scenarios where a Work Order is only invoiced once.
Important: Only the PDF'd Invoice Includes the Attachments
The .dbr version of the Service Invoice will not display the attached documents; it will however include a list of attached files. Only the PDF'd version of this document will include the 'package' of document attachments.
To enable this functionality:
1. The revised Service Invoice serviceinvoicev90b028.rpt dated 2016/02/16 or later must be installed in your database.
2. The Client Site Email Invoices field (a-clntste: clntste.eml-invce) must contain a list of the Document Categories which should be included in the Invoice Package. The included documents must be attached to the Work Order being invoiced prior to the generation of the invoice. Any documents attached to the Work Order after an invoice is generated will not be included in this package.
For example, to include TechAnywhere Receipts in the Invoice Package for a particular Site, you would enter Receipt in its Email Invoices field.
3. Verify that the xmlToPdf.jar file (located in the same directory as your SAMPro executable) is dated 2015/07/08 or later.
4. Implement the following registry entries:
Id: sys-start-ssrvcebllngcmpte:
Setting Key: IncludeInvoiceDocuments Setting Value: true (default false)
This option is required to implement the new 'package' functionality.
Setting Key: SkipPrintEmailedInvoices Setting Value: true
Implementing this registry allows emailed invoices to be 'skipped' in the print run. Processing will proceed as usual: the Invoices will be displayed and sent to the printer; the user must then confirm that the invoices have printed and post them. However, only those invoices that were not emailed will actually be printed.
Id: sys-report-serviceinvoice:
Setting Key: sectionbackerbitmap Setting Value: Pathname\whitesquare.bmp
This registry is recommended to prevent the invoice bitmap from 'stepping on' the attached documents. The bitmap may be obtained from support.
Setting Key: ShowDocumentDescription Setting Value: Y
This option should be enabled to display the Document Description of the attached graphic document on the upper left-hand corner of the page. Note that the attachments themselves (along with the Description) are only shown when the invoice is PDF'd.
The revised Service Invoice Report (SERVICEINVOICEv90b028) dated 2016-11-11 and this release support registries to skip printing and/or emailing service invoices with a negative total.
Id: sys-report-serviceinvoice
Setting Key: SkipEmailNegativeInvoice Setting Value: Y (default is N)
Id: sys-start-ssrvcebllngcmpte
Setting Key: SkipPrintNegativeInvoices Setting Value: true (default is false)
The revised Report Service Invoice dated 2017-04-14 (SERVICEINVOICEv90b028.rpt) supports a registry option to skip print $0 DUE invoices (e.g., COD Invoices). Note that $0 Dues includes will still be attached as documents when the print in confirmed; they simply will not be physically printed.
Id: sys-start-ssrvcebllngcmpte
Setting Key: SkipPrintZeroDueInvoices Setting Value: true (default false)
The new Report Service Invoice (SERVICEINVOICEv90b028.rpt) dated 2017-05-16 supports a new registry setting which will allow both Billing Address and Email To information to print on the invoice header.
When this registry setting is enabled AND autoemailwhenprinted is also set to true, the physical address will display so that it will appear in the envelope window should it need to be mailed; the email address will appear below the physical address.
When this registry setting is enabled but autoemailwhenprinted is NOT set to true, only the physical address will display.
Registry Id: sys-report-serviceinvoice
Setting Key: ShowBillAddressAndEmailAddress Setting Value: true (default false)
The Service Invoice (SERVICEINVOICEv90b028.rpt) dated 2018-01-16 and this release supports the ability to include custom text in the email message that the Service Invoice is attached to.
A Common Phrase entry must be made which contains the new email message. Tokens in Common Phrases are now supported for this functionality. Token replacements can done with fields from the following tables:
clnt, clntste, invcemstr, jb, wrkordr
Fields should be referenced using database field names
(i.e. invcemstr_id, wrkordr_dte_opnd, clnt_nme)
The following registry setting must be created to invoke this functionality:
Registry Id: sys-report-serviceinvoice
Setting Key: EmailMessageId Setting Value: commonphraseid
In the absence of the registry, "Emailed Report Attached" will be included in the email body.
The new functionality is enabled in this version with the revised Report Service Invoice (SERVICEINVOICEv90b028.rpt) dated 2018-01-16. The following registry is required:
Id: sys-report-serviceinvoice
Setting Key: EmailSubject Setting Value: Text string which supports token replacement
Token replacements can done with fields from the following tables:
clnt, clntste, invcemstr, jb, wrkordr
Fields should be referenced using database field names
(i.e. invcemstr_id, wrkordr_dte_opnd, clnt_nme)
Example:
Setting Key: EmailSubject Setting Value: Invoice ^invcemstr_id^ for ^clnt_id^
The revised Service Invoice dated 2018-04-06 (SERVICEINVOICEv90b028) has the Work Order Equipment Work Perform and Work Order Equipment Work Requested fields expanded to 6000 characters as this field size was increased in the 9.1 image. This change should correct the "Unable to insert into Temp Table #woequipment" SQL error experienced when invoicing work orders with lengthy Work Order Equipment Work Performed or Requested.
The revised Service Invoice (SERVICEINVOICEv90b028.rpt) dated 2018-05-14 supports the new bitmap override by Job functionality.
Registry Id: sys-report-serviceinvoice
Setting Key: BitmapOverrideBasedOn Setting Value: job
This registry entry defines that this override is based on a user field in the invoice's Job record.
Setting Key: BitmapOverrideField Setting Value: job user database field
This registry entry specifies exactly Job User field will provide the override; the database field name must be specified. For example, the following specifies the Job's User 3 field:
Setting Key: BitmapOverrideField Setting Value: jb_usr3
Setting Key: Job~string Setting Value: path\bitmap.bmp
This entry provide the override bitmap file that will be used if the Job record's User field defined above contains the string specified. Notice that a tilde (~) separates Job from the string. As many of these entries may be made as needed to support the various bitmaps.
Example:
Suppose that we have a bitmap file named 010101_invoice.bmp that should be used on invoices associated with Job's having the following text string 010101 in Job User 3 fields.
Setting Key: Job~010101 Setting Value: path\010101_invoice.bmp
Tip: Include the part of the bitmap name as the text string for clarity.
Tip: Including the appropriate values in your job templates will ensure that new jobs are created properly. In addition, using the Custom Fields functionality to specify the allowed values will prevent inappropriate values from being entered.
The revised Service Invoice report (SERVICEINVOICEv90b028.rpt) dated 2019-01-07 supports a registry setting to print the Amount Due of the invoice on the top of the first page, below the Service Location on the right-hand side of the page. It is printed in bold, red text to stand out. This functionality is supported for the STANDARD and CANADA headers; custom report headers can be updated as needed for a small fee.
The following registry is required to enable this functionality.
Id: sys-report-serviceinvoice
Setting Key: ShowAmountDuePage1 Setting Value: true
Revised report (RINIVNV3.rpt) dated 2017-08-13 adds the Site Address to the CANADA header format.
The revised Construction Invoices report (RININV3.rpt) dated 2016-05-12 has been enhanced to show billed retainage as a positive number with the label 'Billed Retainage'. In previous versions of this report, billed retainage was shown as a negative value, with the label 'Less Retainage'.
This report also supports a registry option to override the 'Billed Retainage' label.
Id: sys-report-rininv3
Setting Key: lbl_billedretainage Setting Value: text
This could be implemented to implement the Holdbacks terminology preferred in Canada:
Setting Key: lbl_billedretainage Setting Value: Billed Holdbacks
The revised Progress Invoice (RININV3.rpt) dated 2018-05-14 supports the new bitmap override by Job functionality.
Registry Id: sys-report-rininv3
Setting Key: BitmapOverrideBasedOn Setting Value: job
This registry entry defines that this override is based on a user field in the invoice's Job record.
Setting Key: BitmapOverrideField Setting Value: job user database field
This registry entry specifies exactly Job User field will provide the override; the database field name must be specified. For example, the following specifies the Job's User 3 field:
Setting Key: BitmapOverrideField Setting Value: jb_usr3
Setting Key: Job~string Setting Value: path\bitmap.bmp
This entry provide the override bitmap file that will be used if the Job record's User field defined above contains the string specified. Notice that a tilde (~) separates Job from the string. As many of these entries may be made as needed to support the various bitmaps.
Example:
Suppose that we have a bitmap file named 010101_invoice.bmp that should be used on invoices associated with Job's having the following text string 010101 in Job User 3 fields.
Setting Key: Job~010101 Setting Value: path\010101_invoice.bmp
Tip: Include the part of the bitmap name as the text string for clarity.
Tip: Including the appropriate values in your job templates will ensure that new jobs are created properly. In addition, using the Custom Fields functionality to specify the allowed values will prevent inappropriate values from being entered.
The Report Commissions by Amount Invoices (RCMMSSNRPT5.rpt) dated 2018-02-20 has been updated to include logic for discounts upon receipt. This report requires that total received must match total invoiced to qualify; to prevent qualifying an invoice for commission prior to the complete payment. This version corrects an issue where invoices were missing on the report if a discount was applied. This version shows such invoices as well as the computation for the amount received.
The new Consolidated Invoice Report (RCNSLDTDINVCE.rpt) is used to combine multiple invoices for a client within a specified date range. The consolidated invoice includes such details as the AR Invoice ID, purchase number, client site name, invoice subtotal amount, tax amount, and total invoice amount for each invoice being consolidated. The total line on this report corresponds to the consolidated invoice subtotal, tax, and total amount. The registry for this report includes bitmap placement and auto emailing functionality.
The Report Job Tax Certificate Expiration (RJBTXCRTFCTE.rpt) runs off the Job Tax Certificates table. Any Job's with Tax Certificates what have expired between the Start and End Dates specified in the report will be included on the report. Job, Branch, Project Manager and Job Type ranges allow the report to be filtered as needed.
GMP (Guaranteed Maximum Pricing) implements Cost Plus / Not-To-Exceed invoicing where the Percent Overhead is used to calculate the profit. GMP Contract and GMP SoV are both supported. Billing is accomplished via Record Billing Adjustments. GMP Jobs must NOT be flagged as Service Compute.
New Field: Job Contract Type
Unknown: This option is selected by default when data is converted from an earlier version.
Lump: This option would be used to identify Fixed Fee jobs. Note that the Fixed Fee validation is still performed at the Billing Item level.
T&M: This option would be used to identify Time and Material Jobs. Note that validation is still performed at the Billing Item level.
GMP Contract: When GMP Contract is selected, the maximum price for the Job as a whole must not exceed the sum of the Contract values in its Billing Items / Change Orders which are flagged as Include in GMP. If the sum of the Billing Item / Change Order values was exceeded (and Include in GMP is flagged) , a Job Journal entry will be generated via when Record Billing Adjustments saved if the Job is brought back into compliance.
GMP SoV: When GMP SoV is selected, the maximum price for each Billing Item / Change Order flagged as Include in GMP must not be exceeded.
New Field - GMP Contact Total:
This field specifies the Not To Exceed amount for GMP Contract and SoV type Jobs. When this field is updated, the system will validate that sum of the C.O. Amount (in Change Orders) and Contract Amount (in Billing Items) does not exceed the GMP Contract Total.
Main Tab
New Field - Include in GMP?
This field must be checked if this Billing Item should be included in GMP Revenue Adjustment calculations. If this field is checked, the Fixed Fee box MUST be blank.
Changed Field - Original Contract:
For GMP type Jobs, changes to this field are now validated against the Job's GMP Contract Total field. The sum of the C.O. Amount (in Change Orders) and Contract Amount (in Billing Items) may not exceed the GMP Contract Total.
Invoicing Tab
New Field - Bill Item Group:
This field allows Billing Items to be grouped for reporting purposes. This field is currently supported for a custom AIA-style invoice.
Main Tab
New Field - Include in GMP?
This field must be checked if this Change Order should be included in GMP Revenue Adjustment calculations. If this field is checked, the Fixed Fee box MUST be blank.
Changed Field - C.O. Amount
For GMP type Jobs, changes to this field are now validated against the Job's GMP Contract Total field. The sum of the C.O. Amount (in Change Orders) and Contract Amount (in Billing Items) may not exceed the GMP Contract Total.
Invoicing Tab
Bill Item Group:
This feed allows Billing Items to be grouped for reporting purposes. This field is currently supported for a custom AIA-style invoice.
New Tab: GMP
GMP %:
This field is used to calculate the add-on fee for GMP jobs. It should be completed for Job Cost Codes used for GMP Fees. It should NOT be completed for Job Cost Codes used for GMP Revenue Adjustments. Fees are calculated when Start Compute GMP Special Revenue is run as a scheduled event or when Record Billing Adjustments is run.
Cost Cat:
This field should only be completed if it is for a Job Cost Code which will be used in GMP Revenue Adjustment/Over Contract JCH entries. The Cost Category should have a Posting Cost Type & a Selection Cost Type of Other.
Filters:
Skills - Disciplines - Cost Category
If these filters are blank, the GMP % in this record will always be applied. If one or more of these filters is completed, they will be used to limit the GMP % revenue calculations.
Main Tab:
New Revenue Display Field - Over Contract:
This field is only used for GMP Contract type Jobs. It will be completed by the system if the sum of the Billing Item / Change Order values is exceeded (and Include in GMP is flagged). When Record Billing Adjustments is saved, a Job Journal entry will be generated to with a description of "** GMP Over Contract **" to account for changes to GMP Over Contract calculations.
Billing Tab:
Changed Fields
Ernd %:
Entry in this field is denied unless the Billing Item's Fixed Fee box is checked. Since Billing Items for GMP Contract Jobs are NOT Fixed Fee, this field cannot be changed GMP Contract Jobs.
C.O. Amount - Contract Original
These fields may be adjusted for GMP type Jobs. For example, the CO Amount might be changed if additional work was found. Changes to these fields are validated against the Job's GMP Contract Total field. The sum of the C.O. Amount and Original Contract Amounts may not exceed the GMP Contract Total.
Labor and Other Tabs:
These tabs are not displayed for GMP Contract and SoV Jobs.
Id: sys-viewer-srcrdbllngadjstmts
Setting Key: DefaultGMPCostCode Setting Value: Record Id for Rev Adjustment
The Setting value must specify the Id for all Job Cost Code records used for GMP Revenue Adjustments used to account for Over Contract transactions (but not the fees themselves).
For GMP Contract type billing, these Job Cost Code records should reference the Billing Item used to show the Over Contract entry on the AIA invoice (requires specific AIA report).
For GMP SoV type billing the Billing Item does not need to be entered. A new GMP tab has also been added to the Job Cost Code record.
These starter functions compute and post the revenue adjustments (fees) needed for some GMP type jobs. This special revenue will be posted to Job History as Job Journal entries (of transaction type Actual) so that they will be available for progress invoicing. The Job Journal Parent Date/Period is set from the first child line.
The Job Journal's header Description will be set to "GMP Special Revenue". The revenue will appear on the Job Journal's Expenses tab. The Description on Expense detail will indicate the calculation used to determine the fee:
$33.00 * 10.0000% - $0.00 (Daily Basis Base Revenue * GMP % - Posted Revenue)
The Automated version is designed to be run as a scheduled event at least daily. The Automated version is also launched for a specific Job when it is loaded into Record Billing Adjustments.
As Of GMP Date:
This field specifies the date as of which the Special Revenue is computed. It will default to today's date unless otherwise specified via registry.
Job Id:
This filter allows the user to limit the Jobs this function is run for.
Registry Id: sys-start-scmptegmpspclrvne
This registry is shared by the automated and manual Start Compute GMP Special Revenue functions.
Setting Key: AsOfGMPDate Setting Value: today (default is today)
This option currently supports a Setting value of today. If the Setting Value is empty, the As Of GMP Date will be set to 01011900 (the blank date).
Setting Key: defaultGMPJobId Setting Value: JobId
This option is currently deprecated.
It is not always possible to finalize the job setup for its construction jobs prior to real costs posting to JCH. This includes the list of Cost Codes, the Schedule of Values (Billing Items), the Default Billing Items for Cost Codes, the Rate Schedule info, etc.
This function's purpose is to retroactively apply Rate Schedule rates and default Billing Items to already-posted JCH data for a user-specified Job. The function presents a list of qualifying job history entries for this Job. For each selected JCH entry, it 're-thinks' billing information and updates the JCH record when changes are required.
This function also evaluates and makes adjusting Job Journal entries for billed JCH data. For any JCH entries that qualify for re computation, a Job Journal entry is generated to capture the difference in revenue amounts after the function is run. The Job Journal entries are then eligible for billing and could result in an additional invoice or a credit memo.
This process cannot be performed on a job that has an Invoice Status of either 'Ready' or 'Printed'. If the specified job has an Invoice Status of either 'Ready' or 'Printed', the user is given the opportunity (via form prompter) to reset the status to Hold. The user can either abort the recompute or elect to have the status reset to 'Hold'.
Entries Which Are Skipped:
1. GMP Special Revenue-type rows will be processed ONLY for the purpose of resetting their Billing Item Rns when necessary. Their revenue values will NOT be recomputed.
2. Entries from the following source journals are skipped:
AR Cash Receipts - AR Sales - GL Journal
Job Budget - Job Cost EOM
Bill Adjustment - IM Journal -
Quote Budget - Projected Cost - PR Check
Shop Ticket - Shop Order Jrnl
3. Reversing and reversed entries are skipped.
Entries Which Make the Selection List:
1. Entries that satisfy one or more of the following revenue-based criteria:
(a) new Revenue Rate, (b) new Billing Rate Type Id, (c) new Extended Revenue.
2. Entries also make the selection list when the JCH Billing Item no longer matches the Default Billing Item from the JCH Cost Code record.
3. Both billed and unbilled JCH data (supporting the above criteria) will be considered. .
Record Change Log entries are created for each changed JCH record and changed Source Journal Record.
An attempt is made to find and update the corresponding original source journal child lines to keep them consistent with the revised JCH. Values updated are the Revenue Rate, Unit Price, Extended Price, Billing Rate Type Id and Billing Item.
Job Id:
Enter the Job Id of the Job to be processed. This field is required.
Cost Code:
This range may be used to limit this function to the Job Cost Code(s) specified in this filter.
Billing Item:
This range may be used to limit this function to the Job Cost Code(s) specified in this filter.
Click the Go button to continue.
Do
This field enables you to select which lines should be recomputed. Double-click on the Do field to select or deselect an item (or press the Spacebar when the caret appears on this field). The following fields are displayed for informational purposes:
Type:- Date: - Quantity/Hour - Source Journal - Unit Cost - GMP Special Revenue?
Old Bill Item - Old Bill Type - Old Rvne Rate - Old Unit Price - Old Total Revenue
The current Job History detail up for recomputation.
Bill Item - Bill Type Id - Revenue Rate - Unit Price - Total Revenue
The new job history detail which will be generated when this line is recomputed.
Job Cost Categories with a Selection Cost Type of Equipment are now supported on the Inventory and Material tabs.
|
Flat Rate Category |
Revised Cost Category Rules |
Old Cost Category Rules |
|
Inventory Tab |
ok: mat, eqp |
ok: mat |
|
Material Tab |
ok: mat, oth, sub, eqp |
ok: mat, oth, sub |
Clicking the Auto Fill button now correctly displays the AR Inv Amt in the ARInvoices list.
Changed Field: Invoice Description
The Invoice Description field has been expanded from 400 to 3000 characters.
Changed Field - Invoice Amount:
Refines display of this field to correctly handle credit memos and bad debts listed in the AR Invoices tab.
Changed Field - AR Inv. Amt:
This release corrects the display of the AR Invoice Amount column so that it doesn't blank when the Consolidated Invoice is saved.
New Column: Amount Due
This new column displays the amount not yet paid on this Invoice.
If a Subcontractor PO is generated without an Other Rate Id, and you try to partially voucher it in the AP Journal it will change the Bill Type ID to n/a and remove the Revenue Rate. To avoid this problem, add a line to Other Rate tables related to Subcontractors to define how the Bill Type Id and Revenue Rate should be set if an Other Rate was NOT specified.
Example: Set the Revenue Based on the Amount:
Other Rate Table Child Tab
Other Rate Id: (blank)
Level: 99,999,999.99
Rate: 1.00
Bill Type: Multiplier
In this release, the Bill Type defaults from the Billing Rate Type specified in the Other Rate record (if not overridden by the Other Rate Table) instead of defaulting to n/a. This allows for any potential revenue to calculate when the Other Rate is manually added or imported into a work order (unless n/a is specified in the Other Rate record. In previous versions if an Other Rate record did not specify a Standard Rate, and was missing from the Rate Schedule's Other Rate table, the Bill Type would default to n/a.
When the Rate Schedule is saved, the detail lines are re-ordered with the most recent entries at the top. Validation prevents overlapping date ranges and gaps.
This release corrects the following sporadic errors: Runtime error: "containsPoint:" not understood and 'last character must be sign or digit'.
This release corrects a problem in recent versions which did not allow negative Change Orders to be processed.
A registry entry is available to automatically restarts at the Job Id input screen after clicking Save. Clicking the red X closes the function so it will not reopen. See 9.1.4 for details.
Validation has been added to warn the user if Sales or Use Tax has not been computed when the invoice is saved as Ready to Print. Validation has been extended to warn the user if Exempt Jobs have not had their Exempt Amount computed when the invoice is set / saved as Ready to Print.
The following warning will be displayed if a sales or use taxable invoice is saved as Ready To Print if there is a Next Invoice Amount but the Taxes tab is blank.
Warning: Compute Sales Tax has not been Pressed.
Ok to continue?
Click No to return to Record Billing Adjustments to click Compute Sales Tax before saving. If you click Yes to continue, the appropriate entries will NOT be made to the Sales Tax Table which is used for Tax reporting.
The Work Order COD Tab's Invoice Reference is now cleared during the Job Invoice Reverse so that the user may edit the COD child tab before re-billing the Work Order.
Changed Field: Effective Date
Validation has been added to prevent the reversal's Effective Date from preceding the invoice's original Effective Date.
When this reversal function is run, the Invoice Master will retain it's the original Effective Date,but now writes the reversal's Effective Date to the new Invoice Reversed Effective Date fields in the Invoice Master record. The Accounting Period and Description of the reversal will also be written to the new Invoice Reversed fields.
New Field: PO#
The Invoice Master PO# is now displayed in this field. This field only supports the Customer's PO# for Service Compute and Progress Jobs.
Changed Field - Effective Date:
The Effective Date of the Invoice. In Version 9.0 and below, this field was revised if the Invoice was reversed so that it falls within the reversal Accounting Period. In Version 9.1, the reversal function retains the Effective Date, but writes the reversal's Effective Date to the field below.
New Fields: - Invoice Reversed:
Period Id: Effective Date: Description:
These fields have been added to allow an invoice to be reversed without changing the original Effective Date of the invoice. These fields will be updated when Reverse Job Invoice is run.
See Customer Note *** for the Avalara Web Service.
In previous releases, updating existing Sales Tax Authorities / Groups from Avalara ignored updates where the Sales Rate was changed to zero because zero tax rate Authorities were ignored. In this release, zero tax rates updates are properly accounted for when Tax Group records are updated. However, as a result of this change, updated and newly processed Tax Groups will include Tax Authority records with zero tax rates if applicable.
This release also corrects a sporadic issue where the Sales Tax Authority information was too large to fit in the Use Tax Info fields on the detail lines of the AP Journal; Inventory Adjustments Journal; Inventory Receipts Journal; Purchase Order; and Work Order viewers. This issue emerged when updated Tax Groups included zero rate Authorities.
WARNING: Do Not Filter the Avalara Update
If you filter your Avalara update to a specific Zip Code, only that Sales Tax Group would have its Sales Tax Group Rate recalculated. If the update to that Group included changes to rates also impacting other Group (e.g., the State Rate), the applicable Tax Authority would be updated, but the other Tax Groups referencing it would not have their Group Tax Rates reset. This is a particular problem since TechAnywhere uses the Group Tax Rate. For this reason, we strongly recommend that you allow your Avalara updates to run wide open so that all applicable Sales Tax Groups will be properly updated.
The system now incorporates Sales Tax Authority GL Entities into credit-side tax cost processing when the GL Entity is not set from other sources.
Purchase Order Inventory and General lines:
Now uses GL Entity from the PO parent when available, otherwise from Tax Authority. Previously, only the PO parent's GL Entity was considered.
AP Journal: All child lines
Now uses GL Entity from the AP parent when available, otherwise from Tax Authority. Previously, only the AP parent's GL Entity was considered.
Inventory Adjustment Journal:
Now uses GL Entity from the parent when available, otherwise from Tax Authority. Previously, tax costs from To/From used the associated Company Balance Sheet GL Entity.
Work Order Inventory / Other Lines
The system now uses the GL Entity from the Tax Authority when not supplied by other defaults (e.g., Company Balance Sheet GL Entity).
Work Order Entry
The system now uses the GL Entity from the Tax Authority when not supplied by other defaults (e.g., Company Balance Sheet GL Entity).
Inventory Receipt Journal
The system now uses the GL Entity from the Tax Authority when not supplied by other defaults.
This release corrects a recent problem generating billings for Client Sites with a payment alias setup for automatic credit card payments.
When Service Compute is run, an entry to the WO's Log Tab will be made: set the Status to Billed, the Date Logged and Work Date to today's date, and the User Id to person running the Compute.
This release provides an option to clear the 'Unknown' Status condition using the Invoice Master viewer's Record > Clear Unknown menu option to Full users with access to the Invoice Master record. Doing so will clear the Invoice Id from Job History, set the Invoice Master Status to Computed making it eligible to be reused, and set the Effective Date to 1900-01-01.
Usage restrictions are as follows ...
1. Status = Unknown
2. Entry Type = Sales
3. Can't have any prior AR activity.
4. Must be Full or Special User with ability to Access/Change Invoice Master Record (this functionality was previously restricted to users running in development mode).
Note On Compute Service Invoice
When Compute Service Invoice is run, the Invoice Master Status is now set to 'Computed' when gracefully rolling back a cancelled invoice run (where the user did not confirm that the invoices had printed successfully). Previously, the Service Invoice code set the Invoice Master Status to 'Unknown' for both normal and abnormal termination of the process. Immediately following an abnormal termination the Status will be the #UserId temporary marker. Next time the same User processes ANY service invoices, the Status will be changed from the temporary marker to 'Unknown'.
If Intercompany is enabled, the balance sheet GL Entity is not 'sticky'. Customer Note 1.14 details the new registries for setting the Default Balance Sheet Entity for this journal or globally.
If Intercompany is enabled, the balance sheet GL Entity is not 'sticky'. Customer Note 1.14 details the new registries for setting the Default Balance Sheet Entity for this journal or globally.
If Intercompany is enabled, the balance sheet GL Entity is not 'sticky'. Customer Note 1.14 details the new registries for setting the Default Balance Sheet Entity for this journal or globally.
The report (RGLJRNL.rpt) dated 2016-12-16 fixes a sporadic issue where the report did not match the GL Journal viewer total debits and credits.
The new Bank Deposit Journal Report (BNKDPST.rpt) prints the Journal Entries and their associated receipts. The report runs by the bank GL Account and a Start/End date based on the Bank Deposit Effective Date.
GL Reports (.grpt) now omit printing lines for Obsolete GL Accounts when the line has no non-zero columns. This is regardless of the IncludeZeroLines registry entry.
A warning is now displayed when the user first accesses a journal entry which has been replaced by one with a higher 'tack' number. This warning is designed to prevent the user from wasting time by attempting to make changes to a journal entry record which cannot be saved because it has already been replaced. See Customer Note 1.1.2 for a registry to disable this warning globally or by individual viewer.
In Version 9.0, original EOM UVP entries posted a WorkOrder Reference Id to GL History. However, because this field was not part GL Journal itself, edited GL Journal entries lost the WO references for both the reversing and new go-forward entries. In this release, a new GL Journal column has been added (newgljrnllst.gljrnllst_rfrnce_wrkordr_rn). When EOM UVP (GL Journal) entries created in this release or later are edited, the WO reference in the reversing and go forward entries is retained in GL History.
New Field: GL Entity Usage Filter (SQL)
Reserved for future use.
New Field: GL Account Usage Filter (SQL)
Reserved for future use.
The "Total Deposit" column has been added to the Bank Deposit List views.
This release expands the Bank Deposit Journal Check No. display field from 20 to 25 characters to support the AR Cash Receipts and AR History Check numbers.
In this release, the Report Title is cleared when a GL Reporting Period is cloned: it will be set correctly based on the Fiscal Year and Date when the new record is added.
In previous releases, validation ensured that ONLY the most recent Bank Reconciliation transaction (as established by highest TrxId per GL Bank Account / GL Entity combination) was eligible for edit. This rule did not always result in the appropriate transaction being available for edit.
This release refines the edit validation so that any existing Bank Reconciliation transaction may qualify as eligible for edit, provided the edit won’t undermine or conflict with a more recent transaction. This means that transactions may be “undone” via edit in reverse transaction id sequence in order to work backwards to address an issues in Bank Reconciliation transactions prior to just the last one posted versus previously when ONLY that last transaction posted could be edited.
If the GL Account / Entity combinations for the annual sum of Debits and/or Credits exceeds 100M, this function evaluates and parses calculations that exceed table constraints into multiple GL Journal lines to prevent truncation errors.
In previous releases, the Posted By and Date Posted fields were available to users in the filter/range screen of View GL History, however not present as columns in either List View for that particular viewer. This has been corrected, and Posted By/Date Posted are now available columns when viewing the list of GL History transactions.
IMPORTANT: As of version 9.1.611.042, access to this module is now controlled via the vrgstry.cus and vrgstry.sam files. If your firm is running this module your support representative must provide you with upgraded files. This release also corrects issues with intercompany security.
Many SAMPro Users have a Construction element to their business as well as Service. Many Users also have technicians that do both Service and Construction work, depending on work load. This creates a need to schedule technicians for many days on one Job, and also see all work scheduled in one place.
Previously, the only way to accomplish this was to create Work Orders for each Job/Cost Code/Bill Item through New Call, and add several Technician dispatch lines; one for each technician for each scheduled date. This would then allow traditional dispatching and TechAnywhere use.
The Job Scheduling module allows Installation Work Orders to be generated from the Job's WO Creator tab (enabled via registry). A special starter function, Start Create Job Scheduler WOs, will be enabled when this module is purchased. It will generate the Installation Work Orders using the information provided on the Job's WO Creator Tab.
In addition, there is now a Job Scheduler tool in DBAnalytics that allows ease of finding the appropriate, available technicians for each Installation Work Order and schedule for several days at once, all while tracking scheduled vs.... estimated hours. The Job Scheduler Dispatch Board also give you a view of all work scheduled with a day, week, or two week view.
The following registry entry is required to make the new WO Creator tab (Scheduler child table) visible in the Job Viewer.
Id: sys-viewer-vjb
Setting Key: ShowJobScheduler Setting Value: true (default is false)
Id: sys-viewer-vjb
Setting Key: JobCreatorTechnicianFilter Setting Value: listoftechs
The Setting Value listoftechs would be replaced by a comma separated string of Technician Ids which are allowed to be entered on the Job's WO Creator tab. This registry may be used to force Work Orders to be created for "techs" representing areas or groups instead of actual Technicians. Since the Date and Hours on Work Orders created from the WO Creator tab are generally estimates, some users may not wish to immediately assign them to real Techs.
In previous releases, the registry setting Id: sys-viewer-vjb and setting key: childtabs the could not be reliably used because the Employee Overrides & Prevailing Wages child tabs both had the same exact TabId: wages. This resulted in display issues and an application crash when these tabs were clicked with this registry enabled.
In this release, the wages TabId on the 'Employee Overrides' tab has been changed to empwages to allow the childtabs registry to be set properly. The 'Prevailing Wages' tab retains the wages TabId.
To set the WO Tech status to something other than the default 'Pending' for these Work Orders set this registry item.
Id: sys-start-scrtjbschdlrwo
Setting Key: JobSchedulerWOTechStatus Setting Value: tech status
Where tech status is replaced by the technician status to be used when the work order is created.
Registry Id: sys-start-scrtjbschdlrwo
Setting Key: JobIdCostIdforWOName Setting Value: true (default is false)
When Work Orders are created, this option generates the Work Order Name from the Job Id and Job Cost Code Id separated by a hyphen. For example, for Job Id 1643453 and Job Cost Code Id HVAC the Work Order Name would be generated as 1643453-HVAC. If this registry is not set, the Work Order Name will be blank.
Registry Id: sys-start-scrtjbschdlrwo
Setting Key: DisableDefaultCallScript Setting Value: true (default is false)
When set to true, the Work Order's Closing Call Script (on the Other Info tab) be blank; it will NOT be set from the Site's WO Closing Call Script field.
Registry Id: sys-start-scrtjbschdlrwo
Setting Key: DefaultPO Setting Value: true (default is false)
This setting causes the new WO's PO Number to default from the Job's PO Number.
This tab provides a basis for scheduling personnel for construction/installation type jobs. The information in this tab will be used by Start Create Job Scheduler WOs to generate Work Orders for this Job; these Work Orders will be linked to this tab when they have been created. This Starter function is only available if this module has be implemented in your database.
When a Job is cloned, the contents of the WO Creator tab is also cloned (minus the Work Order link).
When the Insert/Copy button is clicked for a lines which has the WO already assigned the WO Id will not be copied.
The information on this tab, along with the Work Orders generated from it, supports a custom Job Scheduling Analytic for construction type jobs. It allows for the scheduling of workers (Technicians) for the Work Orders associated with this construction job. Since the actual scheduling is managed via Work Orders, the scheduler will also be able to view resources (Work Order Technician Tab entries) allocated to Service and PM jobs.
The Job's WO Creator tab includes a button, Create Job Work Orders. Clicking this button launches the Start Create Job Scheduler WOs function with the selected Job Id loading into the range field.
One Installation Work Order will be created for each group of lines with the same Work Start date, Job Cost Code, Job Billing Item, Equipment Id and Work Code. The certification field will act as default filter for the Job Scheduler analytic. Since the resource (Technician) scheduling will be manage via the Analytic, only a single Technician line will be included on the Work Order when it is initially generated. The Technician Id in the line will default the Work Order’s technician or the default will be set (Unassigned) if left blank. The Site Equipment's Escalation Profile to set the new WO's Escalation Profile.
Equipment Id:
The Equipment to be used when the Work Order is generated.
WO Id:
This display-only field will be completed when a Work Order has been generated from this line.
Cost Code: Billing Item:
Provides the default Cost Codes and Billing Items for the Work Order. Typically, the Cost Code would represent a phase of the job.
Work Code Id:
Provides the default Work Code when the Work Order is generated.
Certification Id:
When the custom analytic is enabled, this field will act as the default filter for the analytics Certification filter. Certifications are used in this manner might include Plumber Lead, Plumber Helper, Electrician Lead, Electrician Helper, etc.
Bud Hours:
This display-only field displays the number of hours budgeted in Job History for the Billing Item / Cost Code values specified on this line.
Est Hours:
The Estimated Hours required to complete this line. When the starter function is run to generate Work Orders, this field will be used to set the Estimated Hours field on the Work Order Equipment tab.
Work Start:
The date this work is scheduled to start. All lines with the same Work Start Date Job Cost Code, Job Billing Item, Equipment Id and Work Code will be combined into one Work Order when Start Create Job Scheduler WOs is run.
Tech Id:
If completed, this Technician will be assigned to the Work Order generated for this line. Typically, this would be used to specify a placeholder (unassigned) for the Company or Branch the Job belongs to.
Work Requested:
This required field will be used to set the Work Order and Work Order Equipment Work Requested fields when the Work Order is generated.
The information on the Job's WO Creator tab is used by this function to generate Work Orders for this Job.
Start Date: End Date:
These fields define the range of Start Work Dates on the Job's WO Creator tab that you wish to create Installation Work Order. You may enter the dates in mm-dd-yyyy format or double-click on these fields to access the calendar viewer to do so.
Job Id:
If you wish to only create work orders for specific Job Id (or double-click to select from a list). Several Jobs may be specified by separating their Id's with a comma.
Click the Go button to continue.
This checklist appears immediately after the Create Job Schedular WOs starter function has been run so that you can verify which Installation Work Orders will be generated
Important Fields:
Do
This field enables you to select which Installation Work Orders should be generated. A check appears in the Do field if an item is selected. Double-click on the Do field to select or deselect an item (or press the Spacebar when the caret appears on this field).
Job Id: Cost Code: Bill Item: Work Code Id: Equipment Id:
Work Start: EstiHrs: Tech Id: Cert Id:
These fields are displayed for informational purposes so that you can verify which PM's should be generated.
Click the Go button to generate the selected Work Orders.
This version extends Double Signature support to MICR PR Checks. A v.cus supporting a double-line form is also required for this functionality. To force a double signature line on a Payroll check for amounts exceeding $10,000 (for example) use:
Id: sys-report-rprchck
Setting Key: DoubleSignatureAmount Setting Value: 10000
Registry Id: sys-report-rprchck
Setting Key: SkipPrintEFTChecksIfEmailAddressSetup Setting Value: true
This registry setting will skip printing the PR Check if the Employee's email address is set up and print a 'voided' check if the Employee's email address is blank.
Important: the following Registry settings for must also be enabled for this new registry setting to take effect:
Setting Key: SkipPrintEFTChecks Setting Value: true
Setting Key: AutoSaveBySection Setting Value: true
Some recent versions of Troy printer drivers (and other drivers used to print MICR checks) require that a specific MICR font is specified in the SAMPro check reports. In previous versions this required a customization file to specify the font and font size. In this release, the MICR font may be specified in the registries for Payroll, Accounts Payable and PR Miscellaneous Deductions checks. The true type GnuMICR font is currently recommended for most applications.
Important: The MICR font must be installed in Windows on all computers checks will be run from.
Id: sys-report-rprchck
Setting Key: FontForMICR Setting Value: GnuMICR
The Setting Value is case sensitive - be sure that matches the filename of the true type font file. Note that the file extension is NOT included in the Setting Value.
Setting Key: PointSizeForMICR Setting Value: 10 (point size for font default is 10)
Additional registry entries are required for MICR printing: see Help for additional settings for check printing.
This case extends Double Signature support to MICR PRMD Checks. A v.cus supporting a double-line form is also required for this functionality. To force a double signature line on a Miscellaneous Deduction check for amounts exceeding $10,000 (for example) use
Id: sys-report-rprmdchck
Setting Key: DoubleSignatureAmount Setting Value: 10000
This release adds support for the followings registry options to the PR Miscellaneous Deductions check (sys-report-rprmdchk) and the AP Manual Check (sys-report-rapchckmnl).
Id: sys-report-rprmdchck
Setting Key: DefaultGLBankAccount Setting Value: GLAccountId or
Setting Key: GLBankAccount Setting Value: GLAccountId
Setting Key: DefaultGLBankEntity Setting Value: GLEntityId or
Setting Key: GLBankEntity Setting Value: GLEntityId
The GLBankAccount and DefaultGLBankAccount options provide a means of defaulting the bank account. Use of GLBankAccount and DefaultGLBankAccount should be thought of as mutually exclusive even though the Registry viewer won't prevent it. Do not use both!
Intercompany Note: If the DefaultGLBankAccount option is set, the GL Bank Account specified in the registry defaults when the user selects the Company (or it defaults if only one Company is specified in the database). The Account is cleared if the user selects a different Company for which the registry is not set.
The rules for Entity defaulting and validation are similar to the above description for GL Accounts.
Id: sys-report-rprmdchck
Setting Key: disabledFieldsParent Setting Value: glentty.id
This option is designed to prevent the GL Entity from being inadvertently entered for non-Intercompany SAMPro installations. It should only be enabled if the GL Entity should NEVER be entered when printing this type of check.
Some recent versions of Troy printer drivers (and other drivers used to print MICR checks) require that a specific MICR font is specified in the SAMPro check reports. In previous versions this required a customization file to specify the font and font size. In this release, the MICR font may be specified in the registries for Payroll, Accounts Payable and PR Miscellaneous Deductions checks. The true type GnuMICR font is currently recommended for most applications.
Important: The MICR font must be installed in Windows on all computers checks will be run from.
Id: sys-report-rprmdchck
Setting Key: FontForMICR Setting Value: GnuMICR
The Setting Value is case sensitive - be sure that matches the filename of the true type font file. Note that the file extension is NOT included in the Setting Value.
Setting Key: PointSizeForMICR Setting Value: 10 (point size for font default is 10)
Additional registry entries are required for MICR printing: see Help for additional settings for check printing.
The Salaries DB Entity is typically supplied by the Cost Code. In some scenarios, it may be desirable to have the Entity come from the Employee when available.
When the following registry setting is implemented, the Employee's GL Entity is used as the Debit Entity (if not overridden by the Earnings Record) for ALL earnings that have both Job Cost Labor Entry and Job Cost PR Check set to false. Note that the Debit GL Entity from the Earnings record (if completed) still has the highest priority, with or without the registry.
Id: sys-ffv-global-settings
Setting Key: UseEmployeeEntityForEarningsNotCosted Setting Value: true
WARNING: the new registry option 'UseEmployeeEntityForEarningsNotCosted' has different behaviors for the DB and CR sides. Hierarchy is as follows:
DB without new setting ... Earnings DB Entity, Cost Code Entity, Employee Entity
DB with new setting ... Earnings DB Entity, Employee Entity, Cost Code Entity
CR without new setting ... Employee Entity, Earnings CR Entity
CR with new setting ... Earnings CR Entity, Employee Entity
This release implements an option to accrue burden for overhead labor without forcing Burden GL to use Wage GL. This enables Burden allocations on time charged to indirect jobs.
Id: sys-ffv-global-settings
Setting Key: AccrueBurdenCostForOverheadLabor Setting Value: true
Note:
The ReclassifyBurdenCostForOverheadLabor option is similar but set the Burden GL equal to the Wage GL when the accruing the burden. AccrueBurdenCostForOverheadLabor allows the Burden GL to stay as specified in the accrual.
Configuration Note:
If both Global Settings option AccrueBurdenCostForOverheadLabor and UseEmployeeEntityForEarningsNotCosted are set to true, configuring Standard Cost Earnings records so that the GL Debit and GL Credit point to the same account leads to a net zero GL effect when standard costs are charged to overhead jobs.
The registry fixes known labor costing issues where the dollars posted to GL Cost-of-Sales and JCH do not match. When enabled, is acts as a comprehensive calculator for Labor Pay Rates, Job Cost Rates and GL Accruals, impacting payroll calculations in the Labor Journal, WO Labor, WO Entry, the Employee Rate Test tab, and Start Compute Payroll.
Id: sys-ffv-global-settings
Setting Key: LaborRatesAndAccrualMethod Setting Value: 7687
IMPORTANT NOTE: We strongly recommend discussing this option with your support rep AND running tests with this registry enabled BEFORE turning it on in your live system. In general, this option should make posting more accurate, but it may be impacted by the customer's specific configuration. The new Select Rate Method to Test field on the Employee Rate Test tab will help with initial testing (Customer Note 12.5.2).
Employee Viewer Rate Test Tab:
New Field: Select Rate Method to Test
By default, the Rate Method will be set to configuration currently in use (see table below). Switching to a different Method resets the Rate Test Tab to the values which would be obtained if that method were in effect.
|
Method |
Implemented Via |
|
7687 |
Registry Id: sys-ffv-global-settings Setting Key: LaborRatesAndAccrualMethod Setting Value: 7687 |
|
6654 |
Registry Id: sys-ffv-global-settings Setting Key: LaborJobCostRateMethod Setting Value: New |
|
4124 |
Registry Id: sys-ffv-global-settings Setting Key:LaborJobCostRateMethod Setting Value: BurdenOnWagesOnly |
|
989 |
Pay Type implemented as an option in the Employee Earnings and Earnings Group List tables |
Registry Id: sys-aft-
Setting Key: Format Setting Value: TD80
See Help for additional required fields AFT processing. Make sure that the edOriginatorName field is a max of 15 characters.
This registry provides an override to the labor line GL Entity which normally defaults from the Job Cost Code for Burdens Not Costed.
Registry Id: sys-ffv-global-settings
Setting Key: UseEmployeeEntityForBurdenNotCosted Setting Value: true (default false)
If enabled, the system will use the GL Entity from the Employee instead of the Job Cost Code if: 1) Both the Job Cost Labor Entry AND Job Cost PR Check fields are blank in the Earnings Record AND 2) The Earnings Record is of Type Burden. This registry applies to Direct and Indirect (OH) Job.
This registry enables different behaviors for the DB and CR sides. Hierarchy is as follows:
DB without new setting ... Earnings DB Entity, Cost Code Entity, Employee Entity
DB with new setting ... Earnings DB Entity, Employee Entity, Cost Code Entity
CR without new setting ... Employee Entity, Earnings CR Entity
CR with new setting ... Earnings CR Entity, Employee Entity
This registry provides an override to the labor line GL Entity which normally defaults from the Job Cost Code for Indirect Burdens.
Registry Id: sys-ffv-global-settings
Setting Key: UseEmployeeEntityForIndirectBurden Setting Value: true (default false)
If enabled, the system will use the GL Entity from the Employee instead of the Job Cost Code if: 1) the Earnings Record is of Type Burden AND 2) The Job is Indirect (Overhead field check).
This registry enables different behaviors for the DB and CR sides. Hierarchy is as follows:
DB without new setting ... Earnings DB Entity, Cost Code Entity, Employee Entity
DB with new setting ... Earnings DB Entity, Employee Entity, Cost Code Entity
CR (with or without new setting) ... Employee Entity, Earnings CR Entity
This registry provides an override to the labor line GL Entity which normally defaults from the Job Cost Code for Indirect Standard Costs.
Registry Id: sys-ffv-global-settings
Setting Key: UseEmployeeEntityForIndirectStandardCost Setting Value: true (default false)
If enabled, the system will use the GL Entity from the Employee instead of the Job Cost Code if: 1) the Earnings Record is of Type Standard Cost AND 2) the Job is Indirect (Overhead field checked).
This registry enables different behaviors for the DB and CR sides. Hierarchy is as follows:
DB without new setting ... Earnings DB Entity, Cost Code Entity, Employee Entity
DB with new setting ... Earnings DB Entity, Employee Entity, Cost Code Entity
CR (with or without new setting) ... Employee Entity, Earnings CR Entity
This registry provides an override to the labor line GL Entity which normally defaults from the Job Cost Code for Direct Wages Not Costed.
Registry Id: sys-ffv-global-settings
Setting Key: UseEmployeeEntityForDirectWagesNotCosted Setting Value: true (default false)
If enabled, the system will use the GL Entity from the Employee instead of the Job Cost Code if: 1) Both the Job Cost Labor Entry AND Job Cost PR Check field are blank in the Earnings Record AND 2) The Earnings Record is of Type Wages AND 3) the Job is Direct (Overhead field blank).
This registry enables different behaviors for the DB and CR sides. Hierarchy is as follows:
DB without new setting ... Earnings DB Entity, Cost Code Entity, Employee Entity
DB with new setting ... Earnings DB Entity, Employee Entity, Cost Code Entity
CR (with or without new setting) ... Employee Entity, Earnings CR Entity
This release implements registry-controlled refinements for the Earnings record's Taxable flag. This lets you specify that tax for certain specified Authorities or Groups should NOT be assessed for a Taxable fringe. The User1 and User2 fields of the Earnings Record are used to specify which taxes to exclude. The following registries are required to enable this functionality.
Id: sys-compute-payroll
Setting Key: FringeTaxExceptionUser1 Setting Value: TaxAuthorityId
Setting Key: FringeTaxExceptionUser2 Setting Value: TaxTableId
(Note: the Setting Values of TaxTableId or TaxAuthorityId can be used with either of the above setting keys.)
If either or both of these registries are enabled, Compute Payroll checks the User 1 and/or User 2 fields of the Earnings Record to see if there are any Taxable Fringes should NOT be taxed by the listed Tax Authorities or Tax Tables. Note that this ONLY works for Tax Tables specified as 'Always Withhold' on the Employee's taxes tab.
Earnings Record:
Changed Fields: Earnings User1 - Earnings User2
These fields may be used to specify a list of Tax Groups or Tax Authorities for which tax should NOT be assessed if enabled via the above registry setting:
If the Earning Record is of Type Fringe, with the Taxable box checked AND
The FringeTaxExceptionsUser1 or FringeTaxExceptionsUser2 registries are set AND
The Tax Table is specified as 'Always Withhold' on the Employee's taxes tab.
This release addresses a problem with the option format ADPKaback. The conflict using the PRS Reimb Code in Other Rate records for PR Export processing in conjunction with TechAnywhere has been resolved.
This release also supports earnings 3 code ADC (Additional Compensation).
This new format provides a customized ADP detail record generated by the Report PR Export function. This new processing will be enabled via the following registry options and entries in the Employee User2 field and with consultation with ADP.
Id: sys-pr-export
Setting Key: format Setting Value: ADPKaback
Setting Key TaxFrequencyField Setting Value: emplye_usr2
Note: If the ADPKaback format is specified, the FileId, PathName and CompanyCode keys must also be completed in the registry. The AltEmployeeIDField key is supported. It is optional and if the key is not present, the emplye_id field is used.
Employee Record
The Employee User2 field must be set to the appropriate TaxFrequency value. This value will be included in the ADP export detail for the ADPKaback format.
The following registry setting may be used to override the Pay # in the PR Export file for the ADPKaback format only:
Id: sys-pr-export
Setting Key: PayNumberField Setting Value: emplye_usr3
For example, entering a 0 (zero) in emplye_usr3 field would force a blank to be printed in the Pay# field in the export file.
The following changes were made to the custom Paychex format PayChexDayNite:
Extract the new PayChex Employee # (Employee User1 field) into Employee Id, positions 1-6
Do not extract the SS# into positions 119-128, leave blank.
The Report PR Export function now supports the Paychex SPI Flex Format. The following registry is required to enable this functionality.
Id: sys-pr-export
Setting Key: format Setting Value: PaychexSPI
This setting specifies that the Paychex SPI Flex format will be exported. If this setting is enabled, the Paychex format setting should not be enabled!
Setting Key: PathName Setting Value: path
This setting specifies the complete path of the directory to which SAMPro will export the Paychex file.
Setting Key: ClientNumber Setting Value: client#
This required setting specifies the client number assigned to your firm by Paychex. It will be used to generate part of the filename of the Paychex file.
Registry Id: sys-viewer-vlbrjrnl
Setting Key: DefaultJobByEquipmentId Setting Value: true
By default, the system uses the Job in the Work Order header as the default job for entering WO-related detail in the Labor Journal. This release supports the above registry setting to alter this behavior. If this registry entry is enabled (and the referenced WO is NOT preventative maintenance), the system will check to see if there is a default service job in the equipment header. If so, the Job, Cost Code and Billing item to the from the Equipment will be defaulted instead of from the WO header. If the job info is blank in the equipment record, the system uses the job info in the work order header.
The TechAnywhere Labor Post also follows this registry.
For Preventive Maintenance Work Orders, Job information defaults from the WO header, regardless of whether or not this registry entry is enabled.
Note: registry options to provide this functionality is also available in the Work Order, AP Journal and Purchase Order registries. A separate registry will be provided to support this functionality in TechAnywhere posts to the Labor Journal in a future release.
In previous releases of version 9.1, the Employee's Earnings and Deductions group tabs, and the Earnings Group and Deduction Group child tabs were automatically sorted in descending order by the End Date of each child line. Due to issues maintaining complex Earnings and Deduction Groups, the default behavior has been changed back so that the lines are NOT resorted when the record is saved. If you wish to have the child lines sorted, the following registry settings(s) must be implemented:
Id: sys-viewer-vernngsgrp (Earnings Group)
Setting Key: NoSortOnChildren Setting Value: false (default is true to prevent sorting)
Id: sys-viewer-vddctngrp (Deduction Group)
Setting Key: NoSortOnChildren Setting Value: false (default is true to prevent sorting)
Id: sys-viewer-vemplye (Employee - Earnings and Deductions Tabs)
Setting Key: NoSortOnChildren Setting Value: false (default is true to prevent sorting)
Registry Id: sys-ffv-global-settings
Setting Key: PRAccrualGLEntityMatch Setting Value: true (default false)
When this registry is enabled, the Earnings Credit/Debit will always be the same for PR-to-GL accruals. When enabled, the credit side GL Entity of an Earnings ID will follow the same GL Entity used by the Debit (instead of using the GL Entity on the Employee record).
This registry provides optional control over the use of the Employee GL Entity specified on the Employee record's Other tab. By default, the Employee record's GL Entity is used as the primary source when Compute Payroll is run. The GL Entity in the Payroll Tax Authority, Deductions, Earnings or Worker's Company records provide a secondary source for the GL Entity if the GL Entity is blank in the Employee record.
The following registry reverses the default behavior, using the Employee's GL Entity as the secondary source and the control record's (Payroll Tax Authority, Deductions, Earnings, Worker's Comp or Other Rates operating as payroll Reimbursement codes) GL Entity as the primary source of the GL Entity.
Id: sys-ffv-global-settings
Setting Key: EmployeeGLEntityPayrollToGLH Setting Value: secondary
Print PR Checks supports the Hard Block Branch logic (implemented by the global registry BranchFilterWithHardBlock option) in this version. The Hard Block on Branches is maintained regardless of how the Branch filter range is set.
New Field - Check Print: All Checks - Physical Checks - EFT Checks
This field may be used to separate EFT and Physical Checks. The All Checks option prints both Physical and EFT checks. Select Physical Checks to only print live checks, or EFT Checks to live the run to EFT's.
The new Federal Tax Rate and State Tax Rate overrides on the Labor Journal Hours Tab Detail allow large Bonus Checks to be generated without the need change the Employee Record's Taxes tab. See Customer Note 12.17.4 for additional information on using the new fields.
1. Establish a new PAYROLL PERIOD for bonus checks. Example: 2017-Sept-B.
Note: Unless overridden via registry, BONUS amounts (entered on the Labor Journal) will NOT Accrue/post to the GL, regardless of how the Accrue to GL field is checked in the Payroll Period.
Note: PTO Accrual and Bonus Pay Periods
Typically, PTO Hours would not be accrued on bonus payroll periods. Do NOT check the Accrue PTO or the Remote Technician Applet boxes on you Bonus Payroll Period.
2. Establish a new PAY TYPE if one doesn't already exist.
Pay Type Id: Bonus Description: Bonus Check Label: Bonus
Rate Factor: 1.000 Show Rate on CK: optional
Hours Type: Other GL Acct Id: GL for Wages or Bonus Wages
Earnings Grp Id: n/a
3. In the LABOR JOURNAL, enter all bonus amounts using the new bonus Pay Period Id setup in step 1 above (example: 2017-Sept-B).
After inputting zero hours to an overhead Job and your Bonus Pay Type, double click on the MAGNIFY GLASS of the line. Confirm and edit as follows:
Hours: 000.00
Salary? (not checked)
Extra? (not checked)
Pay Type Id: Bonus
Bonus Amount: Enter Bonus Dollars to Pay this Employee
Federal Tax Rate:
State Tax Rate:
These fields provide a flat rate override to the Federal / State Income Tax rate brackets in the Employee's Federal (FED-M or FED-S) and State Tax Tables. These fields are intended to be used for Bonus pay only. If these field are blank, the Federal / State Tax Table will be used as before. Enter the appropriate rate for bonuses prescribed by the tax authority.
Important Notes On Usage:
1. The overriding federal and/or state tax rates are applied directly to the Bonus Amount with which they are associated. Taxable wage reductions (125, 401k, etc) are NOT applied to the Bonus Amount before computing FIT/SIT using the special tax rates. Tax is on Total Earnings when using this option. If this is not desired, the old methodology of changing the Employee record's Tax tab to specify a flat tax FED-bonus entry may be used instead.
2. Taxable wage reductions will eventually reduce the Taxable Wages so payroll reports, including W2s, will have the correct info.
Consider the example where an employee received a $10,000 bonus with 20% special FIT tax rate, 10% special SIT tax rate and 5% 401k deduction. In the event special tax rates have been specified, the following is the order in which the calculations occur:
Gross Wages = $10,000
FIT = $2,000 (10,000 x .2)
SIT = $1,000 (10,000 x .1)
401k = $500 (10,000 x .05)
Taxable Wage = $9,500 (10,000 - 500)
4. Run the COMPUTE PAYROLL function for the new bonus Pay Period Id and the print the PAYROLL WORKSHEET before printing your checks to confirm your bonus checks are correct for the new bonus Pay Period Id.
Tip: Use Pay/Deduct Cycle Code XXXX to skip all deductions!
This release corrects an issue on checks grouped by Vendor; the total is now correctly printed according to the detail lines on check.
This report supports the Hard Block logic (implemented by the BranchFilterWithHardBlock global settings registry option) in this version. The Hard Block is maintained regardless of how the Branch filter range is set.
This release supports GL Debit and Credit posting for Deductions withholding (PR Check) & relief (PRMD Check) using the following GL Entity posting precedence:
1. As per Employee GL Entity reference if present, else
2. As per Deduction Code GL Entity reference if present, else
3. As per Respective Check processing "Bank " GL Entity referenced
New Option: Include Dir Deposit Section?
The revised Report Payroll Worksheet (RPRWRKSv90b001.rpt) dated 2017-11-14 includes a Direct Deposit section which is enabled by checking this option. For employees with no check issued for the pay period, the section will show the appropriate info from the Direct Deposits tab in the Employee record. For employees with a check issued for the pay period, the report will show direct deposit info from the check table.
This report also includes the Branch Id as a filter, and supports the Hard Block logic (implemented by the BranchFilterWithHardBlock global settings registry option) on the report. Note that report filters will not display the User's branch filters but the Hard Block is handled by the report.
Executive PR processing has been added to the following reports via the following filter:
New Filter - Executive PR:
If you are an Executive Payroll user, this field will default to Y; to run this function for all employees (Executive or not) clear this range. If your User record is not flagged as Executive Payroll, you will only be able to run this function for other non-Executive users even if you clear the filter.
New Filter - Executive PR:
This function is now sensitive to whether the user has Executive PR privileges. If you are an Executive Payroll user, this field will default to Y; to run this function for all employees (Executive or not) clear this range. If your User record is not flagged as Executive Payroll, you will only be able to run this function for other non-Executive users even if you clear the filter.
New Filter - Executive PR:
This function is now sensitive to whether the user has Executive PR privileges. If you are an Executive Payroll user, this field will default to Y; to run this function for all employees (Executive or not) clear this range. If your User record is not flagged as Executive Payroll, you will only be able to run this function for other non-Executive users even if you clear the filter.
This system report supports Executive PR and Security (Intercompany).
New Filter - Executive PR:
This report is now sensitive to whether the user has Executive PR privileges. If you are an Executive Payroll user, this field will default to Y; to run this function for all employees (Executive or not) clear this range. If your User record is not flagged as Executive Payroll, you will only be able to run this function for other non-Executive users even if you clear the filter.
This new report, dated 2015-08-19, excludes AP and PRMD checks. Only PR checks (both Executive and non-Executive PR) will be listed.
See Customer Note 12.2.16 for updated information on the new T4 (Standard) reports which do not require a Native PCL printer.
This release supports an enhancement to allow Earnings records to be set up with a W2 Category of OI:40 and an Earnings Type of Wage.
Earlier fixes to T4 fields include:
1. Union Dues reporting in Box 44
2. Employee and Company Registered Pension Plan contributions in Box 52
3. Any Earning or Deduction specifying an Other Information Box # (W-2 Category = OI:xx eg OI:40.
This release corrects an issue with the Employer EI Premium being overstated on the T4 Summary.
The 4-up options of BC2, 1x4 & Dx4 have been removed. These options were previously deprecated due to alignment issues.
The release modifies the logic to skip print of Local Line 2 in Copy 2 of W2 (registry enabled) so that line 1 taxes are displayed correctly.
The W2 Year is now printed below the Copy label on the Plain Paper Copy version of the report.
If Intercompany processing is enabled then the following W2 Employer Info will now come from the appropriate Company records, NOT the registries:
Company Name
Company Address
Company Federal EIN
In previous releases, it was necessary for Intercompany users to generate multiple registries to support this information: companyname-securityid, companyaddress-securityid, companyfederalEIN-securityid.
If Residual Tax Withholding is used, Local wages may be overstated on Copy 2 of the W2's. The following new registry entry will omit the print of Local Line 2 on the W2's.
Id: sys-report-rw2
Setting Key: OmitCopy2LocalLine
Setting Value: true (default is false)
Some customers are configured to use Local Tax Authorities for Counties and Other Tax Authorities for Cities. This registry should be enabled to include Cities (flagged as Other) in the W2 Copy 1 & Copy 2 for localities.
Id: sys-report-rw2
Setting Key: ProcessOtherAsLocal Setting Value: true (default is false)
This release corrects the landscape formatting of the printed Electronic Payment Register report generated when Report EFT Payroll is run to produce the electronic file for direct deposit.
This release corrects the landscape formatting of the printed Electronic Payment Register report generated when Report AFT Payroll is run to produce the electronic file for direct deposit.
The revised report (RPRDEDDTL.rpt) dated 2017-08-30 includes a new filter range for the GL Entity ID which relates to the GL entity assigned to the employee records.
Corrects a problem where duplicate lines appeared if the Employee Deductions Tab included multiple lines with the same Deduction Id for different date ranges. This system report does not need to be installed.
The 4-up options of BC2, 1x4 & Dx4 have been removed. These options were previously deprecated due to alignment issues.
The new Report PR W-2s (Standard) and Report PR W-3s (Standard) do not require a printer that supports native PCL printing with a PCL 5 or 5c printer driver. These report may required some changes to your existing registry entries, but are much simpler to run. If you still have the same printer / printer driver that you used for your W2’s last year, you may use the old version of Report PR W-2.
Step 1. Once the new version has been installed, run Start Function List Update to add the new reports (Report PR W-2s (Standard) and Report PR W-3s (Standard) to the Report menu.
Step 2. Go to the User Group (versions 9.0 and 9.1) or User Groups and Functions (version 8.2) record for the users who will run these reports and give them access to the new reports. They must log off and back on to access the reports. Note that if you are running under User Group All you must also log off and on to run the new reports.
Step 3. The new Report PR W-2s (Standard) and Report PR W-3 (Standard) use the same registries as the old reports – review or create these registries/records as needed:
companyEINfederal (see Help for details)
Company Record: If Intercompany processing is enabled then the following W2 Employer Info will now come from the appropriate Company records, NOT the registries: Company Name, Company Address, Company Federal EIN
sys-report-rW2 (also sets contact info for the W-3 – see Help for details)
Changes for W2 Printer Registry
sys-printer-w2 (sets margin adjustments)
Tip: Most printers require negative margin adjustments for the new Report PR W-2s (Standard). We recommend starting with the following settings and adjust as needed following your alignment print:
Id: sys-printer-w2
Setting Key: marginx Setting Value: -0.05
Setting Key: marginy Setting Value: -0.6
Reminder: Negative margin setting values move the report text closer to the upper left-hand corner. Setting values without the negative sign move the report text to the right (marginx) and down (marginy).
Note: it is not necessary to specify a default printer in this registry if you are using the new Report PR W-2s (Standard) report.
New Registry for W3 Printer
The following registry may be used to specify margin adjustments on the W-3 if they are different from the W-2. Most printers require negative margin adjustments for the new Report PR W-3s (Standard). We recommend starting with the following settings and adjusting as needed following your alignment print:
Id: sys-printer-w3
Setting Key: marginx Setting Value: -0.05
Setting Key: marginy Setting Value: -0.72
Step 4. Unless your support representative updated your Folders view or made the appropriate Function Substitution, you will need to run the new reports from the Report Menu. Run Report W-2 (Standard) and print a test alignment of your tax forms for one or two employees before running all copies. You will be prompted to run the W-3 (see the W3 Printing Tip below), although Report PR W-3s (Standard) may be also be run stand-alone.
Make any adjustments needed to the horizontal or vertical positions via the sys-printer-W2 and/or sys-printer-W3 registries and recheck for alignment as needed.
Step 5. Once you are happy with your alignment, run the necessary copies of your W-2 and W-3 forms (see Help for details).
W3 Printing Tips:
The Copy A option of Report PR W-2s (Standard) allows the printing of a W3 form at the end of the report. The system will print the Copy A’s and summary page as usual, and then pause. The following message box will appear:
Print W3 Form? Insert W3 Form Now.
If you want to print the W3, DO NOT RESPOND TO THIS MESSAGE IMMEDIATELY. To print the W3 form, the user should verify that all Copy A’s plus the summary page have been printed, and then load the W3 form in the printer.
After the W3 form has been loaded, the user should then click Yes in the message box to display and then print the W3 form. Note that if taxes for more than one state have been assessed, an X will be printed in the State portion of Box 15, and the Employer’s state ID number will be blank.
This release supports an enhancement to allow Earnings records to be set up with a W2 Category of OI:40 and an Earnings Type of Wage.
The new Report PR Canadian T4s (Standard) and Report PR Canadian T4 Summary (Standard) do not require a printer that supports native PCL printing with a PCL 5 or 5c printer driver. These reports may require some changes to your existing registry entries, but are much simpler to run. If you still have the same printer / printer driver that you used for your T4’s last year, you may use the old version of Report PR Canadian T4.
Step 1: Once the new version has been installed, run Start Function Update to add the new reports (Report PR Canadian T4s (Standard) and Report PR Canadian T4 Summary (Standard) to the Report menu.
Step 2: Go to the User Group (versions 9.0 and 9.1) or User Groups and Functions (version 8.2) record for the users who will run these reports and give them access to the new reports. They must log off and back on to access the reports. Note that if you are running under User Group All you must also log off and on to run the new reports.
Step 3. The new (Report PR Canadian T4s (Standard) and Report PR Canadian T4 Summary (Standard) the same registries as the old T4 reports – review or create the registries listed below as needed.
Changes for T4 Printer Registry
This registry manages the margin adjustments to enable the report to align correctly on the form.
Tip: Most printers require negative margin adjustments for the new Report PR Canadian T4s (Standard). We recommend starting with the following settings and adjust as needed following your alignment print:
Id: sys-printer-t4
Setting Key: marginx Setting Value: -0.63
Setting Key: marginy Setting Value: -0.85
Reminder: Negative margin setting values move the report text closer to the upper left-hand corner. Setting values without the negative sign move the report text to the right (marginx) and down (marginy).
It is not necessary to specify a default printer in this registry if you are using the new Report PR Canadian T4s (Standard) report.
New Registry for T4 Summary
The following registry may be used to specify margin adjustments on the T4 Summary (Standard) if they are different from the T4 (Standard). Most printers require negative margin adjustments for the new Report PR Canadian T4 Summary (Standard). We recommend starting with the following settings and adjusting as needed following your alignment print:
Id: sys-printer-t4summary
Setting Key: marginx Setting Value: -0.55
Setting Key: marginy Setting Value: -0.95
Step 4. Unless your support representative updated your Folders view or made the appropriate Function Substitution, you will need to run the new reports from the Report Menu. Run Report PR Canadian T4 (Standard) and print a test alignment of your tax forms for one or two employees before running all copies. You will be prompted to run the T4 Summary (although Report PR Canadian T4 Summary (Standard) may be also be run stand-alone).
Make any adjustments needed to the horizontal or vertical positions via the sys-printer-t4 and/or sys-printer-t4summary registries and recheck for alignment as needed.
Step 5. Once you are happy with your alignment, run the necessary copies of your T4 forms. A message will be displayed while the forms are still printing:
Print T4 Summary Form? Insert Form Now.
If you want to print the T4 Summary, DO NOT RESPOND TO THIS MESSAGE IMMEDIATELY. The user should verify that all T4's have been printed, and then load the T4 Summary form in the printer.
After the T4 Summary form has been loaded, the user should then click Yes in the message box.
Registry for Setting Contact Info for the T4 Summary
Id: sys-report-rT4
Setting Key: t4contactperson Setting Value: Firstname Lastname
Setting Key: t4telephone Setting Value: aaa eee nnnn
(Note: you must include 3 spaces in between each set of numbers)
Setting Key: t4extension Setting Value : nnn
Setting Key: t4sin1 Setting Value : # # # # # # # # #
Setting Key: t4sin2 Setting Value : # # # # # # # # # (if applicable)
Setting the Company Name and Address for the T4 and T4 Summary
Id: companyname
Contents: Your Company Name
The Company Name printed on the T4 and T4 Summary Reports is derived from the companyname registry. The name may be entered in the header Contents field: a Setting Key and Value are not required.
Id: companyaddress
Setting Key: Line1 Setting Value: Street Address
Setting Key: Line2 Setting Value: City, Prov, Postal Code
Tax Authority Records
For any provincial Tax Authority Records, you need to put the province code in the ‘Prov:’ field.
Deduction Records
For the deduction records for Union Dues or Charitable, need to populate field ‘Deduction User 1’ with Dues or Charitable, respectively.
Employee Records
For any employee that is CPP, EI or PPIP exempt, in the Employee Viewer, on the ‘User Fields’ tab, need to populate Employee User 8, 9 or 10 respectively with a ‘Y’.
The revised Report W2 Electronic File (RW2EFb72vb105.rpt) dated 2018-02-16 supports the following options:
Philadelphia W2's
To support Philadelphia Electronic W2 filing the following additional registry options must be enabled:
Id: sys-w2-ef
Setting Key: reEmployerContactName Setting Value First Name Last Name
Setting Key: reEmployerContactPhoneNumber Setting Value:
Enter the area code and phone number without parentheses or hyphens.
Setting Key: reEmployerContactPhoneExtension Setting Value: if applicable
Setting Key: reEmployerContactEMail Setting Value: email of the contact at your firm
Setting Key: reEmployerContactFax Setting Value: fax of the contact at your firm
Setting Key: rsStateControlNumber Setting Value: as supplied by the state of PA
NOTE: The registry entry for rsStateControlNumber should only be enabled for Philadelphia W2 reporting. This registry must be disabled when generating electronic W2s for other authorities.
Oklahoma W2's
To support Oklahoma State Electronic W2 filing the following additional registry options must be enabled:
Id: sys-w2-ef
Setting Key: rsOKWithholdingAccountNumber
Setting Value: as supplied by the state of Oklahoma
Report PR 941 Quarterly Summary (RPR941S.rpt)
The revised report dated 2016-04-16 or later supports SS Rate information stored in only FICA SS table or split between FICA SS & FICA SSER. This is not a recent update but it is important.
Report PR 941 Quarterly Summary (State) (RPR941SSTE.rpt)
This new report is designed to assist the user in completing the Employer’s Quarterly State Tax Return. The user specifies the PR Year, PR Quarter and State when running the report.
Report Payroll Employee Data (RPREMPD.rpt)
The revised report dated 2018-12-12 supports Intercompany Security and other refinements.
Report PR Payroll Register (RPRREGR.rpt):
The revised report dated 2018-12-12 supports Intercompany Security and signed total fields.
Report PR Summary (RPRSUMM.rpt)
The revised report dated 2018-12-12 supports Intercompany Security and other refinements.
Report PR Federal Tax (RPRTAXF.rpt)
The revised report dated 2018-12-12 supports Intercompany Security and other refinements.
Report PR Local Tax (RPRTAXL.rpt)
The revised report dated 2018-12-12 supports Intercompany Security and other refinements.
Report PR Other Tax (RPRTAXO.rpt)
The revised report dated 2018-12-12 supports Intercompany Security and other refinements.
Report PR State Tax (RPRTAXS.rpt)
The revised report dated 2018-12-12 supports Intercompany Security and other refinements.
Report PR Workers Compensation Summary (RPRWCIS.rpt)
The revised report dated 2018-12-12 supports Intercompany Security and the addition of a Total Earnings column.
Report PR Union By Employee (RPRUNNE.rpt)
The revised report dated 2018-12-13 supports Intercompany Security and other refinements.
PR Union By Employee 2 (RPRUNNE2.rpt)
The revised report dated 2018-12-13 supports Intercompany Security and other refinements.
Report State Unemployment Electronic File (RSTTEUE.rpt)
The revised report dated 2018-12-26 supports Intercompany Security and other refinements.
Report PR Certified Payroll (RPRCRPR.rpt)
The revised report dated 2018-12-13 supports Intercompany Security and other refinements.
NOTE: If you are running a custom version of the Certified Payroll Report (with the extension USE, UHC, WHD, DeBella) please contact your support representative to see if you need an updated version.
Report PR Worksheet (RPRWRKSv90b001.rpt)
The revised report dated 2018-12-12 supports Intercompany Security and other refinements as well as a Direct Deposit section.
Report W2 Electronic File (RW2EFv72b005.rpt)
The revised report dated 2018-02-16 supports Qualified Small Employer Health Reimbursables in RW & RT records, RE contact information, and Oklahoma state reporting.
This new record allows a Supervisor to be specified when Labor is entered. This information is written to Job History so that a record of the Supervisor responsible for each labor entry line is maintained; this information may be used to support a custom Safety Incident Analytic.
The Supervisor Id may be specified in the detail lines of the following journals: Job Journal, Labor Journal, Time Labor and Work Order Labor. The Magnify button must be used to access the Supervisor field in these records.
The Supervisor is set when time is entered via a specific custom time entry screen; this information is imported to SAMPro so that it is included in Job History. TimeAnywhere may be customized to support the entry of the Employee's Supervisor; contact your Account Manager for additional information.
Supervisor Id: Supervisor Name:
These fields identify the Supervisor.
Contact Id:
The Contact record associated with this Supervisor. The phone, fax and email contact information shown below defaults from the Contact record.
Employee Id:
The Supervisor's Employee Id.
When Intercompany is enabled and a detail line contains a Job Id, any changes to the line's GL Entity are validated to ensure that the new GL Entity belongs to the same company as the Job.
A warning is now displayed when the user first accesses a journal entry which has been replaced by one with a higher 'tack' number. This warning is designed to prevent the user from wasting time by attempting to make changes to a journal entry record which cannot be saved because it has already been replaced. See Customer Note 1.1.2 for a registry to disable this warning globally or by individual viewer.
PR-to-GL Accruals:
In previous releases, accruals were skipped for Standard Cost type Earnings record when an Overhead Jobs was specified. In this release, accruals are correctly posted for Standard Cost Earnings for Jobs that are not Direct.
Previously, changing certain values (Hours, Pay Type, etc) didn't always cause the GL Accrual Info to be recalculated. The Accrual Info is now correctly set in the Employee, Labor Journal, Payroll Period and Work Order viewers, and in Compute Payroll.
This release corrects a spurious 'Please clear line '#' and re-enter Bonus Amount') message when using Insert/Copy to enter multiple lines with the Bonus field completed.
Changed Field - Cost Category:
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
New Field - Supervisor Id:
If completed, this field specifies the Supervisor responsible for the work in this entry.
Changed Field - Bonus:
Since a Bonus should never be entered on a line which also records hours, validation prevents the user from entering hours and a Bonus on the same line.
Labor Journal Hours Tab Detail View
Note: a new v.cus file may be needed to see these fields if a data-conversion was not triggered when upgrading to this version.
This enhancement eliminates the need to edit the Employee record before and after bonus checks are run in order to apply a Federal Income Tax (and if needed, State) flat rate to bonus pay. See Customer Note 12.2.5a for additional Usage instructions and details to running Bonus Check with this newer methodology.
New Fields:
Federal Tax Rate:
State Tax Rate:
These fields provide a flat rate override to the Federal / State Income Tax rate brackets in the Employee's Federal (FED-M or FED-S) and State Tax Tables. These fields are intended to be used for Bonus pay only. If these field are blank, the Federal / State Tax Table will be used as before. Tax is on Total Earnings when using this option. If this is not desired, the old methodology of changing the Employee record's Tax tab to specify a flat tax FED-bonus entry may be used instead.
Changed Field - Cost Category:
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
New Field - Max Hours:
This field supports PTO based on a Annual Maximum Balance (or Cap) for companies with a “Use it or Lose it” PTO policy. This field specifies the Cap or maximum total PTO hours 'in the bank' that this employee is allowed to accrue for the specified Pay Type Id/Sate range. When Compute Payroll is run, the accrued hours may be limited so that the Max Hours Cap is not exceeded.
Setup:
Typically, the PTO tab would need to be set up based on the employees date hired (anniversary date) and Years of Service (i.e. 1-4yrs, 5-9yrs, 10-14yrs, 15+).
New Fields:
Employee Viewer Rate Test Tab:
New Field: Select Rate Method to Test
By default, the Rate Method will be set to configuration currently in use (see table below). Switching to a different Method will automatically reset the Rate Tab to the values which would be obtained if that method were in effect.
|
Method |
Implemented Via |
|
7687 |
Registry Id: sys-ffv-global-settings Setting Key: LaborRatesAndAccrualMethod Setting Value: 7687 |
|
6654 |
Registry Id: sys-ffv-global-settings Setting Key: LaborJobCostRateMethod Setting Value: New |
|
4124 |
Registry Id: sys-ffv-global-settings Setting Key:LaborJobCostRateMethod Setting Value: BurdenOnWagesOnly |
|
989 |
Pay Type implemented as an option in the Employee Earnings and Earnings Group List tables |
Pay Amount:
This field displays the result of the Pay Rate times the Hours specified.
Amount Cost:
This field displays the result of the Unit Cost times the Hours specified.
New Fields:
Direct Pay:
Overtime:
This field is only used to provide the default Overtime Pay Type Id for direct jobs on a specific custom time entry application. The field is limited to Pay Types set to a Job Use type of All or Direct and a Category of Overtime.
Doubletime:
This field is only used to provide the default Doubletime Pay Type Id for direct jobs on a specific custom time entry application. The field is limited to Pay Types set to a Job Use type of All or Direct and a Category of Doubletime.
Indirect Pay:
Overtime:
This field is only used to provide the default Overtime Pay Type Id for indirect (overhead) jobs on a specific custom time entry application. The field is limited to Pay Types set to a Job Use type of All or Indirect and a Category of Overtime.
Doubletime:
This field is only used to provide the default Doubletime Pay Type Id for indirect (overhead) jobs on a specific custom time entry application. The field is limited to Pay Types set to a Job Use type of All or Indirect and a Category of Doubletime.
Labor Rates:
Overtime:
This field is only used to provide the default Overtime Labor Rate on a specific custom time entry application.
Doubletime:
This field is only used to provide the default Doubletime Labor Rate on a specific custom time entry application.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter.
New Fields - User 11-20:
Added User fields 11-20 for informational and reporting purposes.
Tax for Authorities not marked 'Always Withhold' are only assessed for labor on Jobs referencing that Tax Authority, correcting a problem in recent releases.
Registries are now required to automatically sort the Employee's Earnings and Deductions tabs, and the Earnings Group and Deduction Group child tabs. See Customer Note 16.6.3.
This release implements performance improvements in this function.
This release corrects the setting of the Earnings Id where a 'fixed' earning amount type is specified (such as a Bonus amounts entered on the Employee Recurring Wages tab).
New Display Only Field: Deduction Cycles
This display field the default Deduction Cycles specified in the selected Payroll Period.
Changed Field: Pay/Deduction Cycles To Include
This field now defaults from the Deduction Cycles field in the Payroll Period.
If a Pay Type is flagged as Union Exempt, the Employee's Earnings Group will NOT be written to PR History for this Pay Type when Compute Payroll is run. This corrects an issue in previous releases where Union Exempt pay types appeared on Union reports.
This release corrects a sporadic virtual stack overflow error when OT Premiums are allocated.
This release implements intercompany processing for employer taxes (etc) allocated during the compute.
Compute Payroll now supports the Hard Block logic (implemented by the BranchFilterWithHardBlock global settings registry option) in this version. The Hard Block is maintained regardless of how the Branch filter range is set.
Compute Payroll now supports PTO based on a Annual Maximum Balance (or Cap) for companies with a “Use it or Lose it” PTO policy. When Compute Payroll is run, the accrued hours may be limited so that the Max Hours cap (specified on the Max Hours field of the Employee's Paid Time Off tab) is not exceeded. If PTO hours are 'lost' to the Max Hours cap being exceeded, the hours and earning lost will be written to the PTO Hours Lost and PTO Earning Lost in Payroll History.
In previous releases, if annualized Gross Pay was not high enough to qualify for a taxable rate line on an applicable Tax Table, extra withholding would not be applied. This release corrects this issue and allows the specified extra withholding to be applied. Note that if the extra withholding would result in negative net pay, the compute will return an error. This must be corrected (e.g., by temporarily reducing the extra withholding) before a check can be produced.
This release refines the disposable pay garnishment calculations for US and Canadian Payroll users where the garnishment is a percentage of disposable pay. These are now based on the settings of the new Disposable Income fields in the Deductions record. See Customer Note 12.15.1 for details on these new fields.
The Security is now set using the same logic as manual Labor Journal entries.
Negative hours (with a leading minus) are supported in this version.
New Fields - Earnings User3-5
These additional fields may be used for payroll setup.
Earnings Record Changed Fields - GL Debit changed to GL Debit (Indirect):
GL Account
The GL Account expense account earnings / accruals are posted to for Overhead (Indirect) Jobs when the Payroll and Post Payroll to GL functions are run.
GL Entity:
The Entity charged for expense for Overhead (Indirect) Jobs.
New Fields - GL Debit (Direct)
GL Account
The GL Account expense account earnings / accruals are posted to for Direct Jobs when the Payroll and Post Payroll to GL functions are run.
GL Entity:
The Entity charged for expense for Direct Jobs.
The database conversion process completes these new fields by from the original GL Debit fields.
In the original implementation, all N/A-type earnings were subject to CIP Discounting. In this case, a flag has been added to the Earnings record to allow selection of specific N/A earnings to discount.
New Field - CIP Discount?
If this field is flagged and the Earnings Type is N/A, CIP Discounts will be applied to this Earning record.
Upgrade Note: If CIP Discounts were implemented in Version 9.0, this box MUST be flagged for the discounts to continue to be taken.
Registries are now required to automatically sort the Employee's Earnings and Deductions tabs, and the Earnings Group and Deduction Group child tabs. See Customer Note 16.6.3.
New Field - Classification Id:
This field has been added for reporting purposes at the level of distinction "by Union Classification."
New Fields: Deduction Group User3-5
These additional fields may be used for payroll setup.
Registries are now required to automatically sort the Employee's Earnings and Deductions tabs, and the Earnings Group and Deduction Group child tabs. See Customer Note 16.6.3.
The Hours Tab is now filtered based on the User's Executive PR and Branch Filter fields. Data for Executive Payroll Employees (Executive P/R flagged in the Employee record) will only be displayed if the Executive PR? box is checked in their User record.
Filtering based on the User's Branch Filter only comes into play when the hard-block filtering option is turned on via the following registry setting:
Id: sys-ffv-global-settings
Setting Key: BranchFilterWithHardBlock Setting Value:true
New Field: Executive Payroll
When this field is flagged, only users who have the Executive Payroll field flagged in their User record can:
Access the Payroll Period Record
Access Labor Journal Transaction for Executive Payroll Periods
Run Compute Payroll for Executive Payroll Periods
Print Payroll Checks for Executive Payroll Periods
Print PR Miscellaneous Deduction Checks for Executive Payroll Periods
Important Note: If the Executive Payroll box is checked the Default Payroll flag should NEVER be set.
New Field: Deduction Cycles
If completed, this field provides the default values for Start Compute Payroll's Pay/Deductions fields so that Deduction will not be accidentally skipped. Deduction Cycle information is maintained in the Deductions Group record (for union payroll) and the Employee Deduction tab (non-union). Up to five Deduction Cycles may be specified; they should NOT be separated by commas.
Examples:
If a Deduction Code of M is used for Monthly deductions, it would be entered in the Deduction Cycle of Payroll Periods used for Monthly pay.
If Deductions Codes are not used for Bonus pays, the Deduction Cycle could be set to XXXXX to prevent all Deductions from being taken. A Deduction will not be taken unless its cycle is specified; if a Deduction Cycle is blank in the Employee or Deduction Group, it will be taken if one of the Deduction Cycle fields in the Payroll Period is blank. Setting all fields to X or another character never used for Deduction Cycles will prevent this.
New Field: Accrue Bonus Pay
This box should be flagged if Bonus Pay entered for this Payroll Period should be accrued.
IMPORTANT:
If Bonus Pay should NEVER be Accrued, disable this field via registry.
This box may ONLY be checked if the sys-ffv-global-settings registry option LaborRatesAndAccrualMethod is set to 7687.
The sys-ffv-global-settings registry option AccrueBonusPay and Payroll Period User2 fields may be used to enable Bonus Pay Accrual instead of checking this box.
This function now correctly identifies all eligible Recurring Labor and Other entries. Previously, entries were skipped if the Employee Start/End Date fell entirely within the Payroll Period's Effective Dates.
New Filter - Executive PR:
If you are an Executive Payroll user, this field will default to Y; to run this function for all employees (Executive or not) clear this range. If your User record is not flagged as Executive Payroll, you will only be able to run this function for other non-Executive users even if you clear the filter.
Executive Payroll checks are not displayed unless the User's record has Executive PR flagged.
This new Viewer lists ONLY PR checks. It is sensitive to the user's/employee's Executive Payroll status. If the User's record has the Executive PR? box checked, PR Checks for all Employees will be listed. If the User does not have Executive PR privileges, only checks for those Employees who are NOT flagged as Executive Payroll will be listed.
View Checks: Although this existing function is still available, we recommend reviewing which User Groups need it. It still shows PR and Vendor checks, and is NOT sensitive to Executive Payroll.
User Group: Since this is a new viewer, access must be assigned to the appropriate User Group(s). Unless the User Group also need access to AP Checks, we recommend turning off access to View Checks.
Unless Checks are being entered as part of the startup process, edits to View Checks (Employee) should be disabled. We recommend the following settings for the new View Checks (Employee) viewer.
Id: sys-viewer-vchcklstpr
Setting Key: DisabledFieldsParent
Setting Value: gl-bnk: glaccnt.id,glentty.id,chck.nmbr,chck.amnt,chck.rfrnce-nme,chck.dte-chck,chck.type,chck.dscrptn
Setting Key: disabledFieldschild
Setting Value: chcklst.amnt-grss
New Field: Union Exempt
This box should ONLY be flagged if this Pay Type is used for certain types of union-exempt pay. Two things happen differently when time is charged to a Pay Type that is Union Exempt when Compute Payroll is run:
1. All fringe-type lines from the Earnings Group are ignored.
2. All lines from the Deduction Group are ignored.
If a Pay Type is flagged as Union Exempt, the Employee's Earnings Group will NOT be written to PR History for this Pay Type when Compute Payroll is run. This corrects an issue in previous releases where Union Exempt pay types appeared on Union reports.
Changed Field - Union Exempt:
In previous releases, Pay Types marked as Union Exempt still showed up on the Union Reports. In this release, Wages connected to union-exempt Pay Types (vacation, holiday, etc) now post a zero to the PR History Earnings Group column so they will not be picked up by the report. Two things happen differently when time is charged to a Pay Type that is Fringe Exempt ...
1. All fringe-type lines from the Earnings Group are ignored.
2. All lines from the Deduction Group are ignored.
Prior to this enhancement, customers had to create special "no-fringe" earnings groups for all their union related earnings groups. On these "no fringe" earnings group, they remove all Fringes and remove the Union Id to eliminate the wages & fringes from their union reports for PTO.
New Fields - Earnings Group User3-5:
These additional fields may be used for payroll setup.
New Fields: Deduction User3-5
These additional fields may be used for payroll setup
This release refines the disposable pay garnishment calculations for US and Canadian Payroll users where the garnishment is a percentage of disposable pay. These are now based on the settings of the new Disposable Income fields in the Deductions record. Note: if the Disposable Limits field is blank for a garnishment deduction on the Employee's Deduction tab, payroll taxes will NOT be deducted before the garnishment is assessed. We recommend setting this field to 99 unless a specific percentage is required.
New Fields - Disposable Income:
Statutory? (set only for mandatory non-garnishments)
This field would only be checked if this non-garnishment deduction is a mandatory (not voluntary) deduction. For example, Health Insurance or involuntary retirement or pension contributions would be Statutory in the US. In Canada, Canadian Pension Plan and Union Dues would be considered Statutory.
Non-Statutory? (set only for voluntary non-garnishments)
All voluntary, non-garnishment deductions. For example most 401K contributions (US), loan repayments, and uniform type deductions.
Allow Statutory? (set only for garnishments based on current regulations)
This field would be checked if this is a garnishment type deduction (e.g., child support) AND that Statutory Deduction should be applied to the disposable pay for this garnishment.
Allow Non-Statutory? (set only for garnishments based on current regulations)
This field would be checked if this is a garnishment type deduction (e.g., child support) AND that Non Statutory Deductions should be applied to the disposable pay for this garnishment.
Validation:
Deductions CAN be marked as either Statutory or Non-Statutory (but not both)
Deductions CAN be marked as Allow Statutory, Allow Non-Statutory or both
Deductions can NOT be marked as both (Statutory or Non-Statutory) & (Allow Statutory or Allow Non-Statutory). In other words, if you mark one of the top two you are not allowed to mark one or both of the bottom two, or vice versa.
This function has been enhanced to deny the import of blank GL Entity codes if Inter-Company is enabled. Also includes validation for debits = credits by Company if Inter-Company is enabled.
This function has been enhanced to deny the import of blank GL Entity codes if Inter-Company is enabled. Also includes validation for debits = credits by Company if Inter-Company is enabled.
This release extends the functionality of the Overtime calculator work even when checks are not actually printed and posted. To accomplish this, registry settings have been enabled to change the functionality of the Payroll Period's Post History button to generate Job and GL History as well as Payroll History (default functionality). Note that the Post History button must be clicked after Compute Overtime and Compute Payroll have been run.
In addition to the existing registries required for Start Compute Overtime (in sys-start-scmpteovrtme and sys-strart-scmptepryll), the following registries are available to enable/control this Compute Overtime enhancement.
Id: sys-start-scmpteovrtme
This required setting enables this Overtime functionality.
Setting Key: Method Setting Value: Hutchinson
The following settings are only applicable if the Method is set to Hutchinson as shown above.
These settings specify the hours that are to be considered 'regular' hours (in additional to the regular hours entered) when computing overtime. Note that 'regular' hours may be reclassified as overtime when the Compute Overtime function is run.
Setting Key: IncludeHolidayHours Setting Value:Y (default N)
Setting Key: IncludeVacationHours Setting Value:Y (default N)
Setting Key: IncludeSickHours Setting Value:Y (default N)
The existing registry options for sys-start-scmpteovrtme must also be set (see Help for Registry Start Compute Overtime).
Id: sys-compute-payroll
These settings specify the hours that are to be considered 'regular' hours when the Compute Payroll function is run. The user will be warned if the user's regular hours exceed 40 (or the value set via registry) as a reminder to run Compute Overtime first.
Setting Key: RegularHoursIncludesHoliday Setting Value: true (default false)
Setting Key: RegularHoursIncludesSick Setting Value: true (default false)
Setting Key: RegularHoursIncludesVacation Setting Value: true (default false)
The existing registry options for sys-start-scmptepyrll must also be set (see Help for Registry Start Compute Payroll).
Id: sys-viewer-vpyrllprd
This registry impacts the Payroll Period's Post History button. When enabled, clicking it will generate Job and GL History as well as Payroll history.
Setting Key: PostJCH Setting Value:true
The following registry is also recommend to ensure that the Accrue to GL flag is set in the Payroll Period viewer:
Setting Key: AccrueToGL Setting Value: true
Require that the Payroll Periods Per Year is set in the Employee record to prevent errors when Overhead and Payroll are computed.
Id: sys-viewer-vemplye
Setting Key: RequiredFieldsParent Setting Value: emplye.py-prds
1. Verify that all registry setting have been properly entered.
2. Enter labor for a Payroll Period which has the Accrued to GL box flagged.
2. When the entries for the Payroll Period have been completed, run Start Compute Overtime.
3. Next run Start Compute Payroll.
4. In the Payroll Period viewer, click the Post History button to generate Payroll, Job Cost and GL History without printing / posting checks.
5. Run the reports used to generate information for your payroll service.
This release refines payroll processing for Medicare Additional .9% Penalty so that is it is no longer necessary to predict when the user will exceed the $200,000 and enable / disable the Always W/H flag on the Employee Tax Tab's FICA MCAD entry.
The new functionality is enabled by changing the FICA MCAD Tax Table as describe in Step 1 below. If you change the Tax Table, you must also complete steps 2-4 below or the additional Medicare tax will NOT be deducted properly. If you do NOT change the FICA MCAD table, you may continue to as before.
FICA MCAD - the Base Tax tab must be changed to specify the following lines so that the first $200,000 of earnings will be exempt from the 9% penalty. This change is what triggers the new behavior.
|
Limit: |
Rate: |
Add'l Amount: |
|
200,000.00 |
0.000 |
|
|
999,9999.99 |
0.900 |
|
Verify that the FICA MC Authority is NOT set to Annual Compute.
In the Employee record's Taxes Tab, employees should have the FICA MC AND the FICA MCAD flagged as Always W/H all year. This configuration can be applied to ALL employees, however this is most conveniently applied at the beginning of the Payroll Year.
If the new functionality is to become effective for the current Payroll Year in process then a PR Journal Adjustment will need to be applied for each employee subject to the tax in order to synchronize Taxable and Exempt values pertaining to Tax Table FICA MCAD.
There are 3 possible starting points in such cases that are best identified by running Report PR Summary for the period 1/1/2017 – date of the last posted PR Check.
#1. Employee has no prior tax history related to FICA MCAD
Option #1: Delay adding or designating FICA MCAD as “Always W/H?” until commencement of Payroll 2018. Recommended if employee is not expected to exceed $200,000 for the current year.
Option #2: Create a PR Adjustment transaction to initialize FICA MCAD for YTD activity. Value for FICA MCAD “exempt earnings” should equal FICA MC “taxable” + “exempt” per the PR Summary Report. Recommended if employee is remotely likely to exceed $200,000 for the current year.
#2. Employee does have some prior tax history related to FICA MCAD and has not yet exceeded $200,000 in subject wages this year.
MUST!!!: Create a PR Adjustment transaction to initialize FICA MCAD for YTD activity. Value for FICA MCAD “exempt earnings” should equal FICA MC “taxable” + “exempt” per the PR Summary Report.
#3. Employee does have some prior tax history related to FICA MCAD and has already exceeded $200,000 in subject wages this year.
MUST!!!: Create a PR Adjustment transaction to initialize FICA MCAD for YTD activity. However an exact prescription for the adjustment that will be required is subject to additional and specific analysis.
This enhancement is applicable to a scenario where the WC state from the Job is used to determine the Cost Cat Workers Comp codes to use in the Labor Journal and WO Labor tab. In addition, unique Security-specific WC codes are implemented for each company containing the proper rates, and then added multiple WC codes with the same state to the cost category. Previously, when the system matches up the Job WC state to the Job Cost Category WC Code, it did not stay within the same security and just selected the first one on the list.
In this release, Security has been built into this matching process so that it uses the appropriate WC code for the company that the job/labor journal transaction resides in.
When Payroll checks are voided the system now eliminates the document attachment (if one exists) to the Employee record. The attachment to the Check record is retained.
New Field: Check Description:
This field defaults from the Check record. It may be edited by the user to note the reason for the void. If the Check Description field was blank when the Check is voided, the system will continue to default in the Description using the following format: Voided 07/09/2018 01:36:39 PM UserId.
This release no longer accrues the Union Fringes for Pay Types checked Union Exempt.
Corrects a recent problem with Pay Types and TimeAnywhere messages caused by pulling defaults in the employee record.
Changed Field - Transaction Id: The Transaction Id now displays the latest Labor Journal entry associated with this record. The View button also opens the most recent Labor Journal Transaction.
New Field - Submitted By:
This display-only field identifies who submitted the hours from TimeAnywhere (either the Employee himself or the Crew Manager/Foreman).
New Field - Submitted By:
This display-only field identifies who submitted the expenses from TimeAnywhere (either the Employee himself or the Crew Manager/Foreman).
New Field - Submitted By:
This display only field identifies who submitted the expenses from TimeAnywhere (either the Employee himself or the Crew Manager/Foreman.
Changed Field - Setting Value:
This field has been expanded from 100 to 1200 characters.
The check for zero hours has been removed from the TimeAnywhere post to support entries by the employee as a place marker for StandBy per diem.
When Labor Journal entries are generated by TimeAnywhere, the Labor Journal Entered-By will be set equal to the TimeAnywhere Submitted-By.
This release corrects 'Import Message' and 'Export Message' button issues that resulted in the dropping and corrupting of some TimeAnywhere messages.
In recent releases, the Quote Manager's and Quote Master's Approval Wizards were revised to set the Work Order's Sub NTE set from the sum of the Extended Costs on the approved Sub Scope lines, and the Work Order's Client NTE from the sum of the Extended Price on the approved Scope lines including Revenue Adjustments not included. This was done to support SubAnywhere.
Since this functionality is not in alignment with the business practices of certain customers, a registry is available to override the new default behavior. When the following registry is set to false and the approval wizard is run, the Client and Sub NTE of new work orders will be 0, and the Client and Sub NTE's existing work orders will not be changed. For Both Quote Master and Quote Manager:
Id: sys-viewer-vwrkordr
Setting Key: UpdateNTEAmounts Setting Value: false (default is true)
Note that this registry is set the Work Order registry!
This registry allows the user to manually set the Quote Scope's Status to Printed in the Quote Scope Viewer (Quote Manager users) and in Quote Master's Scope tab. The registry was implemented to allow users running Crystal Reports to set their Quotes to Printed since Crystal does not support the print confirmation available in the SAMPro Quote report. Note that fully approved Scopes may not be set to Printed.
Id: sys-viewer-vqtescpe
Setting Key: AllowPrintedScopeStatusToBeSetManually Setting Value: (default false)
Id: sys-viewer-vqte
Setting Key: AllowPrintedScopeStatusToBeSetManually Setting Value: true (default false)
The functionality to launch Report Quote Recap WO when a quote is posted has now been added to the Quote Manager Approval Wizard. Previously, this functionality was limited to the older Quotemaster Approval Wizard. It is enabled via the following registry:
Registry Id: sys-viewer-vwrkordr
Setting Key: ProduceQuoteRecapReport Setting Value: true
With the following registries enabled, when the Approval Wizard is run, the contents of the source Work Order's User fields will be written to the new Work Order (when that option is selected).
For Quote Master set:
Id: sys-viewer-vqte
Setting Key: CopyWOUserFields Setting Value: true (default is false)
For Quote Manager set:
Id: sys-viewer-vqtemngr
Setting Key: CopyWOUserFields Setting Value: true (default is false)
By default, the Quote Approval Wizard updates the WO Equipment Work Performed from the Scope of Services. This pair of registries entries for Quote Master or Quote Manager results in setting the WO Equipment Work Requested (but NOT the WO Equipment Work Performed) then the Approval Wizard is run.
Id: sys-viewer-vqte (Quote)
Id: sys-viewer-vqtemngr (Quote Manager)
Setting Key: SetONLYtheWOWRFromScope Setting Value: true (default false)
Setting Key: SetWOWRFromScope Setting Value: false
Note that SetWOWRFromScope MUST be set to false to enable this functionality.
The revised Report Quoted Form (RQTEFRMv90b035.rpt) dated 2018-10-11 reprints the Scope heading (Option #1 (Continued)) when the Scope spans multiple pages.
The revised report (RQTEFRMv90b035.rpt) dated 2017-11-03 correctly supports negative tax values for negative scopes and quote totals.
The revised report (RQTEFRMv90b035.rpt dated 2017-06-21) evaluates the ‘ n/a’ Tax Type on Scope detail lines based on Cost Category, Quote’s Sales Tax Group, and Quote’s Tax Status. This enhancement supports the global registry DeferTaxStatusDecision=true so that the Tax Type on Quote Scope detail lines defaults to ' n/a'.
This release and the revised Report Quote Form (RQTEFRMv90b035.rpt) dated 2016-09-02 correct the following issues with Estimated Sales Tax:
Fixed fee quotes no longer shows estimated tax if a Cost Category that is designated as nontaxable was selected in the Quote Scope.
Estimate Tax is now correctly printed for non-fixed fee quotes when the Print Quote Total? is cleared.
Estimated Tax is now calculated like tax on a Service Invoice so that the estimated tax on the Quote and the sales tax on the service invoice will agree.
The revised Report Quote Form (RQTEFRMv90b035.rpt) dated 2018-05-14 supports the new bitmap override by Job functionality; the Quote must specify a header Job for this functionality. Note that this functionality only applies to the bitmap, not the sectionbackerbitmap.
Registry Id: sys-report-rqtefrm
Setting Key: BitmapOverrideBasedOn Setting Value: job
This registry entry defines that this override is based on a user field in the quote's Job record.
Setting Key: BitmapOverrideField Setting Value: job user database field
This registry entry specifies exactly Job User field will provide the override for the base 'Setting Key: bitmap'. The database field name must be specified.
For example, the following specifies the Job's User 3 field:
Setting Key: BitmapOverrideField Setting Value: jb_usr3
Setting Key: Job~string Setting Value: path\bitmap.bmp
This entry provide the override bitmap file that will be used if the Job record's User field defined above contains the string specified. Notice that a tilde (~) separates Job from the string. As many of these entries may be made as needed to support the various bitmaps.
Example:
Suppose that we have a bitmap file named 010101_quote.bmp that should be used on quotes associated with Job's having the following text string 010101 in Job User 3 fields.
Setting Key: Job~010101 Setting Value: path\010101_quote.bmp
Tip: Include the part of the bitmap name as the text string for clarity.
Tip: Including the appropriate values in your job templates will ensure that new jobs are created properly. In addition, using the Custom Fields functionality to specify the allowed values will prevent inappropriate values from being entered.
Quote Scopes now support extended revenues of up to $99,999,99. Previously, revenues of ten millions and above resulted in a tab mismatch error in both the Quote Master and Quote Scope viewers.
Import Diagnostics Wizard: Corrects a sporadic Runtime error - system primitive failed.
|
Quote |
Revised Cost Category Rules |
Old Cost Category Rules |
|
Inventory Tab |
ok: mat, eqp |
ok: mat |
|
Material Tab |
ok: mat, eqp |
ok: mat |
|
Other Tab |
ok: mat, oth, sub, eqp |
ok: mat, oth, sub |
|
Subcontractor Tab |
ok: sub, oth, eqp |
ok: sub, oth, eqp |
The user is now prevented from entering an Inactive Vendor on the Materials, Inventory or Subcontractor tabs.
The Quote Status has been added to the QuotesByIdByWorkOrder list after Estimator Id and before Description.
RevAdj:
o Add o Deduct
When SAMPro calculates the AdjBase (Adjustment Base), if it's value is negative, the Add - Deduct button is automatically flipped from its default setting. This supports the correct setting of Revenue Adjustments for negative scopes.
In previous releases, if the Hourly Price was manually adjusted in the Quote Scope Labor tab, the revised value was not carried through to the existing Work Order when the Approval Wizard was run (the value from the Labor Rate was defaulted instead). In this release, the Quote Scope's Hourly Price is correctly set as the Work Order Labor's Revenue when the quote is approved.
When the Create Job Budget option of the Quote Approval wizard is selected, Budgeted Revenues are now written for T&M Quotes; previously only Budgeted Costs were written. The Quote's Revenue Adjustments also generate a Budget Entry (+ or -) to the Job / Cost Code specified.
The Wizard now writes to the Work Order Log Tab when a new WO is created or updated.
Revenue Adjustments of approved option(s) are now included in the NTE Client field when a new WO is created unless the NTE update is suppressed via registry.
This release corrects a problem in the Approval Wizard where the Scope of Services text written to the WO Work Requested was converted to all lowercase. The Scope of Services is written to the WO Work Requested if the SetWOWRFromScope option is enabled in sys-viewer-vqtemngr.
New Button: Reset Tax Type
Click this button to reset the Tax Type of the detail lines for all Open Scopes based on the Quote Manager's Tax Status and Tax Group, as well as the Cost Category of the Scope detail lines. This button would be used if Scope lines were entered before the Sales Tax Group was set, or if the Sales Tax Group or Tax Status was changed after adding lines. The Quote report calculates Estimated Tax for non-Fixed Fee Scopes on a line by line basis so it is important that the Tax Type is set correctly.
The Quote Status has been added to the QuotesByIdByWorkOrder list after Estimator Id and before Description.
In this release, all Notes attached to the Quote Manager and each of its associated Scopes will be available from the Quote Manager AND Quote Scope viewers. For example, for a quote with 2 scopes and notes entered on the Quote, Scope 1 and Scope 2, will have all 3 notes attached.
Import Diagnostics Wizard: Corrects a sporadic Runtime error - system primitive failed.
This release corrects sporadic Tab Mismatch errors on multiple labor, inventory, material and other line extended price summations.
This release corrects a sporadic Runtime Error when clicking the Flat Rate Import button.
New Scopes automatically default the Job's Revenue Adjustment Id. If a Work Order with a single piece of Equipment is specified in the Quote / Quote Manager, the Equipment Id also defaults on new Scopes.
The rules regarding allowed Cost Category Selection Types have changed as follows on the following tabs:
|
Quote Scope |
Revised Cost Category Rules |
Old Cost Category Rules |
|
Inventory Tab |
ok: mat, eqp |
ok: mat |
|
Material Tab |
ok: mat, eqp |
ok: mat |
|
Other Tab |
ok: mat, oth, sub, eqp |
ok: mat, oth, sub |
|
Subcontractor Tab |
ok: sub, oth, eqp |
ok: sub, oth, eqp |
The user will now be prevented from entering an Inactive Vendor on the Scope's Materials, Inventory or Subcontractor tabs.
Quote Scopes now support extended revenues of up to $99,999,99. Previously, revenues of ten millions and above resulted in a tab mismatch error in both the Quote Master and Quote Scope viewers.
Changed Fields: Rate Schedule, Gross Margin % - Markup %
If the Rate Schedule, Margin or Markup is changed, the system will recompute the prices on previously entered lines as needed. Only Scopes with a status of Open or Accepted (if enabled via registry) are eligible for the change. Clearing the Rate Schedule, Margin AND Markup fields (so that none are set) does NOT trigger the recompute.
New Button: 
Clicking the Recompute Scope button will recompute the prices based on the Rate Schedule, Gross Margin % or Markup % This button is useful to use if the Rate Schedule has recently been changed. The button may only be used for Scopes with a status of Open or Accepted (if enabled via registry).
New Button: 
This enhancement extends the "Copy From" functionality to allow a Scope to be copied from any Quote, not just the one that the current Scope belongs to.
When the "Copy From Any Scope" icon is pressed, the system validates that the current Scope has been Added/Saved. Next, the wizard allows the user to select the Quote Id to copy from; the current Quote Id will be defaulted but may be changed by the user so that any Quote may be copied from. Next, the Scope selection screen will appear, so that the user can choose which option to import. Note that all the child tabs from the selected Scope are imported EXACTLY as they existed in the original Quote/Scope.
Main Tab 
Clicking this new button accesses the Scope's Quote Manager record.
Quote Scope Viewer Scheduling Tab:
Opened By - Date Opened - Time Opened: Previously, these fields were updated with the current User, Date and Time if a Scope was reopened. Now they are only set when the Scope is created.
Changed Fields -
RevAdj:
o Add o Deduct
When SAMPro calculates the AdjBase (Adjustment Base), if it's value is negative, the Add - Deduct button is automatically flipped from its default setting. This supports the correct setting of Revenue Adjustments for negative scopes.
In this release, all Notes attached to the Quote Manager and each of its associated Scopes will be available from the Quote Manager AND Quote Scope viewers. For example, for a quote with 2 scopes and notes entered on the Quote, Scope 1 and Scope 2, will have all 3 notes attached.
Changed Fields - Quantity - PO Id: Vendor Id:
The PO Id will default from the source Work Order's Purchase Order Id when the user enters the Quantity and then tabs out of the field. The Vendor Id will be defaulted from the PO.
Previously, this functionality only existed in the old Quote viewer's Subcontractors tab.
Work To Do Pane New Field - Customer PO#:
When posting to a New WO, this field will be used to set the PO# field on the Work Order with the PO# provided by the customer. The User is required to enter the Customer PO# number if the PO Required field is flagged in the Site's Service tab.
Previously, the Remote Technician warning was treated as an error and the approval stopped. In this release, the warning is suppressed so the Approval wizard can run.
The Quote's Service Category defaults the new WO's Service Category. If the Quote's Service Category is empty, the new WO's will continue to default from the Work Code.
When the Approval Wizard is run, the Tax Group and Tax Status in the selected Job are now used to when generating Work Order detail lines.
Since Payroll Period validation is not applicable to WO Labor flagged as Quoted, the Approval Wizard ignores this validation when generating WO Labor lines.
When a Work Order is created/updated from the Quote/Quote Manager, the Work Order's Sub NTE will be set from the sum of the Extended Costs on the approved Sub Scope lines. The Work Order's Client NTE will be set from the sum of the Extended Prices on the approved Scope lines, Revenue Adjustments not included. In previous releases, the Approval Wizard did not update the Work Order's Client NTE or Sub NTE. A registry is available to disable this behavior; see Customer Note 14.1.1.
The Work Order's Date Earliest Start is now set to the current date when a new Work Order is generated from the Quote or Quote Manager's Approval Wizard. The Work Order's Date Earliest Start is also set to the current date if the Approval Wizard posts to an existing Work Order whose Date Earliest Start has not yet been set.
New Field: Opportunity Type
This text field may be used to categorize this opportunity (e.g., Solar, Plumbing, Heating, etc.).
New Field: Contact Type Id:
This optional field defaults from the Contact record but may be changed by the user if needed.
This new tab enables multiple Contacts to be associated with an Opportunity. This tab is currently use for informational and custom report purposes only.
Contact Id:
Enter a valid Contact Id (or double-click to select from a list). You may create as may lines as needed to accommodate all contacts. The display-only Name, Firm, Email and Phone number fields will default from the Contact record.
Contact Type Id:
This optional field defaults from the Contact record but may be changed by the user if needed.
Active quotes are those which have not been fully approved (via the approval wizard) or declined.
Registry Id: sys-newcall
Setting Key: ShowActiveQuotesForClientSite Setting Value: true (default false)
If this registry is enabled, the following message will be displayed if any quotes with the Status Category of Active exist:
There are active quotes for the selected site. Would you like to view them?
If the user clicks Yes, a list of active quotes will be displayed; the user may access them if their security allows. If the user clicks No, the message box will be closed.
The following registry has been revised to omit writing the Market Source to the new Site and Client records. Previously, the Market Source was only omitted from the new Site.
This registry entry impacts the New Call Create (flashlight) and New Call New COD screen where a new Client Site (and Client if applicable) are created along with the new Work Order.
Id: sys-newcall
Setting Key: MarketSourceNoSite Setting Value: true (default false)
If false or registry key is absent, continue to write the NewCall Market Source to the new Site and or Client and WO (default behavior).
Previously, the system would only warn the user when creating a work order for a piece of equipment referencing a closed job, yet still allow work order creation. A registry has been added to disallow users to create a work order referencing a closed job via the equipment default service job.
Registry Id: sys-newcall
Setting Key: ClosedJob Setting Value: error (default warning)
When set to error, user will be unable to create work order. When set to warning, user is warned that creating a work order against a close job will lead to undesired results.
The following registry option causes the system to ignore the default technician specified in the Site or Equipment. When it is enabled, the Technician Id will be set to blank (unassigned) when the Equipment is selected (regardless of whether it whether it was manually selected or defaulted). After the equipment has been selected, the user may then enter the Technician Id or use TechFinder to do so.
Id: sys-newcall
Setting Key: IgnoreDefaultTechFromClientSite Setting Value: true (default is false)
This release supports a registry to disable writing to the New Call status pane when the mouse is moved. This has demonstrated some small improvement in New Call performance.
Id: sys-newcall
Setting Key: MouseMoveDisabledOnForms
Setting Value: form,form1,sidebar,topbar,sitesearch,wrkordr,clntste,clntsteeqpmnt
The above setting value disables writing to the Status Pane when the mouse is over any of the New Call Panes.
This registry should be set to enable Preventative Maintenance Work Orders (generated by Create PM Work Orders) to be assigned a special status when they are created even when NewWorkOrderStatus is set (which trumps the older StatusForPreventiveMaint registry option).
Registry Id: sys-web-access-none and sys-web-access-technician
Setting Key: OverrideNewWorkOrderStatus Setting Value: astatus
Registry Id: sys-start-scrtepmwo
Setting Key: ReqPMPartsStatus Setting Value: status
By default, PM Work Orders which were generated with any ReqResource lines were ALWAYS set to Waiting Parts. This registry provides an override so that users can specify a different status for PM's with ReqResource parts.
Example: To set PM's with ReqResource lines to Waiting Service:
Id: sys-start-scrtepmwo
Setting Key: ReqPMPartsStatus Setting Value: Waiting Service
Registry Id: sys-start-scrtepmwo
Setting Key: GetServiceAccountManagerFromClientSite Setting Value: true (default is false)
If the above registry is enabled, Start Create PM Workorder will default the Service Account Manager from the Client Site only when Preventive Maintenance Work Orders are generated. If this registry is not enabled or the value is false then it will set the Service Account Manager first from the Client Site Equipment then from the Client Site, maintaining the previous default behavior.
This registry may be used to modify the calculation of the Sub NET / PO amount for Master Contract linked equipment. By default, when a PM Work Order is generated for a Subcontractor technician, the sub's NTE amount will be set to Cost amount on either the Inspections tab or the Provider Rates tab on the Master Contract record.
In this release, the following registry modifies this; if the Master Contract does NOT have a Cost amount on either the Inspections tab or the Provider Rates tab, the Equipment record's Sub NTE will be used to set the Sub NTE on the Purchase Order and PM Work Order when Create PM Work Orders is run. This functionality requires that the PM is generated for a Subcontractor Tech.
Id: sys-start-scrtepmwo
Setting Key: LastResortSubNTE Setting Value: equipment
By default, entries on the Client Site WO Other tab are not added to Preventative Maintenance Work Orders created by Start Create PM Work Orders. The following registry may be implemented to add Client Site WO Other lines to Workorder Other Records when processing PM Workorders.
Registry Id: sys-start-scrtepmwo
Setting Key: ClientSiteWOOtherAdd Setting Value: true (default is false)
Registry Id: sys-viewer-vwrkordr
Setting Key: AllowNegativeInventoryQuantity
Setting Values: true (default is false)
Implementing this registry setting prevents the user from manually entering negative Inventory lines on the Work Order Inventory tab. Typically, this would be enabled to require IM ADJUSTMENT transactions to be made to "return" items to a stocking location. Ideally, the Return Wizard process to would be used to do so. This type of transaction influences the Average Cost Calculation whereas direct WO Inventory activity does not.
WARNING: As of this release, this new option is applied to both the Actual and the Billable quantities. With the new option enabled one cannot give a billing credit (negative Billable Qty) to adjust and/or correct an invoice.
By default, when the user double-clicks New Call's Default Service Job field, the system filters the list to jobs belonging to the selected Site. The following registry (in conjunction with Service Category settings) provides a mechanism to over-ride the New Call's determination for how to filter the "Default Service Job" selection pick-list. For example, Equipment with a Service Category of UTILITY could be set to filter to a special utility job or jobs not connected to the specific Site.
Warranty Jobs:
This registry could also be used to expedite the selection of Warranty jobs in New Call. For example, different Warranty Jobs for the Service Category HVAC could be set up Carrier, Trane, and so on. In this case, the Job Type in these Warranty Jobs would be set to HVAC. The Job Type in the regular Jobs would NOT be set to HVAC.
Registry To Specify the Service Category Field to Filter On
Id: sys-newcall
Setting Key: JobFilterByServiceCategory Setting Value: User5 (User1 - 4 also supported)
The Setting Value specifies which of the Service Category User fields will contain the SQL statement to control the filtering. In the above example, User5 is specified, but User1, User2, User3 and User4 are also supported.
Service Category
Service Category User1-5
This field may be used for overriding the Job filtering in New Call. The field value must be set as necessary for each individual Service Category that has special job filtering requirements. For example, to specify the Job filtering for the selected Service Category to use the specific Job Type of UTL, the field would be completed as follows (note that the Job Type Id is single-quoted): jbtype_id='UTL'
Tip: Relabel the Service Category User Field
The Custom Fields functionality may be used to relabel the User field used for the Job filtering override (e.g., Job Type Filter).
Job:
For those Jobs you wish to enable for Job Filter overrides in New Call, set the field specified in the Service Category User field. In our example, the Job's Job Type would be set to UTL.
New Call:
In this scenario, suppose a user selects Equipment belonging to Service Category Utility in New Call. Initially, the Default Service Job will default from the Equipment record. However, double-clicking on the Default Service Job displays a list of Jobs whose Job Type is set to UTL instead of Job for the selected Site. Note that the user may manually enter any valid Job Id. This functionality ONLY impacts the filtering of the Job list.
The default behavior for version 9.1 is that, if the PM Task List Id not specified on the PM Master Contract schedule line, the system now looks to see if there is one specified in the Client Site Equipment. This task will be defaulted to the Client Site Equipment PM line and PM Work Order. This enhancement allows for different task lists to be assigned by equipment scheduled.
In previous versions of 9.1, there was no way of changing the default behavior. In this release, the following registry may be implemented to disable the default behavior; if it is set, the Equipment's Service Task will NOT be used if the Master Contract Schedule's Service Task is blank.
Registry Id: sys-ffv-global-settings
Setting Key: disableUseEquipmentHeaderServiceTasks Setting Value: true (Default false)
If the user changes the description of a Gen Item after it is imported into the WO from a source PO a disconnect is created when running Create EOM Unvouchered AP GL Entries (seomunvchrdap). Those changed lines will not be included in the GL Journal written by the function.
A registry has been added to previous these lines from being changed on the Work Order's Other tab. If the following registry is implemented, the system will display an error message if the user attempts to change the description on an Other tab line associated with a PO and imported from JCH. Note that the Setting Value is false to implement this behavior.
Registry Id: sys-viewer-vwrkordr
Setting Key: AllowEditOfPOGENDescriptions
Setting Value: false (Default is true to preserve current behavior)
A new registry is available to specify the status eligible for Start Work Order Batch Close. By default, only Work Orders with Technician lines set to Billed or Cancelled are eligible for this function. The following registry overrides this.
Id: sys-start-swrkordrbtchclse
Setting Key: ClosedTypesList Setting Value: list of tech statues
Example:
Setting Key: ClosedTypesList Setting Value: cancelled,billed,no bill,tech declined
Note that the default statuses of cancelled or billed must be included in the registry for them to be eligible to be closed.
This release supports additional Certifications to be specified for use with TechFinder. When the following registry entry is enabled, a comma-delimited list of Certification Ids in the Work Code User1 field will be added to the Certification Id range field when TechFinder is launched from New Call or the SAMPro Dispatch board. This list will be appended to the list from the selected Site and Equipment records.
Note that when TechFinder is launched from the Dispatch Board, the Work Code on the Work Order's Main tab will be evaluated for Certifications.
Id: sys-ffv-global-settings
Setting Key: CertificationFromWorkcode Setting Value: true (default is false)
Tip: If this registry is enabled, use the Custom Fields functionality to relabel the User 1 field as 'Certifications'.
This registry is currently supported by SAMPro's New Call, Project Work Order Generator and Work Orders generated by TechAnywhere.
Id: sys-behavior-ClientSiteWOOther
Setting Key: OtherRateId Setting Value: ExceptFor:servicecategory1,servicecatory2,...
or
Setting Key: OtherRateId Setting Value: OnlyFor:servicecategory1,servicecatory2,...
In this registry, the Setting Key is the Other Rate Id. The Setting Value specifies the option (OnlyFor: or ExceptFor:) followed by a list of the Service Categories the Other Rate pertains to. If an Other Rate if not defined in this registry, it will continue to be added to Work Orders to maintain default behavior.
The OnlyFor: option defines which Work Orders (by Service Category) will have will have a Work Order Other line generated from the Site's WO Other tab.
The ExceptFor: option is used to specify Service Categories should be excluded from this line.
Examples:
Setting Key: Trip1 Setting Value: OnlyFor:HVAC,REFRIG,PLUMBING
Setting Key: Trip2 Setting Value: OnlyFor:UTILITY,NETWORK
Setting Key Truck Setting Value:ExceptFor: NETWORK
In this example, a Site could include the Trip1, Trip2 and Truck Other Rates. However, the Service Category of the Work Order would determine which would be added to the Work Order Other tab.
Results:
Service Category: HVAC - Other Rates Lines: Trip1 and Truck
Service Category: NETWORK - Other Rate Line: Trip2
In certain installations, the Classic Dispatch Boards may display with the last technician column twice. If this occurs, the following registry setting may be enabled to force a redraw of the last quarter of the classic board to prevent the problem. This may result in additional flashing during the redraw, so this registry should only be implemented if the problem exists and it bothers the users.
Registry Id: sys-viewer-vdsptchbrd
Setting Key: useCase8798code Setting Value: true (default is false)
The revised report dated 2016-02-25 adds an option to Skip PO Summary. In addition, Multi-page textbox processing was added for the Work Requested field.
This release plus the revised Report PM WorkOrder List (RPMWRKORDRLST.rpt) dated 2017-09-12 supports the OrderBy registry (if present) for the function Start Create PM Work Orders (sys-start-scrtepmwo). This means that the function's checklist and the report will appear in the same order.
Important Note to Sybase Users:
If the Client Site Equipment's Inspection Date is referenced in the OrderBy statement, its database name must be entered as clntsteeqpmntpm.clntsteeqpmntpm_dte_schdld_inspctn instead of clntsteeqpmntpm_dte_schdld_inspctn to prevent a Sybase error -144 column not found error when the report is run.
Id: sys-start-scrtepmwo
Setting Key: OrderBy
Setting Value: clntste_id,clntsteeqpmntpm.clntsteeqpmntpm_dte_schdld_inspctn,tchncn_id,clntsteeqpmnt_id
The revised report (RSRVCEHSTRYDTL.rpt) dated 2017-10-04 includes a new range filter, Equipment Type Id.
When Intercompany is enabled and a detail line contains a Job Id, any changes to the line's GL Entity are validated to ensure that the new GL Entity belongs to the same company as the Job.
This release provides a performance enhancement when opening Work Orders when the sys-viewer-vwrkordr registry's option GrossMarginFromJobHistory is enabled.
Corrects a "key is missing" error which occurred when a work order was saved immediately after being opened.
Corrects a sporadic issue if a user attempted to edit a previously invoiced line resulting in negative 'ghost' lines on subsequent invoices for that Work Order.
Imported Material and Other lines now retain their Job information even when DefaultJobByEquipmentId is enabled.
The Gross Margin is no longer calculated if the Work Order or Job Id is empty to improve time loading the empty Work Order viewer.
Quoted Lines: Previously, entering a labor budget on the Labor Tab by checking lines as 'quoted', resulted in the quoted line posting to GL when the WO was marked as Invoice Ready. In this release, the system never posts to GL for quote-type WO Labor lines.
Labor Tab Header: The Actual Hours: Billable Hours: fields display a running total of hours entered on the Work Order. Negative labor hours are now subtracted from these running totals instead of being added.
PR-to-GL Accruals: In previous releases, accruals were skipped for Standard Cost type Earnings record when an Overhead Jobs was specified. In this release, accruals are correctly posted for Standard Cost Earnings for Jobs that are not Direct.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
New Field (Magnify view) - Supervisor Id:
If completed, this field specifies the Supervisor responsible for the work in this entry.
Job Type has been added as a new filter range option. This lets users filter Work Orders by the Type of Job in the Work Order header.
When searching for WO Techs with the WorkOrdersByBranchIDByWorkOrderID' list selected, only the Primary Tech is actually searched for. The Primary Tech has been added to this list to help avoid confusion.
The Date Scheduled Range has been relabeled as Original Date Scheduled to clarify its function.
This field has been expanded from 3000 to 6000 characters.
In previous releases, it was possible for the total # of character across several WO Equip – Work Performed field to exceed the character limit of Invoice Description of Work Performed. In this release, when the Build Description button is clicked, if the system detects that the resultant string will exceed 6000 characters the user will be alerted and offering the choice to “paste anyway?”
Yes will move the text (truncation will result as always has). Selecting No will cancel the operation.
When No is selected the user will have the opportunity to populate Invoice Description of Work Performed with some standard language such as “Details by Equipment to follow…”.
To include all of the WO Equipment Work Performed on the invoice, the Equipment Work Performed Addendum - Show on Invoice? box should be checked.
New Field: Equipment Work Performed Addendum - Show on Invoice?
When this box is checked, the revised Service Invoice (SERVICEINVOICEv90_b002.rpt revised 2015-11-02) will continue to print the Invoice Description of Work Performed. In addition, a page break AFTER the Invoice Total/AR Summary will occur and additional (addendum) page(s) will print as necessary to present the COMPLETE – Work Performed text associated to EACH WO Equipment record on the work order.
Note that if the Show Equipment Detail box is flagged when printing the invoice, the Equipment Work Performed will be listed in the body of the WO as well. Typically, this option would NOT be used in conjunction with the new "Equipment Work Performed Addendum - Show on Invoice" functionality.
If an Inventory line flagged as 'Extra' is added to a Preventative Maintenance Work Order, the AR Invoice Id will not be written to Job History based on the PM Invoice Id being completed in the Work Order. This allows these lines to be billed separately on the Preventive Maintenance Work Order apart from the existing PM Invoice.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
The rules regarding allowed Cost Category Selection Types have changed as follows on this tab:
|
Work Order |
Revised Cost Category Rules |
Old Cost Category Rules |
|
Inventory Tab |
ok: mat, eqp |
ok: mat |
Customizations available with this release correct a display issue when the vertical lines that separate the Revenue Rate, Unit Cost, and Cost Category disappeared, except for the line containing the cursor. A new v.cus file will be required to see this correction; standard customizations are included with this release; contact your support rep a company-specific customization is needed.
Lines for Fixed Fee Billing Items (for Use Tax Jobs) flagged as Extra now have the Use tax factored in when the Revenue is calculated. The Tax Cost is also set when a Standard Cost Other Rate is selected.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
The rules regarding allowed Cost Category Selection Types have changed as follows on this tab:
|
Work Order |
Revised Cost Category Rules |
Old Cost Category Rules |
|
Other Tab |
ok: mat, eqp, oth, sub |
ok: mat, oth, sub |
New Fields: User1-5
These user-defined fields have been added to the Magnify view of the Work Order Other tab.
Changed Field: Unit Price
This release corrects the calculation of the Unit Price in the specific scenario where the Bill Quantity was edited to a different value than the Actual Quantity for lines where there is a "tax cost" to be included in the basis of calculating the Unit Price. This issue primarily impacts situations such as calculating the Canadian PST as an additional cost on a line to be included in pricing mark-up. When adjusting the Unit Cost to include Tax Cost on the Work Order Other tab, the system now uses the Actual Qty, not the Billable Qty.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
Location Id and Vendor Id Validation:
In previous releases, validation did not allow a Location and Vendor to be entered manually on the same line. However, if the user ran the RR Wizard but cleared the OK box at the end (so that the PO was not created), both the Location (defaulted from the Wizard) and Vendor were entered. In this release, the validation has been refined to allow the User to clear the Vendor or Location if both have been completed and the line has not been requisitioned.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
The rules regarding allowed Cost Category Selection Types have changed as follows on this tab:
|
Work Order |
Revised Cost Category Rules |
Old Cost Category Rules |
|
Required Resources Tab |
ok: mat, oth, sub, eqp Inventory Item must use a Cost Type of material or equipment |
ok: mat, oth, sub Inventory Item required a Cost Type of material. |
The Email address from the Site's upper Contacts tab is now displayed below the Site's Phone and Fax numbers.
Changed Field - Sub NTE:
The Field Label 'Sub NTE' has been changed to 'Sub/PO NTE' to better define it's meaning.
Changed Field - Work Requested:
This field has been expanded from 3000 to 6000 characters.
New Field: Email Address
When a Site is selected in New Call, the Client Site's Email field is now defaulted to the Work Order Email field. The user may manually update this field if desired before adding the Work Order. Escalations for the new Notification Source 'Work Order' will be sent to this address.
The Email address for the Scheduled Events is set when the WO is generated. Changing it in the Work Order after creation will not propagate the change to the Events themselves. See Customer Note 16.10.2 for additional information concerning this field.
The following fields have been repositioned on the Main tab to minimize scrolling on the wider screen monitors employed by most SAMPro user:
Moved from near the bottom of the Main tab to just below the Original WO field in the third column of fields:
Account Manager Id, Sales Manager Id, Dispatcher Id:
Display Fields moved from below the Original WO to the fourth column below the Return to Inventory button:
Esc. Profile Id, Gross Margin Id, Rate Schedule Id:
The Security Id and Company Id have been moved from near the bottom of the Main tab to the left of the Return to Inventory button.
If the registry DeferTaxStatusDecision is set to true, the Flat Rate Revenue line imports correctly. Previously, only the costs were imported.
New Field - Tech Id:
The new Tech Id field is set with the Technician's Id if the Call Script is updated from TechAnywhere.
Changed Field - Cycle Code Filter: When manually adding a line, the Cycle Code's 'CC' filter is now pulled from the line's Work Code to filter the Metrics lines that are automatically added. This release correctly sets the Cycle Code Filter when Equipment is manually added with a Work Code referencing a Cycle Code. This will prevent TechAnywhere sync issues resulting from an incorrectly formatted filter.
Changed Field - Work Requested:
This field has been expanded from 3000 to 6000 characters.
Changed Field - Work Perform:
This field has been expanded from 3000 to 6000 characters.
The Milestones Tab was initially designed to be populated the Project Work Order Generator. This release allows Milestones to be added to any Work Order for reporting purposes.
Tip: If using the Milestones on a manually created Work Order, first set the Date Must Complete and the Time Must Complete and SAVE the Work Order before added the Milestones. The Milestone's End Date/Time are controlled by the Days/Time Offset fields and the Work Order's Date/Time must complete.
Also in this release, if the user changes the Milestone's End Date/Time, the Days/Time Offset fields will automatically be updated (if the Fixed Date / Time boxes are not checked).
See Customer Note 16.17.4 for additional information on using this tab.
The following tech Statuses have been added with their corresponding Work Escalation Status: Parts Backorder, Parts Issue and Parts Shipped. These new statuses fall above Parts Received and below Parts Ordered in precedence.
A new tech Status, Wait Tracking, has been added; it has a corresponding Work Order Escalation Status of Wait Tracking (Status Category Completed), This new status falls above Completed and below Over Budget in precedence.
A new tech Status, Over Budget, has been added; it has a corresponding Work Order Escalation Status of Over Budget (Status Category Completed), This new status falls above Completed and below Wait Paperwork in precedence.
'Purchases Blocked' subcontractor Technicians may NOT be selected on the Tech tab. Previously, this validation was only applied to "Payments Blocked" technicians. See Customer Note 16.16.1 for details.
This release refines the update of the Purchase Order if one Subcontractor Tech (with a referenced PO) is changed to another. The AP Term in the PO is forced to match the terms from the Vendor record, even if blank (unless overridden by customization). The PO's Sales Tax Group is updated from either the Vendor (by default) or Job record (if the DefaultPOTaxGroupFromJob is set to true in sys-viewer-vprchseordrlst registry).
Previously, the Work Order Purchases Tab always displayed the quantities Received and Vouchered as 0.00 (zero) if a Purchase Change Order was created after PO Receipts, even if the items had been received. In this release, the quantities Received and Vouchered are always displayed correctly.
This release corrects a display problem in Work Order List views that included the Work Order Work Requested on the list. In earlier versions of 9.1 certain fields on the list would appear blank.
When searching for Work Order Techs with the WorkOrdersByBranchIDByWorkOrderID' list enabled, only the Primary Tech will be included in the search. The Primary Tech has been added to the list to avoid confusion.
When Service Compute is run, an entry to the WO's Log Tab will be made: set the Status to Billed, the Date Logged and Work Date to today's date, and the User Id to person running the Compute.
Certification tabs have been added to the Equipment (see Customer Note 2.3.2) and Site (see Customer Note 2.4.1) records. Also see Customer Note 16.1.9 for a Registry to add Work Code Certifications to TechFinder
When TechFinder is launched from New Call, the Certification from the Equipment's Main Tab is listed on the Certification range (along with those from the Equipment's and Site's Certifications tabs and the Work Code). This list is prepended with an ampersand & so that only those Techs with all the Certifications listed appear in TechFinder.
When TechFinder is launched from the Dispatch Board or Work Order Tech tab, all Certifications from the Work Order's Site, first Equipment Id, and Work Code (if registry enabled) will be listed. This list is prepended with an ampersand & so that only those Techs with all the Certifications listed appear in TechFinder.
When PM's are generated for contracts with TimeofServiceBill? box flagged, the Cost Category will always be set on the WO Other tab.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
New Field: Original Start Date:
This informational field may be used to record the original Start Date of the Master Contract.
Changed Field: ScvTasksId:
In previous releases, if a Service Task Id wasn't specified on the Schedule tab of PM Master Contract then no Task List was attached to the PM Work Order generated from that line. In this release, if the Service Task Id is blank, the system now looks to see if there is one specified in the Client Site Equipment. This Service Task will be defaulted to the Client Site Equipment PM Schedule and then to the PM Work Order itself. This enhancement allows for different Task Lists to be assigned by the Equipment scheduled. If a Service Task List is specified on the Master Contract's Schedule line, it will continue to be used for all Equipment scheduled for from that line. See Customer Note 16.1.6 for a registry to disable the new behavior.
This release allows for handling of multiple sites when TimeOfService Earn? is set to Y. Additionally, when Revenue Values as %? is set to Y along with TimeOfService Earn? users may specify a percentage value in Revenue Per Visit on each Schedule line of the contract.
When only TimeofService? is set to Y and multiple sites are specified - the system will evenly prorate the revenue on the corresponding RevAdjust lines that are added to the Preventive Maintenance Work Orders generated through Start Create PM Workorders.
When both the TimeOfService? and Revenue Values as %? fields are set to Y with multiple sites specified - the system calculates the percentage of revenue specified in the Revenue Per Visit field based on the Site Contract Value. This percentage is reflected in the RevAdjust lines on the Preventive Maintenance Work Order generated through Start Create PM Workorders. The sum of the Revenue Per Visit on all Schedule lines must equal 100% in the Master Contract record. If the user fails to enter a percentage in the Revenue Per Visit field the system will evenly prorate the revenue.
Note - the Advanced Billing will still be prorated evenly across all months set to Bill? on the Setup/Renew tab of the Master Contract.
Users may now edit the Under Contract status of Equipment records without the list being resorted. This makes it easier to work with very large contracts.
Click Magnify
New Field: Disabled
When this field is flagged, this event will be ignored when scheduled events are generated for a new Weblog or Work Order. Weblogs and Work Orders created before line was flagged as disabled will not be impacted; the Scheduled Event will still be processed.
This release supports tokens for the Latitude and Longitude fields in the Client Site. The token ^clntste.geo_code_latitude^ references Latitude and ^clntste.geo_code_longitude^ references Longitude.
The new ^workperformedall^ token displays the Equipment Id, Name and Work Performed of all Equipment lines on the Work Order when the Scheduled Event is executed.
The new IVR Instructions field on the Client Site record may be used in escalation emails (using the token ^clntste_ivr^) to the Technician. It is also designed for future use in TechAnywhere.
Previously, to attach SAMPro documents to an escalation profile email, you had to select the documents by category at the time of New Call creation. This would add those documents to the work order at that time, and only those documents could be attached to the notification email. In this release, you can specify which categories of documents will be attached on each individual line of the escalation profile. This allows for documents added after initial creation to be attached to the corresponding email as the work order's technician status changes.
To attach documents to escalation notifications based on pre-determined document categories listed in Function Parameters field of Escalation Profile:
The document(s) must be attached to the work order prior to the specified status change to be eligible for attachment.
The Attach Document flag must be checked on child line of escalation profile. Hit the green plus sign on the top left corner of the escalation profile line to show the Function Parameters field. Set the document categories you wish to attach to the notification that is triggered by that lines status change. “Categories=” will precede a comma delimited list of valid document categories.
Tip: Double click the Category field in any document viewer in SAMPro to view a list of valid Document Categories. Custom Document Categories may be added manually and will be included if specified. ***NOTE – SAMPro generated invoices are given a category of “Invoice” (not “Invoices”) and MUST be specified as such in the escalation profile for inclusion.
Important: The document must be a filetype capable of opening via email. We recommend autosavefiletype = PDF be set in all report registries for the documents you wish to attach via escalation profile. Reports that autosave as a .dbr can only be opened in SAMPro and therefore will not open via email. Any/all pre-existing document records should be converted from .dbr to PDF before utilizing this functionality.
Example:
Status From: Parts Received
Status To: Completed
Function Parameters: Categories=Quote,VendorInvoice
In the example above, any document with a category of Quote or VendorInvoice that is attached to the work order prior to that status change will be attached to the email and sent to the contact specified in the Notify Id.
When a Notification Category is set to Account Manager, the Work Order's Account Manager's Contact Record Email Address is used to derive the 'email to' of the scheduled event. Previously, the Site's Account Manager was always used, regardless of whether is was set in the Equipment record or changed in New Call. Note that if the Account Manager is cleared in New Call the selected Site's Account Manager Contact will continue to be used for Account Manager Notifications and Alarms.
Now supports posting to expanded Work Order Labor and Inventory cost and price fields. Also supports Accounting Periods with WO Inventory to GL flagged.
Now purges scheduled events for archived WO's.
If the WO's Date Work Completed is set, it is now used for the archived Tech line. If the Date Work Completed is not set, the archived Tech line has today's date, as before.
New Field: Date Completed:
This field allows the user to include only those Work Orders whose Date Work Completed falls on or before the selected date (subject to the Date Opened Date Closed settings). If this field is completed, Work Orders whose Date Work Completed is blank will also be excluded. If this field blank, the Work Order's Date Work Completed will not be considered by this function when generating the checklist.
This release corrects an issue when the Market Source was not always written to the Work Order. It also corrects a sporadic problem where the WO Email was not defaulted from the Client Site.
The Work Requested verbiage from the selected Web Log is used to generate the new Work Order's Work Requested and Equipment Work Requested, correcting a sporadic problem in previous releases.
'Purchases Blocked' subcontractor Technicians may NOT be selected in New Call but "Payments Blocked" technicians may be selected. See Customer Note 16.16.1 for details.
The PO Required field is once again enforced; corrects a problem in recent versions.
The Site's Service Manager is no longer cleared when changing the Job changes the Client. Corrects a problem when the sys-newcall option ServiceManagerBasedOnSite=true.
In this release, Ctrl-A is ignored instead of generating an error. The Add WO button must be clicked to add the Work Order; the keyboard equivalent is not supported.
This release corrects a performance slowdown loading New Call in recent versions.
This release refines handling of the middle pane so that the Client Site List (and not the Master Contract pane) is displayed after the user completes a Call Script.
Changed Field: Weblog
When a Weblog from TechAnywhere is entered in New Call, a wizard displaying the Weblog information will appear. The following buttons allow you to process the Weblog as follows:
Proceed: Clicking this button will use this Weblog to create a new Work Order. The contents will load into NewCall to allow the dispatcher to finish creating the new Work Order.
Decline: Gives the user the opportunity to change a Weblog to the status of ‘Cancelled’ to remove it from the list of New/Unacknowledged Weblogs.
AssignToWO: Click this button to select an existing Work Order to assign this Weblog to. The Weblog’s Equipment and Work Requested contents will be added to the Work Order's Equipment Tab. The Weblog will also be changed to Acknowledged and reference the selected Work Order.
Cancel: Returns you to the New Call with the weblog field cleared. It only cancels the operation of selecting the Weblog; it does NOT set the Weblog's status to Cancelled. Note: Pressing the X works the same as the Cancel button.
New Field: Work Order Email
When a Site is selected in New Call, the Client Site's Email field is now defaulted to new Work Order Email field. The user may manually update this field if desired. Escalations for the new Notification Source 'Work Order' will be sent to this address.
The Email address for the Scheduled Events is set when the WO is generated. Changing it in the Work Order after creation will not propagate the change to the Events themselves.
The Work Order Email is also set from the Site Email by the following functions:
Start Create PM Work Orders
Start Create Job Scheduler WOs
TechAnywhere - new WOs created from TechAnywhere
QuoteMaster/Quote Manager (new Work Orders generated by this function).
New Source: Work Order
If the Source 'Work Order' is selected, the Work Order's Email Address field will be used when generating Email Notifications/Alarms.
Notification Category:
Escalation Profiles for Work Orders now support Notification Categories with a Source of Work Order.
The NTE amount from the selected Service Request now defaults to the NTE Client field which will populate the corresponding field in the newly created Work Order.
Also fixes an error accessing the FMMSInfo table when the Vendor Value includes an apostrophe (e.g. "Domino's").
This release corrects issues in the FacilitySource integration when selecting the web log.
This release corrects an issue where changing the selected Site Equipment updated all applicable fields except the field the cursor was positioned on. In this release selecting the Site Equipment also updates the New Call 2 field the cursor is positioned on.
New Field: Original Caller
This field lists the person who called in this Work Order. It defaults from the Contact 1 First and Last Name fields in the Client Site record (if completed); if these fields are not completed it will default from the Client Site Contact 2 information. This field may be changed by the user; it will be written to the Work Order's Original Caller field.
New Field: Original Caller
This field lists the person who called in this Work Order. If completed by the user, it will be written to the Work Order's Original Caller field.
The Quote Report Id (QuoteDefaults tab) and the GL Entity Id (COP tab) are now defaulted from the Client Site template to the new Client Site created by this function.
This release corrects an extremely sporadic problem where closing the Dispatch Board after setting a Custom Date on the Date Range tab resulted in a childless copy of the selected Work Order being generated.
Error Handling: corrects a 'doWIthIndex:' error related to list pane filtering, and a very sporadic 'key is missing error' on certain mouse movements. Also corrects a sporadic "System Primitive Failed" error when clicking on the column header of the Time Chart.
Column Filters: If you use the new column filtering on the Workorder List, these filters are cleared on the Workorder List pane when a new Technician is selected on the Tech Status Summary (upper) pane.
When UseOutlook is enabled via registry, clicking the Email button launches the Outlook form and sets the Email To field with the Tech’s Email Address 2.
'Purchases Blocked' subcontractor Techs may NOT be selected if their required insurance is expired on the selected date.
When a Subcontractor Tech is changed on the WO Tech tab or the Dispatch Board, the system automatically changes the Vendor in the associated PO. In this release, the PO's A/P Terms and Sales Tax Group are also updated from the Vendor record.
When the Tech Lists button is clicked, the Dispatch Board Id and Name will both appear when the list of Dispatch Boards is displayed. This release also corrects a System Primitive Error in the Tech Lists tab when the user clicked at the top of the tab so that no list was selected, and displays Tech Lists with 15 character Id's correctly.
Work Order changes are only allowed from the Dispatch Board if the User belongs to a Group with Change permission for View Work Order or Work Order Dispatcher.
Corrects an 'argument must be a collection' error launching TechFinder.
The Date Range button has been added to the Classic and Day boards. This allows users to switch the Date Range without having to switch to the Powerboard first.
This release corrects an overlap issue that made it difficult to click the left arrow to change the Date Scheduled.
The Work Order Summary screen is accessed from the Power Board by right-clicking on a Work Order and selecting Update Work Order. It allows the dispatcher limited edits to specific WO fields. This function was never designed to support the deletion Work Order lines. The Delete Line button has been removed from the side button bar in this release to avoid confusion. This release also corrects a 'key is missing error' when Equipment is added or changed on the Equipment tab.
The Work Order's Earliest Start date has been added to the Power Board as a new column. This column will initially be located on the extreme right-hand side of the work order list, but drag and drop may be used to reposition it according the user's preference.
This release corrects a formatting issue which prevented GPS stops from getting to Fleetmatics.
This release provides revised handling of the cancellation of a schedule date, and direction request to be compatible with the Fleetmatics work order format.
This release corrects a problem where only the first line marked "Already Done" was handled correctly. In this release, all PM's checked as "Already Done" will have the Equipment PM Schedule line updated with "NO WO" as the WO ID.
When the TechServiceParts=No registry is enabled and Service Parts and Tasks are specified, the Tasks now correctly written to the WO Equipment Work Requested
When this function generates a PO for Subcontractor Techs, the Site Equipment being serviced is completed on the PO's Gen line.
If this box is checked and the Technician Id field is also completed, the Technician Id selected will be assigned to ALL work orders generated by this function. If the Override ALL Tech? box is blank, the Technician Id (if selected) will only be used where a Technician is not specified in the Equipment or Site record. If the Override ALL Techs? box is checked the Technician Id must be completed. Additional changes to the Technician may be made when the Create PM WOs checklist screen is displayed.
Changed Field - Method:
The obsolete TechAnywhere option has been removed from the list of Methods to avoid confusion. This option was for RTD (Remote Tech Device for the Blackberry) notifications in previous releases.
NOTE: If any Notification Category records specifying the Method 'TechAnywhere' exist in your data, the 'Selected Record Not Found' message will appear when selecting from a list. The Notification record's Id must be typed in to access / edit the record. You may wish to Obsolete these entries.
New Source: Work Order
If the Source 'Work Order' is selected, the Work Order's Email Address field will be used when generating Email Notifications/Alarms.
Corrects a problem where TOS Equipment values and Client Site Billing amounts were being combined.
In previous releases, Start Renew Service Contract renewed schedules on inactive pieces of equipment if they are marked OK to renew. In this release, Active/Inactive status of the equipment be considered during the renewal process so that Equipment flagged as Inactive will be skipped.
This release corrects the issue where manual changes to the New Value field in the Start Renew Service Contracts Checklist were being ignored. The PM Billing lines on the Client Site were generated in the amount of the original contract, rather that the New Value entered during the renewal function. PM Billing lines are now given the cumulative total of the manually entered New Value.
The Description column has been enhanced to better define that type of renewal being run based on the types of lines filled in on the Site PM Billing and/or the Site Equipment PM Schedule:
PM Billing has no value and PM Schedule has no contract value: T&M Inspections
Scheduled PM Billing has no value and PM Schedule has contract value: Equipment: Time of Service Billing
PM Billing has value: Site: Bill in Advance
New Fields:
Vendor Name:
If the Vendor field is completed on this subcontractor technician record, the Vendor's Name will be displayed, and the following fields will be completed if applicable.
Insurance Required: Insurance Expired:
The insurance required field defaults from the Insurance Required field in the Vendor record. If this field is checked, the system will check the INS tab in the Vendor record to determine if all insurance is still valid. If not, the Insurance Expired field will also be checked.
Payments Blocked:
If this display field is checked, the Vendor’s Insurance is flagged as 'Block Payments' and it is currently expired. A 'Payments Blocked' subcontractor may now be selected in New Call, the Dispatch Board or on a Work Order in SAMPro 9.1.611.045 and above. This was not true in previous releases.
Purchases Blocked:
If this display field is checked, the Vendor’s Insurance is flagged as 'Block Purchases' and it is currently expired. A 'Purchases Blocked Tech' may NOT be selected in New Call, on the Dispatch Board and on Work Orders.
RAQ Group:
This field is reserved for TechAnywhere use.
Technician User 6-10
These fields are designed for use with TechAnywhere.
The new Project Manager Work Order Generator is designed to streamline the process of creating a large number of Work Orders to implement a one-time project. For example, suppose that your firm wins a contract from BigBox to install Gizmos at all of its stores. This will require hundreds – or thousands – of Work Orders to get the Project completed. The Project record is the key to the Project Work Order Generator.
The following records must be configured correctly to run the Start Project Work Order Generator:
Project:
The Project specifies the Equipment and Jobs eligible for use in the Create Project Work Order Generator. Typically, a new Project, Jobs and Equipment would be created for each major Project. After the Project was completed and billed, the Jobs would be closed, the Equipment marked Inactive, and the Project obsoleted.
Job:
Job records used by the Start Project Work Order must reference the selected Project. To be used with this function, Jobs should be flagged as Service Compute.
Site Equipment:
The Equipment Id must match the Project Id exactly! Complete the Esc. Profile Id if you want Scheduled Events generated for the Work Order. The Default Service Job must point to a Job referencing the Project. The Cost Code and Billing Item must also be completed.
Milestone Group:
Defines the Milestone which will be attached to the Work Order. When the Work Order is generated, the Days and Minutes Offset will be used to calculate the End Date and End Time on the Work Order’s Milestone line based on the Date / Time Must Complete.
Call Script:
A Closing Call Script may be applied to the Work Orders if required.
Work Code:
The user may select a Work Code to be applied to the generated Work Orders. The Work Code Id is also used to determine if a matching WO already exists for a given Job.
Once the records have been correctly configured, Start Project Work Order Generator should be run to create the Work Orders needed to implement the Project.
The Start Project Work Order Generator is used to actually create Service Work Orders defined by the Project, Job and Equipment definitions. If a Technician is specified in the Equipment record, the Work Order will be assigned to that Tech.
This function is sensitive to the required fields registry settings for sys-start-snwcll. If a field is required in New Call it must be completed or defaulted when this function is run. If not, an information box describing the issue will be displayed and the Work Order will not be generated.
Project Id:
Select the Project you wish to create Work Order for. Jobs must reference the selected Project AND the Client Site Equipment Id MUST MATCH the Project Id in order to be selected for Work Order generation.
The Project Id must be completed. The user will be warned if the Milestone Group, Work Code, or Call Script are blank.
Milestone Group:
The Milestone Group defines the Milestones which will be attached to the Work Order.
Work Code:
Specifies the Work Code to be assigned to the generated Work Orders. The Work Code Id is also used to determine if a matching WO already exists for a given Job. The Do checkbox on the Checklist screen will NOT be flagged if a Work Order for that Job / Work Code combination exists.
Client NTE - Sub NTE
If these fields are completed, they will provide the defaults for the Work Orders' Client and Sub Not To Exceed (NTE) fields.
Closing Call Script:
Completing this field specifies the Closing Call Script for the generated Work Orders.
Date Must Complete: Time Must Complete:
Enter the Date and Time that the work for the selected Project must be completed. These fields will be used to set the Date and Time Scheduled on the Work Order Technician Tab. In addition, the Days and Minutes Offset in the Group and the Date / Time Must Complete will be used to calculate the End Date / Time on the Work Order’s Milestones.
Default PO#:
The customer's PO# for this work; this field will be used to complete the PO# field in the Work Order.
Dispatcher Id:
If this field is completed it will provide the default Dispatch Id to use when generating these work orders. If it is left blank, the Dispatcher referenced in the Equipment record will be used.
Job Id: Job Name:
The Job Id or Name range may be used to filter the Jobs processed by this function. This would be completed if you did not wish to generate all of the Work Orders for this Project at the same time.
Project Manager Id:
This range filters this function to the Project Manager(s) assigned to the Jobs for this Project.
Site State:
This range filters this function to the State specified in the Job's Site record.
The Checklist displays the results from input filters on the previous screen.
Do:
Lines that are presented with the 'Do' box checked have been validated and will be used to successfully create a Work Order. If the 'Do’ box is not checked, a problem exists for that Equipment or Job. The user will be informed of the particular problem when attempting to check the Do box (for example, if a Job points to the Project but there isn't Equipment for this Job that matches the Project Id).
If a problem occurs, click Ok, then close the Checklist (with the red X in the upper right-hand corner) and correct the problem. After correcting the problems, rerun the function.
Milestone Group: PO#: Work Code: Call Script:
Date Must Complete: Time Must Complete: Client NTE: Sub NTE: Dispatcher Id:
These fields defaulted from the previous screen, but may be adjusted on the Checklist if needed.
The Milestone Group is designed for use with the Start Project Work Order Generator. It will populate the Work Order Milestone tab when the Start Project Work Order Generator creates Work Orders.
Milestone Group Id:
A unique name for this Milestone Group.
Milestone Group Description:
Briefly identifies the purpose of this Milestone Group.
Milestone Group User1-5:
These fields may be used for reporting and other informational purposes.
Obsolete?
If this field is checked, the record is considered Obsolete, and it may not be directly specified during data-entry (either by entering the Id or selecting it from a list).
Milestone Id: Milestone Description:
Enter a Milestone Id (or double-click to select from a list. The display-only Milestone Description defaults from the Milestone.
Description:
This editable field may be used to better define this Milestone. Both the Milestone Description and the Description will appear on the Work Order Milestone tab.
Days Offset: Minutes Offset:
When the Work Order is generated, the Days and Minutes Offset will be used to calculate the End Date and End Time on the Work Order’s Milestone line based on the Date / Time Must Complete.
For example, if the Work Order was generated with a Date Must Complete of April 15, 2017 a Days Offset of 10 would generate Milestone End Date of April 25, 2017. Negative Offsets may also be specified. In the above example, a Days Offset of -10 would generate an End Date of April 5, 2017.
Fixed Date: Fixed Time:
Milestone Dates and Times are set during initial WO creation regardless of whether these fields are flagged. These fields come into play in the Work Order viewer when Date/Time Must Complete is changed. Basically, Fixed means do NOT change the Milestone’s End Date / Time after the initial Work Order creation.
New Tab: Milestones
Work Order Milestones are typically referenced by DBAnalytics for tracking purposes for Work Orders generated by the Start Project Work Order Generator function.
Milestone Id:
Milestones are automatically populated by the Start Project Work Order Generator function when WO's are generated.
They may also be added to any Work Order for reporting purposes.
Tip: If using the Milestones on a manually created Work Order, first set the Date Must Complete and the Time Must Complete and SAVE the Work Order before added the Milestones. The Milestone's End Date/Time are controlled by the Days/Time Offset fields and the Work Order's Date/Time must complete.
End Date: End Time:
This field specifies when this Milestone should be completed.
If this Milestone line was populated by the Start Project Work Order Generator function, the End Date and Time are initially based on the Date and Time Must Complete specified in the function, and the Days and Minutes Offsets of each Milestone.
If the Date / Time Must Complete is changed in the Work Order’s Main tab, Milestones NOT flagged as ‘Fixed’ will have their End Date / Time fields updated automatically on the new Date/Tab and the value of the Offset fields.
If the user changes the Milestone's End Date/Time, the Days/Time Offset fields will automatically be updated (if the Fixed Date / Time boxes are not checked).
If the Fixed Time / Date fields are flagged on a Milestone, changing the Work Order's Date/Time Must Complete does NOT change the Milestone’s End Date / Time fields.
Milestone Description:
This display field defaults from the Milestone record.
Description:
This field is set from the Milestone Group if this line was generated when the Start Project Work Order Generator function was run, It may be changed by the user if needed.
Days Offset: Minutes Offset:
When a Work Order first generated, the Days and Minutes Offset will be used to calculate the End Date and End Time on the Work Order’s Milestone line based on the Date / Time Must Complete. For example, if the Work Order was generated with a Date Must Complete of April 15, 2017 a Days Offset of 10 would generate Milestone End Date of April 25, 2017. Negative Offsets may also be specified. In the above example, a Days Offset of -10 would generate an End Date of April 5, 2017.
If the Work Order's Date / Time Must Complete is updated, the Milestone's new End Date / Time will also be updated using these offsets if this Milestone is not flagged as Fixed Date / Time.
Fixed Date: Fixed Time:
Milestone Dates and Times are set during initial WO creation regardless of whether these fields are flagged. These fields come into play in the Work Order viewer when Date/Time Must Complete is changed. Basically, Fixed means do NOT change the Milestone’s End Date / Time after the initial Work Order creation.
Completed?
Check this field if this Milestone has been completed. If the Completed flag is checked the Milestone cannot be changed.
List View:
A new Sort Order, WebLogByWorkOrderByClientSiteName has been added. This Sort Order also displays the Web Log's Tech Id (of the Tech who added a recommendation and generated the Web Log), Date and Time Logged, and the Work Requested.
Range View - New Ranges:
Dispatcher Id:
This range may be used to filter Web Logs based on the Dispatcher referenced in the Client Site record.
Technician Id:
This range may be used to filter on the Web Log's Tech Id (the Tech who added a recommendation and generated the Web Log).
Work Code:
The Work Code Id has been substituted for Service Category Id on the viewer's Find Data range screen. This prevents an error when filtering by Service Category in the Web Log.
Web Log Viewer:
The Work Requested display field has been expanded from 4 to 14 lines. A revised customization file is required to see this change unless upgrading to this version. .
This release corrects a key is missing error running this starter function with the sys-start-sautoarchivewo registry enabled.
This release eliminates unnecessary updates to Scheduled Event's Record Change Logs. Also streamlines Token Replacement code in the SEM to prevent excess memory usage.
The system no longer pops up a message when a scheduled report is generated from an escalation profile event. In previous releases, reports auto-generated from an escalation profile would cause a message to display when the report was added the report queue. This would cause the scheduled events manager to stop running until the message was cleared. This could be controlled by configuring the batch file running scheduled events with the switch -messageBoxSuppress=yes enabled, but this was not the best solution.
This release avoids a Runtime error: RnFetchErrorForKeyName by preventing the user from scrolling the Start Work Order Daily Edit checklist when Go has been clicked and the Work Orders are being updated
The Inventory Item Id column on the components lines has been expanded to support longer Id's. This system report does not need to be imported.
Corrects errors accessing records encountered in recent releases.
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter.
The rules regarding allowed Cost Category Selection Types have changed as follows:
|
Shop Order/Shop Order Journal |
Revised Cost Category Rules |
Old Cost Category Rules |
|
Job Tab |
ok: mat, eqp |
ok: mat |
If Intercompany is enabled, the system will now check for company security level registry settings when running this function; an error will be displayed if these registries (sys-viewer-vshpordr-securityid) are not found.
By default, Obsolete Locations and Inventory Items are now excluded from Start Backorder Filling. A new registry may be implemented to have Start Fill Backorders include Obsolete Items and/or Locations.
Registry Id: sys-start-sbckordrfllng
Setting Key: IncludeObsoleteLocations Setting Value: true (default is false)
Setting Key: IncludeObsoleteItems Setting Value: true (default is false
Changed Field: Cost Category
This field now supports enhanced filtering provided by the Cost Code's Job Cost Category Usage Filter. Cost Categories are validated (relative to Cost Codes) during data entry upon leaving the Cost Category Id field. The full relationship is validated again when leaving a child line or saving a record.
The rules regarding allowed Cost Category Selection Types have changed as follows on this tab:
|
Work Order |
Revised Cost Category Rules |
Old Cost Category Rules |
|
Required Resources Tab |
ok: mat, oth, sub, eqp Inventory Item must use a Cost Type of material or equipment |
ok: mat, oth, sub Inventory Item required a Cost Type of material. |
This function doesn't change the WO status from Waiting Parts to the Tech's default status (or a value set via registry) unless all requisitioned parts are transferred and all related WO PO line items have been received. In this release, an additional test is made to verify that there are also no unvouchered PO-SUB lines when $Based POs are being used.
This function also eliminates the requirement that Work Orders must have Required Resource entries to be eligible for this function to support the scenario that a Work Order references only a PO with $Based Sub lines.
This new registry tells the post whether or not to include a reference to the Work Order's Job in the Document records created from the uploaded collateral. Note that collateral files will always be attached to the Work Order and to the Equipment record referenced in the TA Collateral List. The collateral being posted from TechAnywhere would add a document reference to the Job from the Work Order.
Id: sys-techanywhere
Setting Key: AttachCollateralToJob Setting Value: true or false (default false)
Id: sys-techanywhere
Setting Key: InventoryCostCategoryId Setting Value: CostCategoryId
When an Inventory PO is created in TechAnywhere, the Cost Category now defaults from the Item's Inventory Group. If the Cost Category is not set in the Inventory Group, this registry is used as a backup to derive the Cost Category.
When Work Order Other lines are posted from TechAnywhere, the system will now adjust the Date or Accounting period based on the following existing sys-techanywhere registry. This will ensure that the Effective Date and Accounting Period are in sync. This is important for clients using the Accounting Period's WO Other to G/L? option. If the registry is not set, the default Accounting Period will be used and no check will be made to ensure that the Effective Date falls within the Account Period.
Id: sys-techanywhere
Setting Key: AdjustDefaultDateOrPeriod Setting Value: Period or Date
In this version, COD and (and other PO changes) are successfully handled since the Billable Quantity and Price updates are posted to the Purchase Order so the standard posting method is now the default. See Customer Note 4.1.3 for details on changes to this Purchase Order registry.
Flat Rates: In this release, when a Flat Rate is referenced, the price from TechAnywhere is always used. Previously, if the price was adjusted using any other price level than 1, the TechAnywhere price override was ignored.
Labor: This release removes the Supervisor logic for TechAnywhere as this never should have been added. This functionality is available in TimeAnywhere.
Labor: The Labor Post now follows the Labor Journal Registry to Use Default Service Job in the Equipment record for all but PM WO’s. See Customer Note 12.1.15 for the registry.
Collateral Documents: TechAnywhere now writes errors to the TechAnywhere Message Directory if a collateral Document fails to post so that the issue can be tracked.
Purchase Orders: PO's will not be updated by the post if no values have changed. This will preclude failed message when the post attempts to update a closed PO.
Quotes: This release corrects a sporadic problem where TechAnywhere combined all outstanding quotes into one message resulting in all scopes being written to all quotes created by the post.
Taylor UWO: This fix applies to customers using the Taylor Universal Work Order functionality. It corrects a 'Key is Missing' error when posting Work Order COD information.
This release supports subfolder logic when a file is archived after a delay; previously, these files were archived in the base archive directory.
The Unit Cost entered by the Tech Material and Other lines now posts back to SAMPro so that the Quote's costs are correct.
To improve performance, the Post now applies a 90 Day cutoff date for documents so that it no longer attempts to archive documents which can likely never be archived. .
Equipment created from the Timesheet is now assigned Security from the Site if applicable.
This release corrects Out of Memory Error when Posting Large Messages.
This release makes the determination of a TA PO's posting style more accurate.
The Tax Type is now set correctly when Flat Rates are posted from TechAnywhere.
PO's generated in TechAnywhere now have their Company / Security set from the Work Order that the material was purchased for.
This release corrects a problem in the TechAnywhere Post cause by the override of the Labor Rate by the Job Cost Category.
When a PO message from TechAnywhere fails (e.g., due to expired insurance), the Vendor Id and Name are now included in the TechAnywhere Error Alert email to make it easier to identify problems with the Vendor.
This release corrects a recent where TechAnywhere post did not update the Job Quantity Ordered and Job Quantity Received on the PO from TechAnywhere.
In previous releases, the TechAnywhere PO Receipt Post could select the incorrect Accounting Period/Effective Date. Typically, this would occur around the time of an accounting period changeover (beginning of the month) due to the Information warning/error "EffectiveDateNotInPeriodRange" causing the TechAnywhere Event Manager to stop running until cleared. For example, if the default accounting period was still December, posting with a January 1st date could generate Information warning/error "EffectiveDateNotInPeriodRange" causing the TechAnywhere Event Manager to stop running until cleared.
In this release, the PO Receipt Post now adjusts the Accounting Period match the Effective Date if possible. The following registry entry may be used to override the default behavior and instead set the effective date to fall within the Default Accounting Period to the default Effective Date. In most cases, the default functionality (period) is preferred. This entry (and the new default behavior) only impacts the TechAnywhere Receipt Post, not manual entries.
Id: sys-viewer-vinvntryrcpt
Setting Key: AdjustDefaultDateOrPeriod Setting Value: period or date (default is period)
When period is specified:
The Accounting Period table is queried for eligible Accounting Periods. To qualify, the period must be Active and its date range must include the defaulted Effective Date. When multiple periods are eligible, the one with the smallest Period Id is chosen to become the new Accounting Period for the current transaction. If no eligible period is found, nothing is changed.
When date specified:.
The Effective Date is adjusted to be either the Start Date or the End Date of the defaulted Accounting Period. The Start Date is chosen when the current date is less than the Start Date. The End Date is chosen when the current date is greater than the End Date.
In the absence of the new setting, it uses the 'adjust period' behavior described above as default.
New Field: Tech Id
This field is updated whenever Call Script info is being posted/updated by TechAnywhere.
When a Work Order is created in TechAnywhere, its Client and Sub NTE fields now default from the Site Equipment record. If these fields are not set in the Equipment record, they will default from the Site record. These fields were not previously set when a Work Order was created in TechAnywhere.
When Equipment is created from the TechAnywhere Timesheet, the Equipment Name now defaults to Pending instead of the Equipment Id to correct an issue with Custom Fields Settings. If Custom Field values are specified for the Equipment Name, Pending must be one of the allowable options.
TechAnywhere Version 4.0.058.008 allows the Technician to replace one piece of equipment with another. This functionality must be enabled in TechAnywhere if desired. From TechAnywhere, the Tech can mark an old equipment record as replaced from the field and create a new equipment record and link it to the old to record equipment that it replaced. This functionality may only be initiated from TechAnywhere.
Site Equipment Service Tab
New Fields: Replacement Equipment Id: Replacement (Date):
These display fields will be completed if the currently selected Equipment Id was replaced by the Replacement Equipment Id on the Replacement date listed from TechAnywhere. If the selected Equipment has NOT been tagged as replaced, these fields well be blank.
When a TechAnywhere Tech decides to replace equipment (Ex. RTU-1), the following will happen as the Replacement Procedure is implemented during the TechAnywhere Post:
Rename original Equipment record from RTU-1 to RTU-1-R
If RTU-1-R already exists (was replaced in the past), use RTU-1-R2, RTU-1-R3 and so on. Note we skipped 'R1' as it makes more sense to do so.
Set the Replacement Equipment Field to link the new RTU-1 equipment to be created soon after.
Set the Date Replaced with the current date.
Set the Deny TA Access flag to Yes, so the old equipment is no longer accessible from TechAnywhere.
The New replacement equipment will be submitted when the technician completes the work order. The new equipment will have the same ID as the original, RTU-1.
You are now left with 2 equipment records. The new RTU-1, and the old RTU-1-R.
This release contains a refinement to this functionality. If the message payload being posted contains a 'ReplacedWith' RN value that has already previously been replaced, do not replace the equipment again (ignore going through the equipment replacement code). This scenario can happen because TechAnywhere maintains this RN value throughout the life of that equipment in the TechAnywhere database. It's possible for this equipment record to send multiple times (in different messages). This change prevents the Equipment from erroneously being replaced.
Client Site Service Tab
New Field - PCR Table Id:
This field is used by TechAnywhere to indicate that Equipment linked to this Site requires a PCR Table. If it is completed, TechAnywhere will force technicians to pick a PCR table ID whenever adding new equipment for a Site with this field completed.
This field also provides the new default value for new Equipment created for this Site in SAMPro.
If Technicians should have access to any of the new statuses (Parts Backorder, Parts Issue, Parts Shipped and Wait Tracking), their TechAnywhere configuration will need to be customized.
This SAMPro release allows specified Work Order User fields to be viewed / modified by TechAnywhere. This functionality must be enabled via the appropriate TechAnywhere configurations. Specific User fields may be configured as read-only. Contact your TechAnywhere support rep for details.
This release corrects issues experienced by some Canadian users uploading invoices. The Invoice Date is now sent in US format even for Canadian users for the I12 and I14 ServiceChannel Invoice Formats.
This release supports Work Order Ids that have characters in them (e.g., prepended with a Branch Id).
This release corrects an error ServiceChannel encountered updating a Weblog record. Also decodes Nancy accented vowels (as found in French) to their non-accented ASCII Equivalents.
Corrects handling of non-printing characters in the Work Requested when a new Web Log record is generated from ServiceChannel.
Incorrectly configured ServiceChannel responses now place a diagnostic message in the offending message record. The invalid response is otherwise ignored so posting is not interrupted.
New registries support setting the Work Code based on the Service Channel Priority, and the Equipment based on the Trade Code.
Map Service Channel Priority Codes to SAMPro Work Codes
Setting Key: PriorityToWorkCodeMappings Setting Value: PriorityCode:WorkCodeId
When enabled, this registry automatically sets the Work Code Id to a value derived from the Service Request's PRIORITY attribute.
This option specifies how the Service Channel Priority Codes map to the SAMPro Work Code Id's when a Work Order is created from a Service Channel . It supports multiple lines so that all ServiceChannel Priority Codes may be properly mapped.
Example: The following option maps the ServiceChannel 'Emergency' Priority Code to the SAMPro Work Code Id 'Safety'.
Setting Key: PriorityToWorkCodeMappings: Setting Value: Emergency:Safety
Map Service Channel Trade Codes to SAMPro Equipment Id's
When enabled, this registry will automatically select the Client Site Equipment based on the contents of the Service Request's TRADE attribute. It supports multiple lines so that all ServiceChannel Trades may be properly mapped.
Setting Key: TradeToEquipmentMappings Setting Value: TradeCode:EquipmentId
Registry Id: sys-FMMS-Vendor-ServiceChannel
Setting Key: IncludeScheduledDateInNewWorkOrder Setting Value: No (default Yes)
When New Call accepts a new Service Request via the weblog, the scheduled and time will be omitted if this option is set to 'No'.
Id: sys-fmms-vendor-ServiceChannel
Setting Key: IncludeMustCompleteDateInNewWorkOrder Setting Value: Y
When this registry is enabled, when a Work Order is generated from Service Channel, the ServiceChannel SCHED_DATETIME will be copied to the Work Orders' Date and Time Must Complete fields.
Id: sys-fmms-vendor-ServiceChannel
Setting Key: UploadEquipmentWorkPerformedNotes
Setting Value: Y
Note that values of Y, y, T, or t enable this mod; the default is that this mod is not enabled. When this option is enabled, Work Order's Work Performed is now sent as Notes to ServiceChannel whenever a Status update is sent.
A Work Order Note is sent to ServiceChannel for each Equipment line in the Work Order.
The Note includes the contents of the Work Order Equipment Work Performed field.
Each note is prefixed with the Equipment Id, Manufacturer, Model, and Serial Number.
If this option is not enabled, the Work Performed will be included in a <RESOL> sub-element of the <CALL> element when a status change is sent.
The previous registry enables a feature that sends a Work Order Note to ServiceChannel for each equipment line on a work order. This registry allows the upload feature to be disabled for specified Equipment Ids. This new registry option may be used to refine which Equipment Id's have their Work Performed uploaded to ServiceChannel. The value of this key is a comma separated list of Equipment Ids to be excluded from the Note sending operation.
Id: sys-fmms-vendor-ServiceChannel
Setting Key: UploadEquipmentWorkPerformedNotesExceptEquipment
Setting Value: Id1,Id2,...
Setting Key: UploadEquipmentWorkPerformedNotes
Setting Value: Y (note that this setting is also required)
The following example would prevent the sending of Work Order Notes for Client Site Equipment Id 'RTU2', but allow that for all other Equipment Id's to be sent.
Setting Key: UploadEquipmentWorkPerformedNotesExceptEquipment
Setting Value: RTU2
Registry Id: sys-fmms-vendor-servicechannel
Setting Key: InvoiceTemplate Setting Value: I.14
Setting Key: InvoiceIsDetailed Setting Value: Y (or y, T or t)
Note:
The Service Channel i.14 invoice template requires that materials are used to complete the job; ServiceChannel will reject the invoice if it doesn't contain material information. Since all jobs do not require materials, this release will add a dummy $0 material line to get around this requirement. The Material Description of 'No Material Required' will be used on the $0 line to conform to ServiceChannel requirements.
This registry disables sending ETA changes to ServiceChannel when a SAMPro Work Order's ETA changes.
Id: sys-fmms-vendor-ServiceChannel / sys-fmms-vendor-FacilitySource / sys-fmms-vendor-Corrigo
Setting Key: UploadWorkorderETAChanges Setting Value: No (default is Yes)
Note this setting is applicable to all FMMS Subsystems (e.g. Corrigo, FacilitySource). Any value beginning with 'Y', 'y', 'T', or 't' is equivalent to 'Yes' and any other value is equivalent to 'No'. The absence of the Registry entry is equivalent to a 'Yes' value. So there will be no change in functionality if the Registry entry is not found.
This registry may be used to disable the updating a SAMPro Work Order's status based on IVR Check-In and Check-Out messages received from ServiceChannel.
Id: sys-fmms-vendor-ServiceChannel
Setting Key: PostIncomingStatusUpdates Setting Value: No (default is Yes)
Any value beginning with 'Y', 'y', 'T', or 't' is equivalent to 'Yes' and any other value is equivalent to 'No'. The absence of the Registry entry is equivalent to a 'Yes' value. So there will be no change in functionality if the Registry entry is not found.
ServiceChannel provides an IVR facility that allows techs to phone into them with a change to a Workorder's status. This change is then forwarded to SAMPro for posting to the SAMPro Workorder. Sometimes it becomes necessary (for ServiceChannel internal reasons) for a tech to make such a IVR entry for a Workorder that has a 'finished' status (e.g. 'billed') within SAMPro. In this release, we prohibit SAMPro from updating a Workorder's status in response to such an inbound IVR status change message for ‘Cancelled’ and ‘Billed’ Work Orders. Note that the Work Order’s current status is derived from the wrkordrlgtype_id on the first line of the Workorder’s Technicians tab.
This functionality may adjusted via registry.
Id: sys-fmms-vendor-ServiceChannel
Setting Key: StatusUpdateIsProhibitedForStatusCodes Setting Value: listofstatuscodes
The Setting Value is a list of status codes separated commas. The codes ‘Cancelled’ and ‘Billed’ are always automatically added to the list. If no entry is found, the list will consist solely of these two entries.
When SAMPro detects certain Status changes to a Work Order, it sends ServiceChannel a CALL XML message that includes TR_NUM and the new ServiceChannel STATUS code. When entering certain Status values, ServiceChannel would like us to include a CHECK element within the CALL XML. The CHECK element includes a TYPE code which corresponds to the new Status Code.
Registry Id: sys-FMMS-Vendor-ServiceChannel
Setting Key: CheckTypeForServiceChannelStatus
Setting Value: ServiceChannelStatusCode:CorrespondingCHECKTypeCode
1. There may be multiple Registry lines with the ‘CheckTypeForServiceChannelStatus’ key.
2. Each line may consist of multiple mappings with individual mappings separated by a ‘,’ character.
3. The Valid CHECK Type Codes are: IN, OUT, DISP, and CLOSE
Example:
Setting Key: CheckTypeForServiceChannelStatus
Setting Value: ON_SITE:IN, COMPLETED:OUT
4. If a mapping is not found (or evaluates to ‘N/A’), no CHECK element will be included in the CALL XML.
5. There being several ServiceChannel Status Codes beginning with ‘COMPLETED’ , a special ‘short cut’ is available for those Status Codes: If no mapping is found (or if an ‘N/A’ mapping is found) for a Status Code and the Status Code begins with ‘COMPLETED’, SAMPro will try to identify and use a mapping for the ‘COMPLETED’ status code.
Check elements include an ‘ID’ attribute that ServiceChannel uses to internally sequence Check Ins and Check Outs. The restrictions are:
1. Each Check In process should be identified by an ID attribute value greater in value than that used in any prior Check In processes.
2. Each Check Out process should be identified by an ID attribute that matches that used in the corresponding Check In process.
In order to implement this sequencing, SAMPro must somewhere retain the appropriate Check Sequencing information. This has been implemented as follows:
1. Sequencing information will be retained on one of the Work Order’s User Fields.
2. The User Field to be used will be identified in the following registry entry by the line having the key ‘. The value of this key should be a number between 1 and 5 inclusive.
Registry Id: sys-FMMS-Vendor-ServiceChannel
Setting Key: WOUserFieldNumberForCheckInCheckOut
Setting Value: a number between 1 and 5 inclusive.
3. The chosen User Field in the Work Order should be customized to ‘SC In/Out Count:’.
4. If no ‘WOUserFieldNumberForCheckInCheckOut’ key is found, the value of the next RN will be used for the ID attribute. This will not result in proper sequencing.
5. The format of the In/Out Count field will be of the form ‘inCount/OutCount’.
Example: ‘2/1’ meaning there have been 2 CHECK INs but only 1 CHECK Out.
6. A blank value of the in/Out Count Field will be treated as ’0/0’ so there is no need to initialize this field.
7. Whenever SAMPro sends a CHECK IN, it will increment the Work Order’s inCount; whenever SAMPro sends a CHECK OUT, it will increment the Work Order’s outCount.
8. Whenever SAMPro sends either a CHECK IN or a CHECK OUT, it will use the value of the Work Order’s inCount for the ID value, ignoring the outCount. Thus a CHECK IN can have multiple CHECK OUTs. Note that because of this, the outCount is actually irrelevant in this processing and is maintained only for informational purposes.
Caution:
This feature should only be used for customers not using ServiceChannel’s IVR check-in/check-out system. It is not clear at this time what will happen if, for example, a Check-Out is sent to ServiceChannel as a response to SAMPro processing a Check-Out message sent by ServiceChannel itself.
When New Call creates a new Workorder based on a Service Request from ServiceChannel (via the Weblog), it must send ServiceChannel a message that the Service Request has been accepted. This message includes a Scheduled Date and a Scheduled Time.
Normally the Scheduled Date and Scheduled Time are derived from the Workorder being created. The following registry may be implemented to derive the Scheduled Date and Scheduled Time are from data in the original Service Request that was sent by ServiceChannel.
Id: sys-fmms-vendor-servicechannel
Setting Key: SchedDateTimeSourceWhenAcceptingWO
Setting Value: ServiceRequest or WorkOrder (default)
If the key is missing or the value is other than 'ServiceRequest' (case insensitive), a value of 'WorkOrder' will be assumed.
If the Setting Value is 'ServiceRequest', then the Scheduled Date and Scheduled Time will be taken from the original Service Request issued by ServiceChannel. If the value is 'WorkOrder', the Scheduled Date and Scheduled Time will be taken from the Workorder being created.
This release adds the flexibility to map SAMPro log status’ to Service Channel log status’ based on registry set values keyed by Client Id (derived from the Job in the WO header).
Normally, SAMPro Workorder status codes are mapped to ServiceChannel status codes via the ‘StatusMappings’ lines found in the SAMPro ServiceChannel Registry entry; they will be used for all Service Channel Clients. However, various ServiceChannel clients may have differing status code mappings. This release extends the SAMPro Registry to allow multiple status mapping sets based on the Workorder's Client Id (derived from the Job in the WO header).
To create a set of Status Mappings in the SAMPro sys-fmms-vendor-ServiceChannel Registry for a specific Client, append a '-' and the Client Id to the 'StatusMappings' key.
Example:
Id: sys-fmms-vendor-ServiceChannel
Setting Key: StatusMappings-Wendys
Setting Value: Acknowledged:DISPATCH CONFIRMED
Tip:
Make sure that a StatusMappings option without the Client Id appended is retained for general use.
An earlier release supported the sending of 'Equipment Work Performed' notes to ServiceChannel on Work Order Status changes. This could be an issue because TechAnywhere may not upload the equipment information to SAMPro for some minutes after the Status Change is uploaded.
This release supports a Registry-specified delay between the posting of the Status change and the sending of the Equipment Work Performed notes. The assumption is that by providing a sufficient delay, TechAnywhere will have uploaded the required Equipment information before the delay expires.
Id: sys-fmms-vendor-ServiceChannel
Setting Key: EquipmentWorkPerformedDelaySeconds Setting Value: delay in seconds
Example: The following will delay the sending of the Equipment Work Performed message for 30 minutes following the status change. The default delay is zero seconds.
Setting Key: EquipmentWorkPerformedDelaySeconds Setting Value: 1800
This release supports a registry to enable enhanced processing to support sales tax for Canadian Service Channel invoicing. The GST will be reported in the 'invoiceTax' column while other taxes are to be reported in the 'tax2' and 'tax2Name' columns. The Sales Tax Authority's 'Tax Code From State' field is used to identify the appropriate tax category to be reported for an invoiced tax amount. This should contain one of the following values: 'GST', 'PST', 'HST', or 'QST'.
The following Service Channel Registry entry is required to turn on Canadian Tax reporting
Id: sys-fmms-vendor-ServiceChannel
Setting Key: InvoiceIsCanadian Setting Value: yes (or begins with 'y', 'Y', 't', 'or T')
Note that the Tax Authority Tax Code From State field has been relaxed to allow values that are longer than 2 characters.
Previously, when a Service Request generated a Weblog in SAMPro the Client Site was not completed. This release has been enhanced to try to identify the proper Site and, if found, use it in the Weblog.
The Work Order's NTE is now set correctly when it is created from a ServiceChannel Service Request (Weblog) processed in New Call.
This release modifies the computation of DATETIME so that it can not be earlier than SCHED_DATETIME to conform with recent ServiceChannel validations.
New Button: ServiceChannel Upload
A new 'ServiceChannel Upload' button will appear on the Document Viewer's list and record screens if the Work Order is integrated with ServiceChannel. Pressing this button from the Document list will give a checklist of all attachments to allow the user to select multiple attachments to send at once. Pressing from the Document record will upload that single attachment. The attachment(s) will be emailed to ServiceChannel where they will be processed at a set interval and attached to the ServiceChannel system.
The COMPL_DATETIME will be sent to ServiceChannel for status change messages beginning with 'COMPLETED'. COMPL_DATETIME is derived from the scheduled date and time on the Work Order's Technicians tab.
When ServiceChannel work order are billed, the invoice is automatically uploaded to ServiceChannel. In previous releases, if the invoice was reversed and re-invoiced, the only way to handle this was to manually press the Submit button in the invoice master.
This release supports the automatic resending of the re-invoiced invoice. Specifically, when an Invoice Master is marked as 'Reversed', any FMMSInfo records meeting the following requirements are located:
The FMMSInfo record's wrkordr_rn field matches the reversed Invoice Master's srvceinvce_wrkordr_rn field.
The FMMSInfo record has it's fmmsinfo_invce_qd column set to "Y".
IF any such FMMSInfo records are found, their fmmsinfo_invce_qd column is reset to 'N'.
This release addresses a situation where ServiceChannel sends SAMPro a CHECK IN (or CHECK OUT) message in which the TR_NUM points to an FMMSInfo record for a Work Order different from that indicated by the CHECK message's WO_NUM value. In this release, if the CHECK message contains conflicting TR_NUM and WO_NUM values:
An entry will be made in the FMMS log file
But a Work Order will not be updated because since we do not know which one is correct
See Customer Note 20.1.13 for a registry to enable Canadian Sales Tax on invoices.
This release expands the support of optional detail lines on Service Channel Invoice I.14 to Other Labor lines.
The Service Channel i.14 invoice template requires that materials are used to complete the job; ServiceChannel will reject the invoice if it doesn't contain material information. Since all jobs do not require materials, this release will add a dummy $0 material line to get around this requirement. The Material Description of 'No Material Required' will be used on the $0 line to conform to ServiceChannel requirements.
ServiceChannel invoice spreadsheets generated by SAMPro can contain multiple invoices. In previous releases, contained a blank line separating the invoices. In this release, the blank line has been eliminated for both the i12 and i14 invoices.
This release corrects issues experienced by some Canadian users uploading invoices. The Invoice Date is now sent in US format even for Canadian users for the I12 and I14 ServiceChannel Invoice Formats.
KPI Definition Import (KPI Import button and Start KPI Definition function): Corrects a problem in recent releases where importing large object KPI's did not actually update the KPI definition column.
DBAnalytics Document Posting supports the UseSubdirectories option in sys-document-archive. This enhancement will alleviate performance issues caused by having too many files in the root archive folder.
Exporting / Importing a User's dashboard profiles now works correctly with List type Analytics.
A new Column, fnctn_prmry_tble, has been added to the Function Table to identify the Primary Table for each Viewer. This field was added to assist in the writing of KPI's and other reporting functions.
Certain Custom PM Workbench analytics depend on knowing which of a job's Cost Codes is designated as the 'Fee Code'. This analytic uses the following registry to determine which of the Cost Code User fields is being used (typically the User4 field).
Id: sys-viewer-vjbprgrss
Setting Key: LumpSumUsrFldNmbr Setting Value: 4 (1,2 or 3 are also permitted)
In this case, the Job Cost User User4 field should be set to Y if it is designated as the 'Fee Code' record or N if it is not.
This Analytic allows the Project Manager (PM) to participate in the billing preparation process without using SAMPro. An IIS web server is required for this Analytic.
PMs may review and 'approve' a Job for billing and then pass it on to the Billing Department in the back office for completion. The Billing Department then uses the Record Billing Adjustments function to finish the invoice preparation, printing and posting. This process is summarized in the following diagram.
Special database fields record the PM's initial approval and any adjustments that should be made Validation controls who may update a Job (the PM using the analytic or the back office billing department).
1. The analytic does not allow the PM to make ANY billing changes when the Job's Invoice Status has a value of "Ready" or "Printed". When the Job reaches this state, the PM should communicate any additional billing changes to back-office personnel who can make the appropriate adjustments. A message to that effect should be given to the PM once additional changes have been disabled.
2. If the Job passes the previous test, the new PM Next Invoice Status must be checked before allowing billing changes. If its value is set to "Imported", advise the PM with an appropriate warning message. A value of "Imported" means back-office personnel have already started processing the job's next invoice.
3. When the previous tests are passed, the PM can use the new analytic to its full potential. These changes will be made to the new Job Billing Item fields noted below.
4. Back-office processing in Record Billing Adjustments will not accept any values in the new Billing Item fields until the Job's PM Next Invoice Status has a value of "Submitted". That means the PM can make (and save) preliminary billing changes that don't go into effect until the PM indicates (via the analytic) that all changes have been made and the job is ready for invoicing. At that point, the analytic should set the value to "Submitted".
Several new fields have been added to the Job Billing Item which may be set by PM's in the new Billing Analytic. They will then be used by Record Billing Adjustments to pass values these values to the Job Billing Item fields used for progress invoicing in SAMPro.
|
New Field Set In Billing Analytic |
Writes to Existing Field in When Processed in SAMPro |
Notes |
|
pm_nxt_invc_ernd_prcnt |
jbbllngitm_cntrct_prcnt_ernd |
RBA |
|
pm_nxt_invce_amnt |
jbbllngitm_nxt_invce_tm |
GMP Jobs |
|
pm_nxt_invce_amnt |
jbbllngitm_nxt_invce_cntrct |
Non-GMP Fixed Fee |
New Field - PM Next Invoice Status
This display field is used in conjunction with certain Progress Billing Invoice / Project Manager Workbench DBAnalytics. This new field is used in conjunction with the Job's pre-existing Invoice Status field that already controls the back-office invoicing process.
This field has four potential values:
The default value is 'Unknown'. This is the value assigned to a new Job. When a Progress Billed Job is posted, the PM Next Invoice Status will be set back to Unknown so that it will be eligible for additional updates in the Billing Analytic.
'PM Review' indicates the PM has started making changes using the Billing Invoices analytic. In this state, the changes have not been submitted for use by the back office billing processes.
'Submitted' indicates the PM has finished preparing for the next invoice and the back office billing processes can begin. Setting the status to 'Submitted' can only be achieved by the PM using the Billing Invoices analytic. The Status will be changed to Submitted when PM indicates he/she is finished with all necessary. The PM is not allowed to make changes the Status has the value of either Submitted or Imported.
'Imported' indicates the back office processing has begun. Specifically, the PM's designated billing values have been imported into the Billing Items via the Record Billing Adjustments function. This takes the place of having back office personnel manually enter the PM's billing values.
Changed Field: Job Id
Validation now prevents Jobs with the PM Next Invoice Status set to 'PM Review' from being selected in Record Billing Adjustments. Jobs with the PM Next Invoice Statuses of 'Submitted', 'Unknown' and 'Imported' (if the Job's Invoice Status is correctly set) are allowed.
The Next PM Invoice Status will be changed from Submitted to Imported when the PM's designated billing values have been imported and the changes saved in Record Billing Adjustments.
New Field: PM Next Invoice Status
This display field is used in conjunction with certain Progress Billing Invoice / Project Manager Workbench DBAnalytics. This new field is used in conjunction with the Job's pre-existing Invoice Status field that already controls the back-office invoicing process.
Validation now prevents Jobs with the PM Next Invoice Status set to 'PM Review' from being selected in Record Billing Adjustments. Jobs with the PM Next Invoice Statuses of 'Submitted', 'Unknown' and 'Imported' (if the Job's Invoice Status is correctly set) are allowed. The Next PM Invoice Status will be changed from Submitted to Imported when the PM's designated billing values have been imported and the changes saved in Record Billing Adjustments.
When a Progress Billed Job is posted, the PM Next Invoice Status will be set back to Unknown so that it will be eligible for additional updates in the Billing Analytic.
SubAnywhere is a web-enabled module which allows your Subcontractors to
Accept or decline your work assignments
Review the Work Requested and other pertinent Work Order information
Update the Work Order's Status
Add negotiated charges to the Purchase Order associated with the Work Order
Set up records for their own Techs: a special mobile web version of SubAnywhere allows these Techs to access Work Order information and make status updates
Submit Quotes for additional work
Update and download documents (such as PDF's and photos)
SubAnywhere includes easy-to-understand Help available from each of its pages. In addition, you may contact your support rep or access the User Forum for a PowerPoint presentation on using and setting up SubAnywhere.
Your support representative will set up the basic framework of SubAnywhere, but the following records may need to be updated in SAMPro:
Technician Record:
Main Tab: Vendor Id is specified
Web Access Tab: Web Access = Subcontractor, Device = SubAnywhere
Vendor Record:
Defaults Tab: verify that the Rate Schedule Id is properly completed. SubAnywhere only allows the Other Rates on the selected Schedule to be entered.
Rate Schedules for Vendors:
Only the Other Rate column needs to be completed. The Other Rate Table defines which Other Rates your Subs will be allowed to choose in SubAnywhere from their drop-down charges list.
Other Rate Tables for Vendors:
If you have negotiated rates, the Rate column should be completed with the price the Sub will charge your company; SubAnywhere users will NOT be able override the price or description when they enter this charge. If the Rate column is empty, the SubAnywhere user can enter price and unique description.
Site Equipment:
Main Tab: An override to the Vendor’s Rate Schedules may be specified in the Equipment record's Service Provider / Rate Schedule field. For example, special higher negotiated rates might exist for equipment located in Manhattan. In this case, this override would be use to generate the Charges drop down list in SubAnywhere for this equipment.
Escalation Profiles:
Please discuss with your support rep.
Registry for Documents Uploads / Download
Scheduled Event for Document Upload / Download
Your support rep should set these up with consultation from your IT department.
A PowerPoint with additional detail is available.
SubAnywhere Document Posting supports the UseSubdirectories option in sys-document-archive. This enhancement will alleviate performance issues caused by having too many files in the root archive folder.
Remote Device Type
New Option: SubAnywhere
If SubAnywhere IS enabled, set the Remote Device Type to SubAnywhere. This field controls whether PO’s are created as Released (None) or Unreleased (SubAnywhere). If a particular subcontractor should not have access to SubAnywhere, set the Remote Device Type to None. The Web Access field should be set to Subcontractor if you want to auto-generate PO’s for them when a Work Order is created in New Call or Create PM WorkOrders; this is true whether or not SubAnywhere is enabled.
When a Work Order is created for a SubAnywhere subcontractor tech in New Call or via Create PM Work Orders, the PO that is simultaneously created will be set to Unreleased to conform to SubAnywhere requirements. To be considered a SubAnywhere tech, the Technician record must: reference a Vendor record; have the Web Access field set to Subcontractor, and have the Remote Device Type set to the new option of SubAnywhere.
When SubAnywhere subcontractor is added to a Work Order, the PO that is generated for the sub (either automatically or by clicking the Create Sub PO button) will be set to Unreleased to conform to SubAnywhere requirements. To be considered a SubAnywhere tech, the Technician record must: reference a Vendor record; have the Web Access field set to Subcontractor, and have the Remote Device Type set to the new option of SubAnywhere.
When a PO is generated for a SubAnywhere Tech, the initial PO status is now set to Released if it will include GEN lines. This prevents SubAnywhere users from adding charges to PO's that already have a cost associated with it from the Equipment's PM Schedule's Contract Cost. The SubAnywhere PO will be set to Unreleased if it does not include a GEN line. The PO's Release Date will not be completed if the PO is Unreleased.
In earlier releases, the Status for a SubAnywhere PO was set to Unreleased regardless of whether or not it included GEN lines.
The Start NetFramework Post function provides a SubAnywhere Scheduled Event Manager for Document Uploads. Specifically, it handles messages for SAMNetFramework applications such as SubAnywhere. Currently, this function supports handling Document Uploads in a fashion similar to DashboardEventManager and Start Dashboard Post. This function should be implemented by adding the Start NetFramework Post to a scheduled event to be run at an interval of your choosing. The following registry is required.
Registry Id: sys-netframework
Setting Key: UploadFolder Setting Value: Absolute file path
The UploadFolder setting is the default location where files from SAMNetFramework applications (e.g., SubAnywhere) are uploaded. This setting can be overridden by the registry of specific SAMNetFramework applications (note: for Sntfrmewrkpst to properly retrieve the file from the overridden location, "Application" must be specified in Message record contents).
This tab will be updated from the new SubAnywhere module's Quotes tab.
Costing and other information (but not pricing) will be imported from this tab by the Quote Scope's Import Sub Quote wizard.
Quantity
The number of this item/charge being quoted.
Other Rate Id:
The Other Rate being quoted.
Tech Id:
The Subcontractor quoting this work
Unit Cost: Extended Cost:
The Cost of the item/item being quoted. This is the price the Subcontractor is charging for the work. These fields will be defaulted from SubAnywhere. Manual entries to this tab do not default the cost.
Unit Price: Extended Price:
These fields will be ignored by the Quote Scope's Import Sub Quote wizard; the markup rules defined in the Scope (Rate Schedule, Markup % or Gross Margin %) will be applied to the imported costs to determine the Scope's revenues.
Description: Other Rate Description:
The Description field must be completed in order for this line to be imported into a Quote Scope; this field will default from SubAnywhere. The display-only Other Rate Description appears for informational purposes.
Equipment Id:
This field must be completed in order for this line to be imported into a Quote Scope.
This functionality is available on the Quote Scope's Main tab and Quotemaster's Scope Tab.
New Button:
This functionality is designed for use with SubAnywhere. When clicked a wizard will be launched to import costing information from the SubQuote tab of the WO referenced in the Quote Manager/Master header. When the costs are imported, the markup rules defined in the Scope (Rate Schedule, Markup % or Gross Margin %) are applied to the imported costs to determine the Scope's revenues. This will be done even if Revenue has been entered on the Work Order's SubQuote tab.
Note: Wizard Requirements
If no lines from the WO SubQuote Tab match the Equip. Id on the Scope, a message stating “No Sub Quote lines found to import matching the Equipment Id on the Scope” will appear.
If the WO Id is not completed in the Quote Manager, the following message will be displayed: “No Sub Quote lines found to import matching the Work Order Id on the Quote”.
If more than a single AR Control GL Account exists in your database, will not be automatically filled in when Report COP Invoice is run. This registry allows the user to default in the correct AR Control GL Account for COP Invoices.
Id: sys-viewer-clntordr
Setting Key: ARControlAccount Setting Value: a valid AR Control GL Account Id
This release corrects an issue where the GL Entity was not defaulting properly from the Recurring Client Order when Start Release Recurring Client Orders was run, leaving users unable to process the resulting Client Order.
By default the GL Entity first pulls from the Location record (Client site second, and Inventory Group third). If intercompany is enabled, the GL Entity will always pull from the Location because the GL Entity is required in the Location record for intercompany databases.
Because of the above, Recurring Client Orders (and Start Release Recurring Client Orders) will now look to the following existing registry for defaulting the GL Entity:
Registry Id: sys-viewer-vclntordr
Setting Key: GLEntityScheme Setting Value: value
where value is replaced by one of the following:
clntste (the GL Entity will be taken from the Client Site referenced by the order; (this pulls the GL Entity into the child lines on the Inventory tab of COP Order & sets the parent COP tab’s GL Entity)
lctn (the COP order will pull the GL Entity from the Location ID and put this on the Main parent tab of the COP Order AND create each Inventory line with the GL Entity from the Location record. It will ignore the info setup on the Client Sites COP tab.
invntrygrp (the GL Entity will be taken from the Inventory Group referenced by the Inventory Item on the order line. This setting ONLY changes/impacts the GL Entity of Inventory lines on the COP order (does not alter any info on the main Parent tab).
*Note - The GL Entity on the expanded child view of the Recurring Client Order will remain blank, but the Client Order generated from the starter function will properly pull the GL Entity from the parent of the Recurring Client Order.
The hard-coded footer text (including quote stated in US $, 30 day valid, and quoted by Customer Service Manager) has been removed from the standard COP Quotation report. The following registry (see Customer Note 23.1.3) or a bitmap/jpg may be used to provide footer information as needed.
Registry Id: sys-report-rordrqttn
Setting Key: ReplacementFooter Setting Value: true
Setting Key: line1 Setting Value: Text for line 1 of footer
Setting Key: line2 Setting Value: Text for line 2 of footer
Setting Key: line3 Setting Value: Text fo line 3 of footer
This release corrects a spurious Runtime error that appeared when launching Report COP Invoice in a database which contained only a single AR Control GL Account,
The Invoice Master's Branch is set from the Client Order's Branch when the COP Invoice is generated.
The hard-coded footer text (including quote stated in US $, 30 day valid, and quoted by Customer Service Manager) has been removed from the standard COP Quotation report. See Customer Note 23.1.3 for a registry to specify customer footer text.
When using Intercompany processing, the GL Entity and Company are now defaulted when the Print Invoice button is pressed from View Client Order.
In order to support Intercompany Processing, Client Orders & COP Invoices now post with the proper Security and Company Security information. This ensures that the COP Orders carry the correct security/company information when the COP Invoices are posted to the AR Sales Journal and carried over into the various history tables (arhstry, glhstry, txhstry, imhstry, invcemstr, etc). In addition, the Start Fill Backorders function now works properly for Client Orders generated in this release when InterCompany is enabled.
If the COP module is set up to default the information from the Client Site’s COP tab instead of the Location (where sys-viewer-vclntordr GLEntityScheme=clntste registry option exists), the system will now use the Client Site’s COP tab's GL Entity for posting the invoices Freight, Dropship Freight and make sure that the COGS posting for dropships uses the same GL Entity for both the debit & credit side of the AR Sales GL journal entry.
Changed Fields - Asset User Fields 1-5:
These fields can be used to set Equipment Fields when creating new equipment via the Create New Equipment button on the Location tab.
The following keys can be entered on any of the Asset User fields pass valid Id's to the corresponding Equipment fields.
Tech=a valid Technician Id
Cert=a valid Certification Id
Script=a valid Call Script Id
Profile=a valid Escalation Profile Id
Metric=a valid Log Form Id
Category=a valid Service Category Id
Important Note:
Do not include a space between the key and the Id. For example, to set the Service Category to HVAC:
Correct: Category=HVAC Incorrect: Category = HVAC
Multiple key/id pairs, separated by commas, can be entered on a single Asset User line.
Tip: Use Custom Fields to Set User Asset Fields
The Custom Fields functionality allows the user to select from a list of appropriate key/id combinations.
DBSellPoint is a point of sales app developed to handle over the counter and retail sales transactions for SAMPro. Payments can be made with cash or credit card, or on account for existing customers. The app is designed to be run on an Android tablet with a credit card scanner, barcode scanner, and a cash drawer,
Returns of DBSellPoint sales are also supported in the app. A PowerPoint presentation focusing using the app itself is available.
This function posts messages (transactions entered in the DBSellPoint app) to the SAMPro database. It is responsible for generating the needed AR Sales Journal, Invoice Master, Inventory History, Job History and Cash Receipts in SAMPro. It handles both DBSellPoint Sales and Returns.
This function will be configured to run automatically by support when it is installed.
GL Entities are derived as follows:
ENTB = Balance Sheet Entity (from Company)
ENTI = Income Statement Entity (from Site COP tab)
Posting of POS sales should use the Entity defined above as follows in posting:
1) Cash Receipts Records
a. GL Entity – use Company ENTB – arrcpts.glentty.rn
2) AR Sales Records
a.AR Control Entity – use Company ENTB – arsls.glentty.rn
b. Entities for GL Posting
i.All Sales Lines, Entity = Site COP ENTI
ii.All Expense (cost) Lines, Entity = Site COP ENTI
iii.Accounts Receivable, Entity = Company ENTB
iv.All Sales Tax Lines, Entity = Company ENTB
v.All Inventory, Entity = Company ENTB
A default customer (Client Site) must be set up for walk up cash/credit customers where the sale will not be for 'on account' or cash sales to an existing customer. The RAQ configDefaultCustomer (site RN) defines the default customer (site) that comes up on POS initial screen. This record will be configured by support when your system is set up.
When an AR Cash Receipts entry is posted from DBSellpoint, the GL Bank Account will default from the Payment Type selected on the POS screen.
When Invoices are posted from DBSellpoint, the Invoice's Due Date, Discount Date, Discount Available are now set based on its AR Terms.
NOTE: If a dollar limit for cash reimbursements is exceeded, a return will require submitting paperwork to accounting and a check gets cut to the customer at some future date. In that scenario, SAMPro provides no automated help in managing the debt or producing the payment. Accounting must create a Vendor record and the appropriate AP Journal entry so the customer eventually gets paid/reimbursed as a 'vendor'.
Returns are defined by messages including the key 'Return=true'? If the customer is reimbursed (cash, credit card credit, etc), the DBSellpoint app will also provide that information so the appropriate negative Cash Receipt can be generated.
The posting depends on whether or not the customer was reimbursed at the POS counter.
If the customer is reimbursed:
The return is treated as a Credit Memo and posts the appropriate Sales and Cash Receipts transactions.
In the Sales Journal, the Invoice Id will be generated by appending the letters CM will to the original POS Invoice Id (e.g.,143234CM). The Transaction Description will be set to 'POS Return Entry'.
The Cash Receipts entry will be made with negative receipts and a Transaction Description will be set to 'POS Return Entry'.
If not reimbursed:
Only a Sales Journal entry will be made using the Costs tab of the Sales Journal to effectively put the Return 'On Account' for the customer. The Client specified in the Sales Journal will be derived from the Client listed on the Site's COP tab.
A Restocking Fee may be assessed in the DBSellpoint return which will reduce the amount of the return. The RestockGLAccount registry detailed in Customer Note 25.4.3 may be used to specify the GL Account restocking fees will post to. If this registry is absent the Sales GL Account will be used.
If the registry is not set, the return amount for each line will be the original sales less the restocking fee. If the registry is enabled then the difference on each line between the original sales and return amount will be posted to the Restock Account.
The Sales Tax Group on the default Client Site's COP tab is the one for the brick and mortar DBSellpoint location the DBSellpoint User is stationed at. This Sales Tax Group will be used for ALL DBSellpoint transactions. The default Site must be specified in the User's Registry tab for each DBSellpoint User.
Key: defaultSite Value: Site Id
Registry Id: sys-start-spntofsleevntmngr
Setting Key: DefaultLocation Setting Value: LocationId
The DefaultLocation is used to set the location for Sales Journal Expense Lines. If this registry is not specified the location 'Main' is Used.
Setting Key: emailpostlogsfrom Setting Value: validemail
This registry defines the 'from' address for DBSellpoint posting logs. It must be a valid email address for the firm running DBSellpoint.
Setting Key: emailpostlogsto Setting Value: validemail
This registry specifies the address receiving the posting logs; typically a support rep or IT administrator.
Registry Id: sys-point
Setting Key: ARControlAccount Setting Value: GLAccountId
This required setting defines the AR Control Account to be used when AR Sales Journal entries are generated.
Setting Key: CollateralDirectory Setting Value: path to uploaded POS collateral files
The CollateralDirectory is required. It identifies the location where uploaded files can be found.
Setting Key: DiscountGLAccount Setting Value: GLAccountId
This registry specifies the GL Account for sales discounts on sales posting. If this registry is absent the Sales GL will be used.
Setting Key: RestockGLAccount Setting Value: GLAccountId
This registry specifies the GL Account for restocking charges on returns posting; if this registry is absent the Sales GL will be used.
AP Journal: Corrects a spurious “Warning: This vendor invoice exists in AP Journal” message which could prevent some AP Journal entries from being edited.
Service Invoice: See Customer Release Note 9.2.I for a revised Service Invoice that supports a Registry to print the Amount Due in red at the top of the first page.
Scheduled Event Manager: This release eliminates unnecessary updates to Scheduled Event's Record Change Logs. Also streamlines Token Replacement code in the SEM to prevent excess memory usage.
XmlToPdf.jar Files:
Java 8-11: See Customer Note 1.6.4 for details on the new XmlToPdf[2019-01-16] Java8-11].jar file which supports Java 8-11, Monthly Folders and a Registry to Retain Sent Files, and correct issues with setting password protection. This file must be renamed as XmlToPdf.jar in order for it to be used. It does not support Java 7.
Java 7-8: Installations with some Java 7 users should rename the XmlToPdf[2017-12-27].jar XmlToPdf.jar in order for it to be used. This file supports the revised W-2 reporting format. It also corrects a file 'cannot find this file' error with UseOutlook enabled for Outlook 2013 and below.
AP Check:
The check total amount has been added to the lower right-hand position of live check and EFT stubs.
See Customer Note 3.1.6a for a registry to control the MICR font used in MICR printed AP checks.
AP Date To Pay / AP Checks: This release prevents users from printing AP Checks that are currently being updated by the AP Date to Pay function, preventing possible double-payment of the Vendor Invoice.
AP Journal:
This release corrects an issue where the Equipment Id was not defaulted. This only occurred if a PO was not specified on the AP entry but a Work Order Id was completed on the General tab.
When Intercompany is enabled and a detail line contains a Job Id, any changes to the line's GL Entity are validated to ensure that the new GL Entity belongs to the same company as the Job.
See Customer Note 3.1.8c for a Registry to Retain the initial Date and Period when a PO is specified.
This release corrects incorrect validation that allowed you to create an AP Journal Entry towards a Cancelled Credit PO. Note that PO's are Cancelled if the status is 'Cancelled' on the Status tab.
Changed Field: Invoice #: By default, the system now prevents the same Vendor Invoice from being vouchered multiple times; previously a registry was required for this validation.
Client Collection Notes List: In previous releases, the user was unable to access obsoleted Collection notes. In this release, the Collection Notes List displays these notes so they can be accessed if needed.
Client Collections All/Open Invoices List: The new Customer PO column references the customer's purchase order associated with the invoice. This list can be used to view paid invoices; see Customer Note 2.5.5.
AR Cash Receipts Journal: The Currency ID contained in the Client record is now written to the Invoice Master for Unapplied Deposits.
COP Invoicing: When using Intercompany processing, the GL Entity and Company are now defaulted when the Print Invoice button is pressed from View Client Order. The Invoice Master's Branch is set from the Client Order's Branch when the COP Invoice is generated.
COP Quotation: The hard-coded footer text has been removed from the standard COP Quotation report. A registry (see Customer Note 23.1.3) or bitmap may be used to provide footer information as needed.
Electronic Payments: SAMPro now supports Electronic Payments. See Customer Note 6.7 for details.
KPI Definition Import (KPI Import button and Start KPI Definition function): Corrects a problem in recent releases where importing large object KPI's did not actually update the KPI definition column.
GL Report Writer: GL Reports (.grpt) now omit printing lines for Obsolete GL Accounts when the line has no non-zero columns. This is regardless of the IncludeZeroLines registry entry.
Inventory Adjustments Journal:
This release corrects the validation so that Serial Numbers can be added from an Adjustment for Intercompany databases. See Customer Note 5.10.1 for details.
When Intercompany is enabled, changes to a To or From line's GL Entity are validated to ensure that the new GL Entity belongs to the same Company as the Job or Location on that same line.
Stock Status Report: See Customer Note 5.3.1 for an enhancement allowing certain locations with 0 on hand to appear on the report (e.g, 0 on hand but 2 on order for stock).
Inventory Item
Location Tab: Obsolete Locations are now displayed at the bottom of the Inventory Item Location tab. The Obsolete flag has been added as a column on the far right of the tab.
BOM Tab: The CVS file generated by the BOM-CVS button now specifies the column heading for the Master Item as "MasterDescription" to avoid conflict with the Component Inventory Item "Description".
Consolidated Invoice: Clicking the Auto Fill button now correctly displays the AR Inv Amt in the ARInvoices list.
Avalara Web Service:
See Customer Note 6.6.3c for an option (highly recommended) to disable calls to Avalara in situations where Use Tax is being calculated.
See Customer Note 6.6.3d for registries to configure or disable Avalara Web Service by Company.
See Customer Note 6.6.7 for recent validations and error handling changes.
See Customer Note 6.6.3e for a registry to Implement Job Specific Avalara Exempt Codes.
Invoice Master: See Customer Release Note 9.15 for a menu option to clear the 'Unknown' Status condition.
Record Billing Adjustments:
See Customer Note 9.1.4a for a registry to deny the selection of Ready to Post. It is strongly recommended to prevent users from posting an invoice without having produced a printed copy.
Validation has been extended to warn the user if Exempt (as well as Sales or Use Tax) Jobs have not had their Sales Tax computed when the invoice is set / saved as Ready to Print.
Service Invoice: When Service Compute is run, an entry to the WO's Log Tab will be made: set the Status to Billed, the Date Logged and Work Date to today's date, and the User Id to person running the Compute.
Job Change Request: Corrects a display issue if the caret is on the CO Amount or Expected Cost field when the record is saved.
Job
Find Data Filter: A new range, PO#, has been added to allow the user to filter on the customer's PO# on the Job's Main tab. In addition, the PO# has been added as a column to the JobByClientIdByJobId list view.
Main Tab New Display - Only Field - Client Site Info: These new display fields list the Client Site's Name and Work/Ship Address. A new v.cus file may be needed to see these fields.
JC Summary Tab: This release corrects a rounding error in computing a negative gross margin.
Small Jobs: See Customer Note 8.1.9 for a registry to use the Job Date Completed instead of the Date Closed as a trigger in Job EOM for Small Jobs.
PM Workbench: This release expands percentage columns to max out at 999999.9 on the Progress tab. This corrects the handling of lines having a %Used value exceeding 9999.9 so that the Totals display incorrectly.
Report PR Export: Corrects a problem with the sys-pr-export option format ADPKaback.
Garnishments: Disposable pay garnishment calculations for US and Canadian Payroll are now based on the settings of the new Disposable Income fields in the Deductions record. See Customer Note 12.15.1 for details.
Labor Journal: When Intercompany is enabled and a detail line contains a Job Id, any changes to the line's GL Entity are validated to ensure that the new GL Entity belongs to the same company as the Job.
Payroll Checks: See Customer Note 12.1.1b for a registry to specify the MICR font used in MICR printed checks.
Recently Revised Payroll Reports: See Customer Note 12.2.18 for an extensive list of revised reports.
PR Miscellaneous Deduction Checks:
See Customer Note 12.1.2c for a registry to specify the MICR font used in MICR printed checks.
This release corrects an issue on checks grouped by Vendor; the total is now correctly printed according to the detail lines on check.
Union Payroll: This release no longer accrues the Union Fringes for Pay Types checked Union Exempt.
Void Payroll Check: When Payroll checks are voided the system now eliminates the document attachment (if one exists) to the Employee record. The attachment to the Check record is retained.
W2s:
The release modifies the logic to skip print of Local Line 2 in Copy 2 of W2 (registry enabled - Customer Note 12.2.10b) so that line 1 taxes are displayed correctly.
See Customer Note 12.2.10c for a registry to Process 'Other' Tax Tables as 'Local' in Report PR W2s / Report PR W2s (Standard).
Report PR W-2s and Report PR W-2s (Standard): The 4-up options of BC2, 1x4 & Dx4 have been removed. These options were previously deprecated due to alignment issues.
Purchase Order:
Inventory and General Tabs: The new Billable Quantity field appears on the Magnify view of these tabs; it defaults from the Job Quantity Ordered. These fields support the scenario where a TechAnywhere tech changes the Billable Quantity of an item so that it will be correctly imported into the Work Order.
Subcontractor Tab: Changing the Job Cost Category Id now defaults the correct GL Account (from the Cost Category's GL Expense Account) into the line. Previously, the GL Account was only set from the Cost Category when it was first selected.
Start Close Open POs: This release corrects a problem where this function did not always apply Security to the history reversals lines generated by this function.
TechAnywhere PO's: By default, TechAnywhere PO's are now handled like standard SAMPro PO's: See Customer Note 4.1.3 and 4.1.3a for details.
Report Quote Form: The revised Report Quoted Form (RQTEFRMv90b035.rpt) dated 2018-10-11 reprints the Scope heading (Option #1 (Continued)) when the Scope spans multiple pages.
Quote Scope Viewer: On the Subcontractor Tab, the PO and Vendor Id will default from the source Work Order's PO Id when the user enters the Quantity and then tabs out of the field.
Approval Wizard:
See Customer Note 14.1.4 for a Registry To Write the Source WO's User Fields to New Work Order when the Approval Wizard is run.
See Customer Note 14.1.5 for the registries to Update Only the Work Order Equipment Work Requested, not the Work Performed, when the Approval Wizard is run.
Start Material Requisitioning: If Intercompany is enabled, the system nows check for company security level registry settings; an error will display if these registries (sys-viewer-vshpordr-securityid) are not found.
Start Release Work Orders: Changes have been made to support Subcontractor PO's; see Customer Note 18.4.
Fill BackOrders: Obsolete Locations and Inventory Items are now excluded from Start Backorder Filling by default. See Customer Note 18.1.2 for registry to include Obsolete Items and Locations as in previous versions.
In this release, SQL Updates to records are ignored when reports are being executed as scheduled reports. This corrects a record locking issue related to TechAnywhere quoting but impacts all reports run as scheduled events.
Master Contract Equipment Tab: Users may now edit the Under Contract status of Equipment records without the list being resorted. This makes it easier to work with very large contracts.
New Call:
See Customer Note 16.1.1b for a registry to prevent a Work Order from being created to a Closed Job.
A new registry option causes the system to clear the default technician specified in the Site or Equipment record. See Customer Note 16.1.1c.
See Customer Note 16.1.1d for a registry to disable writing to the New Call status pane when the mouse is moved. This has demonstrated some small improvement in New Call performance.
This release corrects an issue when the Market Source was not always written to the Work Order. It also corrects a sporadic problem where the WO Email was not defaulted from the Client Site.
Start Daily Work Order Edit: This release corrects a sporadic Runtime error: RnFetchErrorForKeyName.
Start Create PM Work Order:
See Customer Note 16.1.4b for a registry to include Client Site WO Other Tab Lines on PM Work Orders.
New field - Override ALL Techs? If this box is checked the Technician Id selected will be assigned to ALL PM's, not just those that would otherwise be unassigned. See Customer Note 16.13.1.
Start Renew Service Contracts Checklist: The Description column has been enhanced to better define what type of renewal is being run. See Customer Note 16.15.1 for details.
Work Order:
Intercompany: When Intercompany is enabled and a detail line contains a Job Id, any changes to the line's GL Entity are validated to ensure that the new GL Entity belongs to the same company as the Job.
Gross Margin Tab: This release provides a performance enhancement when opening Work Orders when the sys-viewer-vwrkordr registry's option GrossMarginFromJobHistory is enabled.
Ranges: Job Type has been added as a filter option to the Find Data range screen. This lets users to filter Work Orders by the Type of Job in the Work Order header.
Invoice I.14: This release expands the support of optional detail lines on Service Channel Invoice I.14 to Other Labor lines.
Canadian Invoicing Sales Tax: This release supports a registry to enable enhanced processing to support sales tax for Canadian Service Channel invoicing. See Customer Note 20.1.13.
Documents: Multi-file Document records allow the user to view the files combined into a single PDF, generating a UserId_ViewDocument.pdf in SAMPro's base directory. This file is now deleted when the user logs.
Emailing: This release corrects an issue where using the CopyAll registry setting in sys-email resulted in a duplicate email if the email came from escalation event.
Lists: Corrects the spurious display of the Cut, Paste and Customize menu when right-click filtering on a list.
Error.log Maintenance: If the error.log exceeds the maximum size of 1 gigabyte, it will be renamed and a new error.log started. See Customer Note 1.1.5 for a registry to control the maximum size for archiving the Error Log.
Printing: This release corrects a very sporadic Runtime error: The parameter is incorrect. (OS error 16r57) experienced by some remote users.
Reprinting Reports: This release refines the functionality used to reprint a DBR report where the server with the original bitmaps was changed (a problem if mapped drivers were NOT specified). See Customer Note 1.3.5.
Quick Attach:
Performance enhancement that is especially noticeable if the save path directory has many files.
Quick Attach documents may now be attached to 'locked' journal entries (both the Add and Save button disabled). These documents are attached immediately when the record is NOT in Add mode.
Viewers:
Corrects the caret position when typing wraps around to next line in a text box.
This release improves the Warning message that displays when you leave a record that has changes that have not yet been saved.
TechAnywhere PO's: In this version, COD and (and other PO charges) are successfully handled since the Billable Quantity and Price updates are posted to the Purchase Order so the standard posting method is now the default. See Customer Note 4.1.3 for details. Also see Customer Note 4.1.3a for a recommended registry setting to control changes to TechAnywhere PO's that were generated in the field.
Work Order User Fields: This SAMPro release allows specified Work Order User fields to be viewed / modified by TechAnywhere. This functionality must be enabled via the appropriate TechAnywhere configurations. Specific User fields may be configured as read-only. Contact your TechAnywhere support rep for details.
Message Viewer: This release corrects 'Import Message' and 'Export Message' button issues that resulted in the dropping and corrupting of some TimeAnywhere messages.
Import Sales Tax (Avalara): See Customer Note 6.5 for enhancements that have been made to manage tax anomalies within the Avalara data, and to alert the user to manual changes that may be required.
Work Order Inventory Tab: This release corrects an issue which prevented PM Work Order Inventory Extras from being billed.
Start Renew Service Contract Checklist: This release corrects a recent issue where manual changes to the New Value field in Checklist were ignored; see Customer Note 16.15.1.
View GL History: The Posted By/Date Posted have been added to the GL History List views.
Start Create Job Scheduler Work Orders: Work Orders created through this function use the Escalation Profile that is assigned to the piece of equipment. This release corrects an issue in 9.1 where the appropriate Scheduled Events were not created for Work Orders generated by this function.
AP Journal:
The AP Journal posting logic has been corrected to reverse the sign on JCH Committed Cost $ when posting a PO-SUB line for a Credit Memo.
Intercompany: If Intercompany is enabled, the balance sheet GL Entity is not 'sticky'. Customer Note 1.14 details the new registries for setting the Default Balance Sheet Entity for this journal or globally.
AP Date-to-Pay List: This release implements special handling for 'over paid' invoices so that the overpayment is NOT erroneously defaulted to the Discount and Retainage fields.
Start Void AP Check: The new field 'Check Description' field may be edited to note the reason for the void.
Vendor List View: A new Sort Order, VendorByNameByAccountNumber has been added. The list displays the Vendor Name and Id, City, State, Address and Account Number (from the Vendor Default tab).
Vendor Range View: The Vendor's Account Number has been added as a Range field.
Vendor Record: Customer Note 3.1.9 details a registry to implement Vendor Id Auto-sequencing.
AR Sales - Intercompany: If Intercompany is enabled, the balance sheet GL Entity is not 'sticky'. Customer Note 1.14 details new registries for setting the Default Balance Sheet Entity for manual entries in this journal.
AR Cash Receipts - Intercompany: If Intercompany is enabled, the balance sheet GL Entity is not 'sticky'. Customer Note 1.14 details new registries for setting the Default Balance Sheet Entity.
Client Collections: This release corrects a display error in the High Balance Date field on the Client Collections screen. Previously, the most current invoice date always appeared in the High Balance Date field.
Avalara Web Services: Corrects a problem encountered when the Server name includes a backslash.
Bank Deposit, Bank Transfer and Bank Reconciliation - Intercompany: If Intercompany is enabled, the balance sheet GL Entity is not 'sticky'. Customer Note 1.14 details new registries for setting the Default Balance Sheet Entity for entries in these journals.
Start Release Recurring Client Orders: See Customer Note 23.1.2 for a registry to set the GL Entity.
COP Invoice Processing: This release implements the following validations when intercompany is enabled: the GL Entity is a required field AND the selected GL Entity must belong to the selected Company.
DBAnalytics Document Posting supports the UseSubdirectories option in sys-document-archive. This enhancement alleviates performance issues caused by having too many files in the root archive folder.
Bank Deposit Journal: The "Total Deposit" column has been added to the Bank Deposit List views.
Job EOM Processing: Change Requests (CORs) will be processed if the Dates Approved & Declined = 1900-01-01 and the CO Amount & % Likelihood <> 0. They are treated as Fixed Fee with the CO Amount adjusted by % Likelihood.
Job Viewer Registry: This release fully supports the childtabs registry option to customize child tab names and order. See Customer Note 11.1.2a.
Job Billing Change Request: Previously the CO Amount: and Expected Cost: fields were display-only based on the Change Request's Budget Tab. These fields may now be manually updated if no Budget Tab lines are present. If Budget lines are added they will overwrite the manually entered CO Amount and Expected Cost values when the record is save. It may be necessary to refresh the record after the save to see the change.
Job Cost Codes / WBS Import: See Customer Release Note 7.2.6 for the Registry to Set Job Cost Code's Entity from the Discipline Id During WBS Import
Default Balance Sheet GL Entity: If Intercompany is enabled, the balance sheet GL Entity is not defaulted (via 'sticky' behavior). The registries discussed in Customer Note 1.14 implement setting the Default Balance Sheet Entity globally for the supported journals as well as journal-specific override/exception registry keys.
Inventory Adjustment Journal: Corrects a problem where the tax cost (on Use Tax jobs) was sticking when using the copy/insert line button and was not properly updated when the line was edited.
Quote Manager / Scope: All Notes attached to the Quote Manager and each of its associated Scopes will be available from the Quote Manager AND it's Quote Scope viewers.
Quote Manager Approval Wizard: Corrects a problem where the Labor Revenue written to the Work Order was defaulted from the Labor Rate instead of the Labor Price defined/adjusted in the Quote Scope.
Return Authorization: This viewer now supports Intercompany Security; the Company's Security is correctly written to inventory history.
Start Service Billing Compute: See Customer Note 9.1.3a for a registry to clear the Billing Agent User Id in the Service Invoice's report range screen.
Record Billing Adjustments: Validation has been added to warn the user if Sales or Use Tax has not been computed when the invoice is saved as Ready to Print; see Customer Note 9.8.1 for details.
Start Void PR Check: The new field 'Check Description' defaults from the Check record. It may be edited to note the reason for the void. If the field is blank when the Check is voided, the system will continue to default in the Description using the following format: Voided 07/09/2018 01:36:39 PM UserId.
Portrait Format Purchase Order: See Customer Note 4.2.1a for a registry to enable PO's to be printed in a portrait format. Revised graphics are required.
PDF'd Purchase Orders:
Corrects an issue where, if the global registry UseConvertedDBRs was set to true, landscape PO's archived as PDF's were generated in portrait format. See Customer Note 1.5.4 for additional details.
Start Document Archive Maintenance's option to convert DBR's to PDF's also generated PDF'd PO's as portrait instead of landscape. The correct orientation is now maintained when a report is converted to PDF.
Start Close Open POs: POs that have one or more lines with net Inventory Receipt Journal receipts <> zero are automatically excluded from this function; see Customer Note 4.4.
Unvouchered A/P: This release eliminates a sporadic error when saving a PO when Unvouchered A/P box is flagged in the Accounting Period and receipts are made directly on the PO.
Classic Dispatch Board: See Customer Release Note 16.1.21 for a Classic Dispatch Board Registry To Correct the Last Tech Column if it is duplicated.
Escalation Profiles: This release supports tokens for the Latitude and Longitude fields in the Client Site. The token ^clntste.geo_code_latitude^ references Latitude and ^clntste.geo_code_longitude^ references Longitude.
New Call: The Work Requested verbiage from the selected Web Log is used to generate the new Work Order's Work Requested and Equipment Work Requested, correcting a sporadic problem in previous releases.
Scheduled Event Manager: The system no longer pops up a message when a scheduled report is generated from an escalation profile event; see Customer Note 16.20 for details.
Web Log: In this release, the Work Code Id has been substituted for Service Category Id on the viewer's Find Data range screen. This prevents an error when filtering by Service Category in the Web Log.
Work Order:
Technician Tab: The following tech Statuses have been added: Parts Backorder, Parts Issue, Parts Shipped and Wait Tracking. See Customer Note 16.3.12 for details.
Purchases Tab: Corrects a sporadic display issue; see Customer Note 16.3.13.
Required Resources Tab: Validation has been refined to allow the User to clear the Vendor or Location if both have been completed when backing out of the RR Wizard, and the line has not been requisitioned.
Work Order List: This release corrects a display problem in Work Order List views that included the Work Order Work Requested on the list.
Work Order Range / Find Data: When searching for WO Techs with the WorkOrdersByBranchIDByWorkOrderID' list selected, only the Primary Tech is actually searched for. The Primary Tech has been added to this list to help avoid confusion.
SubAnywhere Document Posting supports the UseSubdirectories option in sys-document-archive. This enhancement will alleviate performance issues caused by having too many files in the root archive folder.
Custom Fields: This functionality has been enhanced to be viewer-specific in most cases. See Customer Note 1.17; a new v.cus is required to see the enhancement.
Document Management: This release allows legitimately 0 byte files to be attached to prevent looping with certain TechAnywhere attachments.
Positive Pay: See Customer Note 1.12.3 the registry to enable Positive Pay Processing for BBT.
Positive Pay: See Customer Note 1.12.4 for the registry to enable the custom Wells Fargo2 format. This registry supports a custom layout required by a specific SAMPro user.
Viewers: The user may now toggle between the Magnify and Line views of the selected child tab line with the key board equivalent Ctrl+Q or Ctrl+q.
Statuses: If Technicians should have access to any of the new statuses (Parts Backorder, Parts Issue, Parts Shipped and Wait Tracking), their TechAnywhere configuration will need to be customized.
Post: When WO Other lines are posted from TechAnywhere, the system will now adjust the Date or Accounting Period based on the existing sys-techanywhere registry option AdjustDefaultDateOrPeriod=Period or Date.
Job EOM: See Customer Note 8.1.8a for a registry setting to skip Change Orders that haven't yet been approved. This release also corrects a sporadic problem where the GL Entity was not always set when trying to appropriate the revenue across the cost codes.
Job Billing Change Request (COR): See Customer Note 8.13.4 for a registry to set the Change Order's Invoice Report Fields on Converting the COR to a Change Order.
EFT / Direct Deposits: See Customer Note 12.1.1a for a new PR Check registry option to print the Direct Deposit Stub if Employee Email is Not Set Up and EFT's are Normally Skipped.
Send Email/Scheduled Events: This release corrects an issue in the previous release where some installations running with smtp / unauthenticated email did not have their text emails (with no PDF attachments) sent.
Expired Insurance Certificate Notice Report: Revised report (REXPRDINSRNCE.rpt) dated 2018-05-08 provides for bitmap placement when emailing your Vendors. See Customer Note 3.2.12.
Client Site: When the user manually clears the Payment Alias field, the Masked CC No:, CC Expiration Date:, and CC Trx. Id: fields are also cleared. Previously, these fields were not cleared when the Payment Alias was.
Corrects a ">" Not Understood error when getting a list of files sorted by creation date.
Inventory Adjustments Journal: This release properly validates that the From GL Entity is required for Intercompany installations.
Location Viewer: When the Import Stock Levels button is clicked from the Location Viewer, the system now requires that a valid Location Id is selected. The user may double-click on the field to select an Id.
Avalara Sales Tax: This release supports an alternative method of computing sales tax using the Avalara Web Service Integration instead of SAMPro's internal computations. See Customer Note 6.6 for details.
New Report Job Tax Certificate Expiration: See Customer Note 9.2.5 for details.
Compute Payroll: This release implements performance improvements in this function.
Report PR W2's / Report PR W2's (Standard): If Residual Tax Withholding is used, Local wages may be overstated on Copy 2 of the W2's. See Customer Note 12.2.10b to omit the print of Local Line 2.
Approval Wizard: When exporting to a New Work Order, the User is now required to enter the Customer PO# number if the PO Required field is flagged in the Site's Service tab.
Notifications: When a Notification Category is set to Account Manager, the WO's Account Manager's Contact Record Email Address is used to derive the 'email to' of the scheduled event. See Customer Note 16.6.4.
Service Billing Worksheet Report: Corrects a Key is Missing error running this report.
ServiceChannel:
Previously, when a Service Request generated a Weblog in SAMPro the Client Site was not completed. This release identifies the Site if possible for use in the Weblog.
This release corrects issues experienced by some Canadian users uploading invoices. The Invoice Date is now sent in US format even for Canadian users for the I12 and I14 ServiceChannel Invoice Formats.
See Customer Note 20.1.12 for a registry to delay the ServiceChannel upload of Work Performed after a status change to accommodate delays in the TechAnywhere upload of this information.
See Customer Note 20.7 for enhancements on dealing with jobs that do not require materials on the i14 format, and for improvement to invoice spreadsheets.
ServiceChannel invoice spreadsheets generated by SAMPro can contain multiple invoices. In this release, the blank line previously separating invoices has been eliminated for both the i12 and i14 invoices.
Start Renew Service Contracts: Corrects a problem where TOS Equipment values and Client Site Billing amounts were being combined.
Sub Techs: Purchases Blocked' subcontractor Technicians may NOT be selected in New Call, the Work Order and the Dispatch Board, but "Payments Blocked" Technicians may be selected. See Customer Note 16.16.1.
TechFinder: When TechFinder is launched, the Certification from the Equipment's Main Tab is listed on the Certification range (along with those from the Equipment's and Site's Certifications tabs and the Work Code).
PDF's: The XmlToPdf.jar file dated 2018-06-29 writes to the xmltopdf.log file to provide diagnostics if a PDF conversion fails. This file required Java 8 or above on all machines sending email.
Document Scanning / Archiving: This release corrects a timing issue where SAMPro would attempt to create an archive before the original document is done being scanned / saved.
This release supports a config that automatically sends the Quote Recap Report to the Service Manager every time TechAnywhere creates a quote. Contact your TechAnywhere support rep for information.
Start Recompute T&M Revenue Values: This function now evaluates billed as well as unbilled JCH entries. See Customer Note 9.3.6 for details on this function.
Service Invoice: Revised report (SERVICEINVOICEv90b028.rpt) dated 2018-05-14 supports the new bitmap override by Job functionality. Customer Note 9.2.1h.
Progress Invoice Template 3: The revised Progress Invoice (RININV3.rpt) dated 2018-05-14 supports the new bitmap override by Job functionality. Customer Note 9.2.2a.
Clone Job Button: See Customer Note 8.1.9 for a registry to default the cloned Job's Branch from the Site instead of the template Job.
Report Quote Form: Revised Report (RQTEFRMv90b035.rpt) dated 2018-05-14 supports new bitmap override by Job functionality; see Customer Note 14.2.1a.
Quote Manager Scope Tab: The ScopeWorkOrder column has been moved to the left of the ScopeOfServices column. Previously, a large "ScopeofService" entry pushed the ScopeWorkOrder column off the screen.
Dispatch Board: Corrects an extremely sporadic problem where closing the Dispatch Board after setting a Custom Date on the Date Range tab resulted in a childless copy of the selected Work Order being generated.
Project WO Generator: The Dispatcher Id has been added to the initial Starter screen; if completed it provides the default Dispatcher Id to use when generating these work orders. If blank, the Dispatcher referenced in the Equipment record will be used. The Dispatcher Id also appears on the Checklist Screen and may be changed on a line by line basis if needed.
When a Flat Rate is referenced, the price from TechAnywhere is always used. Previously, if the price was adjusted using any other price level than 1, the TechAnywhere price override was ignored.
AP Journal:
General Tab: The Other Rate Id AND Cost Category Id fields have been moved to the right of the Job Cost Code to support manual entry when Cost Category usage restrictions are in place. A new customization file is needed to see the change.
Currency Conversion: Corrects a currency conversion rounding error between the cost written to the Subcontractor, General and CM tabs and that posted to Job History which prevented vouchering.
Intercompany Processing: Client Orders & COP Invoices now posts with the proper Security and Company Security information. See Customer Note 23.3.
Stock Status Report: This release corrects a minor rounding problem resulting in the sum of individual Location Totals not adding up to All Reported Locations Total.
Inventory Adjustments Journal: See Customer Note 5.1.5 for a registry to Create Warnings for Exceeding Quantity / Unit Cost Thresholds in Inventory Adjustments.
Inventory Receipts Journal:
Refines precision in cost calculations to correct a problem where received POs could not close at AP voucher due to pennies left committed.
Corrects an issue where some general items not referencing an Other Rate wrote to Job History with Labor as the jchstry_type if the Auto Set Quantity Received button was used.
Inventory Restock Pick List Entry: The system now sets security overrides when appropriate to support intercompany processing.
Consolidated Invoice Report: New report lists AR Invoice ID, PO, site name, invoice subtotal amount, tax amount, and total invoice for each invoice being consolidated. Supports auto emailing. See Customer Note 9.2.4.
Other Rates: The Bill Type defaults from the Billing Rate Type specified in the Other Rate record if not overridden in the Other Rate Table. See Customer Note 9.6.2.
Record Billing Adjustments: This release corrects the following sporadic errors: Runtime error: "containsPoint:" not understood and 'last character must be sign or digit'.
Service Invoice: Revised report supports the expanded the expanded Work Order Equipment Work Performed and Requested fields. See Customer Note 9.2.1g.
WBS Import: See Customer Note 7.2.5 for a registry to implement optional job cost burdening by Cost Code. This allows the Hourly Burden to be pre-set based on defaults established in this registry entry.
Check and Check (Employee) Viewers: Executive Payroll checks are not displayed unless the User's record has Executive PR flagged.
Compute Payroll: This release corrects the setting of the Earnings Id where a 'fixed' earning amount type is specified (such as a Bonus amounts entered on the Employee Recurring Wages tab).
PR-GL Accruals: See Customer Note 12.1.17 for a Registry to Force Earnings Credit GL Entity to Always Follow Debit GL Entity on PR Accruals.
Sort Earnings / Deductions Tabs: Registries are now required to automatically sort the Employee's Earnings and Deductions tabs, and the Earnings Group and Deduction Group child tabs. See Customer Note 16.6.3.
T4 Processing: This release supports an enhancement to allow Earnings records to be set up with a W2 Category of OI:40 and an Earnings Type of Wage.
W2s / W3s: If Intercompany processing is enabled then the following Employer Info will now come from the appropriate Company records, NOT the registries: Company Name, Company Address, Company Federal EIN.
Report PO Form:
New Ranges on Purchase Order Report: Vendor Id, WO Id and PO Date Entered.
This release corrects a spurious 'trim blanks' error when the Windows Printer Dialog box is enabled but 'PrintConfirmationDisabled' was not enabled.
PO Reorder Advice Report: This report now gets Security from Location/GL Entity/Company/Security links if Intercompany is enabled. Previously the report would always try to pull the Security from the Location.
Purchase Order: Validation now ensures that the Location Id is completed before any detail lines are added.
Revenue Adjustments are now correctly posted from TechAnywhere.
Corrects a spurious 'Runtime error: "qteinv_optn_cde:" not understood' using the Copy from Any Scope button.
Quote Scopes now support extended revenues of up to $99,999,99.
Create PM Work Order Checklist: This release corrects a problem where only the first line marked "Already Done" had there Equipment PM Schedule line updated with "NO WO" as the WO ID.
Escalation Profile: Enhancement allows documents attached to the Work Order after it's initial creation to be attached to scheduled event emails; see Customer Note 16.6.3.
Dispatch Board:
Email Button: When UseOutlook is enabled via registry, clicking the Email button launches the Outlook form and sets the Email To field with the Tech’s Email Address 2.
Work Order Summary: Supports the Ctrl + S shortcut (Save) in the Work Order Summary (accessed from the Power Board by right-clicking a work order and selecting Update Work Order).
Tech List Tab: Corrects display issue when a Tech Lists with a 15 character Id was selected.
Error Handling: corrects a 'doWIthIndex:' error related to list pane filtering, and a very sporadic 'key is missing error' on certain mouse movements. Also corrects a sporadic "System Primitive Failed" error when clicking on the column header of the Time Chart.
Column Filters: If you use the new column filtering on the Workorder List, these filters are cleared on the Workorder List pane when a new Technician is selected on the Tech Status Summary (upper) pane.
Project Work Order Generator: In this release the Work Code Id selected on the initial screen is used when deciding that a matching WO already exists for a given Job. The Do checkbox on the Checklist screen will NOT be flagged if a Work Order for that Job / Work Code combination exists.
Work Order:
Equipment Tab: The Cycle Code Filter is correctly when Equipment is manually added with a Work Code referencing a Cycle Code, preventing TechAnywhere sync issues
Inventory Tab: New customizations corrects a display issue with the vertical lines that separate the Revenue Rate, Unit Cost, and Cost Category. See Customer Note 16.3.4a.
This release corrects a "key is missing" error which occurred when a work order was saved immediately after being opened.
ServiceChannel:
This release supports Work Order IDs that have characters in them (e.g., prepended with a Branch Id).
Properly handles Inbound Folder containing Subfolders.
Corrects an error ServiceChannel encountered updating a Weblog record.
Also decodes non-ascii accented vowels (as found in French) to their non-accented ASCII Equivalents.
Registry: In a previous release, we added a feature that sends a Work Performed Note to ServiceChannel for each equipment line on a work order. Now the upload feature can be disabled for specified Equipment Ids via registry (Customer Note 20.1.4a).
Document Archive Maintenance: When Force Archive and Convert to PDF are both flagged, the archived .dbr file is now converted to a PDF. Previously, the file extension was changed but the file remained in .dbr format.
Error Handing: Internal refinements to prevent spurious error messages, including: sporadic file sharing errors when starting up SAMPro or attempting to delete files as part of the Quick Attach functionality, hardware-associated Runtime Error: 'Float denormalized operand', "Argument must be a collection" on accessing viewers and functions, and ">" Not Understood error (EDI Helper).
Make PDF: The new PDFJoiner.jar file supports joining secured pdf's, such as invoices received from Vendors. See Customer Note 1.16 for details.
Reporting:
Most Report Range fields have been expanded from 999 to 1999 characters.
The software double checks that the selected printer is valid and warns the user if it is not.
Registry: See Customer Note 1.1.3 for a refinement to the dbreportfiles registry.
Scheduling Enhancement: In this release, the system allows you to easily update, copy or cancel a scheduled report. See Customer Note 1.3.4 for details.
Database: SAMPro now attempts to recover the database connection if a temporary ‘Comm Link Failure’ (CLF) occurs. See Customer Note 1.15.
User viewer - Import Profile Button: Corrects a Key Is Missing error when importing certain older analytics.
Labor Post: Removes the Supervisor logic for TechAnywhere; this functionality is supported in TimeAnywhere.
Equipment Replacement: Refines handling of subsequent replacements. See Customer Note 19.7.1.
PO: When a PO message fails (e.g., due to expired insurance), the Vendor Id and Name are now included in the TechAnywhere Error Alert email to make it easier to identify problems with the Vendor.
Corrects a problem where Labor Journal TimeAnywhere postings were coming it with no Security. In this release, the Security Id is based on the Employee record for both original and Intercompany Security models.
AP Journal:
This release refines the Manual Check # validation tests so that it ignores check #'s for Check records of type 'EFT'.
When a manual check / EFT is recorded in this journal, the Bank's currency will be used for this portion of transaction; the forces the currency factor to 1.0 when the purchase and payment are in the same currency.
Report AP Vendor Payment History: This new report shows the total amount paid by vendors based on the AP Journal Effective Date - see Customer Note 3.2.11.
AR Cash Receipts: Correct a spurious error 'no unpaid invoices found for specified client' when entering a consolidated invoice.
Inventory Restock: This function now sets the Inventory History Security for Intercompany databases. Validation also prevents To and From Locations from being in different Companies.
Service Invoice: Supports Token Replacement for the Email Subject and Message. See Customer Note 9.2.1e and 9.2.1f for the revised report and registries to enable.
Report Commissions by Amount Invoiced: Revised report (RCMMSSNRPT5.rpt) dated 2018-02-20 includes logic for discounts upon receipt. See Customer Note 9.2.3.
New Job Contract Type - Small Job: Costs and Revenues are not recognized on a Small Job until the Job Date Closed is set. See Customer Note 8.6.11 for details.
New T4 - T4 Summary: Report PR Canadian T4 (Standard) and Report PR Canadian T4 Summary (Standard) do NOT require a printer that supports native PCL printing with a PCL 5 /5c printer driver. See Customer Note 12.2.16 for details on these new reports.
Report W2 Electronic File: The revised Report W2 Electronic File (RW2EFb72vb105.rpt) dated 2018-02-16 supports registry options for the state of Oklahoma and the city of Philadelphia; see customer note 12.2.17.
Job Scheduler: Access to this module is now controlled via the vrgstry.cus and vrgstry.sam files. If your firm is running this module your support representative must provide you with upgraded files. This release corrects issues with intercompany security.
Subcontractor POs: When changing from one Subcontractor Tech to another Sub on the Work Order or Dispatch Board, when the Vendor is updated in the associated PO the AP Terms and Tax Group will also be updated. Only PO's with no child lines will be updated.
Work Order: A new tech Status, Over Budget, has been added; it has a corresponding Work Order Escalation Status of Over Budget (Status Category Completed), This new status falls above Completed and below Wait Paperwork in precedence.
Dispatch Board: Corrects a spurious 'technician is INACTIVE' message when using the Available Hours tab to assign WO to a tech whose Tech Id exceeds 10 characters.
Site WO Other: See Customer Note 16.1.20 for a registry to specify which lines from the Site WO Other Tab should be added to new WO's by Service Category.
Master Contract:
When PM's are generated for contracts with TimeofServiceBill? box flagged, the Cost Category will always be set on the WO Other tab.
Time of Service Earn Enhancements: Supports handling of revenue proration for multiple sites. See Customer Note 16.5.4 for details.
TechFinder: Corrects a ‘receiver is not a boolean’ error that occurred if the global registry option CertificationFromWorkcode = true was not set.
Clear Checks: A warning now alerts the user in Clear Payroll Checks and Clear Accounts Payable Checks if the selected GL Account has ever been referenced in a Bank Reconciliation Journal entry.
Email: See Customer Note 1.6.2 for details on recent UseOutlook enhancements.
User: The Clone Profile button may now be used to clone DBAnalytics settings if the user only has ACCESS (but not EDIT permission) in the User Viewer.
This release refines the edit validation; see Customer Note 10.8.1.
Inventory Receipt Journal: The new Inventory Packing Slip button calls a new report, Report Purchasing Packing Slip (RPOPCKNGSLP.rpt). See Customer Note 5.2.1 for details.
Inventory Receipt Journal: This release supports a registry to deny the over receiving of Stock Items. See Customer Note 5.1.4.
Report SOP Transfer Tickets: The Inventory Item Id column on the components lines has been expanded to support longer Id's. This system report does not need to be imported.
PR to GL Accruals: The software now gets Labor GL Info for each line to ensure proper GL distributions have been determined.
Job Progress Viewer: This release corrects a sporadic display issue on the Margin %.
Job Budget Tab: Budget entries made entered on this tab now post to Job History with the correct Security when using the Intercompany model. Customer Note 8.6.5.
Project Manager Workbench Cost Codes Tab: The Cost Code Name has been added to this tab to the right of the Cost Code Id field.
Print POs: Corrects the sporadic error "You cannot change this Purchase Order because it was spooled to the printer, but it was not marked as being successfully printed".
Purchase Order Subcontractor Tab: The Tax Amount (if applicable) is successfully recomputed when the C.O. Amount is changed on an existing line.
Quote Manager: The functionality to launch Report Quote Recap WO when a quote is posted has been added to the Quote Manager Approval Wizard; Customer Note 4.1.3.
CrystalViewer Web 4.0: This program written by Data-Basics Inc. allows SAMPro users to view Crystal Reports on their workstations. This program is only for viewing existing Crystal Reports and not for any type of report development. See the CrystalViewerWeb 4.0 SAMPro.pdf file for installation details.
Web Log: Corrects handling of non-printing characters in the Work Requested when a new Web Log record is generated from ServiceChannel.
Work Order Milestones Tab: This release allows Milestones to be added to any Work Order. See Customer Notes 16.3.11 and 16.17.4 for details.
Work Order Equipment / Metrics Tabs: When manually adding an Equipment line, the Cycle Code's 'CC' filter is now pulled from the line's Work Code. It is used to filter the Metrics lines that are automatically added.
When a PO is created in TechAnywhere, the Cost Category now defaults from the Item's Inventory Group. If the Cost Category is not set in the Inventory Group, the sys-techanywhere option InventoryCostCategoryId continues to derive the Cost Category.
The TechAnywhere Labor Post follows the Labor Journal Registry to Use Default Service Job in the Equipment record for all but PM WO’s. See Customer Note 12.1.15 for the registry.
1099 Form: The revised Report AP 1099 (also titled Report Vendor 1099's) supports a new registry to set the State EIN. Customer Note 3.2.9.
1099 Electronic Files: The new Report AP Electronic Files function creates the file that is used to submit 1099’s electronically. See Customer Note 3.2.10 for details on implementing with required registries.
Bank Deposit Journal Report: This new report (BNKDPST.rpt) prints the Journal Entries and associated receipts by the bank GL Account. The Start/End date is based on the Bank Deposit Effective Date.
Progress Invoices (RININV3): The Effective Date is set in the Invoice Master when a Progress Invoice is posted, correcting an issue in recent releases. In addition, the Job PO is now posted to the Invoice Master for progress-type invoices.
Inventory Restock List: Corrects a sporadic "Runtime error: system primitive failed" error on re-opening restock entries.
Quote Approval Wizard: The Work Order's Date Earliest Start is now set to the current date when a new WO is generated. The Date Earliest Start is also set when posting to an existing WO whose Date Earliest Start has not yet been set.
Dispatch Board: The Work Order's Earliest Start date has been added to the Power Board. This new column is initially located on the extreme right-hand side of the work order list, but drag and drop may be used to reposition it.
New Call: The registry option to omit the Market Source when creating new Sites has been revised to also omit writing the Market Source to the new Clients. Customer Note 16.1.1a.
TechFinder: This release supports additional Certifications per Work Code to be specified for use with TechFinder; see Customer Note 16.1.9 for details and the registry to enable.
Work Order: Corrects a 'receiver is not a Boolean' error editing the Required Resource tab. Also corrects writing of Work Requested in new Work Orders.
Corrects a PO Posting issue in the previous 9.1.611.038b version.
AP Check: See Customer Note 3.1.6 for a new Registry to Protect Dollar Amount in Canadian AP Checks.
AP Journal:
New Button - Reset Tax On Lines: If enabled via registry (Customer Note 3.1.3a) this button automates the process of changing the Tax Group on all of the Inventory, General and Subcontractor lines, and automatically adjusting the tax amount.
New Field - Last PO Receipt: Displays the most recent receipt date of the selected PO. See Customer Note 3.3.5 for details.
Registry: Customer Note 3.1.8 lists an option to display an Error or Warning when selecting a PO whose Last PO Receipt precedes the AP Journal's Effective Date.
Registry: See Customer Note 3.1.8a for a AP Journal Registry to Use the Default Service Job in the Equipment record for all but PM WO’s.
AFT Processing: This release supports AFT/AP Link Reporting For RBC (Royal Bank of Canada). See Customer Note 3.1.7 for the registry. The Check Reference Name is included in the Positive Pay file.
AR Cash Receipts: This release employs the new list filtering functionality so that the user can easily filter on the Open Invoices to be paid. Customer Note 6.3.4a.
Report Customer Statements: The revised report replaces 'Print Zero Balance Statements' with the more flexible 'Print Statements With Balance Over' field. See Customer Note 6.2.2.
Invoice Master: The Show Invoice button also displays COP Invoices if applicable.
Start Create GL End Of Year: If the GL Account / Entity combinations for the annual sum of Debits and/or Credits exceeds 100M, this function evaluates and parses calculations that exceed table constraints into multiple GL Journal lines to prevent truncation errors.
PR Miscellaneous Deduction Checks: This release supports GL Debit and Credit posting for Deductions withholding (PR Check) & relief (PRMD Check); see Customer Note 12.2.2a.
Payroll Period: When the new Executive Payroll field is flagged, only users who have the Executive Payroll field flagged in their User record can run functions and access transactions for this Payroll Period. See Customer Note 12.10.2 for details.
Payroll Worksheet: Revised report supports optional Direct Deposit section showing Direct Deposit info from the Employee (no check issued) or the Check. Customer Note 12.2.3.
Labor Journal: See Customer Note 12.1.15 for a Labor Journal Registry to Use Default Service Job in the Equipment record for all but PM WO’s.
New W-2/W-3: The new Report PR W-2s (Standard) and Report PR W-3s (Standard) do NOT require a printer that supports native PCL printing with a PCL 5 /5c printer driver. See Customer Note 12.2.15 for details on accessing and running these reports.
Purchase Order:
See Customer Note 4.1.1a for a Purchase Order Registry to Use the Default Service Job in the Equipment record for all but PM WO’s.
This release refines the message displayed if the associated Work Order's Sub/PO NTE values has been exceeded. See Customer Note 4.3.6 for details.
Corrects an error when using the subcontractor tab for a foreign currency Vendor.
When the Receive button is clicked the Inventory Receipt Journal is opened correctly.
Quote: This release corrects a display issue on the Quote Viewer's Gross Margin tab where the last digit of the GM% was obscured.
Quote Scope Revenue Adjustment: When SAMPro calculates the AdjBase (Adjustment Base), if it's value is negative, the Add - Deduct button is automatically flipped from its default setting. This supports the setting of Revenue Adjustments for negative scopes.
Report Quote Form (Standard): The revised report (RQTEFRMv90b035.rpt) dated 2017-11-03 correctly supports negative tax values for negative scopes and quote totals.
Quote Approval Wizard: Previously, if the Approval wizard encountered the "WARNING: this work order has open assignments to a remote technician" the approval stopped. In this release, the warning is suppressed so the Approval wizard can run.
Dispatch Board:
Date Range Tab: Corrects a display issue selecting a User Range.
Corrects a Runtime Error when a new user opened the Board for the first time.
Master Contract:
A new registry sets the Sub's NTE from the Equipment record if the Master Contract does NOT have a Cost amount on either the Inspections or the Provider Rates Tab. Customer Note 16.1.4a.
Subcontractor Validation:
New Call: 'Purchases Blocked' subcontractor Techs may NOT be selected in New Call. Previously, this validation was only applied to "Payments Blocked" technicians.
Power and Classic Dispatch Board: 'Purchases Blocked' subcontractor Techs may NOT be selected.
Technician: The new Vendor Name, Insurance Required, Insurance Expired, Purchases and Payments Blocked display fields appear on the Main tab. See Customer Note 16.16.1.
Work Order: 'Purchases Blocked' Techs may NOT be selected on the Tech tab. Previously, this validation only applied to "Payments Blocked" Techs.
Work Order Labor Tab: Previously, entering a labor budget by checking lines as 'quoted', resulted in the quoted line posting to GL when the WO was marked as Invoice Ready. In this release, the system never posts to GL for quote-type WO Labor lines.
Work Order Main Tab and Client Site Service Tab: The Field Label 'Sub NTE' has been changed to 'Sub/PO NTE' to better define it's meaning.
Work Order Batch Close: A new registry is available to specify the statuses eligible for Start Work Order Batch Close. Customer Note 16.1.8.
Web Log: The Work Requested display field has been expanded from 4 to 14 lines. A revised customization file is required to see this change unless upgrading to this version. .
Document Management: Corrects a 'Runtime Error: “isOkToRecord” not understood ' and the '"Archive File Location Does Not Exist" error' experienced by some users.
List Filtering Enhancement: This enhancement allows you to right click on column titles to apply filters to the selected column. See Customer Note 1.9.3 for details.
Positive Pay Processing: This release adds Positive Pay reporting for RBC (Royal Bank of Canada. See Customer Note 1.12.2 for the necessary registry entries.
User Group: Corrects a problem where 'cloning' a User Group cleared all selected lines. The settings from the original record are now retained in the newly created one.
XmlToPdf.jar File: The revised file dated 2017-12-27 supports the revised W-2 reporting format. It also corrects a file 'cannot find this file' error with UseOutlook enabled for Outlook 2013 and below.
Quote Enhancements: This release supports the ability to post quote discounts and to email the SAMPro-generated quote report. See Customer Note 17.8 for details.
Equipment Replacement: TechAnywhere V4.0.058.008 allows the Technician to replace one piece of equipment with another if enabled. See Customer Note 19.7.
Require a PCR Table: TechAnywhere uses the new PCR Table Id in the Site's Service Tab to indicate that new Equipment for this Site requires a PCR Table. See Customer Note 19.8.
Labor Posting: Corrects Labor Posting issues in recent releases.
AP Journal: Corrects an error -143 when a Credit Purchase Order is selected.
AP Manual (Single Write) Checks: This release supports registries to default the GL Account and or Entity, and to disable the GL Entity (for non-Intercompany installations) See Customer Release Note 3.1.5.
COP Invoices: This release corrects a spurious Runtime error that appeared when launching Report COP Invoice in a database which contained only a single AR Control GL Account.
When Invoices are posted from DBSellpoint, the Invoice's Due Date, Discount Date, Discount Available are now set based on its AR Terms.
Bank Reconciliation Journal: This release adds additional refinements when establishing if the selected transaction is editable. See Customer Note 10.7.1 for details.
Inventory Adjustment Journal: This release corrects a rounding issue that caused the amount expensed/ relieved from inventory to differ from Intercompany transactions.
Employee Taxes Tab: Tax for Authorities not marked 'Always Withhold' are only assessed for labor on Jobs referencing that Tax Authority, correcting a problem in recent releases.
Workers Comp: This release applies Security filtering based on the Workers Comp Category in the Labor Journal Hours tab and the Work Order Labor tab. See Customer Note 12.20.1.
PR Miscellaneous Deductions Check. This release supports registries to default the GL Account and or Entity, and to disable the GL Entity (for non-Intercompany installations) See Customer Release Note 12.1.2a and 12.1.2b.
Purchase Order List: The PO's "ordered by" field has been added to the sort option PurchaseOrderByVendorAlphaByIdByDescription after the status column.
Import Diagnostics Wizard: Corrects a sporadic Runtime error - system primitive failed.
Auto Archive Work Orders: This release corrects a key is missing error running this starter function with the sys-start-sautoarchivewo registry enabled.
Dispatch Board: This release corrects a System Primitive Error in the Tech Lists tab when the user clicked at the top of the tab so that no list was selected.
Work Order Other Tab: Corrects the calculation of the Canadian PST on edited lines as an additional cost on a line to be included in pricing mark-up. See Customer Note 16.3.4a.
Work Order Technician Tab: Refines the update of the referenced Purchase Order if one Subcontractor Tech is changed to another. The AP Term in the PO is forced to match the Vendor record; the PO's Sales Tax Group is updated from the Vendor (default) or Job (registry enabled).
This release supports mapping SAMPro log status’ to Service Channel log status’ based on registry values keyed by Client Id. See Customer Note 20.1.11 for detail.
This release corrects a recent problem where the TechAnywhere post did not update the Job Quantity Ordered and Job Quantity Received on the PO from TechAnywhere.
TechAnywhere now writes errors to the TechAnywhere Message Directory if a collateral Document fails to post so that the issue can be tracked.
AP Date-to-Pay List: A new registry entry can be used to control the sort order for this function (e.g., sort invoices by due date). See Customer Note 3.1.4 for details.
AP Journal:
Reversing General lines are now flagged as No Discount to avoid discount calculation issues when the Date Effective is edited.
The 'Check Number' filter range has been renamed to 'Manual Check #' for clarity.
Since Job Cost Categories only needed if a Job/Work Order is specified, the Job Cost Category is cleared if a Job is NOT specified on a detail line when an entry is loaded.
PWP Billed List: This function has been enhanced to include UNBILLED JCH lines for Service Compute Jobs lacking a Work Order reference. See Customer Note 3.11.1 for details.
Report AP Check Register: Revised report (RAPCHEKv72b001.rpt) dated 2017-08-15 includes a new range filter, Check Number, to enable printing for a specific check or range of check/eft numbers.
Start Create EOM Unvouchered AP GL Entries: Credit Side Entities are now generated when Intercompany is enabled without a separate registry; see Customer Note 3.1.2a.
Vendor Open Invoices Tab: AP Retainage is now included in the calculation of the AmountOwed column.
AR Cash Receipts Journal: If a customer pays the same invoice twice, a registry allows the user to 'clone' the original Cash Receipt to create the overpayment entry. See Customer Note 6.3.5 for details on Applying Overpayment to the Original Invoice.
This release tightens Job Cost Category / Job validation.
AR Sales Journal: Tightens Job Cost Category / Job validation.
Client Collections Screen: The "Invoice Date" field in the summary pane has been relabeled as 'High Balance Date' to better describe its meaning.
Report Customer Statement: Revised report (RCUSTSTMNTv80b048.rpt) dated 2017-10-06 prints the consolidated invoice description for consolidated invoices.
Report AR Aging: See Customer Note 6.2.1 for updates to this report as of 2017-09-19.
GL Reporting Period: In this release, the Report Title is cleared when a GL Reporting Period is cloned: it will be set correctly based on the Fiscal Year and Date when the new record is added.
Inventory Adjustments Journal: This release corrects issues with unbalanced GL entries: extended costs are now correctly rounded instead of being truncated.
Inventory Item:
The Inventory Item Extended Description columns have been added to the InventoryItemByGroupByIDByExtendedName Inventory Item list.
A saved range can be added to enable the user to search on the first Extended Description column: sql=(invntryitm_dscrptn_extndd like '%text%')
Inventory Receipts Journal:
Important: Un-receipted lines are no longer displayed in existing entries to enforce the requirement that a new Inventory Receipt entry must be created to re-receipt items.
Serial Inventory: See Customer Note 5.7.3 for a procedure to re-receive a serialized item.
Corrects a sporadic Tab Mismatch error receiving quantities via the Auto Set Qty Rec'd button.
Create PM Billing: Corrects a recent problem generating billings for Client Sites with a payment alias setup for automatic credit card payments.
Record Billing Adjustments:
In previous releases, clicking the Save button automatically restarted the function. In this release, a registry is required to do so: see Customer Note 9.1.4.
This release corrects a problem in recent versions which did not allow negative Change Orders to be processed.
The new PM Next Invoice Status display field is used in conjunction with certain Progress Billing Invoice DBAnalytics. See Customer Note 21.3.4 for details.
Start Reverse Job Invoice: The Work Order COD Tab's Invoice Reference is now cleared so that the user may edit the COD child tab before re-billing the Work Order.
Progress Invoice Template 3: Revised report (RINIVNV3.rpt) dated 2017-08-13 adds the Site Address to the CANADA header format.
Invoice Master Viewer - New Field: PO#: The Invoice Master PO# is now displayed in this field. Currently, this field only supports the Customer's PO# for Service Compute Jobs.
Job Billing Item Change Requests: Corrects handling of JC history 'JBI Budget' entries when the Convert Job COR to CO button is clicked as will as rounding issues with the viewer.
Job EOM: Customer Note 8.1.8 specifies new registry options to control the Cost of Goods Sold Account by Cost Type.
Project Work Order Generator: The following Ranges have been added to the initial range screen to provide additional flexibility: Job Name, Project Manager Id, Site State.
Compute Overtime Enhancement: This release extends the functionality of the Overtime calculator work even when checks are not actually printed and posted. See Customer Note 12.18 for details.
Report PR Deductions Detail: The revised report (RPRDEDDTL.rpt) dated 2017-08-30 includes a new filter range for the GL Entity ID which relates to the GL Entity assigned to the employee records.
Report PR Miscellaneous Deduction Check Detail: Corrects a problem where duplicate lines appeared if the Employee Deductions Tab included multiple lines with the same Deduction Id for different date ranges. This system report does not need to be installed.
Job Viewer's Create PO Button: If the BranchOverrideFrom global option is set to 'job' the Branch is correctly reset from the Job's Branch when the Vendor is entered after the Job Id is completed.
Purchase Order: When a PO record is loaded or saved, the Job Cost Category will be cleared if a Job is NOT specified on a detail line. This release also tightens Job Cost Category / Job validation.
Quote / Quote Scope: Corrects sporadic Tab Mismatch errors on multiple labor, inventory, material and other line extended price summations.
Quote; Quote Manager Lists: The Quote Status has been added to the QuotesByIdByWorkOrder list after Estimator Id and before Description.
Quote Approval Wizard:
When the Job Budget option is selected, Budgeted Revenues are now written for T&M Quotes; previously only Budgeted Costs were written. The Quote's Revenue Adjustments also generates a Budget Entry (+ or -).
The Wizard now writes to the Work Order Log Tab when a WO is created or updated.
Previously, the Remote Technician warning was treated as an error and the approval stopped. In this release, the warning is suppressed so the Approval wizard can run.
Work To Do Pane New Field - Customer PO#: When posting to a New WO, this field sets the PO# field on the Work Order with the PO# provided by the customer.
The Description entered on the Scope's Material tab is now accurately written to the Purchase Order instead of being overwritten by the Other Rate Id's Description.
Use Crystal Quote Registry: See Customer Note 14.1.4 for registry to enable the Quote to allow blanks in the Report Id to so that Crystal Reports may be run.
Set Scope Status to Printed: See Customer Note 14.1.2 for registries to permit users to manually set the Scope Status to Printed (designed for Crystal Report Quote users).
Site Equipment: The Equipment Type Id is no longer cleared when the PCR Table Id is updated in the Equipment record or via TechAnywhere.
Subcontractor Work Orders: When a Subcontractor Tech is changed on the WO Tech tab or the Dispatch Board, the system automatically changes the Vendor in the associated PO. In this release, the PO's A/P Terms and Sales Tax Group are also updated.
New Call 2: This release corrects an issue where changing the selected Site Equipment updated all applicable fields except the field the cursor was positioned on.
Report PM WorkOrder List: This release plus the revised report support a registry to allow the Create PM WO checklist and the report to appear in the same order. See Customer Note 16.2.2.
Service Invoice: Corrects a sporadic issue if a user attempted to edit a previously invoiced line resulting in negative 'ghost' lines on subsequent invoices for that Work Order.
This release refines handling of a ServiceChannel CHECK IN (or CHECK OUT) message with conflicting TR_NUM and WO_NUM values. See Customer Note 20.6 for details.
Quoting: The ServiceChannel Upload button has been removed from the Quote and Quote Manager viewers because the quote/proposal integration has been disabled by ServiceChannel.
Shop Order Transfer Ticket: Corrects errors when accessing records in recent releases.
Document: This release corrects a sporadic 'Runtime error: index: 1 is outside of collection bounds' which showed up in Windows 10 (fresh install) when trying to show an image in a Document record.
Keystrokes: Shift+Tab now moves the caret back one field. Ctrl+G acts like Shift+Tab in Viewers, Reports and Starters. Ctrl+G retains its 'Go' functionality in the Viewer, Reports and Starter menus.
Positive Pay (BoA): This release supports Bank Of America Positive Pay Reporting w/ Payee Information. See Customer Note 1.12.1 for the registry to implement.
Printer Selection: This release corrects an issue where the defaultprinter option in the sys-printer-functionid registry was ignored; see Customer Note 1.2.1a for details.
Switch Security Identity: Switching Security from the File>Switch Security Id menu no longer terminates the User's Web sessions.
Viewers: This release corrects sporadic errors encountered when clicking the End key and then editing an Id field that already contains the maximum number of characters.
Purchase Orders:
PO's will not be updated by the post if no values have changed. This will preclude failed message when the post attempts to update a closed PO.
This release corrects a sporadic problem where the Equipment Id on the PO's Gen tab was cleared on general items received in TechAnywhere.
Quotes:
Corrects a sporadic problem where TechAnywhere combined all outstanding quotes resulting in all scopes being written to all quotes created by the post.
Prices for Other and Material items are now successfully posted for TechAnywhere Quotes. Corrects an issue in recent releases where costs but not prices were posted.
Taylor UWO: This fix applies to customers using the Taylor Universal Work Order functionality. It corrects a 'Key is Missing' error when posting Work Order COD information.
Corrects a recent problem with Pay Types and TimeAnywhere messages caused by pulling defaults in the employee record.
AP Journal: Postings to the Bank Account specified in the AP Manual Check section ONLY use the GL Entity on the Main tab when InterCompany is enabled via registry. If InterCompany is NOT enabled, the GL Entity is not used for Manual Check / EFT / CC posting and Check records.
AP Select Invoices for Payment/Date to Pay: In this release, the Next Pay Amount field will be completed appropriately when the Next Pay Day field is blank (01/01/1900).
Cash Receipts Journal Open Invoices List: The Invoice Description for each Invoice, CM or Unapplied Payment is displayed in this new column on the right-hand side of the list.
Client Collections: The Email button has been added to the Collection Notes viewer.
Progress Billing Analytic: This Analytic allows the Project Manager (PM) to participate in the billing preparation process without using SAMPro. An IIS web server is required. See Customer Note 21.3.
GL Trial Balance Report: Corrects sporadic display issue running report with GL Entity viewer open.
Inventory Adjustment Journal: Corrects issue with extraneous posts to the blank or default account on Location to Location transfers.
Job:
Copy From Client Button: When clicked, the Job's Sales Tax Group, Service Zone and Branch are also set from the Zipcode table for the Client's Zipcode. See Customer Note 8.1.7 for a registry to only copy the Address fields from the Client to the Job's Invoice Address.
Import WBS Button: Corrects a case-sensitivity issue.
Job Journal: Previously, the Total Labor Cost display field was not promptly updated if the global registry LaborRatesAndAccrualMethod=7687 was enabled. This field is now correctly updated when the Job Cost Code is entered.
Labor Journal Hours Tab: Since a Bonus should never be entered on a line which also records hours, validation now prevents the user from entering hours and a Bonus on the same line.
Payroll Period: The new Deduction Cycles field provides the default values for Start Compute Payroll so that Deduction will not be accidentally skipped. See Customer Note 12.10.2.
Purchase Orders:
A new warning appears when accessing a PO which has been replaced by one with a higher 'tack' number; this helps prevent the user from wasting time by attempting to make changes to a PO which cannot be saved. Customer Note 4.1.2 has a registry to disable this warning.
Branch Id: Corrects setting the Branch Id when the global setting BranchOverrideFrom=job is enabled and the Work Order Id filled in before the Vendor is selected.
Quote Scope: Corrects sporadic Runtime Error when clicking the Flat Rate Import button.
Quote Manager: This new button resets the Tax Type of detail lines for all Open Scopes. See Customer Note 14.4.2 for details.
Approval Wizard: Revenue Adjustments of approved option(s) are now included in the NTE Client field when a new WO is created unless the NTE update is suppressed via registry.
Revised Report Quote: The revised report dated 2017-06-21 correctly evaluates the ‘ n/a’ Tax Type on detail scope lines. See Customer Note 14.2.2 for details.
Dispatch Board Work Order Summary: Delete button removed; see Customer Note 16.11.2.
Master Contract / PM Work Orders: If the PM Task List is not specified on the Master Contract Schedule, Create PM WO's uses the one in the Equipment record. See Customer Note 16.1.6 for a registry to Disable Use of Equipment Service Task when Master Contract PM's are Created.
Notification Category: The obsolete TechAnywhere option has been removed from the list of Methods. It was used for Remote Tech Device/Blackberry notifications in earlier versions.
Start Renew Service Agreements: In this release Equipment flagged as Inactive will be skipped.
Work Order Labor Tab Header: The Actual / Billable Hours: fields display running totals of hours entered on the Work Order. Negative labor hours are now correctly handled in the total.
Work Order Revenues Tab: Corrects an error when double-clicking on an AP Journal line.
Work Order Registry to Prevent Editing WO Other Lines Imported from PO: This registry is recommended if Create EOM Unvouchered AP GL Entries is run. See Customer Note 16.1.7.
Journals: A warning is displayed when accessing a journal entry which has been replaced by one with a higher 'tack' number to help prevent the user from wasting time by attempting to make changes to a journal entry cannot be saved. See Customer Note 1.1.2 for a registry to disable this warning.
Licensing: This release closes a loophole which allowed more Full User and TechAnywhere (Technician) records to be created than allowed by license. See Customer Note 1.11 for details.
The check for zero hours has been removed from the TimeAnywhere post to support entries by the employee as a place marker for StandBy per diem.
AP Journal: This release corrects the calculation of Tax Cost on subsequent AP entries where the PO had previously been partially vouchered.
Ranges Screen: New filters for the Client's Street, City, State and Zip fields.
List Screen: New Sort Order ClientsByClientMailingAddress displays the Client's City, State, Zip, Street Address and Client Name.
Collections Screen: The first column of the Past Due summary box has been re-titled '1-30 Days' for clarity. It was previously titled 'Current'.
Custom PM WorkBench: Certain analytics depend on knowing which of a job's Cost Codes is designated as the 'Fee Code', the registry setting in Customer Note 21.2.1 is required.
Customize Service Invoice Email Message: The revised Service Invoice and this release support custom text in the email that the Service Invoice is attached to. See Customer Note 9.2.1e for details.
Job WBS Import: The Job viewer's WBS Import process needs to know which Cost Code should be marked as the 'Fee Code'. See Customer Note 8.1.6 for a registry to enable.
Job Progress: See Customer Note 8.1.5 for a new registry which allows the system to reflect >100% complete with a negative CostToComplete "projection".
Job - Invoice Email To: Double-clicking this field brings up a list of valid email addresses from the Site and Client records for the user to select from. Email Groups will not appear on the list, but may be added manually and enclosed by brackets [emailgroupid].
Report Jobs in Progress: The revised report replaces the Over/Under Billed column heading w/ Total Billed JTD - Cost JTD. The report is sensitive to the CO Date Approved; see Customer Note 8.2.6.
Report WIP Summary 2 (% Completion Method): New report calculates Total Estimated Revenue from the Contract Amounts in the Billing Items. See Customer Note 8.2.7.
New Call: The PO Required field is once again enforced; corrects a problem in recent versions.
This release supports subfolder logic when a file is archived after a delay; previously, these files were archived in the base archive directory.
Report AP Canadian Electronic T5018s: This new function creates the files that is used to submit the T5018s electronically to the CRA (Canadian Revenue Agency).Customer Release Note 3.2.7.
AR Cash Receipts Journal - Open Invoice List: The new PO# column displays the customer's Purchase Order specified in the Work Order's PO# field.
Service Invoice: Revised report supports a new registry setting which will allow both Billing Address and Email To information to print on the invoice header. Customer Release Note 9.2.1d.
Paychex SPI Flex Format: Report PR Export now supports this format; Customer Note 12.1.14.
Purchase Orders: Corrects setting the Branch Id when the global setting BranchOverrideFrom=job is enabled and the Work Order Id filled in before the Vendor is selected.
New Call: New registry controls (by Service Category) over which Jobs are displayed when the Default Service Job field is double-clicked or the Id Lookup button is pushed. Customer Note 16.1.5.
Refines handling of invalid responses from ServiceChannel to prevent HTTPServer crashes.
Status Pane: The bar at the bottom of SAMPro screens now displays the value of the field that the mouse is hovering over; enable the user to view fields not fully displayed in the data-entry screen.
Timesheet: When Equipment is created, the Equipment Name now defaults to Pending instead of the Equipment Id to correct an issue with Custom Fields. If Custom Field values are specified for the Equipment Name, Pending must be one of the allowable options.
Service Invoice: Revised report dated 2017-04-14 supports a registry option to skip print $0 DUE invoices (e.g., COD Invoices). See Customer Note 9.2.1c for the registry to enable and details.
Avalara Sales Tax for Use Tax Jobs: Corrects a sporadic issue where the Sales Tax Authority information was too large to fit in the Use Tax Info fields on the detail lines of the AP Journal; Inventory Adjustments Journal; Inventory Receipts Journal; Purchase Order; and Work Order viewers. This issue emerged when updated Tax Groups included zero rate Authorities.
Start Compute GMP Special Revenue: This function posts the special revenue will be posted to Job History as Job Journal entries so that they will be available for progress invoicing. In this release, the Compute sets the Job Journal Parent Date/Period from the first child line.
Web Log: A new Sort Order, WebLogByWorkOrderByClientSiteName has been added the List Viewer. Dispatcher and Technician Ranges have also been added: see Customer Note 16.16.
See Customer Note 20.1.10 for a registry to derive the Scheduled Date / Time of the Accepted Request Message from the Original ServiceChannel Request when a WO is created in New Call.
Start Move Generic Documents: This new function is designed to move the generic text files generated by a text printer out of the main SAMPro directory. See Customer Note 1.3.3 for details.
Document Archive Maintenance: The DBR to PDF function now uses the report's internal bitmap path to set the pdf graphics if available.
Registry Viewer: The new Sort Lines button allows individual registry entries to be sorted alphabetically; see Customer Note 1.1.
Quotes: The Unit Cost entered by the Tech Material and Other lines now posts back to SAMPro so that the Quote's costs are correct.
New Call: When a Work Order is created in TechAnywhere, its Client and Sub NTE fields now default from the Equipment record. If not set in the Equipment record, they default from the Site.
Service Invoicing: Corrects sporadic 'key is missing' errors invoicing COD WOs. Potentially OOB Cash Receipts / AR Sales can appear on the Checklist but cannot be flagged for processing.
Inventory Adjustment Journal: This function now supports the 'creation' of serialized item records (via an Adjustment entry) for Intercompany users.
View Inventory Restock List Items Tab: The new Stocked field is checked if the Item is flagged as a Stocked. The Reorder Level: and Order Up To: fields default from the Restock To Location.
Medicare Additional 9% Tax: This release refines payroll processing for high wage earners. See Customer Note 12.19 for details on the requirements to support this enhancement.
Bonus Pay - Labor Journal Hours Tab: See Customer Notes 12.4.1a for information on the new Federal and State Tax Rates fields for Bonus Pay and Customer Note 12.2.1a for simplified Bonus Pay Check procedures.
W2 Forms (Plain Paper Copy): The W2 Year is now printed below the Copy label on the Plain Paper Copy version of the report.
Canadian T4s: See Customer Note 12.2.9 for recent corrections to T4 fields.
PR Export Custom: See Customer Note 12.1.13 for custom changes to the Paychex format.
Generate Recurring Labor Journal: Correctly identifies all eligible Recurring entries. Previously, entries were skipped if the Employee Start/End Date fell within the Payroll Period's Effective Dates.
Labor to GL Accruals: Corrects a sporadic problem where changing certain values (Hours, Pay Type, etc) didn't always cause the GL Accrual Info to be recalculated.
Payroll Period New Field - Accrue Bonus Pay: Flag this box if Bonus Pay entered for this Payroll Period should be accrued. See Customer Note 12.10.2 for details on usage.
When entering certain Status values, ServiceChannel prefers a CHECK element within the CALL XML. See Customer Note 20.2.9 for the Registry options to enable this functionality.
Reverse Posted Invoices: This release supports the automatic resending of the re-invoiced invoices. See Customer Note 20.5 for details.
Incorrectly configured ServiceChannel responses now place a diagnostic message in the offending message record. The invalid response is otherwise ignored so posting is not interrupted.
Create PM WOs: When the TechServiceParts=No registry is enabled and Service Parts and Tasks are specified, the Tasks now correctly written to the WO Equipment Work Requested.
New Call:
The Site's Service Manager is no longer cleared when changing the Job changes the Client. Corrects a problem when the sys-newcall option ServiceManagerBasedOnSite=true.
Registry to Omit Market Source when Creating New Site Record; Customer Note 16.1.1a.
Site Equipment:
List: New Sort Order: ClientSiteEquipmentByIdByBarcode
New Field Range: Bar Code
Work Order:
See Customer Note 16.1.5 for a registry to deny manual entry of negative Inventory lines.
Corrects an error adding a Call Script for the second (or greater) Equipment on the WO.
Create PM WOs: Refines setting of PO Status; see Customer Note 22.1.2.
Software Expiration Warnings: See Customer Note 1.1.1 for a registry to limit SAMPro expiration warnings to selected Users/User Groups.
Id Lookup : Improved performance when an Id-lookup list is initially opened or resorted.
SAMPro Upgrade Processing: For SQL Server database users, SAMPro will check for database table change rights and uncommitted transactions to ensure a successful database conversion.
Reports: This release supports the Global Registry to enable the Windows Printer Dialog for all reports instead of the SAMPro printer list. See Customer Note 1.3.2 for details.
Equipment created from the Timesheet is now assigned Security from the Site if applicable.
Start TechAnywhere Post: To improve performance, the Post now applies a 90 Day cutoff date for documents so that it no longer attempts to archive documents which can likely never be archived.
New Call: When a Work Order is created in TechAnywhere, its Client and Sub NTE fields now default from the Site Equipment record. If these fields are blank in the Equipment record they will default from the Site record.
The Report Vendor Payment History (VNDRPYMNTS.rpt) dated 2017-01-26 was revised to display the 1099 Category of each Vendor. You may also filter on the 1099 Category in this report.
AP Journal: This release refines the allocation of line item Tax Cost credit amounts to Tax Authorities; this will correct a GST/PST issue with Canadian (and some other) installations. A Tax Authority only qualifies for inclusion in the allocation when EITHER of the following is true:
1. The APJ line's Tax Type is Use.
2. The Group Tax Authority line's Job Cost flag is True.
AP Journal: This release closes a loophole which allowed users to voucher Credit PO's multiple times.
AP Checks: This release corrects sporadic locking issues when various users attempted to print AP Checks for different securities at the same time.
Cash Receipts Journal / Invoice Master:
When an Unapplied Deposit is entered, the Invoice Master Entry Type is now set to Unapplied; it was previously set to Credit Memo or Unknown.
When a database conversion is triggered, previously entered Unapplied Deposits will have their Effective Date, Entry Type and Status reset to the new values.
KPI Definition Import: This release corrects an issue where this function would sometimes fail.
DBSellPoint is a point of sales app developed to handle over the counter and retail sales transactions for SAMPro. See Customer Note 25 for details on this new application.
Compute GMP Special Revenue: When this function is run via Record Billing Adjustments entry the Job Journal Transaction Type is correctly set to Actual when GMP Job History Lines are generated.
Create PM Invoices: See Customer Release Note 9.1.2 for a new registry to default the Service Account Manager from the Site to PM Invoices.
Avalara Sales Tax: In this release, zero tax rates updates are properly accounted for when existing Tax Group records are updated. See 9.11.1 for details and important information on filtering updates.
Sales Tax Authority: The system now incorporates Sales Tax Authority GL Entities into credit-side tax cost processing when the GL Entity is not set from other sources. See Customer Note 912.1 for details.
Inventory Receipt Summary Tab: This new tab displays the expected Vendor Invoice Cost. Expected Vendor Tax is also shown if a Tax Group with "job costed" authorities exists on the PO. This tab may be disabled if the cost should not be displayed. See Customer Notes 5.7.1 and 5.7.2.
Inventory Adjustment Journal: This release corrects posting to GLH if single company Intercompany is enabled. Previously, this posting was only correct if the AppliedBurdenGLAccountId was enabled.
View Inventory Restock: Corrects an error with the List Sort Order RestockListByToByFrom.
Inventory Physical Count: The Inventory module must be enabled in order to access this function.
Compute Payroll:
Corrects an issue with PTO $$ Accruals when pay rate calculations are enabled via the global registry option LaborRatesAndAccrualMethod set to 7687.
Refinements to Extra Withholding - see Customer Note 12.6.1.
Override Job Cost Entity with Employee Entity: These global registries provide specific overrides to the labor line GL Entity which normally defaults from the Job Cost Code:
Burden Not Costed (Customer Note 12.1.7)
Indirect Burden (Customer Note 12.1.8)
Indirect Standard Cost (Customer Note 12.1.9
Direct Wages Not Costed (Customer Note 12.1.10)
Registry to Specify Exceptions to Taxable Fringes: This release implements registry-controlled refinements for the Earnings record's Taxable flag; see Customer Release Note 12.1.11 for details.
TimeAnywhere: Enhancement to support Process TimeAnywhere Files in a Sybase environment.
Custom PR ADP Export: See Customer Note 12.1.12 for details on the new format ADPKaback.
Quote Viewer Scope Tab and Quote Scope Viewer Scheduling Tab:
Opened By - Date Opened - Time Opened: Previously, these fields were updated with the current User, Date and Time if a Scope was reopened. Now they are only set when the Scope is created.
Quote Scope Main Tab
Clicking this new button accesses the Scope's Quote Manager record.
Quote Approval Wizard: The Quote's Service Category defaults the new WO's Service Category. If the Quote's Service Category is empty, the new WO's will continue to default from the Work Code.
Required Resource Wizard: Corrects sporadic problems with Inventory line consolidation.
Scheduled Report: Previously, installing a revised report for a scheduled report could result in messages / errors. These issues are corrected so that the revised scheduled report runs properly.
See Customer Note 20.2.6 a new registry to disable sending ETA updates to ServiceChannel (also supported for FacilitySource and Corrigo.
See Customer Note 20.2.7 for a registry to disable updating SAMPro Work Order Status from Service Channel IVR Messages.
In this release, we prohibit SAMPro from updating a Work Order's status in response to an inbound IVR status change message for ‘Cancelled’ and ‘Billed’ Work Orders. See Customer Note 20.2.8 for additional details and a registry to adjust this behavior.
Create PM Work Orders: See Customer Release Note 16.1.4 for a new registry to default the Service Account Manager from the Site to PM Work Orders.
Client Site Service Tab: The new IVR Instructions field may be used in escalation emails (using the token ^clntste_ivr^) to the Technician. It is also designed for future use in TechAnywhere.
Dispatch Board: When the Tech Lists button is clicked, the Dispatch Board Id and Name will both appear when the list of Dispatch Boards is displayed.
Escalation Profile: The new ^workperformedall^ token displays the Equipment Id, Name and Work Performed of all Equipment lines on the Work Order when the Scheduled Event is executed.
Fleetmatics: Corrects a formatting issue which prevented GPS stops from getting to Fleetmatics.
Maintenance Service Authorization (Custom): Adds new field and corrects issue cancelling alarms.
Master Contract: If the Service Task List is blank on the Master Contract Schedule Tab, the system now looks to see if one is specified in the Site Equipment and uses that instead. Customer Note 16.5.3.
New Call 2: The Original Caller field has been added. It defaults from the Site Contact 1 or 2 fields, but may be changed by the user; it will be written to the Work Order's Original Caller field.
New Call 2 New COD:
The Original Caller field has been added. If entered by the user, it will be written to the Work Order's Original Caller field.
The Quote Report Id (QuoteDefaults tab) and the GL Entity Id (COP tab) are now defaulted from the Client Site template to the new Client Site created by this function.
Project Work Order Generator: See Customer Note 16.15.1-4 for details on this new function which allows a whole 'Project' of Work Orders to be generated. This function also supports Work Order Milestones via the new Milestone Group.
Work Order:
Minor field position changes on the Main Tab minimize scrolling; Customer Note 16.3.7.1.
GL Entities are now properly set when Work Order Labor lines were edited.
Technician Web Access Tab: In version 9.1.609.027 and above, the Remote Device Type must be set to the new value of SubAnywhere on the Technician Web Access tab to trigger the processing needed for SubAnywhere Techs. See Customer Note 22.1.1 for details.
Equipment created from the Timesheet is now assigned Security from the Site if applicable.
AR Cash Receipts Journal: This release refines the setting of the Invoice Master Record when an Unapplied Deposit is entered. See Customer Note 6.3.3 for details.
Client Site List: The new Sort Order ClientSitesByIdByRn lets the user sort by the Client Site Rn column. This allows the list to be sort by the newest/oldest record added.
Report Journal Listing GL Entries: The report (RGLJRNL.rpt) dated 2016-12-16 fixes a sporadic issue where the report did not match the GL Journal viewer total debits and credits.
Start Job Invoice Reverse: Enhancements provide new Invoice Reversal Effective Date, Accounting Period and Description fields which are written to the Invoice Master. See Customer Note 9.9-10.0.
Start Recompute T&M Revenue: Previously named Start Recompute Unbilled T&M Revenue Values, this function has been enhanced to include previously billed historical data. It is designed to retroactively apply Rate Schedule rates and default Billing Items to already-posted JCH data for a Construction Job.
Report Sales Summary by Sales Rep: Revised report (RSLSSMMRYSLSRP) dated 2016-12-20 correctly displays the current year's sales amount if more than one Sales Rep is specified on the Commissions tab of the Job by taking the share percentage into consideration.
Report Job Cost Details – Direct: This new report (RJBDTLDRCT.rpt dated 2017-01-10) resembles the original Report Job Billing Details but skips all overhead jobs in order to prevent typical users from running the report for indirect overhead jobs and seeing confidential data.
Classic Board: Corrects an 'argument must be a collection' error launching TechFinder.
New Call:
Corrects a recent performance slowdown loading New Call.
Ctrl-A is ignored instead of generating an error. The Add WO button must be clicked to add the Work Order.
New Call (FMMS):
The NTE amount from the selected Service Request now defaults to the NTE Client field which will populate the corresponding field in the newly created Work Order.
Also fixes an error accessing the FMMSInfo table when the Vendor Value includes an apostrophe (e.g. "Domino's").
Corrects issues in the FacilitySource integration when selecting the web log.
Login: Corrects a 'failed to set read permissions for user' error logging in with an SQL 2008 database.
Events Managers: The Dashboard, Point Of Sale, Reports, Scheduled Events and TechAnywhere Events Managers have been refined to better handle recurring events that have been interrupted and need re-scheduled.
TechAnywhere PO Receipt Post: This Post now adjusts the Accounting Period match the Effective Date if possible. The registry entry detailed in Customer Note 19.3.1 may be use to instead set the Effective Date to fall within the Default Accounting Period.
Registry to Attach TechAnywhere Collateral Files to the Job Record: See Customer Note 19.1.1.
Cash Receipts: 'Receipts Entered' field is correctly updated when Other Tab lines are added or deleted.
Client Site: Five new User fields (Client Site User 6-10) added for use with reporting, analytics, etc.
Job Cost Code Main Tab: If the new Obsolete? field is checked, the record is considered Obsolete, and it may not be directly specified during data entry.
Job Billing Item Main Tab: If the new Obsolete? field is checked, the record is considered Obsolete, and it may not be directly specified during data entry.
Report Sales Summary by Sales Rep: Revised report (RSLSSMMRYSLSRP) dated 2016-12-20 correctly displays the current year's sales amount if more than one Sales Rep is specified on the Commissions tab of the Job by taking the share percentage into consideration.
Employee Rate Test Tab: This release corrects timing issues that could cause the GL Entity Id to be omitted when GLH distributions were calculated.
Labor Journal: Corrects a spurious 'Please clear line '#' and re-enter Bonus Amount') message when using Insert/Copy to enter multiple lines with the Bonus field completed.
Approval Wizard: Registry to Not Update Work Order NTE Amount; Customer Note 14.1.1.
Logon: Corrects sporadic 'trimblanks not understood' error.
Job Viewer Import WBS Button: Compute JCH Unbilled Revenue now runs during the import so that when a Billing Item is created or updated the Cost Code and Billing Items will be re-aligned if needed.
Contact Quotes Tab: Double clicking on a line launches Quote Manager instead of Quote Master.
Asset Viewer: See Customer Note 24.3 for details on using User Fields 1-5 to set Equipment fields when creating new Equipment records via the Create New Equipment button.
Exporting / Importing a User's dashboard profiles now works correctly with List type Analytics.
Job Cost Category - New Fields User3-5:
These fields are designed for use with web-based PO processing if implemented on your system.
Project Manager Workbench: Corrects an error when deleting a line from the Contacts tab.
Labor Journal Hours Tab:
If Start and Stop Times are display via customization, the Billable Hours field now appears to the right of Actual Hours. Billable Hours will also appear on the Detail view.
Resolves JCH rounding issues when registry in customer Note 12.1.5 is enabled.
Labor-to-GL Accruals: Refines calculations of percentage-based wages, fringes, standard cost and burden.
Compute Payroll:
The pay method is forced to 'flat' when hours = 0 and pay amount <> 0 to overcome a sporadic Labor Journal issue.
If a Pay Type is flagged as Union Exempt, the Employee's Earnings Group will NOT be written to PR History so that Union Exempt Pay Types will not appear on Union reports.
Pay Type Viewer: The Fringe Exempt field has been relabeled as Union Exempt.
Create PM WOs: A new registry to override the status of PM Work Orders with ReqResource Parts is detailed in Customer Note 16.1.8a.
AP Journal: Corrects error when an entry for a PO with Subcontract lines is edited.
See Customer Notes 3.1.1a and 12.1.6 for AP and Payroll for the TD80 support registries.
Opportunity Viewer: The new Contacts tab allows multiple Contracts to be associated with each opportunity. See Customer Note 15.1.1 for details.
Corrects a problem in certain Drilldown reports (including DGLHSTRY.rpt - Report GL History by Account) where the Drilldown displayed a blank page.
Service Invoice: The revised Service Invoice and this release support registries to skip printing and/or emailing service invoices with a negative total. See Customer Note 9.1.2b for registry details.
Quote Manager: Corrects a problem in the Approval Wizard where the Scope of Services text written to the WO Work Requested (if enabled via registry) was converted to all lowercase.
Master Contract: The new Original Start Date field may be used to record the original Start Date of this Contract.
Taylor UWOs: Dates and times entered on the Main tab are now correctly copied to the UWO tab.
Technician Viewer: New RAQ Group and User fields have been added for TechAnywhere use.
Work Order:
Call Script Tab: The new Tech Id field is set for TechAnywhere updates.
Expanded Fields: The Work Order Work Requested and Performed, and the Work Order Equipment Work Requested, and Performed have been expanded from 3000 to 6000 characters.
Supports the I.14 Service Channel Invoice (Customer Note 20.1.5 has the registry details).
Corrects Out of Memory Error when Posting Large Messages.
AP Journal: A 'Requires Approval' override is available if 1) requires approval would be set via a registry AND 2) the User has access to Start AP Payment Approved List. Customer Note 3.3.6.
COP Invoice: If multiple AR Control GL Account exist, the AR Control Account will not when Report COP Invoice is run. See Customer Note 23.1.1 for a registry to default the Account.
Burden Allocation for Overhead Labor: New registry option to accrue burden for overhead labor without forcing Burden GL to use Wage GL. Customer Note 12.1.4.
Match Job Cost / GL Accrual of Labor: Customer Note 12.1.5 has this new registry option.
Employee Viewer Rate Test Tab: The new Select Rate Method to Test field allows the user to compare results under different costing/accrual methodologies. See Customer Note 12.5.2.
WO Labor, Labor Journal: Previously accruals were skipped for Standard Cost type Earnings when an Overhead Job was specified. Accruals are now correctly posted for Jobs that are not Direct.
Pay Type: In previous releases, Pay Types marked as Union Exempt still showed up on the Union Reports. See Customer Note 12.13.1.
Purchase Order Subcontractor Tab: If completed, the Tax Group on the PO header is now carried to Subcontractor tab for Tax Cost calculations. See Customer Note 4.3.4 for details.
Quote Scope: This release corrects a sporadic 'Record Not Found' error when attempting to change the Equipment Id in a previously saved Quote Scope record.
The COMPL_DATETIME will be sent to ServiceChannel for status change messages beginning with 'COMPLETED'. COMPL_DATETIME comes the Tech Tab's scheduled date and time.
Dispatch Board: Work Order changes are only allowed from the Dispatch Board if the User belongs to a Group with Change permission for View Work Order or Work Order Dispatcher.
AP Journal:
The Add Taxes buttons now splits taxes correctly between the GL Accounts referenced in the Tax Group's Authorities.
Registry to Allow Vendor Billings to Exceed Earnings on Sub PO's. Customer Note 3.1.4.
AP Journal Subcontractor Tab:
When a PO is partially vouchered and the Amount is changed, the Revenue is now correctly recalculated based on the new Amount.
If a PO is generated without an Other Rate Id, when it is partially vouchered will change the Bill Type ID to n/a and remove the Revenue Rate. See Customer Note 9.6.1 for an Other Rate Tab configuration tip to avoid this problem.
AP Payment Approval: Start AP Payment Approved and Start AP Payment Approved PM now classify AP Retainage properly.
Report Unvouchered AP Summary (RUNVCHRDAP3): Report revised 2016-06-15 adds ending date header and corrections to page header.
Start AP Payment Approved List: New field to limit this function to Overhead Jobs; new Job Id range. See Customer Note 3.9 for details.
Start Create EOM Unvouchered AP GL Entries:
New registry defaults Date Closed range for only PO's; See Customer Note 3.1.2.
Enhancements reduces PO-GEN line issues caused by editing WO-Other Descriptions.
GEN lines from Credit POs are ignored unless the line's Receipted-to-JCH flag is true.
Vendor:
Defaults Tab: A new 1 Invoice Per Check? field has been added to the Defaults tab. See Customer Note 3.8.1 for details on using this functionality.
Vendor Insurance Tab: This tab is now automatically sorted in descending order by the End Date. The most recent dated Insurance Entries will appear at the top of the tab.
AR Cash Receipts Journal:
Tab Mismatch functionality has been added.
Credit refunds may now be processed via Open Edge / XCharge. See Customer Note 6.3.2 for details.
Clearing a previously selected Cash Receipt in an existing Bank Deposit makes that Cash Receipt eligible for editing. The update from that Cash Receipt is now more selective so that previously changed Bank Deposit lines are not impacted.
Avalara Sales Tax: This release corrects an issue where existing Tax Groups were not always updated by the Start Avalara Import function.
Client Collections Screen:
Clicking this button launches Report Customer Statements. A registry may be specified to launch a different report; Customer Release Note 2.5.1.
Credit Card Processing: The OpenEdge (XCharge) Transaction Id is now referenced in the Work Order COD, AR Cash Receipts, and AR History records, when posting COD Service Invoices (where the alias is set) to the AR Cash Receipts Journal.
Drilldown Service Profitability Component Report: The revised component report CSERPFT1.rpt dated 2016-09-28 corrects an error when drilling down from the Drill Service Profitability report.
Report AR Aging: The revised report (DARAGE.rpt) dated 2016-04-05 gets the PO from the Work Order if the PO is blank in the invoice. Provides new option to Show Collection Notes.
Report AR Sales Journal Post Summary (RARSLSJRNLPSTNG.rpt): The revised report dated 2016-09-26 supports Report Totals Debit Amounts exceeding $9,999,999.
Report Credit Card Expiration: This new report lists upcoming Credit Card Expiration dates in the Client Site. See Customer Note 7.6.4 for details.
Report Credit Card Expiration for Master Contract: This new report lists upcoming Credit Card Expiration dates in the Master Contract Site list. See Customer Note 6.2.5 for details.
Report Customer Statements: Revised report includes a Print Zero Balance Statements option and registry to customize the text. See Customer Note 6.2.2b. Also adds an option to Omit Invoice Description.
Report Customer Statements 2: Revised report includes a Print Zero Balance Statements option and registry to customize the text. See Customer Note 6.2.3.
Emailing Reports: SAMPro's Email form supports an expanded Message field of 1200 characters to allow the contents of a Common Phase to be included.
Documents:
Validation now requires that the Document File Location exists (Add mode). In Change mode, either the Document File Location or the Archive Location must exist.
Supports use of the File Location field to store a web address. See Customer Release Note 1.5.3 for details.
Corrects a display issue with double-keyed records (e.g., Site Equipment) so that the Reference Name always defaults from the specified record.
Document Archive Maintenance:
Now puts convertedDBRs in the root of the document\archive\convertedDBRs with subfoldering (YYYY-MM) if it is enabled.
The new Days Past to Check PDF Archives field controls the functionality which converts documents from XML to PDF. Customer Note 1.5.2.
MS SQL Server Conversion: When MS SQL Server databases are upgraded, the main primary key index will be changed from a nonclustered to a clustered index to enhance database performance. See Customer Note 1.26.
Quick Attach: Supports additional document references in the PO, Inventory Receipts, Inventor Adjustments, and Cash Receipts Journals. See Customer Note 1.10.2a.
Record List Panes: Performance enhancement when record lists are accessed and resorted.
Registry: The child pane is now sorted alphabetically by the Additional Contents field when it is saved. Disabled rows (which begin with an 'x') are grouped together at or near the bottom of the list.
Saved Reports and Bitmaps: This release enhances the logic used to find a bitmap logo to display on a saved SAMPro report if it is not found in the original location (e.g., after a server move). See Customer Release Notes 1.2.2 for details.
Security Override: A new registry allows the user to set restrictions for a security(ies) to be hidden as a global registry but allow user specific registries to allow certain users access to the blocked security(ies). Customer Note 1.1.5.
User Security: Corrects a 'Key is Missing' error when the user switches security where the Group Id is blank on the Additional Profiles tab of the User record.
User Viewer:
Disabling a User Account now terminates any active sessions the User is running. See Customer Note 1.8.2 for detail.
UserLogonSummary Tab: This new tab lists the SAMPro versions this User has logged onto, and shows if they are currently using the software. Customer Note 1.8.3.
Viewers: The mouse's scroll wheel is supported in 'textbox' fields. To use: Select the field on the screen; position the mouse cursor over the field and then scroll with the mouse wheel.
GL Report Row Layout: To print Underlines below totals see Customer Note 10.2.4.
GL Income Report: corrects display issue when this report is held open.
Compute Corporate Metrics: See Customer Note 5.1.3 for a registry to refine the Inventory so that if an item’s on-hand quantity is <=0 AND the transaction will reduce the quantity on hand further, then do not use the transaction in the turns calculation.
Inventory Adjustments Journal: When Location adjustments are edited, the GL Account and Entity from the Inventory Item's Group are updated if needed when the Inventory Item is changed.
Inventory Item Stock Status: Changed Field: Unit Cost (was Average Cost): The Cost displayed is based on the Item's Cost Method. The label has been changed to the generic Unit Cost.
Inventory Item:
See Customer Note 5.1.2 for a registry to limit writing to the Inventory Vendor Tab to Purchasing Agents.
The user is allowed to clear the Superceded By field. However, clearing the field does not clear the Inactive flag which may have been set manually or via registry.
Inventory Item Locations Tab (detail view): New Field: Obsolete - This field will be flagged if the Location referenced on this line is Obsolete.
Inventory Receipts Journal: Corrects a sporadic problem where clicking the "Auto Set Qty Rec'd" button did not always complete the Location fields.
Inventory Restock: Corrects 'receiver is not a boolean' error when accessing an Inventory Restock record and immediately clicking the Print Pick Ticket button.
Restock Pick List Report: This report is now ordered by the Bin/Location and then the Inventory Id. The Transaction Id and Date Printed have been added to the report.
Start Import IM Adjustments: This new function imports Inventory Adjustment entries from a Database table or a csv file. See Customer Note 5.8 for details.
Location Viewer: Special handling of the Obsolete flag provides the option of removing items with zero quantities from the Inventory Item''s Locations tab. See Customer Note 5.6.2 for details.
Consolidated Invoice: Correction and enhancements; see Customer Notes 9.5.1-2.
Construction Invoicing (RININV3): Enhanced to show billed retainage as a positive number with the label 'Billed Retainage'. Also supports a registry option to override the 'Billed Retainage' label (for Canadian users). See Customer Note 9.2.2 for details.
Invoices Tabs: Support revenue type "n/a" in the Invoices tab of the following viewers: Job; Project Manager; PM Workbench; Billing Item; and Work Order.
Record Billing Adjustments: Security Id from the Job is used when creating the Invoice Master.
Rate Schedule: When the Rate Schedule is saved, the detail lines are re-ordered with the most recent entries at the top. Validation prevents overlapping date ranges and gaps.
Report Service Invoice (SERVICEINVOICEv90b028.rpt):
Revised 2016-04-05. Added PO Id to AR Summary section.
See Customer Note 8.1.2 for a registry option which enables users to skip the physical printing of zero dollar service invoices.
Record Billing Adjustments: This function now automatically restarts at the Job Id input screen after clicking Save. Clicking the red X closes the function so it will not reopen.
Recompute Unbilled JCH T&M Revenue Values: Corrects error when evaluating revenue adjustment lines.
Start Compute GMP Special Revenue: This function now sets the Job Journal Transaction Type ('Actual') correcting a recent issues where it was set to 'Unknown'.
Job:
Create PO Button: When this button is clicked, the caret will be positioned in the Vendor Id when the PO is opened to save keystrokes.
The new JobByProjectDescriptionByJobId option on the Job List's Sort Order Pane displays: Project Description - Project Id - Job Id - Job Name - Site Id - Site Name.
The user is now warned when changing the Overhead? flag on a Job which has non-zero Job History. See Customer Note 8.1.5 for a registry to change the warning to an error to prevent this change.
Job Journal:
Tab Mismatch logic has been refined to consider all versions (base,-01,-02,etc) when determining if the post to GL will be in balance.
See Customer Note 8.5.3 for additional Inter-Company support.
Budget / Budget Change entries do not require Accounting Period / Date validation; only 'Actual' type entries do. The Transaction Type CANNOT be changed once data has been entered on child lines.
Co Equip Tab: Registry To Require Net Zero Costing (Customer Note 8.1.3).
Main Tab: The default Transaction Type is now set to 'Unknown', forcing the user to decide on the Transaction Type before entering detail lines. Custom Field functionality may be used to set the default Transaction Type to 'Actual' if preferred.
Expenses Tab: Now supports Cost Categories with a Selection Type of Equipment.
Job Scheduling - New Module: The Job Scheduling module allows Installation Work Orders to be generated from the Job's WO Creator tab (enabled via registry). See Customer Note 11 for details.
Project Manager Workbench Contract Items Tab: The right-click 'Quick Edit' functionality has been disabled for GMP-type Jobs.
Report Job Billing Report (RBLLRPT.rpt): The revised report (AKA Report Job Billing Recap) dated 2016-03-31 supports Security Id processing and corrects an issue which caused it to 'hang' in some environments.
Report Profitability by Client (DCPFTRv73b029.rpt): The revised report dated 10-19-2016 enhances how the billed costs are calculated for the Labor, Material, Other, and Subcontract columns at the Client, Client Site, and Bill Item Summary levels.
Compute Payroll:
Corrects a sporadic virtual stack overflow error when OT Premiums are allocated.
GL transaction activity related to the Compute Overtime function has been refined so that transaction effective dates match work dates.
Supports Intercompany processing for employer taxes (etc) allocated during the compute.
Labor Journal - New Button:
If an employee's pay (earnings) rate was changed mid-pay period after time has been entered, clicking this button recomputes each line; see Customer Note 12.17.2.
Labor to GL Accruals: Registry to Use Employee Entity for Earnings Not Costed. See Customer Note 12.1.3.
Payroll Period: The Hours tab is now filtered based on the User's Executive PR and Branch Filter fields. See Customer Note 12.10.1 for details.
PR Miscellaneous Deduction Checks: The Vendor correctly writes to the Check record when multiple Vendors are included in the Check run.
Revised Report Payroll GL Accounts: The revised Report Payroll GL Accounts (RPRGLAC.rpt) dated 2016-06-10 includes a new GL Account range.
Start ADP Import Payroll
Start Payroll GL Import
Enhanced to deny the import of blank GL Entity codes if Inter-Company is enabled. Also includes validation for debits = credits by Company if Inter-Company is enabled.
T4 Forms: Corrects an issue with the Employer EI Premium being overstated on the T4 Summary.
Purchase Order:
Corrects spurious Tab Mismatch errors encountered when a PO is created or edited for a foreign currency Vendor (Currency Id set in Vendor record).
The new Receive button on the top button bar launches the Inventory Receipts Journal with a new transaction started for the selected PO.
Quote Scope Viewer:
New button recomputes non-fixed prices. Changing the Rate Schedule, Gross Margin or Markup now automatically recomputes prices. Customer Note 14.5.3.
Allows a Scope to be copied from any Quote. Customer Note 14.5.3.
Tax Group Id: Tax Status: These fields are only used for determining estimated tax on the Quote report. When the Approval Wizard is run, the Job's Tax Status and Tax Group will be used when writing lines to the Work Order.
The user will now be prevented from entering an Inactive Vendor on the Scope's Materials, Inventory or Subcontractor tabs.
New Scopes automatically default the Job's Revenue Adjustment Id. If a Work Order with a single piece of Equipment is specified, the Equipment Id also defaults on new Scopes.
Print Quote: Corrects a sporadic issue where the Quote Id did not auto-fill when the Print Quote button was clicked.
Report Quote: This release and the revised Quote Report correct a number of issues with printing Estimated Sales Tax. See Customer Release Note 14.2.1.
Approval Wizard:
When the Approval Wizard is run, the Tax Group and Tax Status in the selected Job are now used to when generating Work Order detail lines.
When a Work Order is created/updated from Quote/Quote Manager, the Sub NTE and Client NTE are set from the approved options. See Customer Note 14.7.1
Since Payroll Period validation is not applicable to WO Labor flagged as Quoted, the Approval Wizard ignores this validation when generating WO Labor lines.
If a Vendor is Inactive, the user is alerted and the Wizard is blocked.
When the Approval Wizard writes back to the source Work Order, the Work Code on existing Equipment tab entries is retained. The Work Code from Quote / Quote Manager sets the Work Code on newly generated Equipment lines.
The Service Evaluation defaults from the Scope's Equipment the Approval Wizard generates a new WO.
Classic/Day Board:
Corrects an overlap issue that made it difficult to click the left arrow to change the Date Scheduled. The Date Range button has been added to the Classic and Day boards.
Corrects a sporadic 'system primitive failed' runtime error when occurred when the Tech Id was changed on the WO Summary (lower section).
Escalation Management:
Manager Review: This new Technician Status follows Invoice Ready in the Escalation hierarchy; see Customer Note 16.20.1 for details.
Caller Specific Email for Escalation Rules: See Customer Release Note 16.10.2 to learn how the new Work Order Email Address field can be used in Scheduled Events.
Escalation Profile Detail View: When the new Disabled? field is flagged, this event will be ignored when scheduled events are generated for a new Weblog or Work Order. See Customer Note 16.6.1.
Fleetmatics:
Revised handling of the cancellation of a schedule date, and direction request to be compatible with the Fleetmatics work order format.
All Work Order Technician lines are now sent to Fleetmatics.
The schedule date is appended to the end of the WorkOrderID sent to Fleetmatics.
Master Contract: Corrects a "selected record not found" error when selecting a Master Contract from a list displaying an Agreement Type Id which exceeded 10 characters.
New Call:
Master Contract: Refines handling of the middle pane so that the Client Site List (and not the Master Contract pane) is displayed after the user completes a Call Script.
Weblogs: See Customer Note 16.10.1 for details on an enhancement which allows Weblogs from TechAnywhere to be assigned to existing Work Orders.
Subcontractor POs: New registry allows the Date or Accounting Period to be adjusted to keep them in sync for POs generated from New Call. Customer Note 4.1.1.
Report PM Agreement Summary (RPMAGRMNT): Report revised 2016-06-14 fixes alignments in the Invoice section of the report.
Revised Report: Work Order Field Ticket Standard (woticket-db.rpt)
Report dated 2016-02-25 adds Skip PO Summary and multi-page textbox processing,
Start Archive Work Order:
The new Date Completed field allows the user to include only those Work Orders whose Date Work Completed falls on or before the selected date.
If the WO's Date Work Completed is set, it is now used for the archived Tech line. If the Date Work Completed is not set, the archived Tech line has today's date, as before.
Start Scheduled Event Purge: Now purges scheduled events for archived WO's.
Start Create PM WOs:
Corrects a sporadic issue with this function hanging when a single site was selected.
Registry to Override NewWorkOrderStatus for Preventative Maintenance Work Orders (see Customer Release Note 16.1.2 for details).
This function also generates a PO for Subcontractor Techs. In this release, the Site Equipment being serviced is completed on the PO's Gen line.
Taylor UWO: Implements the 2014 extensions to the Taylor UWO subsystem. Also Encodes Trouble Found with leading zeroes on Replacement as well as Original parts.
Work Order:
Required Resources Wizard: Streamlines consolidation messages and lists consolidated items. See Customer Note 16.3.4b.
Create PO Button: When this button is clicked, the caret will be positioned in the Vendor Id when the PO is opened to save keystrokes.
Main Tab: The Email address from the Site's upper Contacts tab is now displayed below the Site's Phone and Fax numbers.
Import Costs: Imported Material and Other lines now retain their Job information even when DefaultJobByEquipmentId is enabled.
Other Tab: Lines for Fixed Fee Billing Items (for Use Tax Jobs) flagged as Extra now have the Use tax factored in when the Revenue is calculated. The Tax Cost is also set when a Standard Cost Other Rate is selected.
Import Flat Rate: If the registry DeferTaxStatusDecision is set to true, the Revenue line now imports correctly. Previously, only the costs were imported.
Performance: The Gross Margin is no longer calculated if the Work Order or Job Id is empty to improve time loading the empty Work Order viewer.
This release modifies the computation of DATETIME so that it can not be earlier than SCHED_DATETIME to conform with recent ServiceChannel validations.
The Work Order's NTE is now set correctly when it is created from a ServiceChannel Service Request (WebLog) processed in New Call.
See Customer Note 20.1.3 for a ServiceChannel Registry To Copy the ServiceChannel SCHED_DATETIME to the Work Orders' Date and Time Must Complete fields.
See Customer Note 20.1.4 for a registry option To Upload Equipment Work Performed Notes on Status Change.
If a Work Order is integrated with ServiceChannel, this button appears on its Documents to simplify the upload of attachments. See Customer Note 20.3.
New Call: When a Work Order is generated from a ServiceChannel Service Request, the WO's Not To Exceed value is now set as per the Service Request's NTE attribute.
Registries: Set the Work Code from Service Channel's Priority, and the Equipment from the Trade Code; exclude Service Channel's Date/Time Scheduled (Customer Notes 20.1.1-2).
This web-enabled module allows your Subs to access work assignments, record negotiated charges, enter quotes and more. See Customer Release Note 22.
PO generated in TechAnywhere now have their Company / Security set from the Work Order that the material was purchased for.
This release corrects a problem in the TechAnywhere Post cause by the override of the Labor Rate by the Job Cost Category.
The Tax Type is now set correctly when Flat Rates are posted from TechAnywhere.
This release makes the determination of a TA PO's posting style more accurate.
The TechAnywhere Post now assigns the Client Site Security to the new piece of equipment added by TechAnywhere.
TimeAnywhere Labor: The Transaction Id now displays the latest Labor Journal entry associated with this record. The View button opens the most recent Labor Journal Transaction.