Contains release notes for SRM (Systematic Rental Management) for the 2020 calendar year.
These release notes address new features and code fixes for the standard release of SRM (Systematic Rental Management) as of 2020. Notes are categorized as either Enhancements (new components or features) or Corrections (bug fixes).
All changes will be fully laid out in the Help Center, located at www.help.texadasoftware.com, following the release.
Click here to learn more about the technical requirements for SRM.
Quick Navigation
- March 2020 - 10.1.2001 Release Notes
- April 2020 - 10.1.2002 Release Notes
- July 2020 - 10.1.2003 Release Notes
- October 2020 - 10.1.2004 Release Notes
October 2020
Version 10.1.2004
| Accounts Receivable | ||
| Ticket # | Type | Description |
| SRM-1431 | Enhancement | An API has been created to enter a Customer Payment and apply the payment to posted unpaid invoices. |
| SRM-383 | With Texada Pay a “Payment Request” email can be sent to the Customer for posted Counter and Work Order invoices from the<Customer Account Inquiry> (ARAR05) and for unposted invoices from a [EMAIL FOR PAYMENT] button on the <Invoice Summary & Totals > (RSIH03) screen. The email that is generated provides the receiving Contact to view the Jasper Invoice and to immediately pay it through a link to Texada Pay. When Texada Pay is not activated this button generates the email with a link to the Texada Pay information & sign up web site. |
| Accounts Payable | ||
| Ticket # | Type | Description |
| SRM-1465 | Enhancement | When the invoices paid by an <AP Check> exceed the space provided on the check stub, an 'Overflow Remittance Advice' report is printed when that check is printed instead of requiring a Void check just for the overflow on the stub. |
| SRM-689 | Enhancement | The <Estimates> (WOEH01), <Work Orders> (WOWH01) & <Repairs> (WORT01) capture a currency code on the document header to pass to the “Repair History’ transactions for improved cost analysis. The Asset repair displays the Currency for the service expenses in the <Repair History Report> (WORT10), <Repair History Report By Product#> (WORT11), <Repair History Inquiry> (WORT05), and the <Print Repair Transactions> (WORT02). |
| General Ledger | ||
| Ticket # | Type | Description |
| SRM-1576 | Enhancement | The <Balance Sheet> (GLSL20) generated from summarized totals was truncating account amounts to 8 characters before the decimal on both the PDF and spreadsheet outputs instead of allowing 9 characters. |
| SRM-1265 | Correction | The Account descriptions were displaying incorrectly in the <Chart Of Accounts> (GLCA01) when the operator paged or arrowed through the screen in an Open Client session. |
| SRM-1115 | Enhancement | The <Post Standard Journals> (GLJH10) utility has been updated to provide the ability to post multiple journals on different dates in one batch by assigning the posting and accrual dates at the Journal level. |
| Counter | ||
| Ticket # | Type | Description |
| SRM-1610 | Enhancement | With the 'Enhanced Tax Codes' option, location tax codes can be loaded into the the <Tax Codes by Postal/ZIP> (DCTXPC01) table and into the <Tax> (ARTC01) table from the <Import Tax Codes by Postal/ZIP> (DCTXPC3) utility. |
| SRM-1580 | Correction | Adding a 'Contract Deposit' Refund with a negative dollar amount in the <Contract Totals and Summary> (RSCH03) screen was not being recognized as a Credit in Texada Pay. |
| SRM-1575 | Enhancement | When a <Contract> with an Authorized Texada Pay amount is closed and the <Rental Return> generates an Invoice for less than the Authorized amount, after any other Deposit Type SA amounts are applied only the amount required to cover the outstanding Invoice total is applied form the Authorized amount, changing the Deposit transaction from Type AU to SA. |
| SRM-1532 | Enhancement | The product 'Insurance' flag set in the <Make/Model Re-Order> (RSPFWIN1) window has been added to display in the <Off Rental By Contracts> (RSFR02) utility, the <Off Rental Summary Report> (RSFR20) and <Off Rental Inquiry> (RSFR06). The 'Australian Company Number' has been added to the <Export/Import Customer Information> (ARCF37) utility templates. |
| SRM-1487 | Enhancement | The billing rate of a <Service Code> transaction that has been auto-added to a <Contract> can be modified in <Contract Services> and changed to a Flat rate or changed to a Percent of rental with Min/Max restrictions if over-ride auto-service calculation is allowed on that Service Code. The <Contract Services> window on the document and in the inquiries displays an 'Automatic' status of Yes, or Override or blank if not auto-added. Invoices also display the 'Automatic' Service status but over-ride is not allowed on the Invoice. When an auto-added Service rate is changed on the Contract, an audit record is written to the <Override Log> (RSMPL10). |
| SRM-15 | Enhancement | A “Service” on a <Contract> can now trigger an order for the associated sales part on a <Purchase Order> whether the Service was manually added to the Contract or selected from the ‘List of Services’ checkbox window. |
| Back Office | ||
| Ticket # | Type | Description |
| SRM-1462 | Enhancement | When <Cycle Billed Invoices> are automatically paid by a Texada Pay Credit Card on file, the invoices were not being posted On Account and so they were not included on the <Customer's Statement>. |
| Inventory Control | ||
| Ticket # | Type | Description |
| SRM-1571 | Enhancement | <Appraisal Values> can be captured for non-bulk rentals including a Retirement flag and the Fair Market Value, the Orderly Liquidation Value, and the Forced Liquidation Value. These appraisal values are reflected in the spreadsheet output of the<Rental Age Report>, <Disposal Transactions Report>, and the <Inventory Clean-up Export/Import> utility. |
| SRM-1461 | Correction | The <Ship Internal Branch Transfer> (INDH02) was allowing a non-bulk product to be selected to replace a 'Group' on the transfer when that non-bulk product was already on another transfer. |
| Purchase Orders | ||
| Ticket # | Type | Description |
| SRM-1581 | Correction | New Products added through Purchase Orders were not showing in Counter Document Search results if the Tag was created in the warehouse receiving. |
| SRM-1514 | Enhancement | The printed <Purchase Order> header should print the primary Division address from <Divisions> (GLDV01) as this is the physical location of the store, as opposed to printing the secondary division used on Customer documents such as Invoices and Contracts that can be set up to be a 'Remit To' address. |
| Work Orders | ||
| Ticket # | Type | Description |
| SRM-1731 | Correction | Work Order Comments were not respecting the print flag when printed to Jasper from SRM or from an API |
| SRM-1391 | Enhancement | The <Work Order> Comments table has been increased to accept 250 characters per comment line, splitting lines at 60 characters to wrap on W.O. documents and the <Open W.O. Report> (WOWH08) and splitting lines at 80 characters to wrap on the <Work Order Report> (WOWH11). Each Comment line is assigned a UUID ( Universally Unique Identifier). |
| Reports | ||
| Ticket # | Type | Description |
| SRM-1489 | Correction | The <Standard Customer Revenue Report> (RSSH17) was not finding Customers when the report was filtered by a 'Customer Type' greater than two characters. |
| System Maintenance | ||
| Ticket # | Type | Description |
| SRM-1713 | Enhancement | A "Beta Applications" table has been added to <Company Texada Parameters> that controls the activation of new features in our Client's code. |
| SRM-1342 | Correction | The user information in FleetLogic was not being updated when an Operator was deleted in SRM unless other operator changes had also been entered. |
| SRM-1466 | Enhancement | The SRM 'Email Signature' format has been improved to support HTML as well as Text formatted signatures allowing links, images, and other HTML styling in the 'DEFAULT EMAIL SIGNATURE' panel of the <Company Email Configuration> setup. |
| Other | ||
| Ticket # | Component | Description |
| SRM-1609 | Data Management | An 'Issue' field to identify card types such as Visa or Mastercard has been added to the <Method of Payments> (ARMP01) table for FleetLogic to use with Texada Pay in order to submit only the Issuer in place of the payment method for Credit Card payment transactions. |
| SRM-1470 | New HTML Email Templates can be used for <Automated Email> (EMAIL) messages and 'Compose & Send' (EMAILIT) messages. | |
| SRM-1427 | jasper | The address fields on Jasper forms for Counter Documents have been lengthened to allow for a 30 character address fields in 'Ship To' & 'Bill To' sections. |
| SRM-1328 | Payment Processing | An authorize-only Texada Pay – Credit Card transaction captured in place of a Deposit on a Contract, can be canceled on the Contract without the card being present to VOID the Credit Card transaction. |
| SRM-1502 | Portal Management | A 'Booking ID' has been added to the new order details that are sent to SRM to identify requests sent from GateWay. This 'Booking ID' can be viewed on the <Portal Confirmation> (TXWO50) screen and can also be used in the search filters for the <Portal Confirmations Search> (TXCHSEL). |
| SRM-1325 | signature capture | Any Safety Sheets associated with the Contract are included in the email generated for a Signed Doc Email request. |
| SRM-1637 | Texada Pay | Texada Pay: To use a ‘Card on File’ to make a payment *FILE can be entered in the payment method field and then the Card or Bank information on file can be selected, so that MOP ‘F’ is no longer required. The API’s for Post Payment on a Current Invoice, Post Payment on a Customer’s Account, Capture a Card and Get a Card all to return the Method of Payment, the Card Type, and the Issuer in the response. |
July 2020
Version 10.1.2003
| Accounts Receivable | ||
| Ticket # | Type | Description |
| SRM-1413 | Correction | The <Statement Letter> (ARLT02) was throwing a parser fail error to the screen when letters were flagged to email even though the email was sent successfully. |
| SRM-1511 | Correction | When the payment history record did not get written to ARCH, an unposted Customer Payment could not be reversed in <Reverse A/R Payments> (ARCH25). |
| SRM-1306 | Correction | Credit Invoices created by reversing a standard Invoice in <Create Invoice From Existing Invoice> (RSCM02) were always printing to PDF from <Reprint Invoices> (RSIH10) instead of emailing to the Contact. |
| Accounts Payable | ||
| Ticket # | Type | Description |
| SRM-1513 | Enhancement | If an <AP Invoice> is created for the purchase of a Rental Asset and the assigned Fixed Asset Tag is missing wrong or deleted before posting, the entire <Post A/P Invoice> (APVI10) processing will fail to throw an Invalid Tag error to prevent any partial posting. The user must delete the offending A/P Invoice detail and re-enter it with a valid Tag. |
| SRM-1056 | Enhancement | An “Alternate Pay To” name & address can be defined in the “ Additional Information” window for a <Vendor> that when activated redirects payment sending checks directly to the customer’s Alt Payee suggest as his financier so that when an <A/P Payment> is made for that supplier the check is made out to and mailed to this designated payee. |
| SRM-1064 | Enhancement | The Excel export output option has been added to the <A/P Payment Report By Invoice> (APAC10) and the <A/P Payment Report By Check> (APAC15). |
| SRM-1385 | Enhancement | When an <A/P Invoice> (APVI03) was entered to bill for inventory received in the Warehouse, without using the <AP Invoice by Purchase Order> (APVI04) option, the WH Trx could not be selected from the ‘Warehouse Transactions’ window or manually entered to define and complete the associated inventory receiving records. |
| SRM-1395 | Correction | The serial number should not be required when the <AP Invoice> (APVI03) is entered without a PO# when the part being invoiced in a Time-Of-Sale Serialized Sales Part. |
| SRM-1396 | Correction | The Purchase Order numbers were being truncated on the <A/P Invoice Posting Journal> (APVI10). |
| General Ledger | ||
| Ticket # | Type | Description |
| SRM-827 | Enhancement | MYOB Essentials' can be configured to integrate with SRM accounting by exporting G/L posted transactions as journals to the MYOB application. |
| SRM-828 | Enhancement | MYOB-AccountRight can be integrated with SRM. |
| SRM-1004 | Enhancement | A “Cash Flow Report” can be generated from the <Balance Sheet> (GLSL20), <Income Statement> (GLSL30), <Income Statement Compared to Budget> (GLSL31), and the <Income Statement with Budget Variance> (GLSL32) reporting options, based on the summarized G/L account totals by using the ‘Cash Flow’ <Statement Layout> (GLSL01) that allows a “C” in the “+/-” column where the “C” calculates a cumulative total of the Liability and Revenue amounts rather than subtracting them as is done in the other layouts. |
| SRM-1314 | Correction | The reversal transactions of a <Standard G/L Journal>(GLJH01) for an Accrual posting transaction Type C was not being reported in the <Tax Activity Report> (GLGL30). |
| SRM-1316 | Correction | The <Standard G/L Journal> (GLJH01) transaction Type C was not reported correctly in <Tax Activity Report> (GLGL30) as “Tax Collected”. |
| SRM-1317 | Correction | The <Standard G/L Journal> (GLJH01) transaction type on an existing journal can now be changed in Change mode. |
| Counter | ||
| Ticket # | Type | Description |
| SRM-1036 | Correction | A <Cycle Billed> Invoice could not be reversed because of an availability restriction if the source <Contract> was flagged for an Indefinite rental period. |
| SRM-1312 | Enhancement | The option is now provided to generate a <Rental Return> (RSCD04) for a Contract by selecting one of the products from a <Pickup Ticket Search> (RSFRPU) filtered by ticket Status. |
| SRM-1507 | Enhancement | "If the “Cycle Bill Interval” is changed in ADD mode on a <Contract> when the document is first created, then the “Cycle Bill Day” is also changed to the 'Day Code' associated with the new billing period. However in CHANGE mode if the ‘Billing Interval’ is changed on the <Contract> then the ‘Billing Day Code’ is not auto-updated as this value may have already been deliberately adjusted. In CHANGE mode the ‘Billing Day Code 'must be updated manually if required. This field is disabled if the <Contract> has already been billed, and for <Reservations> as the 'Cycle Billing Interval' will not be finalized until the reservation is converted to a contract." |
| SRM-993 | Enhancement | Signed Contracts are flagged in the <Contract Search> (RSCS01) window and they display a “signature” icon on the bottom of the <Contract> header (RSCH01B) and details (RSCH02) screens to alert the operator that a signature has been provided. The signed document can be viewed and printed from the <Attachment Files> (ATTACH01) window on the document. Signature attachments cannot be deleted. The <Contract Detail Report> (RSCH55) provides a signature filter option and displays a Signature captured flag on the spreadsheet output. |
| SRM-998 | Enhancement | The <Contracts with Invalid Rates Report> (RSCD73) can be run by the Automated Report Scheduler and emailed to the relevant staff. |
| SRM-1002 | Enhancement | The <On Hold A/R Invoice Report> (RSID07) can be run by the Automated Report Scheduler and emailed to the relevant staff. |
| SRM-1131 | Enhancement | An {eSign} button is provided at the bottom of the <Contract Summary & Totals> (RSCH03) screen to email this contract to the customer requesting a signature on the document. This is useful when the customer is not present. An Email Address selection window is generated where a single address associated with the Customer Contacts can be selected or manually entered to receive the email document request for signature. Once an email is requested the [eSign] button displays as disabled to ensure any changes made to the document are reflected in the emailed document. |
| SRM-1214 | Enhancement | When any of the Document Reprint utilities are printing a single document meaning the From & To document# is the same, the “Compose Email” (EMAIL02) option will always open if the user checks the email box, regardless of whether or not there are Contacts for the customer flagged to receive that document type. |
| SRM-1451 | Correction | When the FL Pickup Load is Cancelled or less than 0 then the Invoice resulting from the Rental Return was losing product detail lines. |
| SRM-596 | Correction | If a company was not using the ‘Operators by Division’ processing then the default ‘Delivery Comments’ defined for the division in the <Delivery Pickup Parameters> were not being added to the ticket comments when the ‘Delivery Ticket’ was created from the <Delivery Console>, and so the comments were not printing on the document. |
| Back Office | ||
| Ticket # | Type | Description |
| SRM-1132 | Enhancement | When a new Operator is created for a new Division Login the operator data values and properties can be copied from an existing operator record. |
| SRM-1211 | Enhancement | Non-Inventory Items returned on a P.O. with a negative quantity could not be refunded in <A/P Invoice by P.O.> (APVI04) because the negative quantity record was not found. |
| SRM-1462 | Enhancement | When <Cycle Billed Invoices> are automatically paid by a Texada Pay Credit Card on file, the invoices were not being posted On Account and so they were not included on the <Customer’s Statement>. |
| Inventory Control | ||
| Ticket # | Type | Description |
| SRM-1400 | Correction | Any new rental or sales item added into SRM in the <Purchase Order> (RSPO01) screen was not appearing in the Counter Document Inventory Searches. |
| SRM-512 | Correction | The <Standard Import> (IMPORT) utility for non-bulk rental inventory was leaving a blank value when the asset was not flagged as metered instead of flagging it as N |
| SRM-789 | Enhancement | The <Update Fixed Asset Tags> (RSRI10) utility can now be accessed from the Inventory Utilities menu and provides the option to <Export Asset Tag > details associated with Depreciation including the Division, Original Cost, Accumulated Depreciation, Date Acquired, and Depreciation Class information and then to re-import the adjusted values. |
| SRM-996 | Enhancement | The <Bulk Disposal Report> (RSBS02) can be run by the Automated Report Scheduler and emailed to the relevant staff. |
| SRM-1250 | Correction | A product Barcode number that equals the associated product number should be acceptable and can be added in the <Write Product # Into Barcode> (RSBB02), <Inventory Cleanup Import> (INCL03), <Update Barcode by Product> (RSPF63), <Data Imports>(IMPORT) and manually into the <Product Barcode> (RSBB08) table for Sales & for Rental products, |
| Purchase Orders | ||
| Ticket # | Type | Description |
| SRM-1450 | Enhancement | The ‘P.O. Reference’ field has been added to the Detailed spreadsheet output of the<Purchase Order Report> (INPH30). |
| SRM-1338 | Enhancement | The Inventory Cost & List value fields throughout the system have been increased in size to accommodate PO's that exceed several million dollars in value, with individual line items being millions on their own. |
| SRM-622 | Correction | The <Inventory Re-Order Report>(RSPO20) was not respecting spreadsheet output request when an export file already existed that had to be cleared before the output was generated. |
| Work Orders | ||
| Ticket # | Type | Description |
| SRM-1062 | Enhancement | The total ‘Labor Cost’ displays on the <Work Order> (WOWH01) header and in the detailed <Work Order Report> (WOWH11) output, where the Labor Cost for each service technician employee that worked on the order is based on his 'Hourly Rate' as set up in <Operator Time Charges> (RSOT01) times the hours logged for his labor on that W.O. |
| SRM-1321 | Enhancement | SRM print options are provided to include the signature or to print the last copy of the document on a reprinted Inspection Form, Pickup Ticket, and Delivery Ticket. |
| SRM-1435 | Enhancement | The <Repair History Inquiry> (WORT05) displays the number of completed Inspection forms associated with that repair and provides a button to drill down to view the individual forms where they can be printed. |
| SRM-678 | Enhancement | When a <Work Order Invoice> is accessed in the <Miscellaneous Invoice> (RSIH01) screen it can not be modified as it must match the source <Work Order> and so a clear warning is generated for Current, Batch & History W.O. Invoices, and a button to <Reverse a W.O.> (WOHH05) is provided for Current Invoices. A [DETAILS] button is also provided to drill down to view the details on the Invoice & W.O. |
| SRM-1320 | Enhancement | W.O. Deposits can be captured in the new <Work Order Deposits > (WOWH35) and can be reflected in the <O/S Deposits Report> (RSCH41) W.I.P. Work Orders can use a partial payment on early Work Order Invoices, applying the remainder to the final invoice. |
| SRM-1504 | Enhancement | The <Post W.O. Work in Progress> (WOIP10) utility has been GUI-ized. When there are errors, a <WIP Posting Error> (WOIP02) screen that stops posting is generated to report invalid G/L account, or date, out of balance, invalid part/service/labor code, etc, that can be fixed on the error screen. Record locking has been implemented on the <Post W.O. Work in Progress> (WOIP10) where only users with <Security Role Permission> (ROLE01) can release the lock. |
| SRM-614 | Enhancement | A Purchase Order number filter has been added to the <Work Order/Estimate Search> (WOWHSEL) utility. |
| Reports | ||
| Ticket # | Type | Description |
| SRM-1457 | Enhancement | The <Work Order Report> (WOWH112) was formatting the Quantity column as a $ figure, rather than a number in an Excel spreadsheet. |
| Utilities | ||
| Ticket # | Type | Description |
| SRM-813 | Enhancement | An additional ‘Product Type’ selection option has been included in the <Inventory Cleanup Export> (INCL02) utility to filter by Sales, Rentals, or Both. |
| System Maintenance | ||
| Ticket # | Type | Description |
| SRM-1294 | Correction | The GL Journal tax transactions were being reported incorrectly in <Tax Activity Report> (GLGL30). |
| Other | ||
| Ticket # | Type | Description |
| SRM-1277 | Enhancement | Third-party Accounting application Xero has been updated from OAuth1.0 to support OAuth2.0 |
| SRM-1364 | API | The option to “Prompt For Maintenance Codes On Work Order Details” was not being respected in FleetLogic Work Orders because the <Company Work Order Parameter> setting was not being passed from SRM to FL by the GLCN table. |
| SRM-1369 | API | The ‘Clerk’ and ‘Division’ values captured in SRM or by API on the <Close Pickup Ticket> and <Close Delivery Ticket> are included in the data that is exported to web services. |
| SRM-1447 | API | The Labour services detail line items were not printing on the <WO Invoice> when the invoice was created and printed from a Web application. |
| SRM-767 | Telematics | The <Telematic Providers> (GLCN90N) table has been reformatted to allow multiple AEMP vendors to be configured and activated or disabled at the same time. |
| SRM-767 | Telematics | Each non-bulk rental Asset can be assigned a Telematic Provider and a unique Telematic ID for that provider in the <Rental Information> (RSFRRATE) window. This information can be updated in the <Rental Inventory (RSPF02), Create Rental Inventory> (RENTALS), <Telematic ID Inquiry> (AEMP03B), <Update Product Rental Information> (RSRF01 and the <Data Import/Export Tool> (XFR15) when the operator as proper <Role Security> to “Assign/Remove Telematic ID” . This information is displayed in the <Inventory Inquiry> (RSRQ50E) and the <Detailed Inventory Inquiry> (RSPF60). |
| SRM-1227 | Data Management | The number of Inspection Forms that can be updated by the <Export/Import Group Information> (GRP695) utility has been increased to five. |
| SRM-1319 | Enhancement | The ‘SRM User License’ count calculation has been changed to increase the number of sessions permitted per license, by only counting the number of OC or MFC “User IDs” as licenses used, and then by allowing multiple runtime sessions per “User ID” up to a maximum of 10. |
| SRM-1322 | Enhancement | QRCode forms were using an explicate expression for generating the QRCodes with an outdated ZXing library. This was not only causing exception on SaaS form generation, but also caused Jaspersoft Studio to crash on attempt to edit |
| SRM-1484 | API | Texada Pay payment transactions generated with 'Global Payments' both ON & OFF are written to the <Texada Payment Log> (TPLOG01) and the <Texada Payment Inquiry> (TPLOG02). |
| SRM-1500 | Order Entry | To avoid confusion, the [CREDIT INV] button is hidden on the <Sales Order Invoice> (RSIH01) screen, as the <Create Invoice from Existing Invoice> (RSCM02) utility only applies to standard invoices and not Order invoices. |
April 2020
Version 10.1.2002
Feature Highlight: Purchase Order Approval Process Update |
||
| Ticket # | Description | Affected Components |
| SRM-1152 | When the “Enable PO Approval” feature is activated in the <Company Inventory Parameters> an "Approver" can be assigned to the <Operator Code> (GLOP01) to define whom the purchasing employee reports to, where this "Approver" has a higher buying limit. This will create a hierarchy of who will approve the Purchase Order. | System Maintenance |
| SRM-1153 | When the “Enable PO Approval” feature can be activated in the <Company Inventory Parameters> a <Security Role Permission> (ROLEPER2) is used to define the dollar limit per <Purchase Order> for operators in this role. When the purchasing employee exceeds the limit a notice is automatically sent to the defined "Approver" who must approve the PO if it is within the "Approver's" own limit. If that "Approver's" limit is not high enough, then his "Approver" would need to approve the P.O. moving up to the next link in the approval chain. | System Maintenance |
| SRM-1154 | Using the PO Approval processing the Approver can Approve or Reject the Purchase Order or he can Reassign a P.O. to an Approver with a higher purchasing limit. | Purchase Orders |
| SRM-1156 | The <PO Approval Report> (RSPO09) can be run by the Automated Report Scheduler and emailed to the relevant staff. | Purchase Orders and Reports |
| SRM-1157 | When a PO has not been approved using the <PO Approval> module activated in the <Company Inventory Parameters>, the PO cannot be printed, emailed or faxed as it is not ready for the Vendor. The option is provided to export the values for an unapproved PO to an Excel spreadsheet from <Purchase Orders> (RSPO01K). |
Purchase Orders |
| SRM-1158 | The PO Approval process uses four "Statuses" -Draft, Pending Approval, Approved and Rejected that restrict access to the <Purchase Order>. -P.O.s that are Approved can only be re-accessed and modified by the final Approver. -P.O.s that are still in Draft, Pending Approval or Rejected can only be re-accessed and modified by the original purchaser and his Approver. | Purchase Orders |
| SRM-1160 |
The “Enable PO Approval” feature can be activated in the <Company Inventory Parameters> (GLCN90) to control how much a purchasing employee can spend on a Purchase Orders in SRM.
|
Purchase Orders, Reports, and System Maintenance |
| SRM-1170 | When the “Enable PO Approval” feature is activated in the <Company Inventory Parameters> and the purchasing employee exceeds his <Security Role> defined limit, his assigned "Approver" must approve the PO if it is within the "Approver's" own limit. If that "Approver's" limit is not high enough to cover the P.O., then his "Approver" would need to approve the P.O. moving up to the next link in the approval chain. | Purchase Orders |
| SRM-1172 | Using the PO Approval processing an email alert is sent to notify the Approver when a “Pending” PO has been assigned to them. The original Requester is also sent an email notification when the PO is Approved or Rejected. | Purchase Orders |
| SRM-1187 |
PO Approval Notes can be added to the Purchase Order by the Requester and the Approver at any level of the processing in the <Purchase Order> itself or in the <Purchase Order Approval> utility until the PO is Approved.
|
Purchase Orders |
| Accounts Receivable | ||
| Ticket # | Type | Description |
| SRM-1233 | Enhancement | The spreadsheet output option has been added to the <Customer Payment History Report> (ARCH20). |
| SRM-1276 | Correction | The <Customer Search> (ARCF06) window was not consistently aligning the columns in the display, based on search parameters. |
| SRM-915 | Enhancement | The ‘Customer Account’ emailing generated from <Customer Account Inquiry> (ARAR05) has been changed to respect the ‘Contact Emailing’ feature. |
| Accounts Payable | ||
| Ticket # | Type | Description |
| SRM-731 | Enhancement | The <AP Recurring Invoices> now respects the <Company Taxing Parameter> to “Calculate Tax on:” A/P or ALL, and prompts for the Tax Code information to be reflected on the <Tax Activity Report> (GLGL30). |
| Counter | ||
| Ticket # | Type | Description |
| SRM-1144 | Correction | The “Contract Override Location Quantity” flag in the <Company Security Parameters> was not being respected by the <Convert Reservation to Contract> (RSRH04) utility. |
| SRM-246 | Enhancement | A Contact email “Payment Receipts” option is provided when the “Contact Emailing” feature is activated in the <Company Email Parameters>, to email the receipts generated from <Counter Payments> (ARPC01). |
| SRM-820 | Enhancement | The <Cycle Billing Day Code Discrepancy Report> (RSBD02) is provided to help users identify mismatched Billing Codes and Contract Out Dates. |
| SRM-1087 | Enhancement | A <Sales Approval Quote> can now be saved for re-use when converting a Sales Approval Quote into a Sales Order. |
| SRM-1191 | Correction | When <Kit> items were flagged not to print and their Groups were set not to check availability, the Kit items still printed on the Jasper form for the <Reservation>. |
| SRM-644 | Enhancement | The product detail 'Notes' that are flagged to print on the <Reservation> details also print on the <Reservation Picking Ticket> (RSRH17) |
| Back Office | ||
| Ticket # | Type | Description |
| SRM-1063 | Enhancement | The ‘Salesman’ as well as the ‘Approval Code’ are provided as selection filters in the <Daily Close Invoice Approval>(RSIH25) screen and the <Invoice Approval Report> (RSIH26) so that if an alternate salesman is assigned at the Contract level and all resulting Invoices would then be using that salesman and be approved accordingly. |
| SRM-1285 | Correction | When a <Work Order> for a non-bulk asset was created through a ‘Product Status Code’ change, the default ‘Posting Type’ defined in the <Divisional W.O. Parameters> was not respected. |
| SRM-1261 | Correction | The <Cycle Billing> (RSCD14) process was popping up ‘Texada Pay’ error messages requiring user input in the Batch run. |
| SRM-1310 | Enhancement | A “Failed Invoices” only option has been added to the <Email Log> (EMAIL10) to list invoices that have failed to send. This can be caused by a bulk run with improper settings, |
| Inventory Control | ||
| Ticket # | Type | Description |
| SRM-1123 | Correction | BOM/Manufacturing was not respecting the <Group> defined ‘Availability Checking’ of components used when assembling a new product in in <Manufacturing Receiving> (INRR01). |
| SRM-1138 | Correction | A Serialized Sales part could not be credited with a negative quantity on a closed <Internal Work Order> because the serial# was not included in the selection window. |
| SRM-1197 | Correction | The <Internal Inventory Transfers> (INDH01) were not respecting product availability for Kit Items. |
| Purchase Orders | ||
| Ticket # | Type | Description |
| SRM-1110 | Enhancement | A ‘Reference’ field of up to 250 characters has been added to the <Purchase Order> (RSPO01) header which prints on the Summary output of the<Purchase Order Report> (INPH30) and is included in the XML exports. |
| Work Orders | ||
| Ticket # | Type | Description |
| SRM-1062 | Enhancement | The total ‘Labor Cost’ displays on the <Work Order> (WOWH01) header and in the detailed <Work Order Report> (WOWH11) output, where the Labor Cost for each service technician employee that worked on the order is based on his 'Hourly Rate' as set up in <Operator Time Charges> (RSOT01) times the hours logged for his labor on that W.O. |
| Reports | ||
| Ticket # | Type | Description |
| SRM-1279 | Enhancement | An existing <Inspection Form> with like attributes can be cloned in SRM to create a new Inspection Form that can then be customized to use as required. |
| System Maintenance | ||
| Ticket # | Type | Description |
| SRM-1282 | Enhancement | An <Export/Import Inspection Forms> (FLINSP8) utility has been created to provide the option to update existing and add new Inspection Forms in bulk. |
| Utilities | ||
| Ticket # | Type | Description |
| SRM-814 | Enhancement | Group and Product “Alt Language Rate Descriptions”can be updated from the <Export/Import Product/Group Rates> (RSFR88) utility. |
| SRM-815 | Enhancement | The “Alternate Language Descriptions” assigned to Sales Products and to Rental Assets can be updated from the <Export/Import Inventory Cleanup> (INCL01) utility. |
| Texada Pay | ||
| Ticket # | Type | Description |
| SRM-1246 | Enhancement | The U.S, ACH, and Capture Card screens have been converted to the standard Texada Pay interface screens for enhanced user experience. |
March 2020
Version 10.1.2001
| Accounts Receivable | ||
| Ticket # | Type | Description |
| SRM-562 | Enhancement | A print [ALL INVOICES] button toggles with a [PRINT NONE] button on the <Customer Accounts Inquiry> (ARAR05) detail screen to flag all eligible invoice to print or not. |
| SRM-1104 | Enhancement | The <Job Sites Report> (ARST10) can now be exported to Excel output. |
| Counter | ||
| Ticket # | Type | Description |
| SRM-1230 | Enhancement | The “Delete Invoice” process has been enhanced to provide an Operator <Security Role Permission> that allows managers or administrators to delete a problem invoice even if it has an associated Source document. |
| SRM-657 | Enhancement | The [DELETE] button on the <Miscellaneous Invoices>screen has been changed to only delete an Invoice that has no Source such as a Contract or Work Order as those transactions should be reversed and re-billed to make corrections. Other invoices such as ‘Miscellaneous’,‘Lease’,’ Sales Order’,’Fast Track’,’ Split’, and ‘Credit Invoice’ can only be accessed if the operator as role security to delete invoices and also has menu role security to access or create the specific type of invoice. A warning is generated if the operator has access to delete but not access to create. |
| SRM-489 | Enhancement | The Date/Time is displayed in red on the product detail line in <Close Delivery Tickets> (RSCH27) for the “Drop Off” date/time when it is later that the Contract date/time and in <Close Pickup Tickets> (RSCH47) for the “Actual” date/time when it is before the Pickup Ticket date/time off, to alert the operator that Off-Rental Time transaction has been triggered. The Notes have been moved to the Expanded 2nd detail line to accommodate this. <Security Role Permissions> have been added for FleetLogic to control the ability to change the 'Actual Date' on the <Pickup Ticket> and the 'Drop Off Date' on the <Delivery Ticket>. |
| SRM-671 | Enhancement | Provide the ability to Authorize a Credit Card - US and Canada with Texada Pay. |
| SRM-942 | Correction | In the <Sales Approval Quote> the Services Search window in Change mode was not displaying all the A,I,O,$,D type services. |
| SRM-945 | Enhancement | The "Close Driver" and "Signer" have been added to the Pickup and Delivery Ticket details viewed from the Pickup/Delivery Consoles in SRM. |
| Purchase Orders | ||
| Ticket # | Type | Description |
| SRM-1099 | Correction | New rental or sales products added through <Purchase Orders> and received into inventory were not being found in the “Inventory Search” on the <Counter Document>. |
| Order Entry | ||
| Ticket # | Type | Description |
| SRM-580 | Correction | The ‘Open Only’ filter was not being respected on the <Sales Order Inq> (OEOD01) for the “By Customer” and the “By Ship Date” options. |
| System Maintenance | ||
| Ticket # | Type | Description |
| SRM-632 | Enhancement | The <Special Rates> (RSSR01) table now opens with a search option that filters the rate table list by full or partial code or full or partial description. |
| SRM-1033 | Correction | The Bank Account # displayed in <Company Information> (GLCN01) for the CPA 055 format in the <Direct Payment Configuration> (APDC01) was reflecting/updating the ‘Originator ID’ field instead of the Bank field. |
| SRM-971 | Correction | The <GL Account Inquiry> (GLGL15) Summary & Details and the <Account Inquiry By Transaction #> (GLGL16) have been changed to respect Restricted Divisional Views. |
| Reports | ||
| Ticket # | Type | Description |
| SRM-974 | Enhancement | The 'Ship To' information from each Invoice has been added to the detailed spreadsheet output of the <Customer Revenue Report> (RSSH17) along with a flag to indicate if the Invoice is the first billing of the Contract or not the first. |
| SRM-1095 | Correction | When “Check location quantity” is yes in the selection filters, the <Maintenance Schedule Report> (WOMS10) would always be blank when running from <Automatic Reports>. |
| Work Orders | ||
| Ticket # | Type | Description |
| SRM-661 | Enhancement | To minimize the impact of a partially closed W.O. issue, the <Reverse W.O.> utility (WOWH31) can be used to reset the Invoice# back to blank so the W.O. can still be billed. |