1. Texada Knowledge Center
  2. Release Notes
  3. (SRM) Systematic Rental Management

2022 SRM (Systematic Rental Management) Release Notes

Contains release notes for SRM (Systematic Rental Management) for the 2022 calendar year.

These release notes address new features and code fixes for the standard release of SRM (Systematic Rental Management) as of 2022. Notes are categorized as either Enhancements (new components or features) or Corrections (bug fixes).

Quick Navigation


May

Version 2022.01

Accounts Payable

Ticket #

Type

Description

SRM-2915

Correction

Bug - The TD Bank was rejecting the Direct Credit Payment EFT format for the 80 BYTE layout.

SRM-2641

Correction

The number sequencing of the <Vendor Information> (APVF01) table was skipping one number after creating a new vendor record.

SRM-2494

Correction

The spreadsheet output for <Aged A/P Summary> (APAP21) now formats columns E to I as "General text & Number category" to better display the currency values.


Accounts Receivable

Ticket #

Type

Description

SRM-2954

Enhancement

The <Customer Payments> (ARAR03) detail screen has been enhanced to dynamically resize by adjusting the number of rows in the paging screen to the size of the browser.

SRM-2904

Enhancement

When entering multiple payments in the <A/R Customer Payments> (ARAR03) utility, the 'Method Of Payment' value will now default to the MOP entered on the previous payment transaction.

SRM-2902

Enhancement

The default radio group value displayed in the 'Payment Confirmation' modal generated from accepting the payment selection in <A/R Customer Payments> (ARAR03) and in <Counter Customer Payments> (ARPC01) has been changed to the more commonly applied 'Accept This Payment' option.

SRM-2850

Correction

Bug - When a new cash customer is added to the <Customer Information> (ARCF01) table on-the-fly from document entry by using the <Driver's License Scan> (ARCF06) feature the new Customer record was not saving the 'Trading As' value or the 'Alpha Key' properly.

SRM-2846

Enhancement

The 'Cancel' column in the <Deposit History> (RSDPVIEW) window on documents has been re-labelled as the 'Void' column to be more intuitive and accounting accurate.

SRM-2790

Enhancement

In the Parent/Child relationship in SRM all Child invoices are included only in the <A/R Account Inquiry> (ARAR05) for the Parent as it is the Parent that pays the invoices.

In the Web services the TK_ACCOUNT_INQUIRY API called for a Child company's "Account Summary", now also reports the Parent's ARAR records generated/associated with that Child account.

SRM-2770

Enhancement

The <Customer Payments> (ARAR03) details screen has been redesigned to display the action buttons above the paging screen so as to include more document detail lines.

SRM-2658

Enhancement

Enhancement - The <Customer List> (ARCF20) has been changed from excluding any customers without an "Account Opened Date" to always including all customers with or without an "Account Opened Date" where the Details and Quick Lists now print the "Account Opened Date" on the PDF and on the PDF Summary identify such customers with as asterisk (*).

The spreadsheet format for all reports includes a column populated with "Account Opened Date".


Enhancement - The <Standard Data Import> (IMPORT2) for new Customer data has been improved to write the 'Account Opened Date' as of the "Import as of" date when no 'Account Opened Date' or an invalid date is passed in by the import, and no error is triggered.


Bug - Add a new customer-on-the-fly from the <Quotations> (RSQH01) header was not writing today's date to the "Date Account Opened" in the 'Customer Credit Information' of the <Customer Information> (ARCF01)


Bug - The Safety Sheets import from the <Standard Data Imports> (IMPORT) was truncating the notes from 70 characters to 51 characters when it updated RSSN table.

SRM-2592

Correction

Bug - <Credit Card Expiry Report> (ARCC05) was not including Texada Pay cards and was not respecting the “Expires In Number Of Days” parameter and instead was always using 30 days.

New feature - When the <Credit Card Expiry Report> (ARCC05) is run manually filters are provided to export ALL Credit Cards & Check records on file instead of just those that are expiring and to filter the Customer selection.


APIs and Synchronization

Ticket #

Type

Description

SRM-2726

Enhancement

The "Allow On Account For Cash Customers" parameter flag has been added to Texada Web configuration data import API.


Backoffice

Ticket #

Type

Description

SRM-2822

Correction

Bug - When the <Daily Close 1> is run by Division and a Batch DC1 is run but not accepted, when that same Batch is run again, the "Invoices In Previous Batch Report" would re-print but not the "Invoice Edit Report".

If the user clicks to Accept that second run then both the "Invoice Edit Report" and the "Invoices In Previous Batch Report" would print again.

SRM-2772

Correction

Bug - Invoices that are flagged to be paid with Auto-Pay during the <Cycle Billing> (RSCD14) process were not being processed with Texada Pay for Australia or New Zealand.

SRM-2618

Correction

Bug - A Blank invoice was being emailed to the customer from the <Daily Close 2> if the Language preference value of Alternate or of Standard was not properly defined in the <Customer Information> table.


Counter

Ticket #

Type

Description

SRM-2966

Correction

Bug - Vertex Address Validation in Sales Quotes was re-arranging the 2nd line of the address.

SRM-2941

Enhancement

The [SUBSTITUTION] button has been added to the “Select a Product from This Group” screens triggered from <Convert Quote to Contracts> (RSQH05) & <Convert Reservation to Contract> (RSRH04) respecting the source document operator Role Security.

SRM-2940

Correction

Bug - Asset Exchange through Texada Web processed through Delivery/Pickup Tickets was not auto-updating the asset to the correct Status Code when automatic processing is enabled.

SRM-2886

Correction

Bug - The Divisional Damage Waiver Taxes were incorrect on a <Reservation> (RSRH01) based on the customer search method.

SRM-2821

Enhancement

The error messaging for the manual Capture Card action when the CVS number is incorrect or the address validation has failed has been improved to better explain the issue.

SRM-2820

Correction

The Contract Deposit Jasper form was printing a Null label in place of the "Document#" label.

SRM-2819

Correction

Voided deposit payments should not be printing on documents -Contract, Reservations, Sales Orders or Work Orders.

SRM-2807

Correction

Bug - The <Inventory Search> (RSEQ01) on counter documents for "Available Only" was excluding Bulk Rental Assets with a Disposed Tag even when there were other active Tags.

Asset Tags with an 'S' status for Scrapped are now handled as Disposed.

SRM-2691

Enhancement

The <Inventory Search> (RSEQ01) for Rental products provides additional Asset Tag filters to include/exclude disposed assets or assets with no tags.

SRM-2578

Enhancement

Job Cost information has been added to the spreadsheet output of the <O/S Contract Report by Name> (RSCH33) and the <Contract Report> (RSCH55).

SRM-2548

Enhancement

To better clarify the Availability status of inventory in the <Inventory Search> results paging screen, the 'N/A' status indicating "Not Applicable" because availability checking is disabled for that product <Group> (RSFGF02), has been changed to just read AVAIL.


Email

Ticket #

Type

Description

SRM-2937

Correction

Fixed a bug causing a file locking situation when emailing from multiple sessions simultaneously.

SRM-2885

Correction

Bug - The Gmail or Office365 authentication was failing if no API keys were configured


Security control - Only the SCS users can change the directories defined in the <Company Miscellaneous Parameters> (GLCN90O) for the Auto Reporting files, WO Service Notes, or Attachment files.

SRM-2836

Correction

Bug - The Office365 - DeAuthorize action was opening the Google security web page instead of the Microsoft security web page.


General Ledger

Ticket #

Type

Description

SRM-2852

Enhancement

The <Job Cost Report> (ARSTC02) detail has been enhanced to include the Product & Service Descriptions as well as the product & service codes on the spreadsheet output.

SRM-2848

Enhancement

When an 'Alternate Payee' name and address has been defined for a supplier in the<Vendor Information> (APVF01) in addition to printing on the Computer Checks and the Purchase Orders for that vendor, this alternate payee name and address is reflected on the <Check Reconciliation> (GLOC33) utility, the <Outstanding Check> (GLOC01) screen and the <Outstanding Check Report> (GLOC30).


Inspections

Ticket #

Type

Description

SRM-2714

Enhancement

The new INSPECTION_MULTIPLE_CHOICE record type can be used for a question/prompt on the <Inspection Forms> (FLINSP06) where the mechanic can select his response from a set of user defined response options.

SRM-2715

Enhancement

Two new fields for Mechanic Instruction information and Mechanic Reference URL have been added to the <Inspection Forms> (FLINSP06) field options and the text in the 'User Prompt' field has been increased to handle 250 characters.

SRM-2635

Enhancement

The 'Inspection Form' format has been improved to list the tasks and checks in two vertical columns for increased efficiency.


Inventory Control

Ticket #

Type

Description

SRM-2768

Correction

Bug - The detailed <Rental Inventory Value Report> (RSIT24) by Class for a Product Class range to PDF was not respecting the "New Page Per Class" parameter when the Date option was not selected for the cost reconstruct calculation.


Order Entry

Ticket #

Type

Description

SRM-2785

Correction

Bug - <Sales Orders> (OEOH01) headers were defaulting to the Customer Salesman Code and were not respecting the Site Salesman Code.


Purchase Orders

Ticket #

Type

Description

SRM-2842

Enhancement

The 'Prevent Negative Purchase Order Quantity' can be set in the <Company Inventory Parameters> to ensure that negative quantity can only be entered on a <Purchase Order> (RSPO1) if there is sufficient positive quantity 'On Hand' to be returned, regardless of the Group availability checking, Class re-rent flag, any Company or Division availability parameters or product requirements.

Negative quantities are always allowed on a PO to reverse a purchase posting for a 'Non-Inventory Transaction'.


When the 'P.O. Approval ' feature is enabled in the <Company Inventory Parameters> (GLCN90K) a <Purchase Order> (RSPO01) with a negative total value respects the same Approval Status based on the dollar amount as an "absolute value".

This means the negative sign is ignored when considering the PO total, so a PO with for a -$100.00 (negative) requires the same approval as a PO with a $100.00 (positive) value.

SRM-2825

Correction

After clicking YES to create a Non-Inventory order trx in <Purchase orders> (RSPO01) it was popping up the Umsage “Inventory not in file for Product RSIL”

SRM-2811

Correction

Purchase Orders with no line Items on the order are now being returned in the 'Open' category of the <P.O. Search> (INPHSEL).

SRM-2810

Correction

Bug - New Sales product records that were created with no quantity in <Purchase Order> (RSPO01) entry did not create the location records and were throwing an RSIL error when the product was added as a P.O. detail.

SRM-2776

Correction

Bug - The Clerk field in <Purchase Orders> was showing the last GLOP user who accessed the PO instead of the actual Clerk who created the Purchase Order or the Clerk manually assigned to the PO.

SRM-2740

Correction

The first run in a new session of the <Warehouse Receipts Report> (INWR80) sorted by Class and output to PDF, was formatted in the wrong font and so it could not display the columns on the right side of the report.

SRM-2526

Enhancement

The <Purchase Order> (RSPO01) "Non-Inventory" order detail can be flagged as "Type" V for 'Contract Service' with the associated Contract# captured in the "Category" input field.

SRM-1615

Enhancement

PO approval feature enhancements:

- Any Approver with an allowable Limit above the P.O. total can approve/reject a Purchasing Request, not just the Approver assigned to the requesting Operator and then this Approver becomes responsible to approve the P.O.

- The original purchasing Requester as well as any Approver with an allowable Limit above the P.O. total can re-access and update the Purchase Order.

Screen reader support enabled.


Reports

Ticket #

Type

Description

SRM-2675

Correction

The <Clerk Document Access Log> was not available on the 'Reports ->Security' menu tree because the function RSCF02 was not correctly flagged to show on menus.

SRM-2620

Correction

Bug - The <Inventory Report with License/Serial #> (RSIT28) was missing the current contract information on some assets because it was not checking the correct RSCD table for the open item details.

SRM-2454

Enhancement

The spreadsheet output of the <License Expiry Report> (RSPF62) has been enhanced to include the Make, Model, Vin #, Engine Serial # and Tag Serial Number for non-bulk Rental assets.

SRM-1889

Correction

Bug - When the <On-Hold Invoice Report> (RSID07) was run using the default values from the Automatic Job (SMCR99) schedule, it was not generating any output.

When the <On-Hold Invoice Report> (RSID07) was run with filters from the Automatic Job (SMCR99) schedule, the output was always to PDF and never to a spreadsheet.


Substitutions

Ticket #

Type

Description

SRM-2870

Enhancement

The "Document Field Access" settings in the operator <Role Permissions> (ROLEPER2) can be set by document type to control the user's ability to enter 'Substitution Transactions' on counter document details including Contracts, Reservations, Worksheets, Rental Quotes and in the Overbookings screen generated from the rental document conversion utilities.

SRM-2639

Enhancement

<Substitution Transactions> (RSSB01) can be processed at the Group level if the group has a rate structure defined, as well as at the product level, for the Requested or the Rented item on rental documents that accept Group line items.

SRM-2638

Enhancement

When a rental product <Substitution Transaction> (RSSB01) is generated on a document any <Special Rates> (RSSR01) for the division or customer on the document are respected for both the Requested product or Group and also for the replacing Rented product or Group.

SRM-2637

Enhancement

When a product substitution is made on a document a Substitution note prints below the product detail of the Contract, Reservation and Quote Jasper documents as defined by the "Customer Message" setup in the <Substitution Reason Code> (RSSBR01) table.

If there is no "Customer Message" associated with the Substitution Reason Code then the reason code description prints.

SRM-2636

Enhancement

The SUBSTITUTION button and processing has been added to reservations, quotes and overbooking screens and the <Substitution Report> (RSSB10)has been enhanced to include the Substitution notes from the document and to reflect substitutions on Reservations, Quotes and Worksheets as well as the Contracts.


System Maintenance

Ticket #

Type

Description

SRM-2944

Enhancement

The SRM "Date Range Override" flag is a security control by <Operator> (GLOP01) to prevent users from making accidental Date errors or from posting into closed accounting periods.

The "Date Range Override" flag is automatically disabled for all operators and can be activated temporarily to allow an operator to make transaction corrections regardless of date.

When an operator logs into SRM the date over-ride feature is automatically disabled for that operator in the log in division.

SRM-2903

Enhancement

The "Prompt to Print Receipt" parameter in the <Company Customer Forms Configuration> (CY_FILE2) has been enhanced to provide the option to only prompt to print a receipt when payments are taken on deposits or on documents, and to prevent the prompt for payment receipt in THE <Customer Payments> (ARPC01) and in <A/R Payments> (ARAR03).

SRM-2849

Enhancement

The <Company Billing Parameter> (GLCN90) to “Bill Current Meter” can be activated to cause the <Cycle Billing> (RSCD14) processing including 'Smart Billing' to respect and to automatically bill up to the current Meter count logged in the <Product Meter Information> (MTRREAD) for the < Rental Inventory> (RSPF02) in the billing run.

This process allows updated meter counts captured from GPS such as by 'Telematics' to be automatically included & invoiced in the standard <Cycle Billing> (RSCD14) run.

When this “Bill Current Meter" is activated in the 'Cycle Billing Settings' of the <Company Billing Parameter> (GLCN90) then the "Meter Count Sheets" billing processing is disabled.

If the asset is on more than one contract the meter units used will not be billed in the <Cycle Billing> (RSCD14) run.

SRM-2796

Correction

The RSCD24 function can be setup to run from the <Job Scheduler> (SCSCRON) to re-instate the 'Bill Thru' date on Contract details where there is a Billed amount but the rscd_billed_thru (date billed thru) is blank.

SRM-2777

Correction

A Driver record cannot be deleted from the <Drivers> (RSDB01) table in SRM if it is referenced in Texada Web/Mobile or in use on an open Delivery or Pickup Ticket.

SRM-2561

Correction

Bug - The OC session could freeze when trying to delete a record from the <Status Code Actions by Group> (RSAR05) or from the <Status Code Actions by Product> (RSAR04) utilities, and so a Delete Selected record pop-up has been provided.


Texada Pay

Ticket #

Type

Description

SRM-2938

Correction

Fixed a bug that would occasionally cause SRM Rollback errors when processing debit or Visa transactions in SRM.

SRM-2933

Enhancement

A Texada Pay payment by Terminal scan provides the option to abort after 30 seconds if the transmission from SRM to OpenEdge is interrupted.

Aborted transactions are tracked in the <Texada Pay Log> (TPLOG01).


Bug - OpenEdge had changed the order of the information passed back to SRM Texada Pay for a Terminal Card payment which was causing a 404 URL response error.

SRM-2925

Enhancement

The "Method of Payment Correction" flag in the 'Document Field Access' settings of the Operator <Role Permissions> (ROLEPER2) controls the user's ability to select the 'Correction' option from the Texada Pay MOP window thst can be used to capture a TP payment in SRM without posting it to the OpenEdge clearing house.

This is useful when a Texada Pay payment has been submitted and accepted by the OE clearing house but the transaction did not get completed and saved in SRM.

An audit entry is written to the <Texada Pay Log> (TPLOG01) with PAYMENT ID = CORRECTION:YYYYMMDD_HHMMSS and the TYPE will be C.

SRM-2851

Correction

Bugs - Texada Pay with Ezidebit clearing house:

1- The <Texada Pay> configuration parameter to 'Refund Existing Payment Only" was not accessible for Australian and New Zealand currencies.

2- A refunded contract deposit that appeared to fail with the message "Refund failed. Do you wish to add it to the refund queue?" was actually approved, printed on the document, processed in the Ezidebit portal and reflected in the <Texada Pay Log> (TPLOG01) but was not written to the <Deposit History> (RSDPVIEW) for the Contract.

3- Refund transactions added to the <TP Pending Refund Queue> (TPRNTN01) were not being written to the <Texada Pay Log> (TPLOG01) when they were processed through <Update TP Pending Refund Queue> (TPRTN02).

SRM-2791

Correction

Bug - Texada Pay was unable to save a new card or process a card payment with a name field of greater than 26 characters.

SRM-2784

Enhancement

Enhancement -

The Texada Pay payments processing has been updated to properly handle Canadian and U.S. payments captured by a terminal device when the OC SRM session becomes frozen or is terminated mid-processing, so that if the session is "resumed" or a new session for the user is opened within 15 minutes, the payment is completed per the clearing house status (Approved or Failed) in SRM and the Receipt can still be printed.

The <Texada Pay Log> (TPLOG01) reflects the payment record information.


Bug -

A Refund deposit was auto-changing from CR to VO when payment the method was for card type M or A even though it had not prompted for Authorization Only.

The processing has been changed for non-Texada Pay payments and deposits when the "Prompt for Authorize Only" feature is enabled in the <Divisional Miscellaneous Parameters> to always prompt for "Authorize Only" for positive dollar amounts which creates a SA (Sale) or AU (Authorize Only) type transaction accordingly and to always prompt for "Void Authorization" for negative dollar amount which creates a CR (Credit refund) or VO (Void) type transaction for the accordingly.

Only the SA and CR type trx update the Accumulated Deposits as a dollar amount was paid or refunded.

The AU and VO type trx are not reflected in the Accumulated Deposits total as no dollars were exchanged.

SRM-2759

Enhancement

The Texada Pay -Terminal Payments uses "processor_response" for response text on Global Payments to improve the clarity of the error to the end user.

SRM-2669

Enhancement

Texada Pay Credit Card payments and deposits for Canadian and U.S. currencies can be voided in SRM before posting when an order is cancelled but only on current documents and on the same day the original payment was taken.

When a Texada Pay Credit Card payment is Voided an audit record is written to the <Texada Pay Payment Log> (TPLOG01).


Users, Authentication and Security

Ticket #

Type

Description

SRM-2976

Enhancement

The <Time Clock> processing only requires the operator code and not the password when the external 'Authentication' feature is enabled in the <Texada Support Parameters>.

When the external 'Authentication' feature is enabled in the <Texada Support Parameters> and an operator does not have <Security Role Permission> (ROLE01) to access a process controlled by the <Module Password> (RSMP01) security, the attempted action comes to a hard stop because the external 'Authentication' feature does not respect a password over-ride by the Supervising operator.

SRM-2866

Enhancement

To ensure system integrity and functionality several critical configuration tables and <Company Parameters> that control export directories and script fields have been restricted to be modified by SCS staff only, including <Cash Drawer> (RSDO01) setup, <Fax Commands> (GLCN90N), <Descartes Configuration> (GLCN90N) pathnames, <Approval Plus> (GLCN90N) directories, and <Daily Close Parameter> (GCLN90M) export directories.

SRM-2982

Enhancement

Added a ‘Change Division’ button to the home screen of Texada SRM, allowing users to change their division without logging out.


Utilities

Ticket #

Type

Description

SRM-2951

Correction

Bug - RSRI10 <Update Asset Tag Utility> was not generating the warning when the user was unable to access Asset Tag Info because of the missing tag quantity.

SRM-2919

Correction

Bug - There was a typo in the <Asset Tag Import> (RSRI27C) prompt for the 'Depreciation Date'.

SRM-2893

Correction

Bug - The <Clone Rental & Sales Products> (RSPF46) utility was copying any existing 'Current Rental Days' from the source asset to the newly created assets when a bulk clone was executed.

SRM-2889

Correction

Bug - A proper mailing error message is generated by the <Customer Balances Export> (XMLEXPA) when the <Email Configuration> does not have a valid smtp host name defined.

SRM-2868

Enhancement

The <Import Asset Tag> (RSRI27) utility now prompts for a 'Depreciation Date' to assign to the new depreciation transactions on each Asset Tag, instead of adding the new the records to history as of the current date.

The 'Depreciation Date' specified for the import needs to be later than the date of the last posted or unposted depreciation trx for the given tag, or the line detail will generate an error and will fail to be imported.

Any product line item that has a new 'Acquisition Date' submitted on Import that is later than the first Depreciation record already captured for that product, will also generate an error and fail to be imported.

SRM-2854

Enhancement

The <Current Product Status Report> (RSAR07) can now be exported to an Excel spreadsheet or output to a PDF report.

The spreadsheet output provides the 'Alternate Location' flag in the STAT column to identify non-bulk rental assets with a Product Status of A that are out on a Contract but have a quantity on-hand at a different Location from that of the Contract.

SRM-2844

Correction

Bug - If the 'Date Due' is changed to a future date in the <Change Contract Date Out/Date Due> (RSCH16) utility on a Contract that was previously only out for 1 day, and has multiple rental product details but where the last product detail line is a zero rental charge, then the total rental charge was changed to zero instead of recalculating correctly.

SRM-2800

Correction

BUG - The <Inventory Clean Up Tool> (INCL03) was importing the blank for the 'Vendor Product Numbers' from col AX on the spreadsheet even when the import parameter was set to "Ignore Blank Values".

SRM-2659

Enhancement

The <Inventory Clean-up Export/Import> (INCL02) utility for rental and sales products has been expanded to include the 'Alternate List' value and for non-bulk rentals to include the 3 character 'Telematic Vendor' code and the 'Telematic ID'.


Work Orders

Ticket #

Type

Description

SRM-2833

Correction

Bug - WO Deposits were not properly re-calculating actual deposit amounts taken and still included Authorized Only amounts and voided TP payment amounts in the Deposits Held total.

The incorrect Deposit Total was then reflected on the printed Work Order document.

SRM-2827

Correction

When a Work Order is created from a Contract and the customer assigned to the W.O. is different from the source Contract, an error was generated and the Work Order was not created.

The W.O. should be created and assigned the new customer#.

SRM-2804

Correction

Bug - Split Billing on <Work Orders> (WOWH01) was allowing the total of the split billing to be greater than 100% and was then generating a credit to force the total to balance.

January

Version 2021.04

Document Header Line-1

Inventory Control

   

Ticket #

Type

Description

SRM-2702

Enhancement

To delete an 'Inspection Form' that is no longer useful but is still in use assigned to a <Group> Z(RSGF02) or a <Model> (RSMM01), the delete action in <Inspection Forms> (FLINSP06) triggers a warning with the number of records currently assigned. The option is provided to automatically remove the form from these records and proceed to delete the form. If the forms are not removed from these records, the Inspection Form cannot be deleted.

SRM-2677

Correction

The <Inventory Count> manual and import updated worksheet quantities has been improved to handle multiple quantities for the Time-Of-Sale Serialized Parts and Serialized Sales Parts better.

SRM-2463

Correction

The <Inventory Search> (RSEQ01) used in the Counter documents with filters for all available products by description, was incorrectly showing assets with <Product Status> flagged for "Available" set to N.

SRM-2445

Enhancement

The <Re-Order Information> (RSRQ50J) window accessed from the <Detailed Inventory Inquiry> (RSPF60) was not properly displaying the "gear" icon 

SRM-1641

Correction

Merge Rental Product Numbers function, RSPFR74 is not considering Asset Finance information in tables AFDTL and AFHDR & was preventing Asset Finance Posting.

 

Integration

   

Ticket #

Type

Description

SRM-2686

Correction

An <Invoice> resulting from a <FIFO Return> for contracts with manually modified rates was not reflecting the changes in the Contract rates.

 

Accounts Receivable

   

Ticket #

Type

Description

SRM-2681

Enhancement

The <Descending Purchases Report > (ARCF48) can be added to the menu tree. However, it is not GUI-ized and the selection filter screen displays badly.

SRM-2585

Correction

Emailing an invoice from <Customer Account Inquiry> (ARAR05) only returned the first <Contact> as a recipient instead of all eligible Contacts to receive Invoices.

SRM-2528

Enhancement

Lockbox Payments have been enhanced to provide the option to apply to the Customer-defined Division or a Selected Division for this batch.

SRM-2485

Enhancement

A Texada Pay refund through <Customer Payments> was not providing the option to print a receipt.

SRM-2470

Enhancement

The "Trading As" value has been added to the Customer - <Standard Data Imports> (IMPORT).

SRM-2404

Enhancement

The option to Auto-apply a payment to Invoices in <A/R Customer Payments> (ARAR03) and in <Counter Payments> (ARPC01) is disabled for payments of a negative dollar amount.

SRM-2366

Enhancement

The <Tax Exemptions> (DCTX01) tables used by 'Enhanced Taxing' on each Customer, Site, Division, Class and Service record can now be populated using a Bulk Add utility and conversely a Bulk Delete utility useful for cleanup.

 

Accounts Payable

   

Ticket #

Type

Description

SRM-2490

Correction

Unable to post AP Invoices after 'Import AP Invoices' due to a blank Repair Code so APVHFX has been added as option 25 to the Support FXMENU.

SRM-1608

Correction

If a company had no blank <Vendor> (APVF01) defined, the error "Vendor Not Found [APVF]" was thrown and the session crashed when the "Alt Pay Address" window was accessed for any vendor from the 'Additional Information' screen.

 

Texada Pay

   

Ticket #

Type

Description

SRM-2680

Correction

When a payment request for an Invoice was sent to a customer, the note that the “Email request has been successfully submitted” was not being triggered the way it does for a Deposit payment request.

SRM-2657

Correction

To better synchronize Texada Pay payments between SRM and OpenEdge, the abort option after 45 seconds has been removed to prevent processing a payment in the clearing house but cancelling it in SRM.

SRM-2643

Enhancement

The same Credit Card number with the same Method of Payment is only stored once in the <Customer Information> so if the same card with the same method of payment is captured a second time, the old token will be deleted and the new one will be used. The name/expiry will also be replaced.

SRM-2609

Enhancement

The Global Payments Authentication tokens have been moved into the Card Readers/Divisions window to allow multiple tokens per company to accommodate payments received into different bank accounts.

SRM-2608

Enhancement

To avoid too many duplicate payment check numbers, the "Check/Reference Number" in <Counter Payments> (ARPC01) and <Customer Payments> (ARAR03) defaults to the method of payment followed by a 4 character last used number.

This can be over-typed as required with an actual Check number.

SRM-2607

Enhancement

The <Method of Payment> descriptions for Texada Pay options M and A have been changed to be more clear in the drop-down boxes where:

A is "Texada Pay Terminal or by Issuer" and M is "Texada Pay Manual or by Issuer"

SRM-2324

Enhancement

The Issuer for TP Credit Card payments has been added to the <Texada Pay Log> (TPLOG01) output and the customer driven <Texada Pay Log Inquiry> (TPLOG02).

Other Texada Pay associated data fields have also been added to the spreadsheet output of the <Texada Pay Log> (TPLOG01)

 

Counter

   

Ticket #

Type

Description

SRM-2667

Correction

When a billing <Invoice> with a source document such as a <Contract> is deleted, a <Document Comment> is automatically written to the source document to note the deleted invoice with the 'Comment' default Print flag is NO.

SRM-2625

Correction

When a new customer is added on-the-fly from the <All In One> (RSTXH01) screen an "Invalid Rental Period" error was thrown at the Email Address input field.

SRM-2581

Enhancement

The Sub Total and Total values on a Sales Invoice with Discounts, directly printed from an <All-In-One Trx> (RSTXH01) were not displaying correct dollar amounts.

SRM-2569

Enhancement

The last signed <All In One Doc> (RSTXH01) can be reprinted from within SRM using the 'RentSalesTrx' Jasper form.

SRM-2527

Enhancement

An Off rental rounding issue in the time off-rent was causing incorrect calculation and billing of on-rent time.

SRM-2522

Correction

A SQL error was being thrown when contracts were printed from the <Reprint Contracts> (RSCD10) utility.

SRM-2481

Enhancement

When a <Quotation> is converted to an Invoice, Reservation, or Contract and the prompt to "Record Clerk Accessing Quotes" is set in the <Company Security Parameter> the <Clerk Confirmation> pop-up is triggered in each of the convert utilities.

The Clerk that is captured in one of these convert utilities is then updated on both the source Quote and the resulting Invoice, Contract, or Reservation.

SRM-2415

Correction

The option is provided to include or exclude Credit Lines in the <Create Credit Invoice From Existing Invoice> (RSCM02) program.

If Credit Lines are included they are added as positive amounts on the resulting credit invoice.

SRM-1835

Enhancement

Deposit Requests can be emailed to the customer for Contracts or Reservations from the Totals screens (RSCH03 & RSRH03) or from the additional Deposit utilities (RSCH15 & RSRH15).

 

Email

   

Ticket #

Type

Description

SRM-2656

Enhancement

With 'GMail,' an API key needs to be setup in the <Web Service API Keys> table because the API service can locate the company when processing the authentication callback from GMail.

 

Work Orders

   

Ticket #

Type

Description

SRM-2655

Enhancement

Reversing Work Orders generated from <Create Credit Work Order> (WOWH33) were not returning the negative parts used back to stock.

SRM-2647

Correction

Products due for Maintenance Type 1 were not always appearing in the Maintenance Schedule Edit report because of an inaccurate day count.

SRM-2520

Correction

Comments added to a contract were not reflected on the Delivery and Pickup Tickets.

SRM-2477

Correction

The Employee code was not always captured correctly in the <Work Order> Labour window when the employee had no hourly rate defined for his Labour Service.

SRM-2419

Correction

Maintenance report notes for one type of scheduled maintenance were appearing on a different maintenance Work Order for the same product.

SRM-2268

Enhancement

The SRM Software references to FleetLogic have been update to Texada Web in the application and the Technical User's Help Manual.

 

Purchase Orders

   

Ticket #

Type

Description

SRM-2626

Correction

The hard coded <Order Code> (INPOC01) of 'INACTIVE' was not preventing Products from being added to the <PO Worksheet> (POWH10) automatically from RSPO20 or manually from POWH01.

SRM-2549

Enhancement

The Delete PO option in <Purchase Orders> (RSPO01) accepts and deletes a blank PO# if the P.O. is in the operator's Restricted View divisions.

SRM-1615

Enhancement

PO approval feature enhancements:

- Any Approver with an allowable Limit above the P.O. total can approve/reject a Purchasing Request, not just the Approver assigned to the requesting Operator and then this Approver becomes responsible to approve the P.O.

- The original purchasing Requester as well as any Approver with an allowable Limit above the P.O. total can re-access and update the Purchase Order.

Screen reader support enabled.

 

System Maintenance

   

Ticket #

Type

Description

SRM-2613

Correction

The "Create W.O. from Create Contract" feature was not respecting the division & location mapping as defined in the <Division WO Parameters>.

SRM-2509

Enhancement

When a Company is flagged as "Disabled" in the <Licenses & Reserved Runtimes> (SCN50), utility users can no longer log into the software.

SRM-2496

Enhancement

The invoice numbers with payment details are printed on the Jasper Receipt for a payment submitted through <A/R Customer Payments> (ARAR03).

SRM-1022

Enhancement

AP Direct Credits can now be submitted to the TD Bank.

 

Data Management

   

Ticket #

Type

Description

SRM-2610

Enhancement

When the 'Group Mapping' has invalid data for the <Customer Pricing Management> the import error to "correct the Quote Groups" is thrown and the import is aborted.

SRM-2537

Enhancement

Barcode printing has been updated to prevent locking other sessions.

SRM-2480

Enhancement

The job RSFR90A has been added to automatic job scheduling to "Purge Old Off Rentals" for Contracts that have been moved to hiEnhancement.

A record is written to the <Delete Log> to identify deleted Off-Rental transactions.

 

API

   

Ticket #

Type

Description

SRM-2568

Enhancement

The Work Order "Posting Type" information of S - Standard, D - Customer Damage, R - Customer Repair or I - Internal has been added to the WOWH table sent from SRM to Texada Web.

SRM-2546

Correction

The Work Order Parts API for split or warranty billing was calculating all the charges using percentages of the Extended price, instead of basing the calculation on a percent the 'List Price' for the Customer portion and percentages of the 'Average Cost' for the Internal and Warranty charges.

Screen reader support enabled.

SRM-2515

Enhancement

When a detail line was deleted from a Rental Return Invoice by an API, the quantity was not being read in properly.

SRM-2421

Enhancement

Split Billing dollar amounts can now be submitted on a Work Order Add & Update APIs for Parts, Labour and Services, which over-ride split percent values when both dollars & percentages are passed in.

 

General Ledger

   

Ticket #

Type

Description

SRM-2559

Enhancement

Unable to reconcile the Bank Account due to a rounding issue so GLGLFX has been added to the Support FXMENU to address rounding issues in the G/L.

SRM-2283

Correction

When the <Trial Balance> (GLGL10) detail report included more that 75 G/L Accounts and was output to PDF using the "Page Break By Account" option, it would fail and hang the Open Client session.

 

Back Office

   

Ticket #

Type

Description

SRM-2558

Enhancement

When the <Daily Close 1> is configured to post by Division using Batches, a spreadsheet is generated to list invoices in previous batches, with invoice #, customer #, DBR#, and on hold flag.

 

Reports

   

Ticket #

Type

Description

SRM-2540

Enhancement

The standard Taxes written-off and collected in the <Bad Debts> & <Collections> utilities are now reflected on the <Tax activity Report> (GLGL30) generated for the BAS (Business Activity Statement) reporting.

SRM-2474

Correction

The <Rental Inventory Value Report> (RSIT24) has been changed to respect the operator assigned "Restricted Views".

SRM-2338

Correction

The <Customer Revenue Report> (RSSH17) was not generating the expected data when the selected 'Customer Type' filter was BLANK.

SRM-2242

Correction

The <Automatic Reporting> for RSPO20 <Inventory Re-Order Report by Vendor> was not generating expected results because the From/To selection fields for the Vendor/Group/Class were not right justifying the filter values.

 

Utilities

   

Ticket #

Type

Description

SRM-2538

Correction

The <Export/Import Group Inspection Forms> (RSGF35) utility can be used to update the Inspection Forms assigned to each <Group> (RSGF02) by exporting a template with or without the existing values and re-importing the modified values.

The assigned Inspection Forms can be flagged to apply to Work Orders, Inspections, Delivery, and/or Pickup Tickets, respecting the type of form configured in <Inspection Forms> (FLINSP06).

 

Signature Capture

   

Ticket #

Type

Description

SRM-2534

Correction

In <Contract> entry when a new Contact is added with email information for a newly added Cash customer, the Contact's email address was not populating the 'To Email' for an eSignature request on that Contract.

 

Tech Debt

   

Ticket #

Type

Description

SRM-2563

Correction

The internal <Equipment Search> (RSEQ01) deCorrectionging has been enhanced so that it only messages when the environment variable is DECorrection_SEARCH_SQL=Y and only for the logged SCS operator. The deCorrection tool (RSEQ02) will now log more details to a text file and download the text file to the client when done.

SRM-2534

Correction

In <Contract> entry when a new Contact is added with email information for a newly added Cash customer, the Contact's email address was not populating the 'To Email' for an eSignature request on that Contract.

SRM-2529

Correction

The 'Product Selection Search' (RSEQ01) used in documents has been optimized to speed up response time for searches by location/class/group but with no product description.

 

Payment Processing

   

Ticket #

Type

Description

SRM-2486

Enhancement

A 'Division' selection filter has been added to the <Payment/Deposit Request Inquiry> (LGC006) that respects the Operator's <Divisional Restricted Views> and the division is also included for each document on the resulting inquiry details.

 

Back Office

   

Ticket #

Type

Description

SRM-2449

Enhancement

Option #22 on the FXMENU has been modified to allow change to the DBR#

 

Jasper

   

Ticket #

Type

Description

SRM-2443

Enhancement

Jasper PO Revisions:

a) Allow space in header for a longer Account#

b) Wrap product description rather than truncate

c) Space between Vendor Product# and product Description in detail lines

d) Add header Notes and Clerk info below product detail lines to the Duplex form

SRM-2231

Correction

The "Rental Period" can be printed on rental documents. including the invoices, contracts, reservations, and quotations.

This is controlled for the contracts, reservations, and quotations by the 'Print Rental Period' flag in the <Division Contract Parameters> and for invoices by the 'Print Rental Period' flag in the <Division Invoice Parameters>.

SRM-2029

Enhancement

In order to minimize negative RSIL quantities for <Sales Inventory> the <Purchase Order> and <Warehouse Receiving> of negative quantities always checks and prevents returning of more quantity than available at the location.

 

Integration

   

Ticket #

Type

Description

SRM-2378

Enhancement

The <Texada Pay Pending Refund Queue> (TPRNT01) table optionally logs any failed Texada Pay Refund transactions that could not be processed through the clearing house because the original deposit or payment has not been approved yet.

This could be a common occurrence for a Card-Not-Present refund on the same day as the original payment of an Invoice or refunding of a Security Deposit.

The refund transactions can then be re-submitted to the clearing house manually at a later time or through <Auto Reporting> using job TPRNT02.

 

Custom Integration

   

Ticket #

Type

Description

SRM-2372

Enhancement

The <Rental Inventory Value Report> (RSIT24) can now be selected and printed by product number regardless of class.