New Enhancements ................................................................................... ii Attention: M.I.S. Manager .................................................................... viii Pre-Installation Checklist – Version 2010.4x to Version 2012 ............. ix Post-Installation Instructions – Version 2010.4x to Version 2012 .........x Orphaned Repair Order Listing ............................................................ xii Attention: Maintenance Manager .......................................................... xv New Documents ...................................................................................... xvi Menu Selections ....................................................................................... 17 Database Changes .................................................................................... 20 Legend ....................................................................................................... 26 Shop Menu ................................................................................................ 27 Facility Menu ........................................................................................... 54 Unit Menu ................................................................................................. 55 Fuel Menu ................................................................................................. 58 Tire Menu ................................................................................................. 60 Part Menu ................................................................................................. 61 Warranty Menu ....................................................................................... 67 System Menu ............................................................................................ 68 Results Now .............................................................................................. 85 New Firmware .......................................................................................... 86 Pur/Inv Menu ........................................................................................... 92 Purchasing ................................................................................................ 92 Invoicing ................................................................................................... 97 Shop Floor Automation Menu .............................................................. 100 Accounting Menu ................................................................................... 108 Appendix A - Pre-Conversion Programs ............................................. 111
ii
TMT Fleet Maintenance™ for IBM i - Version 2012.41
The PCR number and the page numbers listed below in the New Enhancements section are linked to the PCR.
Click on the blue PCR number to “jump” to the PCR note to see more information for the PCR.
After you review a PCR note, you can click on the blue “New Enhancement” link (in the PCR note), and you
will return to the PCR note in this section.
Shop Menu We added a new Firmware that allows you to determine whether Campaign & Work Pending comments
should be retained on the Repair Order when an RO is being closed.
For more information see PCR 3083 on page 30 and page 87
New indicators when an Employee is currently working on an RO Section. New options when canceling a
Repair Order associated with a Road Call or Plan.
For more information see PCR 3184 on page 32
You now have the ability to edit Campaign Section Comments, and they will automatically update all Work Pending’s that have the Campaign assigned to it.
For more information see PCR 2777 on page 35
We added a new Command Key “F10=Mass Create” for Work Pending.
For more information see PCR 3107 on page 36
We added a new wildcard option flag to the Assembly portion of the System Code in the RO/System search screen.
For more information see PCR 2951 on page 39
We added new fields to the RO History Listing selection screen.
For more information see PCR 2587 on page 40
We added new fields to the RO History Outfile report.
For more information see PCR 2998 on page 41
We added a Supplier “Remit-To” field to the Repair Order Listing search screen.
For more information see PCR 3089 on page 41
iii
We added additional fields for the RO Inquiry Detail, (Menu Selection 132 – RO Inquiry Detail).
For more information see PCR 3145 on page 42
We added a new “Navistar Repair Advocate” module for Road Calls. This Module will allow you to link Navistar Dealers to the selected Supplier used on the Road Call, without a requirement to add all the Navistar Dealers to the Supplier Master.
For more information see PCR 2966 on page 44
We added a Mobile Communication Module for the PeopleNet eDVIR Message Import/Export.
For more information see PCR 2979 on page 48
We added a new option flag to the TMTCODES Category “PAY METHOD”.
For more information see PCR 2993 on page 50
We added a new option that allows the user to select from multiple “Remit To” vendors for a Vendor RO.
For more information see PCR 3015 on page 51
We added the ability to prompt for a VMRS Code in the Part Number field for RO Charges when the Source is ‘V’. We also added a new Firmware – “ORO - Prompt for VMRS Code on “V” lines”.
For more information see PCR 3204 on page 53 and 91
Facility Menu No New Enhancements
Unit Menu
We added a new API that will allow you to add or update Units in the TMT Unit Master.
For more information see PCR 3004 on page 55
We added new Listing Options for the “Unit System Cost Analysis” report. The Web Version includes a bar graph and pie chart. The report allows the User to “drill down” and display the RO’s that are included in the “Unit System Cost Analysis” Summary.
For more information see PCR 3145 on page 56
Fuel Menu We added the ability to select the Fuel Types included in the totals for the “Unit Fuel Analysis” report.
For more information see PCR 2977 on page 58
We added a new option for the “Fuel Import Error Listing” report.
For more information see PCR 2923 on page 59
Tire Menu No New Enhancements
iv
Part Menu We added a new feature that will allow you to assign Serial Numbers to parts. Serialized Parts are tracked
with the Serial Number from Purchasing to RO, Invoice, or Indirect Charges and Part Transfers.
Note: Your UserID’s for the Mechanic Workstation needs to have security to Menu Selection 100, option
4=Charges if you allow Mechanics to charge parts.
For more information, see PCR 2909 on pages 32, 47, 62, 64, 65, 66, 86, 95, 101
We added the Wildcard Search feature to the Part Number column for the Part Master and Part Catalog. For more information, see PCR 3155 on page 61
We added two new options for the Part Usage report when selecting the “No Usage” option.
For more information see PCR 3018 on page 62
We added a new Firmware for the barcode Zebra Printer that will allow you to choose a Label Size of1”x4”.
For more information see PCR 2984 on page 63 and page 89
Warranty Menu No New Enhancements
System Menu We have introduced a Mobile App for the Mobile Computing Module.
For more information see PCR 2682 on page 68
We added a new field named “Rpr Days” for System Codes.
For more information see PCR 2884 on page 68
We added a new feature that will automatically keep a log of any Repair Order PM sections as they are
Added, Changed, or Deleted.
For more information see PCR 3049 on page 69
We added a new option to the Miscellaneous Menu that allows you to access the Stored Procedures Master listing.
For more information see PCR 2587 on page 70
We added a new feature that allows the user to display the System Information.
For more information see PCR 2587 on page 71
We added a new Web Service to allow PeopleNet PerformX ECM Meter imports.
For more information see PCR 2960 on page 80
We added a new Module that allows you to import eDVIR’s from a Qualcomm unit.
For more information see PCR 3060 on page 80 and 81
We added new Firmware to display the RO Header or Sections in the RO inquiry.
For more information see PCR 2587 on page 86
We added new Firmware to allow you to choose the default part & labor date for Vendor RO’s.
For more information see PCR 3041 on page 88
We added new Firmware that causes the accounting export to check for the InterCompany Account setup.
For more information see PCR 2587 on page 90
v
We added new Firmware that will allow the TL2000 interface to use a unique vendor number in the Supplier Master.
For more information see PCR 2587 on page 90
We added new Firmware that allows you to select whether or not the list of mechanics will be displayed on the Mechanic Workstation login screen.
For more information see PCR 3020 on page 91 and 102
Purchasing Menu No New Enhancements
Invoicing Menu We added new options that allow you to define which line types will be included in the “Fee” calculation for
Invoices.
For more information see PCR 2948 on page 97
We added a new Menu Selection – 1082 – Invoice Aging Report.
For more information see PCR 3032 on page 99
Shop Floor Automation Menu Do you need an Exit to run when you post Time Cards?
For more information see PCR 3043 on page 103
We added a Time Card Limit of 100 hours.
For more information see PCR 3112 on page 102
We added a new option to the "Request Sts" field for the Parts Workstation. The new option will allow you to select only 'New' part orders.
For more information see PCR 2919 on page 106
We added a new Firmware that will allow you choose to display only Assigned work in the Repair Order
Work listing. For more information see PCR 3114 on page 90 and page 100
We added new options and Command Keys to the Supervisor Workstation.
For more information see PCR 2441 on page 103
We added the ability to use Job Codes with Non-Company Units.
For more information see PCR 3118 on page iii, 105, and page 106
We added the ability to add or require comments to Indirect Labor from the Mechanic Workstation, and the ability to print comments on a Time Card.
For more information see PCR 2493 on page 91, and page 101
We added new Firmware that allows you to select whether or not the list of mechanics will be displayed on
the Mechanic Workstation login screen.
For more information see PCR 3020 on page 102
vi
Accounting Menu We added a new Firmware that allows you to control the "created by user" ID displayed on REPAIR
transactions in the accounting export.
For more information see PCR 2956 on page 89
We added a few new enhancements for the TL 2000 interface.
For more information see PCR 3001 and 3007 on page 108
vii
ResultsNow
Results Now by TMW™ offers a constant dashboard view of real-time business performance information.
It provides the customized details needed to make informed decisions based on performance metrics for shops, units, fleets, and more.
These metrics, or Key Performance Indicators (KPIs), can vary depending on your business needs. View the unique KPIs from the ResultsNow dashboard and configure by day, week, month, quarter, year, and fiscal year. Tracking the KPIs provides detection of any trends and allows response to the trends an easier task to handle.
In addition to providing daily visibility to your key performance indicators on-screen, ResultsNow can also issue notifications via email to appropriate personnel whenever a threshold is violated — for example, if a PM due compliance percentage falls below the set standard.
viii
Attention: M.I.S. Manager
General Information
Installation instructions are found in the Documents directory on the CDROM or CD Image you received with this upgrade. They are also available on the TMW Client Center website.
If you have obtained this Readme from any source other than Client Center, and need to obtain a new copy, you can download it at www.tmwcare.com. (Client Center will only have the most current version of the Readme). If you need a copy of a Readme for a previous version, or you don’t have a Client Center login, please contact [email protected] or call 919-493-4433 to obtain one.
If you are upgrading from a prior version of TMT Fleet Maintenance™ for IBM i, please read the Pre-Installation Checklist appropriate for your current version of TMT Fleet Maintenance for IBM i.
Print files: If you have made any changes to the TMT print files, (in library TMTPGMS), be aware that the
upgrade process will reapply the default settings. You should make a backup copy of any print files you have changed, and reapply your changes after the upgrade has completed.
In V2012.10 the standard RO print program was changed from TMT111P to TMT113P. This program will print the RO in landscape on most HP style laser printers. In order to print the RO portrait use this command to change the settings:
Be aware that any item listed in this document with the open file symbol, ‘’ indicates a data file conversion will run during the upgrade. See the “Legend” at the end of this document for more information.
In Version 2007 we added module security which includes the Accounting Export module. Prior to Version 2007 the Accounting Export transaction creation program (TMT895) did not perform any security checking. Now TMT895 calls our generic security checking program (TMTSECCK). This program validates a user’s right to be in the TMT Fleet Maintenance software and performs Add/Change/Delete/Inquiry checking and since Version 2007, performs module checking. The “user” that submits the TMT Fleet Maintenance EOD process whether done manually using Menu Selection 820, or with a scheduled job must be setup in TMT Fleet Maintenance in Menu Selection 835 - User Profile Master. If the user is not listed, program TMT895 will exit immediately upon checking security and will not create Accounting Export transactions. (The EOD will run successfully without errors, but Accounting Export transactions will not be generated). If you use the Accounting Export and use Scheduled Jobs to run the EOD Process, please be sure the user you have specified in any Scheduled Jobs that run the EOD, are listed in Menu Selection 835. The user does not need to have any specific authority for any of the Menu Selections or sub-options; it just needs to be in the list.
Pre-Installation Checklist – Version 2010.4x to Version 2012
Please review this document, and forward copies to the appropriate TMT users.
Please review the V2012 Pre-Install checklist document for additional information before you begin the
Upgrade, and forward copies to the appropriate TMT users.
If you are using TMT Fleet Maintenance/Shop Floor Interactive, (the TINA Module), prior to installing the upgrade, you will need to Log out all employees, and Post all Time Cards.
Run the EOD Process, (Menu Selection 820), to move all closed Repair Orders, Indirect Charges, and Fuel Tickets to history.
If you use the Advanced Barcode Module, you will need to be sure all transactions have been processed. Use Menu Selection 853, and make sure all of the files listed display zero records. You will also need to use a data base utility tool like DFU or DBU to make sure file BCUPLOAD contains no records.
The “ACCRUAL” member for the Accounting Export files, (ACTXTRAN & ACTXTRND), is replaced anytime you perform a Full Version upgrade. The data will be replaced the next time you run the “Export Accrual Report” from Menu Selection 1220. If you want to retain the data in the “ACCRUAL” member for these files you should plan to create a backup for these two files, (ACTXTRAN & ACTXTRND).
Read “Appendix A – Pre-Conversion Programs” at the end of this document to prepare for the Pre-Conversion special instructions.
If you have Exits setup and in use in Menu Selection 851 – Exits Master, be aware that we have deleted some and combined them with other existing Exits for Repair Orders and Outside Repair Orders. Please review your list of Exits prior to the conversion, and after the conversion to be sure you have them setup properly for your needs. See the Post-Installation Instructions section for a list of changes in TMT Exits.
Please use Menu Selection 848 – Field Change History and review your list of ‘Active’ files prior to the conversion, and/or create a list of ‘Active’ files to be sure you have them setup properly for your needs. After the conversion has completed, and you have entered the new Security Code, use Menu Selection 848 – Field Change History and use option 6=Activate to set the Status to ‘Active’ for all files that you want to track Field Change History for.
We are providing the TMT Version 2012.30 and above for users at IBM i OS Version V5R4M0 or V6R1M0 and above, depending on your current IBM i OS Version. The Version provided for V6R1M0 and above includes embedded objects necessary for the Qualcomm Communication Module. Note: You must be at IBM i OS Version V6R1M0 or above to be eligible to use the Qualcomm
Communication Module. If your current IBM i OS Version is V5RxMx, you will receive a “V5” version for your next upgrade. If your current IBM i OS Version is V6RxMx or higher, you will receive a “V6” version for your next upgrade. If you upgrade your IBM i to OS Version V6RxMx or higher at some point in the future, and you wish to purchase the Qualcomm Communication Module, you may upgrade to the current version of TMT to receive the embedded objects needed at IBM i OS Version “V6” to use the Qualcomm Communication Module. For more information about the Qualcomm Module, see the notes in the “System Menu” section of this document.
x
Post-Installation Instructions – Version 2010.4x to Version 2012
Review Menu Security for new Menu Selections, Sub-options, and Command Keys. (See the lists in the Menu Selections section below).
o Note: Your UserID’s for the Mechanic Workstation needs to have security to Menu Selection 100, option 4=Charges if you allow Mechanics to charge parts.
If you use the Fuel Import Profiles in Menu Selection 499 – Fuel and Meter Import/Export, you will need to define values for the “Trip Ticket” item. (This is required, even if you do not have a “Trip Ticket” number included in your Fuel Import data file).
o If you do not have a “Trip Ticket” value in your Fuel Import file, you may substitute any other data, (except a “blank” column).
Tip: Substitute the Unit Number for the “Trip Ticket” value. Use the same values you have defined for “Unit Number” item in the Fuel Import Profile to define the “Trip Ticket” item.
The conversion will set the sub-option rights for MS 833, 8, & 10 to ‘N’ for all Users. For more information see the notes for Menu Selection 833 in the System Menu section.
After the conversion has completed, and you have entered the new Security Code, use Menu Selection 848 – Field Change History and use option 6=Activate to set the Status to ‘Active’ for all files that you want to track Field Change History for. Please review your list of ‘Active’ files prior to the conversion, and create a list to be sure you have them setup properly for your needs.
xi
If you have Exits setup and in use in Menu Selection 851 – Exits Master, be aware that we have deleted some and combined them with other existing Exits for Repair Orders and Outside Repair Orders. Please review your list of Exits prior to the conversion, and after the conversion to be sure you have them setup properly for your needs.
o New Exits:
Exit Exit Description
Program Type
TMT991 ADD Add
o Changed Exits:
Exit Exit Description
Program Type
TMT181 LOC Service Locator - changed to TMT111 LOC
TMT183 IFO Change – changed to TMT117 IFO
TMT183 INV Edit – changed to TMT117 INV
TMT840U EXT Exit – changed status to Inactive if the Called
Program begins with ‘CLTMA’, ‘CLTMI’, or ‘TMI’
o Deleted Exits:
Exit Exit Description
Program Type
TMT100H F24 Function Key
TMT120 F24 Function Key
TMT180L F24 Function Key
TMT181 ADD Add
TMT181 CHG Change
TMT181 EDT Edit
TMT181 ENT
TMT181 LOC Service Locator
TMT182 ADD Add
TMT182S ADD Add
TMT182S CHG Change
TMT182S ENT
TMT183 EDT Edit
TMT183 IFE Interface
TMT183 IFO Interface
TMT183 INV Invoice
TMT183 VCP COMDATA MasterCard
xii
Orphaned Repair Order Listing
During the Upgrade to Version 2012, the conversion program will make every effort possible to match up all existing Repair Order numbers in all files and assign them with a Repair Order ID Number, (ROID#). This new ROID# is used in all of the files that store the Repair Order Number, and is used as a unique identifier for all Repair Orders. In previous versions, when the RO Number sequence reached 999,999, the Next Number assignment program rolled the number back to '1', and this allowed duplicate RO Numbers to exist in the TMT Fleet Maintenance system. In Version 2012, each RO will have a unique ROID#, so even if there is a duplicate RO Number in the system, the ROID# will be used to link all of the RO Header, RO Sections, Comments, Parts and Labor Charge records together. This design will prevent orphaned Comments, Parts or Labor Charges from a previous RO from being displayed on a new RO with the same RO Number. You can also take advantage of the seven digit RO Number to extend the cycle between RO Number rollbacks. If the conversion program is unable to find a match in the RO files, you will be able to view them in the "Orphaned RO Listing", (program TMT100E). This listing can be used to access any Repair Orders that existed prior to the Upgrade to Version 2012.10 that were orphaned or invalid for some reason. An example would be a Vendor RO that is missing the Outside Repair Master PO information record stored in file “OUTRPRMS”. After the Upgrade, these orphaned RO's will not be displayed in Menu Selection 100 - Shop Repairs, or Menu Selection 180 - Outside Repairs. You will need to temporarily add a Menu Selection to the User Menu 9 to access them. This is a one-time event. Once you have viewed, deleted, or changed the RO, you will no longer need this temporary Menu Selection. To view these RO's you will need to use Menu Selection 837 - Menu Selection Master, to temporarily add a Menu Selection to the User Menu 9. You will need an available Sequence Number (empty Menu line) on Menu 9. The Sequence Number determines the position of the Menu Selection on the Menu 9 page. In the left column, the available positions are 1 - 16. In the right column, the available positions are 17 - 32. (1 & 17 are at the top of the column, 16 & 32 are at the bottom of the column). If you have any files that result in orphaned Repair Order records, there will be a “Record Error Log” report for each file where the Order ID could not be found. These reports are sent to the Spool File for user QSECOFR. It is recommended you save and archive these reports for any analysis that may be needed in the future.
xiii
Use the example below to add a Menu 9 selection to access the "Orphaned RO Listing". (You will need to determine and select your own Menu Selection and Sequence Number).
Be sure to remember to use Menu Selection 836 - Menu Security Master to set security Rights for this new Menu Selection. You will also need to exit TMT, and then sign back into TMT before the new Menu Selection will be displayed on Menu 9.
Use the new Menu Selection to display the "Orphaned RO Listing". It looks very similar to the "Shop RO Listing" displayed in Menu Selection 100, including a Listing Options window with Program and User Defaults options.
xiv
If RO's are listed, then you can use the options to view, delete or change the RO Type.
1) Use option 4=Delete to delete the RO and all of the related records in the new ROHEAD, ROBODY, and
ROLINE files.
*This will most likely be the course of action selected for the majority - if not all of these orphaned RO's.
When this option is used, a window will be displayed advising that all sections will be deleted. Enter a 'Y' for "Delete Repair Order" and press F6. If you have selected multiple RO's to delete, repeat these two steps until you have deleted all Repair Orders selected. When you have deleted the last RO selected, the "Orphaned RO Listing" will be refreshed, and the deleted RO's will be removed from the list.
2) Use option 5=Review RO to view the RO. Look to see if the RO is a Vendor RO. If so, is the PO information
displayed at the bottom of the RO Header screen? Are there any sections? Are there charges if sections exist?
If the Vendor ORO PO information is missing, or sections do not exist, or charges do not exist, then there is no negative impact in the TMT system, and the RO can be deleted. If you prefer to cancel the RO and would like to keep the record in RO History as a Canceled RO, then use option 8=Change RO Type.
3) Use option 8=Change RO Type to move the RO to the Standard RO Listing in Menu Selection 100. Select
this option if you need to add sections or charges.
Note: There is not an option to move an RO to Menu Selection 180.
The RO will be moved, even if the RO Shop, Unit Number or Customer Number are no longer in the system or invalid.
When this option is selected, the list will not automatically refresh. To refresh the listing, use F9=Options, then when the Listing Options window is displayed, select the options you want, and press ENTER to redisplay the "Orphaned RO Listing".
The conversion program will set the “ROTYPE” in new file “ROHEAD” to ‘ZZ’. When option 8=Change RO Type is used, the “ROTYPE” will change from ‘ZZ’ to ‘RO’ so that the Repair Order can be
displayed in Menu Selection 100. (It will not be displayed in Menu Selection 100 until you use option 8=Change RO Type.
If you set the Default Options to '*ALL' and no RO's are listed, and the message "No data found to display." is displayed at the bottom left corner of the screen, then you are done. (Be sure to set the all of the defaults to '*ALL' to be sure no more orphaned RO's exist for any Shop). You can use Menu Selection 837 to delete the new Menu Selection you added to the User Menu 9, and use Menu Selection 836 to ensure it was removed from the Menu Security System.
xv
TMT Fleet Maintenance™ for IBM i - Version 2012.41
If you are upgrading from a prior version of TMT Fleet Maintenance™ for IBM i, please read the Pre-Installation Instructions appropriate for your current version of TMT Fleet Maintenance for IBM i.
If you have obtained this Readme from any source other than ClientCenter, and need to obtain a new copy, you can download it at www.tmwcare.com. (ClientCenter will only have the most
current version of the Readme). If you need a copy of a Readme for a previous version, or you don’t have a ClientCenter login, please contact [email protected] or call 919-493-
4433 to obtain one.
Please forward copies of the Release Notes to the appropriate TMT users.
If you are performing a Version Upgrade, this version includes an update for ATA Manufacturer Codes and VMRS Codes. (A Version Upgrade occurs any time the Version number changes - IE - 2010.xx to 2012.xx). A Release Upgrade will not include new ATA Codes. (A Release Upgrade occurs any time the Release number changes - IE - 2012.10 to 2012.40 is a Release Upgrade).
If you would like to import the new ATA Codes included in the update, use the instructions below to choose Manufacturer Codes or VMRS Codes. The user is allowed to run the import in "Reports Only" mode or run the import and update the data files. In "Reports Only" mode a report is generated to display the codes that will be added or changed without actually updating the data files so you can review the new codes prior to actually updating the files. When you choose to run the import, a report is generated and you have the option to set the status of the new codes to Active or Inactive. Import Manufacturer Codes
Use Menu Selection 833, option 8-Import ATA Codes, then option 1 - Import Manufacturer Codes. Use this option to import the most current ATA/TMC updates included with this Upgrade, to the Manufacturers Codekeys file and generate the "ATA/TMC Manufacturer Code Update Listing" report. You will have the option to print the report for review without actually updating the data files. The report will list the new ATA/TMC updates for the Manufacturers Codekeys listed in Menu Selection 800, Category 0034 - Unit Manufacturers.
Import VMRS Codes Use Menu Selection 833, option 8-Import ATA Codes, then option 2 - Import VMRS Codes.
Use this option to import the most current ATA/TMC updates included with this Upgrade, to the VMRS Codes file and generate the "ATA/TMC VMRS Update Listing" report. You will have the option to print the report for review without actually updating the data files. The report will list the new ATA/TMC updates for the VMRS Codes listed in Menu Selection 814 - VMRS Component Master.
New Documents Below is a list of new documents for Version 2012 by Release Number. All of these documents can be found on the Learning Center (on the ClientCenter under the “Communications” tab). You can use your ClientCenter login to download documents at www.tmwcare.com. If you don’t have a login, please contact [email protected] or call 919-493-4433 to obtain one.
Document Name Description Release Number
Physical File Description Lists all files and fields for TMT Fleet Maintenance 2012.20
PeopleNet eDVIR Setup Instructions
The PeopleNet eDVIR Module is used to send and receive eDVIR messages to and from the TMT Fleet Maintenance™ system when a driver creates an eDVIR or the eDVIR repairs have been completed.
2012.30
Qualcomm eDVIR Setup Instructions
The Qualcomm eDVIR Module is used to send and receive eDVIR messages to and from the TMT Fleet Maintenance™ system when a driver creates an eDVIR or the eDVIR repairs have been completed.
2012.30
Navistar Repair Advocate Setup Instructions
The Navistar Repair Advocate Module is used to send an email to Navistar’s Repair Advocate system when a Road Call is created for a Navistar/International unit.
2012.30
PerformX Meter Import Setup and Instructions
The PerformX Meter import will allow the ECM meter to be imported into TMT Fleet Maintenance™ from the PeopleNet Mobile unit.
Menu Selections may have changed; User Security should be reviewed, using Menu Selection 836 -
Menu Security Master.
Menu Security for Menu Selection 130 – RO History by Unit, requires that the user also has Security Rights for Menu Selection 131 – RO History by Unit/System. Both Menu Selections access the same program, so you could set the Rights to ‘0’, and the Display to ‘N’ for Menu Selection 130, and only allow access to MS 131. If your users are used to using MS 130, and you want to continue to grant access to MS 130, then be sure they have the same access level for MS 131.
The F1 Command Key is used exclusively to display help screens. The F1 Command Key is not displayed at the bottom of the screen.
The following is a list of Menu Selections that were added in Version 2012:
Version Selection Description
2012.40 1082 Invoice Aging Report
The following is a list of Menu Selections that were changed in Version 2012:
Version Selection Previous Description Current Description
No Change
The following is a list of Menu Selections that were deleted in Version 2012:
Version Selection Description
2012.10 120 RO – Inquiry - Current
Selection Defaults
This feature allows the user to "save" the selections for a Menu Selection so the user does not have to enter them every time the Menu Selection is chosen. The user has the ability to switch from the Program Defaults to the User Defaults by pressing the F15 key. The following is a list of Menu Selections we have added Selection Defaults to for 2012:
Version Selection Description Initial Default
No Change
18
The following is a list of Menu Selections that have new sub-options and/or Command Keys for Version 2012:
640 Parts Catalog Master F7 Serial Numbers 2012.40
650 Part Transactions –
View/Print 5 Part Info 2012.40
7 Serial# 2012.40 8 View Order 2012.40 F7 Serial# 2012.40 F8 View Order 2012.40 F9 Comments 2012.40
700 Warranty Part Master 5 Review 2012.10
744 744 – Claims Analysis View/Print
F5 Refresh 2012.20
843 Company Name
Master F13 System Info 2012.10
1050 Purchase Orders F3 Exit 2012.10
F7 Serial Number 2012.40 F16 Part Info 2012.10 F16 Part Info changed to F10=Rsvd Part
Order 2012.40
F21 Print (TMT470P – Fuel PO’s) 2012.10
19
Menu Selection
Description Sub-option
Command Key
Sub-option/Command Key Description
Release Number
1120 Supervisor Workstation
4 Reset TINA Login 2012.40
F13 Create RO 2012.40
1201 Accounting Dates Master
F16 History 2012.10
20
Database Changes
2012.20 PCR 2979 - PeopleNet eDVIR Interface INSPFLDS - Inspection Fields Definition- ISEQ Changed field ISEQ from 2s0 to 13s0 Added field ITYPE (Inspection Type) with attributes 10a Added field IVITAL (DOT Critical) with attributes 1a LINSPFD1 - LF of INSPFLDS - ITYPE/ICOMP Created logical by Inspection Type and Component LINSPCM1 - LF of INSPFLDS - ICOMP Logical File no longer used - Deleted INSPMAP - Inspection Fields Definition - MITYPE/VEHICL/VEHFLT/VEHACT/VEHTY1/MSEQ Added field VEHTY1 (Equipment Type) with attributes 10a Changed field MISEQ from 2s0 to 13s0 Added field MITYPE (Inspection Type) with attributes 10a Added field MSTAT (Map Sequence Status) with attributes 1A LINSPMP1 - LF of INSPMAP - MITYPE/VEHTY1/VEHACT/VEHFLT/VEHICL - Inserted new field MITYPE in key position 1 Inserted new field VEHTY1 in key position 2 Changed field VEHFLT to key position 4 Changed field VEHICL to key position 5 INSPRPTH - Inspection Report Header - IHSHOP/VEHICL/IHDATE(D)/IHTIME(D)/IRPTID Added field IHTYPE (Inspection Type) with attributes 10a Added keyword DESCEND for key field IHTIME LINSPRH2 - LF of INSPRPTH - VEHICL/IHDATE(D)/IHTIME(D)/IRPTID Added keyword DESCEND for key field IHTIME LINSPRH3 - LF of INSPRPTH - IHSHOP/IHDATE(D)/IHTIME(D)/IRPTID - Open Added keyword DESCEND for key field IHTIME LINSPRH4 - LF of INSPRPTH - IHSHOP/IHDATE(D)/IHTIME(D)/IRPTID Added keyword DESCEND for key field IHTIME LINSPRH5 - LF of INSPRPTH - IHSHOP/VEHICL/IHDATE(D)/IHTIME(D)/IRPTID - Open Added keyword DESCEND for key field IHTIME LINSPRH6 - LF of INSPRPTH - IHTYPE/IHSHOP/VEHICL/IHDATE(D)/IHTIME(D)/IRPTID Inserted new field IHTYPE in key position 1 Added keyword DESCEND for key field IHTIME
21
INSPRPTD - Inspection Report Detail - IRPTID/ISEQ Changed field ISEQ from 2s0 to 13s0 LINSPRD2 - LF of INSPRPTD - IDWPNO Created view by Work Pending Number INSPCMTS - Inspection Report Comments - IRPTID/ISEQ Changed field ISEQ from 2s0 to 13s0
PCR 3105 – Increase PRTUSE/PARTUSAG FLEETREF - Fleet Field Reference File Changed field PRTUSE from 5p0 to 6p0
22
2012.40 PCR 2909 – Create Serialized Parts PARTSNMS - Serialized Parts Master Created new physical file with following fields:
SPMSID K1 13P0; Internal Record ID
SPMSHP 6S0; Shop Number
SPMPRT 18A; Part Number
SPMSRL 26A; Serial Number
SPMSTS 1A; Status; valid values are A=Available; D=Dispensed; U=Unavailable
Created new logical files:
LPRTSNMS1 Keys: SPMSHP, SPMPRT, SPMSRL, SPMSTS
LPRTSNMS2 Keys: SPMPRT, SPMSRL, SPMSTS
PARTSNTX - Serialized Parts Transactions Created new physical file with following fields:
SPTSID K1 13P0; SPMSID from PARTSNMS
SPTTID 13P0; R#0609 from PARTRAX
Created new logical files:
LPRTSNTX1 Keys: SPTTID
API_CATL - Part Catalog API External Data Structure
Add field PCELMI Expected Life Utilization
Add field PCELMO Expected Life Months
Add field PCPFC Part Failure Code Required
Add field PCMOQ Minimum Order Quantity
Add field PCLPR Part List Price
Add field PCFPR Part Fleet Price
Add field PCJPR Part Jobber Price
PARTRAX - Part Transaction Audit File Created new logical files:
We changed the program to refresh the RO Listing after new Listing Options are selected. In previous versions, when Command Key "F9=Options" was used, and the new selection resulted in no data, the message "No data found to display" would be displayed at the bottom of the screen, and the previous list of RO's would continue to be displayed. In this version, if there are no RO's to display based on the new selection, the screen is refreshed, and the previous list of RO's is cleared from the RO Listing.
2012.10
100 - Shop Repairs TMT111 04/24/2012 #2912
We corrected all of the programs that have a Time entry field, (Repair Orders, Road Calls, Shop Plans, etc.), to validate the minutes entered. In previous versions, it was possible to enter any value for minutes up to 99, if the hours were less than 23. Example: The program would allow 14:99, and would not allow any value greater than 23:59. Now all the programs validate the minutes value, and will not allow any value greater than 59, or any value greater than 23:59.
2012.10
100 - Shop Repairs TMT111H 06/25/2012 #2587
We changed the program to allow the use of Command Key "F11=RO/Unit Info" in Inquiry mode so that it is available for any Repair Order, no matter what the current status is. In previous versions, this function was only available after the Repair Order was processed into RO History. This Command Key will allow you to display a window that has "Unit Information at the Time of the Repair". The information displayed is a summary from the Unit Master that contains the Fleet Code, Domicile, Cost Center, V.I.N. and other information. If any of the displayed values have been changed in the Unit Master after the Repair Order was created, they will be highlighted in this window to indicate there is a difference between the current value in the Unit Master, and the value that was current when the Repair Order was created.
2012.10
100 - Shop Repairs TMT113C 04/22/2011 #2587
Added new Command Key in RO Section entry screen so Templates can be added to existing Repair Orders.
Automatically displays each Template section. Allows user to edit and review, or skip the template sections being added to the RO.
New Command Key - F8=Template Inquiry (MS 100) Added "View" mode for templates from RO Section entry screen.
N
2012.10
100 - Shop Repairs TMT113C 07/26/2012 #2587
We added the ability to skip an RO Section added using RO Templates. (Does not apply to RO Templates using the "Load All" feature). When an RO Template is used to add RO Sections, now you have the option to review and accept, modify, or skip the Section. In previous versions, if you skipped an RO Template Section during the "add" process, the program would exit the RO Template routine, without displaying the rest of the Sections that may exist for RO Template.
2012.10
100 - Shop Repairs TMT113D 08/22/2012 #3003
We corrected the program to remove RO Header comments from the RO Comments file, (ROCMTS) when the last section of an RO is being deleted, and RO Comments exist. In previous versions, if RO Header comments existed, they were not deleted, and orphaned in the RO Comments file, (ROCOMMST). In previous versions the RO Comments file was named ROCOMMST. In this version, the new RO Comments file name is ROCMTS.
We changed the program to prevent the user from selecting an Inactive Symptom when a unit is Due or Overdue and TMT113M is displayed as you create an RO or ORO to select a PM. We changed the program to treat an entry of "1_", "_1", or "01" as Symptom 01. This field is treated differently in this program than other Symptom selection fields for ease of entry. We corrected the program to only display the list of PM Symptoms for the PM System selected when the user prompted in the Option/Symptom field. In previous versions, if multiple PM’s were displayed in TMT113M, the Symptom List included Symptoms for the other PM Systems.
2012.10
100 - Shop Repairs TMT113P 08/22/2011 #2587 We added the RO *ALERT* and the SECTION *ALERT* to the RO Workcard printout.
2012.10
100 - Shop Repairs TMT115C 08/22/2011 #2587
New Program - replaces TMT120 Includes Rapid Add mode accessed whenever program is called in add mode without specifying a line type (F7 from TMT115). This allows quick entry after entering only the item and cost/hours as long as no errors occur. Selection of multiple line types is allowed and with varying entry styles. Markups are applied against original cost (from part master or rate master) and displayed before committing the charge to the database. Overtime rates are applied against original labor rate before applying markups. In previous versions, the markup was applied first, and then Overtime rates were applied, causing a rounding error in some cases. Shop Markups are allowed when Firmware "ORO - Allow Change to "V" Lines" is set to 'Yes'. In previous versions there was a Firmware conflict that prevented this condition. We changed Firmware "RO Chgs - Req Vendor flds" to only apply to Standard RO's. When this Firmware is set to 'Yes', the user will be required to enter vendor information when the part or labor source on a Standard RO is set to 'V' (Vendor). (Only applies to Standard RO's - does not apply to Vendor RO's).
2012.10
100 - Shop Repairs TMT117 06/08/2012 #2587
The Repair Order close program has been updated and redesigned to appear and work the same for Standard Repair Orders, (SRO's) and Vendor Repair Orders, (VRO's). New features that were added include; The Plan Number, Comments notification, Unit Comments notification, new Command Keys F8=Unit History, and F12=Cancel are displayed now.
2012.10
100 - Shop Repairs TMT119 08/16/2012 #2995
We corrected the program to enforce the Firmware Mileage limit for Batch RO's. In the previous version, Batch RO's allowed meters that exceeded the Mileage limit set in the Firmware.
29
2012.10
100 - Shop Repairs TMT1091D 03/09/2012 #2587
A new process has been added when a user is attempting to reopen a Repair Order with an Invoice attached; the Invoice must first be deleted. The same process applies if an RO is reopened in Menu Selection 140 - Road Calls or Menu Selection 180 - Outside Repairs.
o Use the option Reopen the Repair Order to display the "Reopen Repair Order" window.
The Repair Order Number and Invoice Numbers are displayed. If the user does not have the authority to delete an Invoice (Menu Selection 1079,
option 4=Delete), the message "Access denied for this user." will be displayed.
If the Invoice is open, and the user has authority to delete an invoice (Menu Selection 1079, option 4=Delete), the "Reopen Repair Order" window is displayed, and allows the user to delete the open Invoice so that the Repair Order can be reopened.
o If the invoice is Closed, the user must have authority to reopen an invoice (Menu Selection 1079, option 8=Reopen). The message "Access denied for this user." will be displayed if the user does not have
authority to option 8=Reopen.
o If the Invoice is Closed, and the user has the authority to Reopen an Invoice, the user will have the option to Reopen and Delete the Invoice.
2012.10
100 - Shop Repairs TMT100FN 10/18/2012 #3052
We changed RO Functions to use RPG instead of SQL to improve performance and wait time issues.
30
N
2012.20
100 - Shop Repairs TMT117 12/07/2012 #3050
We changed the program to ensure the PM Scheduler file remains in sync with Repair Orders that have PM sections. In previous versions, the PM Scheduler record was only updated for Vendor RO's when the Invoice was 'Closed', and Firmware "PM (IP STATUS) Pts or Lbr Required" is set to 'No'. During the conversion process for this version, the PM Scheduler file will be updated and put back in sync with any Repair Orders that have PM Sections without charges. We also corrected an error that could occur if the Customer Number is updated during the close or IP process.
2012.20
100 - Shop Repairs TMT100L 12/10/2012 #3067
We modified the program to ensure the sub-options would allow the user to select any valid Repair Order in the RO Listing, and display the RO selected, instead of the last RO displayed on the current page. In the previous version, if a sub-option and RO Number were entered at the cut-option line, (at the top of the page), the last RO on the page was displayed, instead of the one that was entered.
N
2012.20
100 - Shop Repairs TMT113 01/15/2013 #3083
New Enhancement 3083 We added a new Firmware that allows you to determine whether Campaign & Work Pending comments should be retained on the Repair Order when an RO is being closed, and you need to create a Work Pending for sections without charges. Firmware "Retain Comments on RO when Creating WP" was added with four options, Both, Campaign, None, or Work Pending. See the Firmware definitions for each setting in the "New Firmware" section of this Readme document.
2012.20
100 - Shop Repairs TMT115 01/23/2013 #3090
We corrected a record lock error with the Warranty Part Charge file that could occur after a user has accessed an RO that has a Warrantable part charged. The record lock would only occur when a user had accessed the Shop RO Charges in TMT115 and the
last part charge of the section that was accessed has the Warranty flag set to 'Y'. Even though the first user has exited the screen, the lock remained for the Warranty Part Charges file (WARPTCHG) until the first user signed off. If the same user used a second session, (without signing off first), or any other user attempted to access the same RO & Section and used option 3=Charges from the Shop RO Sections screen, (TMT113) to display the Shop RO Charges, (TMT115), the record lock error message would be displayed.
N
2012.20
100 - Shop Repairs TMTAPI100 02/01/2013 #3077
We added more functionality to the TMTAPI100 program. The new feature adds an additional parm that allows three options for Work Pending. Now you have the option to add Work Pending sections, including Campaign sections, or only add Work Pending sections that have a Campaign attached when an RO for a Unit with PMs due is created using this API program. Values for new parameter:
N – do not add Work Pending sections (functions the same as previous versions without this
new parm)
Y – add all Work Pending sections to an existing RO, or a new RO if there is not an existing RO
C – only add Work Pending sections with a Campaign attached to an existing RO, or a new RO
if there is not an existing RO Note: New sections are only added for Work Pending or Campaigns if and only if a PM is also due for
the unit. If you use this API, please review the “API - TMTAPI100 PM Repair Order Listing V2012.pdf” document in the documents file provided for this upgrade.
31
2012.20
100 - Shop Repairs TMT111 02/04/2013 #3092
We corrected the Customer Number override Firmware, ("Override Customer Number"), to behave as it did in Version 2010.41 and previous versions. The "Override Customer Number" Firmware Help Text explains how this Firmware functions: If set to 'Yes' - Allows a user to change the Customer Number on a Repair Order in order to invoice a different customer, other than the customer to which the Unit is assigned. The RO will be created with the default Customer Number from the Customer Unit Assignment file, (Menu Selection 1061 - Customer Unit Assignment). Note: This option does not allow a blank Customer Number on the Repair Order if a Customer Number is currently assigned. If set to 'No' - The RO will be created with the default Customer Number from the Customer Unit Assignment file, (Menu Selection 1061 - Customer Unit Assignment). The user will not be allowed to change the Customer Number on the Repair Order even though the field is not protected.
2012.20
100 - Shop Repairs TMT117 03/06/2013 #3042
We changed the program to prevent a Repair Order from being closed if the Unit Master record is currently locked. After one minute, the "Record Locked" window will be displayed. This window will display the User, File, and record that are locked. The F3=Exit Command Key has been disabled under this condition to prevent the user from exiting the "Record Locked" window, and closing the Repair Order, but leaving any associated Shop Plans open. The user may press ENTER to retry to continue with closing the Repair Order. Recommendation:
If this condition is encountered, the user closing the Repair Order should contact the user displayed in the "Record Locked" window, and request that they exit the Unit Master record for the Unit on the Repair Order, or wait one minute, press ENTER to verify if the record lock has been released.
2012.31
100 - Shop Repairs TMT100G 06/26/2013 #3118
New Enhancement 3118
We changed the Repair Order summary Command Key, (F15=Summary), to display a Repair Order Section Listing that will list a summary line for each section, and the Grand Total for each section. A Command Key is available in the Repair Order Section Listing to display the Grand Total for the Repair Order. The Summary Listing is available when the user is displaying the "Charges" screen for any section of a Repair Order or Vendor Repair Order. The Repair Order Section Listing is also available in Menu Selection 132 - RO Inquiry Detail, when the "Totaling" field is set to 'S' = Section.
2012.31
100 - Shop Repairs TMT1091C 07/23/2013 # 3139
We corrected the program to transfer Repair Order section comments to the Invoice section comments when Firmware "Transfer Cmts to Invoice" is set to 'Yes'.
2012.40
100 - Shop Repairs TMT131M 08/23/2013 #3165
We corrected the program to display the Employee Number in the "(Reassign to Employee)" field. In the previous version, if the User prompted in the "(Reassign to Employee)" field to select the new Employee, the first six characters of the Employees name was displayed instead of the Employee Number when the Employee was being Reassigned on a Repair Order section.
32
N
2012.40
100 - Shop Repairs TMT115C 09/11/2013 #2909
New Enhancement 2909 We added two new User Level Firmware that will allow you set a default Part Quantity, by User, for both Standard Shop Repair Orders and Vendor Repair Orders. The new User Level Firmware are 11038 "ORO Chgs - Default Part Quantity" and 11039 "RO Chgs - Default Part Quantity". When the screen value for the Part Quantity is zero, the program will insert the appropriate Firmware value as determined by the Part Source. If the Part Source is 'V' - Vendor, then the program uses the value from Firmware "ORO Chgs - Default Part Quantity". If the Part Source is not 'V', then the value from Firmware "RO Chgs - Default Part Quantity" is used.
We changed the program to allow the User to enter a Repair Order number in the RO Header screen when using the Batch Repair Order entry process. Now the screen will return the User to the RO Header entry screen after each Batch RO has been entered to begin a new Batch RO. The Repair Order number field will allow the User to enter the next Batch RO Number. Note: This feature requires that Firmware "RO Allow Manually Assigned RO Number" is set to 'Yes'.
Assigned Employees o Open Repair Orders only display currently assigned Employees. Employees that have
worked on the section, and are not currently assigned, are no longer displayed until the Repair Order is closed.
o After the Repair Order is closed, all Employees that have labor time accumulated using the Mechanic Workstation, can be displayed using the Time Cards option. When there are no Time Cards associated with the section, - the Time Card Review Listing will still be displayed - even if there are not any Time Cards to list.
We changed the program to display the value in the "Assigned" sections column on the Shop RO
Listing, (Menu Selection 100), in PINK if the section is currently being worked on. We also made a similar change in the Shop Ro Sections screen, (TMT113). The value in the Employee "Assign" column will display the Employee number, (or '******' if multiple Employees are assigned), in PINK.
If a Reserved Part exists for the Repair Order, then the Repair Order cannot be Closed or Canceled.
o We also added a new message - "Request denied, Reserved Parts exist for this RO."
We added a new message when a Tire Work Card is printed for a Tire Repair Order from Menu Selection 530 - RO - Tires.
o The new message is - "Report output was sent to printer."
33
PCR 3184 (continued)
We added a new function for the "Cancel RO" window to allow the associated Road Call or Shop Plan to remain open. Previous Versions:
In previous versions, if the User canceled a Repair Order without any RO Sections, the Road Call or Plan was automatically closed at the same time.
2012.41:
In 2012.41, the User has the option to cancel a Repair Order without Sections (in the Shop RO Sections screen -TMT113) and remove it from the Road Call or Plan, and leave the Road Call or Plan open so that additional Repairs or Repair Orders can be added to the Road Call or Plan.
a. If there is only a Road Call or only a Plan (and not both), then only "Remove RO from Call?" or only "Remove RO from Plan?" will be displayed
b. If "Cancel the Order" = "Y" and "Remove RO from Call/Plan" is "N" the Call/Plan record will be closed - which is how the "Previous Version" worked
c. If "Cancel the Order" = "Y" and "Remove RO from Call/Plan" is "Y" the Call/Plan record will remain open and the canceled RO will not be linked to it in any way. The user will then be able to "re-use" the Call/Plan - this is the key difference in 2012.41. If a "linked" Road Call was created when the RO or ORO option was used while creating the Road Call, then the "linked" Call record will be deleted
d. If "Cancel the Order" = "N" then "Remove RO from Call/Plan" cannot be "Y"
34
2012.41
100 - Shop Repairs TMT115 12/13/2013 #3020
We added a new button in the Web Edition for the Employees using the Mechanic Workstation to use when charging Job Code Parts. The button is labeled "Add JC Parts" and has yellow letters over a dark blue background to be visibly different than the default buttons with white letters. This button will only be displayed when the Employee is charging parts for an RO Section that includes a Job Code that has a Parts List defined for the RO Shop.
2012.41
100 - Shop Repairs TMT115C 12/03/2013 #3020
We changed the program to process part and labor charges in one step instead of forcing the User to confirm the request to process after they have already pressed F6 or clicked the "Process" button in the Web Version.
2012.41
100 - Shop Repairs TMTWRNT 01/03/2014 #3124
We changed the Warranty program to exclude the automatic deletion of *NON-STOCK parts when the Warranty flag on the Part Master record is set to 'Y', and the VMRS Code is blank, or only contains a partial VMRS Code, (less than nine digits), or contains a VMRS Code of 999 999 999. The Warranty Part Master record in Menu Selection 700 - Warranty Part Master will not change to 'OFF' status for *NON-STOCK parts that have the Warranty flag set to 'Y' and have a blank VMRS Code, a partial VMRS Code less than nine digits, or a VMRS Code of 999 999 999. Non-Stock parts will not be deleted from the Part Master automatically if a Warranty Part Master record exists and Firmware "Delete Non-Stock Parts ?" is set to 'Yes'.
35
2012.41
100 - Shop Repairs TMT117 01/06/2014 #3184
We also made an additional change in the program with regard to processing of the Non-Company Job Code subroutine and the resulting variable it returns. The program was changed to ensure the Job Code edit routine is returning the correct variable if a Repair Order for a Non-Company Unit is being closed, has Job Codes, and the Customer Number is changed. Job Codes can be assigned to a Repair Order for a Non-Company Unit, but the Job Code(s) selected are validated based on the Profile defined on the Job Code(s).
2012.40
110 - RO - Campaigns TMT105H 08/08/2013 #2777
New Enhancement 2777 We changed the Campaign Section Comments to update Work Pending's that currently have the Campaign assigned to it. This feature will allow you to update Campaign Section Comments throughout the life of the Campaign, and have them automatically update all of the Work Pending's that have the Campaign assigned to it. The Campaign Section Comments can be updated at any time, and will automatically update the Campaign Comments on all Work Pending sections. The Campaign Comments will not be updated on any existing Repair Orders. You may update the Campaign Comments on any Repair Order that is currently in Open - 'OP' status. Other Changes include:
Now the program will always write the Campaign Comments ahead of Work Pending Comments, or Comments added by a User, - this includes Comments added by a User directly in a Work Pending or while the Work Pending may have been part of a Repair Order Section.
Campaign comments will not be re-written each time a Campaign is added or removed from an RO Section. They are displayed directly from the Campaign Section Comments on the Campaign. This will eliminate the duplicate Campaign Comments that would occur if a Campaign for a Unit had been added to RO's multiple times, and then put back in Work Pending because the repairs were not performed.
Campaign Section Comments will have a "USER" of '*CAMPAIGN'
Campaign Section Comments will have a Date of 0/00/00 and Time of 'blank'.
If you need to see the Date or Time the Comments were originally created, use the option to display Section Comments in the Campaign Master, 110 - RO - Campaigns.
Campaign Section Comments are "protected" on a Work Pending or Repair Order section, and cannot be changed by a User.
We also corrected an edit for the Symptom Code when a Work Pending is added in "Mass Create" mode.
We added an edit in TMT117 when closing a Vendor RO to prevent a User from entering an Invoice Date that is less than the Down Date.
A new message is displayed for this condition to alert the User:
"Invoice Date cannot be less than the Down Date."
TMT104S no longer ends in error when it is called with a Unit that has a Work Pending header record (WRKPHEAD) and no Work Pending section records (WRKPBODY).
Fixed issue where all three descriptions on the delete window were being populated from the last Sub File Line.
We added edits to prevent the programs from allowing the user to add additional Work Pending sections when a unit has reached the Work Pending section limit of 99 sections. These changes display a message to alert the user 99 sections already exist for a unit when new Work Pending sections are being added to an individual unit or a unit included in a group of units selected for new Work Pending sections or Campaigns. We also added notification when a Repair Order is being closed, and the sections without charges are selected to create a Work Pending section, and the Unit on the Repair Order won't allow additional Work Pending sections. If the unit already has 99 Work Pending sections, then no new Work Pending sections are allowed. If the unit has less than 99 sections, and additional Work Pending sections are being added, the program will only allow up to 99 Work Pending sections to be added.
N
2012.40
111 - RO - Work Pending TMT111 08/16/2013 #3107
New Enhancement 3107 We added a new Command Key - "F10=Mass Create" and changed "F7=Create Work Pending" to "F7-Create". The new "F10=Mass Create" can be secured to prevent Users from Creating Work Pending's. The Security authority a User has currently will be applied to the new "F10=Mass Create" Command Key.
2012.41
111 - RO - Work Pending TMT104 11/07/2013 #3147
We corrected the program to resolve a condition where a Work Pending header may become orphaned when all the Work Pending sections have been removed.
2012.31
112 - Minor Repairs TMT111 07/23/2013 # 3138
We corrected the program to display the default Customer assigned to a unit when a Minor RO is displayed. We also changed the Minor RO message from - "Minor RO already exists." to include the actual Minor RO and to edit by Shop: "Minor RO 1234567 exists for this Unit and Shop". Other changes;
Firmware "Override Customer Number" was not being set on Minor RO's. We changed program TMT111 and display files DSTMT111, WSTMT111.
Batch RO's - the program was using the Down Date from the screen (indndt) instead of (inupdt) to validate the Up Date. This also caused field RO Up Date (ROUPDT in ROHEAD) to be populated with the Down Date.
Vendor RO's - in change or inquiry mode the program was using the RO Down Date (RODNDT from ROHEAD) to populate the Estimated Date on the screen.
o This could cause the program to appear to not update the Estimated Date when the user returned to the program.
37
2012.20
121 - PM Factors Master TMT121 and TMT128 02/18/2013 #3099
We added a warning that will be displayed when the "Last PM Date" exceeds 9,999 days. See the example below.
Now, if the "Last PM Date" exceeds 9,999 days, the Utilization Interval will not error, and will display "9999" as the maximum number of days since the last PM, even if it has been greater than 9,999. See the example below.
In previous versions, an error message would be displayed if the "Last PM Date" was greater than 9,999 days when the PM Information screen above was displayed.
38
2012.31
121 - PM Factors Master TMT121 07/18/2013 #3125
We changed the program to delete the PM Scheduler Header Master record in the PMSCHEDH file when a PM is updated manually to ensure the PM would not be displayed the next time a PM Scheduler report is created or until it becomes Due again. If the Unit has an open Repair Order with a Section for the System Code that is updated, the PM Scheduler record is not deleted. The Next PM Due Date is retained, and displayed on the PM Scheduler report the next time it is created, unless the new Last PM Date and Meter entered match the Down Date and Meter on the current Open Repair Order, then the PM Due Date will display as the Repair Order Down Date. In the previous version, the Last PM Date and Meter information from the previous PM was retained and displayed on the PM Scheduler report, even though it had just been updated manually.
2012.31
121 - PM Factors Master TMT121 07/18/2013 #3134
We corrected an edit that prevents a PM System from being deleted, changed, or added when the same System Code exists on a current Repair Order in 'OP' - Open, 'IP' - Invoice Pending, or 'CN' - Closed Not Updated status for the same Unit. In versions prior to 2012.10, this edit was only applicable to Repair Orders in 'OP' status.
We changed the program to prevent an error when over 9,999 PM's are due for a Shop and "View" is selected. Now, if over 9,999 PM's are due based on the selection criteria, or for any Shop Number, the program will not display the error, and it will only display the first 9,999 Units due in that Shop. In "Print" or "Email" mode, all Units that are due for any and all Shops will be displayed on the printed report. We also changed the program to save the selection options entered until the User exits the PM Scheduling/Planning Report. This is especially useful if the User wants to run the report multiple times, and only needs to change one or two of the same selections each time, like Shop Number or Fleet. We added new Command Key "F5=Refresh". This command key can be used to clear the selections and set them back to the default values.
We changed the PM Scheduler to retain the original PM Due Factor. If the Unit originally becomes due by Days, and then before the PM is performed, the Mileage interval is exceeded, the PM will continue to display as due by the original factor (Days or Miles), that triggered the PM Due message. We also updated the One-Time PM field in the PM Factor Detail file (PMFACTRD). In previous versions, the One-Time PM value was stored in PMFACTRD/UD0109 as a 0, 1 or 2. Now it will be stored in PMFACTRD/FDOTPM as a 'Y', 'N', or 'C'. 0 and N = No, a One-Time PM is not scheduled for the PM defined. 1 and Y = Yes, a One-Time PM needs to be performed at the interval(s) defined. 2 and C = Completed, a One-Time PM has been performed for the PM defined.
We corrected the program to display the Repair Order information in View mode when a Unit Due for a PM also has an open Repair Order for the PM.
2012.10
124 - Parts Pick List Master TMT124 08/22/2012 #3040
We changed the program to correct a record lock error that only existed when a page full of Part Numbers exist for a Parts Pick Master list, and a user attempted to edit the last part on the page. In the previous versions, the program would issue a record lock error. This issue did not occur if the user changed the last record on the page if there was less than a full page of Part Numbers.
39
2012.10
127 - PM Status Listing TMT127 07/24/2012 #2587
We made the following improvements for the PM Status Listing options;
When Command Key "F9=Options" is used to display the Listing Options from within Menu Selection 127, the original values entered will be retained and re-default "*ALL" if the user blanks the field.
We added a second parameter for System Code when called from another program.
Parm Field Size Details
1 Unit 12a Not required, unless Parm 2 is used
2 System 6a Not required
We modified the program to default the System Code if the user calls MS 127 from MS 121 using Command Key "F7=PM Status".
o To use this feature, just place the cursor on a line with a System Code in MS 121, before you use "F7=PM Status".
o If the cursor is placed on a line with a System Code, the PM Status history of a Unit & System can be viewed from MS121.
o If the cursor is not on a line with a system all PM Status records will be displayed for the unit.
We also replaced the "Unit Profile" default of '*ALL' with '*NONE'.
2012.10
131 - RO Inquiry by Unit/System TMT140A 06/19/2012 #2587
We replaced the status type for Repair Orders in history, - "HIST" with the new status "CMPL" - (Complete). We also added "EOD" - End of Day Processing to the Status list. The status of "EOD" will be displayed in reverse image YELLOW, if the Repair Order is currently being processed while the End of Day process is running.
2012.10
131 - RO Inquiry by Unit/System TMT140A 08/20/2012 #2903
We corrected an error with the program that allowed the Shop and Meter to display incorrectly after selecting an invalid option on page one, then paging down to display other pages for the same Unit and System Code.
N
2012.10
131 - RO Inquiry by Unit/System TMT140A 08/20/2012 #2951
New Enhancement 2951 We added a new wildcard (*) feature to the Assembly portion of the System Code so that when the user enters a component (e.g. 013) and an "*" in the Assembly field, the result list will include Systems between 013000 and 013999.
2012.41
131 - RO Inquiry by Unit/System TMT118 12/06/2013 #3202
We corrected the comments program to ensure Repair Order comments are protected if the RO is in "Closed" or "Completed" status. In all previous versions of 2012, the program was allowing the User to Add/Change/Delete comments on RO's in "Closed" or "Completed" status. Now the User will only allow be allowed to view the comments if the RO is in "Closed" or "Completed" status same as Version 2010.
40
N
2012.10
132 - RO Inquiry Detail TMT170 06/21/2012 #2587
New Enhancement 2587 The RO History selection screen has been re-structured to group the selection fields by RO, Section and Charge.
Prompt field additions: o Part Profile - allows the user to select RO's by Part Profile o RO Status
NC ("Not Completed") to select all ROs with a blank Completed Date A blank Completed Date indicates the RO has not been through the EOD
process U* ("EOD Updating") to select ROs currently in the EOD process (RO Status
is no longer "Open", and not yet "Completed") Note: The RO Status prompting is disabled for users with Security Rights set
to '0' (zero) for Menu Selection 801, TMT Codes Master. o Show Calls - Includes RO's with a Road Call attached o Claim Type - allows the user to select RO's by warranty claim type o To Post Date - allows the user to select a date range by Post Dates - (the Completed
Date from the EOD process) o To Post Time - allows the user to select RO's within a range by the time of day the
EOD process updated the RO o Part Failure Code (PFC) - select RO's by new Part Failure Code (assigned during part
charge entry on the RO) o Position - select RO's by Part Position assignment o System (Line) - select RO's by the System Code on the part or labor line o VMRS Code - select vendor or shop parts by VMRS Code o Year & Period range (From-To) - select RO's by Accounting Year and Period they are
posted in o Amount range (From - To) - select RO's by an amount range, including negative
values - (Credit RO's) o (C)harges for Totaling report option - select RO charges by Charges only - displays
the part and labor lines selected (instead of RO's or Sections) o G/L Acct - allows the user to select RO's by General Ledger account
RO History report has been updated to display the new fields o Three new views - by Repair Order, by Repair Order Section, by Repair Order
Charges o The RO History report has a new report header for page one, and standard headings
are displayed on all of the remaining pages of the report
N
2012.10
132 - RO Inquiry Detail TMT170 08/13/2012 #1437
You now have the ability to display the Repair Orders and charges, with a total by Part Number. We added a new "Totaling" option - "Charges". When the Totaling option is set to Charges, and a Part Number has been entered in the "Part Nbr" field, the RO Listing will display a list of matching RO Charges for the part selected, and Command Key "F15=Show Totals" will display the total for all charges displayed.
N
2012.10
132 - RO Inquiry Detail TMT170 08/13/2012 #2335
You now have the ability to display the Repair Orders and charges, using a "Part Profile". A new field was added that allows the user to select Repair Orders by "Part Profile".
N
2012.10
132 - RO Inquiry Detail TMT170 08/14/2012 #2558
You now have the ability to display the Repair Orders using a "Posted Date" and "Posted Time" range. (The Posted Date and Time represents the actual date and time the RO was processed using the End of Day Process). New fields were added to allow the user to list Repair Orders by Posted Date and Time ranges. In the previous version, the user was only allowed to select a "Post Date" and "Post Time".
41
N
2012.10
132 - RO Inquiry Detail TMT170WF 08/21/2012 #2998
New Enhancement 2998 We added these new fields to the Outfile generated from the RO Inquiry Detail selections: RO Status = (OP - Open, IP - Invoice Pending, ER - Error, CA - Canceled, CN - Closed-Not updated, CM - Closed-Processed , U1 - U6 - EOD Processing in progress-stage 1 thru 6) Shop/Vendor = (S - Shop or V - Vendor) Customer Number Completed Date = (EOD Date) Completed Time = (EOD Time) RO ID Number = (Unique identifier used in all RO files) These fields will have values when the RO History Totaling selection is set to "Charges". Line Type = (LB - Labor, or PT - Part) Source = (S - Shop or V - Vendor) Item/Mechanic = (Part Description or Mechanic ID and Name)
N
2012.20
132 - RO Inquiry Detail TMT170 01/09/2013 #3089
New Enhancement 3089 We added a new "Remit-To" field to Repair Order Listing screen. This new field can be used to search for Vendor Repair Orders by "Remit-To" Supplier in conjunction with the other fields available. We also added the "Remit-To" field to the header page for the Repair Order Listing, Repair Order Section Listing, and Repair Order Charges Listing reports. The Repair Order Listing report also has a new column to display the "Remit-To" Supplier.
2012.20
132 - RO Inquiry Detail TMT170R 12/17/2012 #3081
We corrected the program to use the "Domicile" Shop value instead of the "RO Shop" value when a Domicile is selected, and the RO Shop is set to '*ALL'. In the previous version, (2012.10), when a Domicile Shop was selected, and the RO Shop was set to use the default value - '*ALL', and the "Output" was set to 'Email' or 'Print', the program displayed an error message.
We modified the program to display the Cost Center, Domicile, and Fleet Code from the new Repair Order header file, (ROHEAD), instead of the Unit Master file, (VEHCLMSTR), or the Customer Master file, (CUSTMSTR), when an RO is printed from RO Inquiry Detail. Now, when an RO is printed, it will always display the Cost Center, Domicile, and Fleet Code from the Repair Order header file, even if these values are changed in the Unit Master after the RO was created. We also made the same changes for the Repair Orders and Work Cards printed from Menu Selection 100 - Shop Repairs. When the PM Pick List or Diagnostics is included with a Work Card, the program will use the Fleet Code from the Repair Order file. In the previous version, when an RO was printed, if the Unit on the RO also had a Customer Number assigned to it, the RO was displaying the Cost Center Number from the Customer Master record and the Cost Center description from the Unit Master.
42
N
2012.40
132 - RO Inquiry Detail TMT170 09/17/2013 #3145
New Enhancement 3145 We changed the RO Inquiry screen from a two-column format to a three-column format so additional fields could be added. The new fields are: Unit Status Unit Status Include/Exclude Utilization Base Operator Operator Report A Operator Report B Operator Report C Delay Reason Delay System Pay Method Pay Number FROM Invoice Date TO Invoice Date FROM Invoice Amount TO Invoice Amount FROM Down Date TO Down Date Unit Serial# Part Serial# Date Range Selections - Listing Options
The default Date process has been changed;
All "FROM" dates are processed as >= (RO's greater than or equal to the FROM date will be included)
All "TO" dates are processed as <= (RO's less than or equal to the TO date will be included) o All date ranges select records >= FROM date and <= TO date
The default FROM Down Date is the beginning date of the year if no other dates are selected
Up Date and Down Date selections are now independent of the RO status A new data area has been added:
Data Area Name: TMT170DA o Object Type: *DTAARA o Data Type: *CHAR o Data Length: 25
The data area will store up to 25 switches for TMT170S to determine whether the SQL is returned to the user in Summary or Detail mode.
Related changes:
Repair Order Summary
We changed the RO Section Summary view to provide summary and detail total cost information.
o When the User selects "F15=Summary" to display the RO Summary from the Shop RO Inquiry view, (TMT113), or the Shop RO Charges Inquiry view, (TMT115),the RO Summary window is displayed with a Part, Labor, and Total for each section on the RO.
o When the User displays the Shop RO Charges Inquiry, (TMT115), each Line Type (Parts or Labor) display a total line cost. A total for the Parts, Labor and a Total Cost is displayed for the RO Section.
o Added New Command Key "F15=Summary"
Shop Plan
o When a Repair Order attached to a Shop Plan is canceled as it is being created, and before any sections have been added, the Plan Status will automatically change to "Closed"
Vendor Repair Order
o We corrected the program to ensure a User is not allowed to add charges when Firmware "ORO - Allow Editing in IP Status" is set to 'No', and the User has accessed the Shop RO Charges screen (TMT115) for a Vendor Repair Order in 'Invoice Pending' status.
43
2012.41
132 - RO Inquiry Detail TMT744D 10/09/2013 #3141
We changed the program to prevent an error message from displaying when a Warranty History Claim is displayed, and a Labor Line exists with a 0.00 labor hours and 0.00 cost. When the claim is processed to the Claim History file, a record is created in file WCLLBRHS without a value in labor hours (HLHRS) and cost (HLCOST). In previous versions, this error would be displayed when the Warranty Claim was displayed from MS 132 - RO Inquiry Detail, or 744 - Claims Analysis View/Print.
2012.41
132 - RO Inquiry Detail TMT170 01/06/2014 #3218
We corrected the PO Number field to accept numeric entry. In the previous version, the error message "ORO PO# must be numeric." was displayed even though a numeric value had been entered.
2012.20
140 - Road Calls TMT197H 02/08/2013 #3091
We corrected the program to allow option 9=RO (IP) to change the status for Vendor RO's. In the previous version, (2012.10 only), option 9=RO (IP) would not function and allow the Vendor RO status to change.
44
N
2012.30
140 - Road Calls TMT197 04/08/2013 #2966
New Enhancement 2966 Navistar Repair Advocate module Overview
The new Navistar Repair Advocate module is used to send an email to Navistar’s Repair Advocate system when a Road Call is created for a Navistar/International unit. When a Road Call is created for a Unit with a Navistar "Make" code, and the Navistar "Remit To" Dealer is selected in the Road Call Supplier field, a pop up window is displayed that allows the user to select the actual Navistar Dealer the Unit is being repaired at. This process will "link" the Repair Dealer to the "Remit To" Dealer on the Road Call. Features
Create Road Call
Program will display pop up window to identify / select dealer
Unit on Road Call must be an “International” Unit
Navistar Vendor must have been entered on the Road Call
Road Call comments store the "linked" Navistar Dealer Name, Address, Phone Number
Email sent to Navistar supplied email address
Email includes:
Road Call number, Estimated Arrival Time, Unit V.I.N., Unit Number, Mileage, Linked Dealer Address, Driver Name, and Complaint (Road Call Comments)
Implementation
When a Road Call is created for a Navistar unit, with one of the required Navistar Unit "Make" codes, and the selected Supplier has the Navistar Dealer Link setup, then after pressing F6 to process the Road Call, the "Navistar Repair Advocate Email" window is displayed. (See the example below).
The user has the option to press F4 to change the default Dealer, or select a different one, press F6 to send the email to the Navistar Repair Advocate system, or cancel the Navistar email.
45
2012.31
140 - Road Calls TMT198 06/27/2013 #3130
We added three new exits for Road Call Comments; ADD, EXT, and F24. These exits can be setup in Menu Selection 851 - Exits Master. TMT198 - Road Calls - Comments
ADD - This exit runs after Road Call Comments have been entered. To Execute: Add a comment to a Road Call and press ‘Enter’. EXT - This exit runs after the User exits Road Call Comments. To Execute: View/Enter Road Call Comments and press ‘F3=Exit’. F24 - This exit runs after the User uses Command Key F24 in Road Call Comments. To Execute: View/Enter Road Call Comments and press ‘F24’.
2012.31
140 - Road Calls TMT197 07/22/2013 #3137
We corrected the program to save changes made to the "Phone", "Contact" and "Status" fields when a user updates the fields, presses F6=Process, and then option 0="NO ACTION" in the Road Call exit menu.
2012.31
140 - Road Calls TMT197 07/24/2013 #3153
We corrected the program TMT197 to clear pRoid when calling CLTMT111BC or TMT111 in Add mode. In the previous version, when a Road Call was created with multiple Repair Orders, (Standard or Vendor RO's), all RO's created after the first one were being created with the ROID# from the previous RO instead of using the next RO Number as long as the user selected option 1 to Create an RO or option 3 to Create an Outside Repair from the Road Call "Next Action" menu.
2012.40
140 - Road Calls TMT117 09/03/2013 #3158
We changed the program to only display the "Warranty Exceptions" window in "Close" mode and it will no longer be displayed in "Invoice Pending" mode. If the user presses ENTER or F12=Cancel while the "Warranty Exceptions" window is displayed, the program will return to the "Close RO" screen, and not perform any updates.
In previous versions of 2012, the program would display the "Warranty Exceptions" window in "Invoice Pending" mode, and update the ORO status, and fail to update the Road Call to "Closed" (CC) status when the User pressed ENTER. We also corrected the program to update the Road Call status to "Closed Call" (CC) when a User canceled a Repair Order during the RO creation process by exiting before sections are added. In previous versions, this condition would change the Repair Order status to 'CA', and leave the Road Call status open with 'OC' status. This would prevent a User from creating a new Road Call for the Unit.
2012.40
140 - Road Calls TMT197H 09/18/2013 #3145
We changed the program to display both Open Calls and Closed Calls in the Road Call Listing when the Call Status "OI - Open Calls + Invoice Pending" is selected.
In previous versions, the Road Call Listing was only displaying Open Calls that have an ORO' in 'IP' status.
N
2012.41
140 - Road Calls TMT197H 10/21/2013 #3183
We reviewed and corrected all Repair Order related options and messages to ensure they function the same as they do in Menu Selection 100 - Shop Repairs or 180 - Outside Repairs. We also changed RO option "7=Tires" so that it will not be displayed if the User does not have "ADD" Security Rights for Menu Selection 530 - RO - Tires. We corrected option "10=RO Reprint" to function for an RO in 'CL' - Closed status. Added new message - "Report output was sent to printer." We changed the message displayed when option "8=RO Reopen" is used from - "Ro is not closed, cannot reopen" to "Cannot reopen a completed RO".
46
2012.41
140 - Road Calls TMT197 10/28/2013 #3193
We corrected the program to display the Command Key "F17=Messaging". In previous versions, (2012.10 - 2012.40), the command key was not being displayed or function if the User pressed F17 to display the Mobile Communication Messaging menu.
2012.41
140 - Road Calls TMT197H 12/10/2013 #3206
We corrected the program to only display the comments indicator when a Road Call actually has comments. In previous versions, the indicator ('YS') was displayed for all Road Calls, even if the Road Call did not have any comments.
2012.41
140 - Road Calls TMT197 01/13/2014 #3225
We corrected the program to allow Repair Orders, Vendor Repair Orders, Road Calls, and Shop Plans to be created with the "Company Unit" flag set to 'N' for Units that exist in the Unit Master with a Status of '9999' - Reports Only. Note: When Firmware "RO Non-Cmpy Unit - Do PMs" is set to 'Yes', you are not allowed to create
Repair Orders, Vendor Repair Orders, Minor Repair Orders, Road Calls, or Shop Plans and set the "Company Unit" flag to 'N' for Units that exist in the Unit Master with a Status of '9999' - Reports Only.
2012.10
151 - Work Standards Exceptions TMT152R 08/31/2012 #3017
We corrected an overflow error with the program that could occur if the “Work Standards Exception” report included over 100,000 records.
2012.10
160 - Indirect Charges TMT116A 10/17/2012 #2997
We changed the program that generates the Indirect Charge ID to "roll-over" when the Indirect Charges have reached the maximum charge ID number 9,999,999. We added a new Type Code for the Next Number Master in Menu Selection 845. The new Type Code is: 'ICNO - Indirect Charges'. This new Type Code is used to store the next Indirect Charge ID. When the Indirect Charge ID reaches the maximum value of 9,999,999, the program will reset the value for the Next Number Type 'ICNO' back to '1'. This upgrade will move the next Indirect Charge number from Data Area "INDRNO" to the new Next Number Type - 'ICNO'. The Data Area "INDRNO" will no longer be used to store the next Indirect Charge Number. No action is required by the user. After the upgrade is completed, the same sequence of numbers will be used as Indirect Charges are created. The programs affected are: TMTIND - Indirect Labor Additions TMT1050 - Purchase Order Processing TMT116A - Indirect Part Charge Entry TMT116B - Indirect Labor Charge Entry TMT135I - MWS - Indirect Labor Update TMT881D - Barcode - Indirect Labor Charging TMT881E - Barcode - Indirect Part Charges
2012.40
160 - Indirect Charges TMT160H 08/16/2013 #3107
We changed the program to validate the Shop Number field to only allow numeric characters or '*ALL'. The Shop Number field will only accept a numeric Shop Number, ' *ALL' or '*ALL '. In previous versions an error was displayed if alpha characters were entered in the Shop Number field.
Serialized Part Number functionality has been added. The feature will allow you to link the serial numbers for a part to Inventory, Units, and Indirect Charges.
When Serialized Parts are charged out using Indirect Part Charges, the User will be prompted to select the Serial Number(s)
We added a new command key to the Part Master – “F7=Serial Numbers” this will allow the
user to display all of the Serial Numbers currently assigned to the Part Number selected
We added a new column in the "Indirect Cost Charging" screen to indicate charged parts that have a Serial Number - "SN". This column will contain a 'Y' if the part is designated as a Serialized Part
We added an additional description for Serialized Parts on the printed "Indirect Cost Charging" and "Indirect Charge History" reports. The description includes the Serial Number(s)
48
N
2012.20
165 - Inspection Tickets TMT164 01/31/2013 #2979
New Enhancement 2979 We added the ability to interface the Inspection Tickets with the PeopleNet Mobile Communication Module. New Features - Inspection Tickets created from the PeopleNet import;
The conversion program included with this upgrade will create the basic Import/Export Profile records needed in Menu Selection 847 - Import/Export Master. Some additional setup will be required, including the Mobile Comm - PeopleNet Module.
a. An Import Type record will be created named "PeopleNet" i. An Import Profile record will be created named "eDVIR Messages" used to
import the eDVIR from the PeopleNet console in the Unit ii. An Export Profile record will be created named "eDVIR Mechanic Ack" used
to export the eDVIR from TMT back to the PeopleNet console in the Unit
We added a new TMTCODE - "INSP TYPE".
Two new "INSP TYPE" codes will also be added, "STANDARD" and "PEOPLENET".
The "STANDARD" code will automatically be assigned to any existing Inspection Fields and Inspection Fields Maps you may have.
The default "PEOPLENET" fields will be added to the Inspection Fields Definition list during the upgrade to this version. You can view this list in MS 165, F7=Fields Master, then select 'Inspection Type' - "PEOPLENET".
The "PEOPLENET" Inspection Type code will be added to the Inspection Fields Mapping List, and two new 'Equipment Type' codes will also be added; "TRACTOR" and "TRAILER". You can view this list in MS 165, F8=Maps Master, then select 'Inspection Type' - "PEOPLENET".
o ! Both Equipment Types are initially created with the same list of PeopleNet default Inspection fields. You need to review the list and change the status to 'Inactive' for any of the fields that do not apply for each Equipment Type list, (TRACTOR and TRAILER), before you begin using the PeopleNet eDVIR interface. The Inspection fields defined in the Inspection Fields Map must exactly match the PeopleNet form you use.
o If the Inspection Fields Map does not match the PeopleNet form, the Inspection Ticket will not be created.
o The Inspection Ticket will not be created if an Inspection Field Map does not exist for the Unit/Fleet.
Inspections are set to Closed Status if no defects exist, unless a PM is due for the Unit and Firmware "Inspect - Auto Create PMs' is set" to 'Yes'.
The "INSPECTION REPORT (eDVIR) TRANSFER PROGRAM" report is created listing all eDVIRs imported, listing the reported defects and the inspections created.
eDVIR remarks are then loaded into the Inspection Comments file (INSPCMTS). These include the following tags/info:
a. 'eDVIR #TS=' followed by the Import/Export Type Sequence b. 'eDVIR #OR=' followed by the Invoice Transfer Origin c. 'eDVIR #ID=' followed by the Invoice Transfer Record Id d. 'eDVIR #MN=' followed by Vendor Message Id e. 'eDVIR #DN=' followed by Driver Name
We created a new program (TMT164MA) that is called whenever a Repair Order is Closed, or when all sections are completed by Employees using Shop Floor Interactive. Upon successful completion of repairs, a record will be created in the Order Export file, (ORDREXPT). If the Order Export file record exists for the Repair Order, the eDVIR Mechanic Acknowledgment message will be sent to the PeopleNet console in the truck the next time the scheduled job runs.
49
PCR 2979 (Continued) New Features - Inspection Tickets
Inspection Ticket creation
New Command Keys:
F8=PMs - This command will allow you to view the PM Information screen. This command key is position sensitive for each unit listed on the Inspection Ticket. To display the PM Information screen for the Unit, position the cursor in the Unit number field, and press F8.
F9=Remarks - This command key displays the comments window for the Inspection Ticket. This command key is position sensitive for each unit listed on the Inspection Ticket. Position the cursor to the desired line and press F9 to display the comments window.
Remarks are transferred to Repair Order header comments if an RO is created.
Create Repair Order/Work Pending from Inspections
New Command Keys:
F7=ROs - Use this command to display RO History for the Unit. This command key is cursor position sensitive and will display the RO History for the Component on the line selected. If the cursor is not positioned on a Component line, then all RO History is displayed.
F19=WPs - Use this command to display all current Work Pending sections for the Unit.
Options:
Changed option: 3=Create WP Section to: 3=Create WP
Changed option: 4=Create RO Section to: 4=Create RO
Changed option: 6=Component Comments to: 6=Comments
Added new option: 7=Skip
Inspection Ticket Review
New Command Key:
F7=RO - This command key is position sensitive. To display a Repair Order created for this Inspection Ticket, position the cursor to any line with a Repair Order Number displayed in the RO column, and press F7 to display the Repair Order created from the Inspection Ticket.
Changed Command Key;
F16=W/P to F19=W/P - This command key is position sensitive. To display the Work
Pending created for this Inspection Ticket, position the cursor to any line with a Work Pending Number displayed in the W/P column, and press F19 to display the Work Pending created from the Inspection Ticket. If you press F19 on any line without a Work Pending Number, the Work Pending Listing Options window will be displayed to allow you to search the Work Pending Listing, (same as using Menu Selection 111 - RO - Work Pending).
50
PCR 2979 (Continued)
Inspection Fields Master
New "Vital" field added to indicate which Inspection Fields are defined as DOT critical.
The Vital field allows an inspection field to be noted as DOT critical. The idea is that if an inspection report noted issues for a DOT critical component, the defects must be addressed and their resolution recorded.
The listing is now ordered by Component instead of User Description.
The number of inspection fields is no longer limited to 99.
The listing is now ordered by Component instead of User Description. New Command Keys:
F8=Toggle definition, allows the user to toggle the display to include Active Fields, Inactive Fields, or All Fields.
F20=Create SYSKEY, allows the user to create a default Symptom Code for a System Code defined as an Inspection Field, when the System Code does not have any Symptom Codes defined.
Inspection Fields Mapping
New Command Keys:
F4=Prompt - Allows the new Inspection Type to be prompted to select STANDARD or PEOPLENET
F7=Create - Allows the user to display the Inspection Fields Mapping Master to create a new Map Master
N
2012.10
180 - Outside Repairs TMT117 05/01/2012 #2993
New Enhancement 2993 A new option flag has been added to the TMTCODES Category "PAY METHOD" that will bypass the "Invoice Pending" option for Vendor Repair Orders. This new option will force a Vendor Repair Order to "Close" instead of "Invoice Pending" if the user selects the "Pending" option for a Payment Method that has the new "ORO Close" flag set to 'Y'. If the new "ORO Close" flag is set to 'Y', then an alert message, (see below), will be displayed to the user if they select the "Pending" option instead of the "Close" option for a Vendor Repair Order using a Payment Method flagged for "ORO Close". The alert message will advise them that the program has been switched from "Invoice Pending" to "Close" mode when ENTER is pressed before F6 is used to process the Vendor RO. Typically it is beneficial to use this option when the vendor is paid immediately when repairs are completed and an Invoice will not be sent for payment from the vendor based on the Payment Method selected, like "CASH", "CHECK", or "CREDIT CARD". Alert Message: "ATTENTION! The program is now in CLOSE mode based on the Payment Method"
2012.10
180 - Outside Repairs TMT117 09/09/2012 #2792
We changed the program to prevent an update to the Vendor RO when two users attempt to update the ORO at the same time, and user one is closing the ORO while user two is still adding charges. If user one has already begun to close the ORO, user two will not be allowed to add more charges. This was done to prevent errors with the charges. If this were allowed to occur, the result would be a mismatch between the RO total and Invoice total.
2012.10
180 - Outside Repairs TMT180L 06/11/2012 #2587
We changed the program to allow you may enter "######" in the Vendor field in the Listing Options window to filter the Vendor RO Listing by NATC vendors.
51
2012.10
180 - Outside Repairs TMT180L 08/23/2012 #2722
We changed the program to check the status of the Outside Repair Order when the "Charges" option is selected for an ORO in "IP" - (Invoice Pending) status, and Firmware "ORO - Allow Editing in IP Status" is set to 'No'. The program was changed to display the ORO charges in "Inquiry" mode instead of displaying the window that allows the user to select Close or Pending status (TMT186). This change is also effective from other programs that allow a user to display an ORO, like Road Calls, Purchase Orders and Shop Planner.
2012.10
180 - Outside RepairsTMT892H 06/19/2012 #2587
We added the new Repair Order ID number (ROID#), in the display for "Repair Change History" for all Repair Orders. In view mode from Menu Selection 100 or 180, use F16=Change History while viewing the RO Header to display the "Repair Change History", and the new ROID#.
2012.20
180 - Outside Repairs TMT113 12/10/2012 #3078
We modified the program to ensure the Purchase Order header file, (POHEDER), is kept in sync with the new Repair Order header file, (ROHEAD), when a Vendor RO is canceled. In the previous version, (2012.10), when a Vendor RO, (ORO), was canceled before adding any sections, the PO Header file was not getting updated from Open status to Canceled status.
2012.20
180 - Outside Repairs TMT113P 01/08/2013 #3068
We corrected the program to print ORO Work Card when the "Print RO" flag is set to 'Y'.
New Enhancement 3015 We added a new feature that allows you to select from multiple "Remit To" vendors for a vendor. This will be useful when you need to setup an alternate "Remit To" vendor for purchases that may be supplied by the vendor performing the repairs, and billed to another vendor. Example: A tire vendor is providing a new tire, and you want the "Remit To" vendor changed on the Vendor RO to the tire manufacturer for National Account billing, instead of billing from the tire vendor providing the tire. The Supplier Master has a new Command Key, "F9=Remit To". This new command key will display a window that allows you to setup multiple vendors as "Remit To" vendors. A conversion program will run with this upgrade to Version 2012.20 that will automatically add your current "Remit To" vendor as the default "Remit To" vendor for this function. You do not need to do any additional setup, except for the vendors that you want to add an additional "Remit To" vendor to. Vendors that have multiple "Remit To" vendor’s setup will allow the user to select a "Remit To" vendor other than the default "Remit To" vendor when closing a Vendor RO. You may press F4 in the "Remit To" field on the Vendor RO header as you close the Vendor RO to select an alternate "Remit To" vendor.
All Suppliers must have at least one "Remit To" vendor
One "Remit To" vendor must be set as the default
The program will not allow the last "Remit To" supplier to be deleted
The program will not allow the user to exit without a "Remit To" default specified
Security for Menu Selection 630 - Supplier Master for Add / Change / Delete applies to this new feature
52
2012.20
180 - Outside Repairs TMT183 04/15/2013 #2853
We changed the program to ensure that the Vendor RO file, (ROHEAD), is updated with the Payment Method and Payment Number immediately after generating a Comdata Virtual MasterCard number, (Comdata VMC), and before the user presses F6 to process. In previous versions, if the user lost connection, or closed the session after generating the Comdata VMC, and prior to processing the Vendor RO, the Repair Order file was not updated with the Comdata VMC number, and could not be matched to the Comdata VMC transaction. Other Changes:
The User is no longer allowed to exit the Close or Invoice Pending process after the Comdata VMC number has been created, until they press F6 to process the Vendor RO.
If the Payment Method selected matches the Firmware value "COMDATA MC Payment Method", the User will not be allowed to press F6 to process the Vendor RO without first creating a Comdata VMC number.
The Invoice Number, Invoice Date, Payment Method, and Payment Number become protected and changes are not allowed for these fields when the User creates a Comdata VMC.
Intentionally closing the IBM i session will not bypass the integrity of the Comdata VMC number creation process.
After a Comdata VMC number has been created for a Vendor RO, a user is not allowed to add, change, or delete existing RO sections, part or labor charges.
We added the Order Status 'E$' – “ePayment Pending” to the Order Status list.
This status can be used to display any Vendor RO if the Status is 'OP/$', 'IP/$', or 'CN/$'. All of these statuses indicate a Virtual MasterCard has been generated for the Vendor RO.
We corrected the "RECAP OF CLOSED OUTSIDE REPAIR PURCHASE ORDER" report to display "Non-Company" in place of the Unit Description when the Company Unit flag is set to 'N' on the Vendor Repair Order. If the Unit Number on the Vendor Repair Order exists in the Unit Master, and the Vendor Repair Order Company Unit flag is set to 'N', and Firmware "RO Non-Cmpy Unit - Do PMs" is set to 'N', then the Unit
Description will be 'Non-Company Unit'. If the Unit Number on the Vendor Repair Order exists in the Unit Master, and the Vendor Repair Order Company Unit flag is set to 'N', and Firmware "RO Non-Cmpy Unit - Do PMs" is set to 'Y', then the Unit
Description from the Unit Master will be displayed.
2012.41
180 - Outside Repairs TMT115C 10/14/2013 #3180
We changed the program to prevent a Warranty Part Charge record from being created when a VMRS Number is not provided for a Vendor Part Charge line. In TMT115C, the warranty life fields will now only get populated for V lines when a valid VMRS Code has been entered. In previous Versions of 2012, if the Warranty Claim Type on the RO Section was 'NONE' or 'EXPIRED' and the part warranty is also 'NONE' or 'EXPIRED', the program was setting 'ON' the Warranty Part Charge flag for any vendor ('V’) line regardless if a VMRS Code was entered.
Now, a Warranty Part Charge record is only created in MS 700 - Warranty Part Master when a valid VMRS Code is entered. If the VMRS Code is removed from the Vendor Part Charge record, or if the part is deleted from the ORO, the Warranty Part Charge record is deleted in Menu Selection 700.
We also corrected an error with the Part Position logic. In previous versions when a positional part was entered on a Repair Order for a Non-Company Unit, the part position logic would return an error that should have been ignored. This code is used to determine if "F10=Part Positions" should be displayed.
53
2012.41
180 - Outside Repairs TMT186 10/25/2013 #3179
We removed the call to TMT186 from TMT111 to prevent the window from being displayed a second time after the User has already selected one of the options to change the Vendor RO to Closed or Invoice Pending status.
New Enhancement 3204 We changed the program to use new Firmware “ORO - Prompt for VMRS Code on “V” lines” to allow a User to prompt from the Part Number field in RO Charges into the VMRS Code Listing, when the Part Source is 'V' - Vendor, and the User has Security Access to Menu Selection 814 - VMRS Component Master. When the Part Failure Code is defined as required in the Part Master, an error message will be displayed to alert the User a Part Failure Code must be entered. Non-Stock parts will no longer be deleted from the Part Master automatically if a Warranty Part Master record exists and Firmware "Delete Non-Stock Parts ?" is set to 'Yes'. We changed command key F17=Add JC Parts to display in PINK as it has in previous versions. Part Position Assignments are not allowed for Non-Company Units, and the Part Position Assignment window will not be displayed when a part that requires Part Position Assignments for Company Units is charged on a Repair Order for a Non-Company Unit.
2012.41
180 - Shop Repairs TMT117 01/06/2014 #3184
We corrected an issue that may occur when closing an ORO. The program was issuing a false error ‘Invoice date cannot be less than down date’. This could occur when the Down Date is from the previous year and the Invoice Date is from the current year.
We changed the program to prevent the user from changing an Employee to Inactive status, or deleting the Employee if “unposted” Time Cards exist for the Employee.
2012.10
220 - Employee Master TMT225H 09/10/2012 #2990
We changed the program to remain on the same page of the Employee Listing when you use F3 to exit an Employee record. In previous versions, the Employee Listing would return to the top of the list if you had paged down to select an Employee record to Work With, then exit the record. Now it will continue to display the same page you were on when you select the Employee.
2012.20
220 - Employee Master TMT225H 01/11/2013 #3084
We modified the program to prevent an Overflow Error when more than 99 employees were listed on the sub-file, and the user attempted to page down past the 99th record.
We corrected an overflow error with the program that could occur if the “DownTime Analysis” report included over 100,000 records.
55
Unit Menu
2012.10 300 - Unit Master TMT310 03/16/2012 #2837
We changed the program to allow a meter entry of zero if the Utilization Base Code is 0007 - Days, or 0009 - Months, when a new unit is created or updated. The meter update program will also allow you to change a meter back to zero for Days or Months based units. PM's will no longer fail due to the error condition - "RO meter is less than last PM" for a unit with a Utilization Base Code of 0007 or 0009.
In previous versions the user was not allowed to enter an RO meter for a unit with a Utilization Base Code of 0007 or 0009, and the program compared the current meter in the Unit Master, (usually a '1'), and failed the PM.
N
2012.10
300 - Unit Master TMT310 10/01/2012 #3004
New Enhancement 3004 We added a new API that will allow you to update or add Unit Master records from your custom program. The API has the ability to allow the user to pass the information into the TMT Unit Master in Silent Mode offering the ability for the program to pass back error messages to the sending program, or Non-Silent Mode requiring the user to review the TMT Unit Master screen after the data has been passed to the TMT Unit Master.
2012.20
300 - Unit Master TMT310 12/14/2012 #3075
We changed the Unit Status field to display as 'blank' in Duplication Mode when the Unit that is duplicated has a Status of '9999 - Reports Only' to prevent a user from creating the new Unit as a 'Reports Only' Unit. The User must enter a valid Unit Status. If the Duplicated Unit has any other Status except '9999', then it will automatically be displayed in the Unit Status field for the new Unit being created.
2012.10
317 - Unit Component Master TMT317L 03/28/2012 #2906
We changed the program to allow the user to prompt in the Listing Options "Value"' field using F4, to display the related list for certain "Field Types" listed below. If the "Group Code" selected in the Listing Options is defined with a "Field Type" listed below, and the user presses F4 in the Listing Options "Value" field, then a list related to the "Group Code" is displayed - see below. *DATE - Displays the calendar *MAKE - Displays the Manufacturer Codekeys *PART1 - Displays the Parts Catalog
2012.20
317 - Unit Component Master TMT317A 11/28/2012 #3009
We changed the Component Duplication process to update the Component Unit, (COMPUNIT) and Component Warranty, (COMPWARR) files correctly when warranty components are duplicated. In previous versions, if the user included a dash in the Component Code '*TO' field, the file was getting updated incorrectly by including the dash. Example - if the user entered a Component Code of '045-010' in the *TO field, instead of '045010', or '*FROM', the program updated the file with the dash. Now the program has logic to update the COMPUNIT and COMPWARR files without the dash, regardless of how the user enters the Component Code in the '*TO' field.
56
N
2012.40
352 - Unit System Cost Analysis TMT170 09/17/2013 #3145
New Enhancement 3145
We replaced the "Unit System Cost Analysis" report menu with a new three-column Listing Options screen similar to the new screen introduced for Menu Selection 132 - RO Inquiry Detail. This new Listing Options screen is designed to give the User multiple options to create the "Unit System Cost Analysis" report to Include or Exclude Units or RO's as desired.
The available fields are the same as the RO Inquiry Detail with two exceptions. The Company Unit and RO Status fields are excluded from the "Unit System Cost Analysis" report Listing Options screen since this report will only include Company Units and RO's in "Completed" ('CM') status.
The "Unit System Cost Analysis" report has a new view and new options also. In View Mode, the previous header has been replaced, and now three new options have been added. These options allow the User to select any System Code line displayed on the report and drill down to the detail that is included in the Summary line displayed. The three options are:
R=by RO S=by Section C=by Charges
Each of these three views will display the "Repair Order Charges Listing" by the view selected. The User may sort the report by the same sort options available in previous versions:
1. Labor Cost 2. Labor Hours 3. Part Cost 4. Total Cost 5. System Code
Date Range Selections - Listing Options o All "FROM" dates are processed as >= (RO's greater than or equal to the FROM date
will be included) o All "TO" dates are processed as <= (RO's less than or equal to the TO date will be
included) o All date ranges select records >= FROM date and <= TO date
o The default FROM Down Date is the beginning date of the year if no other dates are selected
o Up Date and Down Date selections are now independent of the RO status
2012.10
361 - Install New Meter TMT361 10/18/2012 #3053
We changed the program to prevent decimal data errors when:
the Unit meter is being replaced
there are no Repair Orders for the unit
there are Fuel Tickets for the unit
2012.10
363 - Monthly Util Update TMT363 08/15/2012 #2917
We corrected the program to allow a new meter update when the default Utilization Base code of *PRI is used. In the previous version if '*PRI' was used, the program would display the error message 'Multi-Utilization Type does not exist - MULTUTI2'.
2012.31
363 - Monthly Util Update TMT363 07/17/2013 #3128
We corrected the program to prevent it from being caught in a loop when the last Unit in a selection of Units included a Unit with a Status of 9999 - Reports Only. In previous versions, if the last Unit in the selection had a status of 9999, the program got caught in a loop instead of skipping the Unit and exiting.
2012.10
370 - Unit Master Inventory Reports TMT370 03/19/2012 #2927
We corrected a problem that prevented the program from displaying the correct units when a specific Cost Center and Unit Status "9999 - Reports Only" was selected in combination with the "E - Exclude" option.
57
2012.41
380 - Renumber Units TMT 12/05/2013 #3208
We changed the program to ensure the "Parent" field is updated when a Unit Number is renumbered. In previous versions, the Unit Number on the "Parent" field in the Unit Master was not getting updated when the "Parent" Unit was renumbered using Menu Selection 380 - Renumber Units.
58
Fuel Menu
If you use the Fuel Import Profiles in Menu Selection 499 – Fuel and Meter Import/Export, you will need to define values for the “Trip Ticket” item. (This is required, even if you do not have a “Trip Ticket” number included in your Fuel Import data file).
o If you do not have a “Trip Ticket” value in your Fuel Import file, you may substitute any other data, (except a “blank” column).
Tip: Substitute the Unit Number for the “Trip Ticket” value. Use the same values you have defined for “Unit Number” item in the Fuel Import Profile to define the “Trip Ticket” item.
A “Trip Ticket” definition is NOT ALLOWED for the “Hub” Import Type.
We changed the program to display the negative sign, (-), on the printed report in the "COST PER UNIT USAGE" column when the value is a negative amount. In the online, or "View" mode, the Total Amount, Total Cost, or Use/Unit Fuel will be displayed in red to indicate a negative amount.
N
2012.20
460 - Unit Fuel Analysis Report TMT461 12/03/2012 #2977
New Enhancement 2977 We added a new feature that will allow you to select the Fuel Types you need to include or exclude in the report totals on the "Unit Fuel Analysis" report. We also made several improvements to the report. We added a new flag named "Use in Report Totals" for the Codekey Category "0112 - Fuel Type" in Menu Selection 800 - Codekeys Master. This new flag will allow you to select each Fuel Type you will need to include or exclude in the report totals. The conversion for this version will automatically set all Fuel Type codes to 'Y', except for "ADDOIL", which will default to 'N'. Report changes include: Note: these changes only apply to the printed report.
Removed "(w/o ADDOIL)" from Total Descriptions.
Added "**" next to Fuel Types to indicate the Fuel Types not included in report totals.
Added legend to end of report.
Changed to print "USE PER UNIT FUEL" (MPG) and "COST PER UNIT USAGE"(CPM) for every Fuel Type.
Changed Grand Totals to print "Totals (by Fuel Type)" listed in the report.
2012.20
499 - Fuel Import TMT499I 10/29/2012 #3033
We changed the program to allow the Fuel Import to process Fuel Tickets with a missing Unit Number. In the previous version, when a Fuel Import defined for right-adjusted Unit Numbers, and the Fuel Import contained a record with a blank Unit Number in the import file, the program would issue an error message; 'length or position out of range'. Now, the program will allow the Fuel Import to run without program errors. Any Fuel Tickets processed with a missing Unit Number will display the message as: "Invalid Unit - VHCLMSTR".
59
N
2012.20
499 - Fuel Import TMT499L 10/30/2012 #2923
New Enhancement 2923 We added a new option in the "Run Import" window for the "Fuel Import Error Listing" report. Now you have the option to exclude the transactions that were processed normally without errors. (The "Run Import" window is displayed after using option 6=Process to process a Fuel Import). The new options for "Print Report" are:
No - the "Import Error Listing" report will not be printed
Yes - the "Import Error Listing" report will be printed, including all transactions that passed or
failed
Errors - the "Import Error Listing" report will be printed, only including transactions that failed
We also removed the "Correct Errors" option from the "Run Import" window for Hub Imports.
2012.20
499 - Fuel and Meter Import/Export TMT499L 02/19/2013 #3106 and 3037
We corrected the program to allow a Transmission record to be created or duplicated for a Fuel Import record. In the previous version, the program was not saving the values entered for a Transmission record. We also added a new option to allow the user to change the Properties for a Fuel Import. Option 7=Properties - Use this option to display the properties for the Import/Export Profile selected.
2012.41
499 - Fuel and Meter Import/Export TMT499C 12/04/2013 #3119
We changed the Fuel Transaction correction process to prevent multiple users from accessing the same Fuel Profile at the same time. When multiple Users attempt to access the Fuel Transfer Corrections Listing Options, and the Fuel Profile is "*NONE", a message will be displayed to alert the User with the UserID that currently has the Fuel Corrections locked - "Access Denied. Fuel transaction corrections in progress by user xxxxxx.". If a Fuel Profile (other than the default *NONE), is currently locked by another User, then after 60 seconds, a record lock window will be displayed, including the UserID that has the Fuel Profile locked.
2012.41
499 - Fuel and Meter Import/Export TMT499C 12/04/2013 # 3196
We added a new field for the "Fuel Stop State" in the Fuel Import Profiles. This new field will allow you to define the Beginning and Ending positions of the Fuel State in the Fuel Import file. If the Fuel State is defined in the Fuel Profile and included in the Fuel Import, the Fuel State will also be updated in the Fuel Ticket History file (FULTKHST).
Road Fuel Import - If the Fuel State does not exist in the import file, and a valid Supplier is supplied or a Supplier Override Value is defined, the Fuel State will default from the Supplier Master.
Company Fuel Import - If the Fuel Import contains a valid Shop Number, and the Fuel Profile has the Shop defined or a Shop Override Value is defined, the Fuel State will be populated with the State from the Fuel Shop.
We removed the requirement to define a Trip Ticket Beginning and Ending value for Fuel Imports. Now, the Trip Ticket definition is optional for a Fuel Import Profile.
60
Tire Menu
No updates
61
Part Menu
2012.20 600 - Parts Master TMT620H 11/30/2012 #2978
We changed the program to display a record lock window when two users try to access the same part from the Part Master (MS 600) at the same time. The lock window will be displayed to the second user attempting to access the record from the Part Master or the Core Master. The lock window displays the User ID for the first user, allowing the second user the option to contact the first user to request access to the Part Master record. When the first user exits the Part Master record, it will be released to the second user.
2012.20
600 - Parts Master TMT610, TMT610A, & TMT1041L 02/08/2013 #3085
We changed the formula used to calculate the Reorder Point. The new Reorder Point formula will add the Forecast Period to the Average Lead Time and be multiplied by the Average Demand, then the Recommended Safety Point is added. This change should reduce fluctuations and level out the lows and highs for the Reorder Point calculations. New Reorder Point formula: ((Forecast Period + Average Lead Time) * Average Demand) + Safety Point (The "Recommended" Safety Point) Previous Reorder Point formula: (Forecast Period * Lead Time Demand) + Safety Point Lead Time Demand = (Average Demand * Average Lead Time)
N
2012.31
600 - Parts Master TMT620H 08/09/2013 #3155
New Enhancement 3155
We added the Wildcard search to the Part Number column in the Parts Master and the Parts Catalog. It works the same as the Wildcard search in the other columns, and just for a refresher, the Wildcard Search Definition is outlined below. Wildcard Search for Parts Master Listing
Menu Selection 600
Program TMT620H
Column Heading “Part Number” change to “Part Number (*)” Wildcard Search for Part Catalog
Menu Selection 640
Program TMT600H
Column Heading “Part Number” change to “Part Number (*)” Wildcard Search Definition
Wildcard searches can be done in one of two methods using an asterisk (*) as a portion of the part number entered.
Method 1 – place the asterisk in front of the part number o - This method will display all parts that include the search data
Method 2 – place the asterisk at the end of the part number o - This method will only display parts starting with the search data
Search Definition without Wildcard
If you enter a value to search for without the asterisk, the list will be "positioned" to the value entered, or the next greater value if the entered value does not exist in the list. The list will include all records greater than the value entered.
62
N
2012.40
600 - Parts Master TMT610 09/06/2013 #2909
New Enhancement 2909 Serialized Part Number functionality has been added. The feature will allow you to link the serial numbers for a part to Inventory, Units, Repair Order Charges, and Indirect Charges.
Part Serial Numbers can be added during Purchasing or Physical Inventory, and selected when parts are charged out on a Repair Order or Indirect Charge
When changing to a serialized part where quantity on hand exists, the program will create a physical inventory to lock the part until serial numbers are identified
We added a new command key to the Part Master – “F7=Serial Numbers” this will allow the
user to display all of the Serial Numbers currently assigned to the Part Number selected
We added comments for Part Serial Numbers using program TMT815
Comments are stored in file TMTCMTS using the Part Serial Number as the key field with a "Type" of 'PTSN'
Part Serial Number comments can be displayed anywhere a Part Serial Number can be displayed
A "Cmt" column exists in the "Serial Number Master" window, and a 'Y' will be displayed if comments exist
2012.41
600 - Parts Master TMT610 12/06/2013 #3151
We changed the program to require a System Code for all Part Master records. In previous versions, the program would allow a User to create a *NON-STOCK part record without a System Code.
N
2012.10
623 - Parts Usage TMT622R 10/17/2012 #3018
New Enhancement 3018 We corrected the report to display the data for each line and part. In the previous version, the data displayed was off one line for each part number displayed on the report, and the last part number displayed did not have any data displayed. We also fixed an issue with a program error when a negative quantity was entered for part usage.
We added two new options when the report is generated for parts with no usage. Now you have the option to select the "Months since Last Purchase" and "Include QOH & QOO = 0". "Months since Last Purchase"
Enter a value to exclude parts without usage that were purchased within the number of months selected, prior to and including the current month. Example: If you want to exclude parts purchased in the current month and the previous two months, then enter a '2'. "Include QOH & QOO = 0"
Use this option to include parts that have a zero "Quantity on Hand" and zero "Quantity on Order". Three options are provided: 'Y' - Yes, include parts with a zero "Quantity on Hand" and zero "Quantity on Order". 'N' - No, do not include parts with a zero "Quantity on Hand" and zero "Quantity on Order". 'O' - Only, include parts with a zero "Quantity on Hand" and zero "Quantity on Order".
2012.20
623 - Parts Usage TMT622R 11/30/2012 #2986
We changed the program to display a negative sign in the Quantity on Order column for parts that have a net total negative value, which normally indicates a credit Purchase Order exists for the part. We also modified the program to allow it to be compatible for IBM i Operating Systems below V6R1M0. In previous versions, when 'Total Usage Qty' = 0, the usage report was using a FULL OUTER JOIN which is NOT supported below V6R1M0. This modification was needed to ensure all records from both the Part Master file, (PARTMSTR), and the Part Usage file, (PARTUSAG), including those in the PARTMSTR file , without a match in the PARTUSAG file, and also the ones in PARTUSAG without a match in PARTMSTR file are displayed. This has been replaced with a UNION JOIN of a LEFT OUTER and an EXCEPTION JOIN.
63
2012.20
623 - Parts Usage TMT622R 02/22/2013 #3105
We increased the amount of part usage that can be tracked each month for parts. In previous versions, the program would only allow a maximum of 99,999 units per part to be tracked. Now, the program can allow 999,999. We also increased the columns in the Part Usage report to display the new larger quantity. We changed the report totals to display the maximum allowed for the field, (999,999) without displaying an error message if the totals exceed the field maximum. We also added editing to prevent a user from creating a credit or adjustment for a part that would cause the Quantity -on-Hand to exceed the maximum in inventory allowed, (99,999). This includes part credits on a Repair Order, RO Section deletes with parts, Part Transfers, Indirect Charges, and Inventory Adjustments.
2012.40
623 - Parts Usage TMT622R 08/23/2013 #3162
We corrected the program to list only the parts defined in the selected Part Profile. In previous versions, when a Part Profile was selected for the Parts Usage report, parts that were not defined in the Part Profile were also included on the report. We also corrected the printed report to include all parts selected. In previous versions, the print option was only displaying first line from the parts selected for the report.
New Enhancement 2984 We added a new Firmware, "BC Zebra Printer Label Size:1=1x4;2=2x4”. This new Firmware will allow
you to choose a 1" x 4" or 2" x4" label when using a Zebra GX420t label printer.
2012.10
630 - Supplier Master TMT630 03/16/2012 #2587
The Warranty Labor Rate field size has been reduced from a seven digit field, (99,999.99) to a five digit field, (999.99) to prevent errors that occurred during the EOD if a value greater than 999.99 was entered for the Warranty Labor Rate amount.
2012.10
630 - Supplier Master TMTAPI 04/03/2012 #2981
We changed the Supplier Master API import program to populate the "Warranty", "After Market Labor", and "Include MWS Data" fields by the 630 TMT API program. The value entered in the "API_SUPP/VNDSVC" field in the API passes values to these fields in the Supplier Master file displayed in Menu Selection 630. Also, the print default field will be populated now in the Supplier Master from the value entered in the "API_SUPP/VNDEPO" field. The API passes the "Print Default" value of 'Y', 'N', 'E', or 'F' to the printer field for the Supplier Master record. Please review the on-line Help for the "Print Default' value in the Supplier Master to read more about the definition for each of these values.
2012.20
630 - Supplier Master TMT630 12/04/2012 #2992
We changed the program to use the Security Rights setting for Menu Selection 630 to determine if the user should have View/Add/Change/Delete rights for Command Key "F8=Export Setup" on the Supplier Master record.
2012.41
630 - Supplier Master TMT630N 10/03/2013 #3178
We corrected an error message that was displayed when deleting a Supplier Master record. In previous versions the "Navistar Module - Access Denied" window was displayed or an error message for logical file LPOHDR7, or both when a Supplier Master record was deleted. We also corrected an error on logical file LPOHDR6 that occurred when a Supplier Name was changed.
64
N
2012.40
640 - Parts Catalog Master TMT600 09/06/2013 #2909
New Enhancement 2909 Serialized Part Number functionality has been added. The feature will allow you to link the serial numbers for a part to Inventory, Units, and Indirect Charges.
We added a new field to the Part Catalog Master - "Serialized Part". This field can be set to 'Yes' or 'No' to indicate if the part should be managed as a Serialized Part
After a part has been set to "Serialized", the User should use F10=Update Masters to update the Serialized Part flag for the Part Masters that contain the part
We added a new command key to the Part Master – “F7=Serial Numbers” this will allow the
user to display all of the Serial Numbers currently assigned to the Part Number selected
When changing to a serialized part where quantity on hand exists, the program will create a physical inventory to lock the part until serial numbers are identified
2012.41 640 - Parts Catalog Master TMT600H 10/10/2013 #3155
We corrected the program to refresh the screen and display all the part records in the Parts Catalog beginning at the top of the Listing when a part has been selected using option "2=Work With" at the top of the Listing on the Cut-Option line. In the previous version, when the User returned to the Listing after pressing ENTER in the selected part record, the Listing displayed the message - "!! No Data" and none of the part records were displayed. We also corrected the program to display the Job Number, Job Queue Name, and Library Name in the completion message that is displayed after the User has used "F10=Update Masters". In the previous version, these details were omitted from the completion message.
2012.10
650 - Part Transactions - View/Print TMT655V 06/19/2012 #2587
We added a new field in the Part Transaction file - PARTRAX. The field named PREFSCT will be populated with the Repair Order section for part charges for Repair Orders. This field will only be populated with RO section numbers for RO's created beginning with version 2012.10. Any RO part charges from previous versions will display as blank in this new field. It will not be updated with the RO section for RO part charges from previous versions. This new RO section number will allow the program to display the RO section when Command Key "F8=View Order" is used.
Added a new Part Transaction Information window to display ALL of the PARTRAX information o The Part Transaction Information window includes command keys that allow the User
to display the Serial Number detail including the Serial Number History and Comments o View the Order - Purchase Order or Repair Order o Serial Number comments
Removed the Sub File fold lines since this information can now be viewed in the Part Transaction Information window
When a Serialized part is added or updated, an additional record for the Serial Number is created and displayed in the Part Transaction Listing.
o The "Qty" on this record will display a zero since the record represents the addition of the Serial Number, and does not represent a change in Quantity on Hand
The Part Adjustment record will display the "Qty", and will not display Serial Numbers Part Transaction Report
Added Serial# (*) field to the screen so the User can subset the Part Transactions by serial number
Wildcard allows for 123* or *123 (for example) to subset the list of Part Transactions by Part Serial Number
We changed the program to refresh the message displayed for the Parts Usage Adjustment. In previous versions, when the "Update Usage" flag was changed from 'Y' to 'N', after the Usage Adjustment message was displayed on the screen, the screen was not refreshing and removing the message. (A Usage Adjustment message should not be displayed if the "Update Usage" flag has been set to 'N').
2012.41
651 - Adjust Parts Inventory & Usage TMT650 12/10/2013 #3195
We changed the program to display the "Record Lock" window when a User is displaying a Part Master record, and another User is attempting to create a Physical Inventory Update in Menu Selection 651 - Adjust Parts Inventory & Usage or Menu Selection 652 - Physical Inventory Adjustment that will include the Part Number that is currently in use. The "Record Lock" window displays the UserID that has the Part Master record locked. If this occurs, the User that has the Part Master record locked should be requested to exit the Part Master record to release the lock condition so that the Physical Inventory may proceed.
We increased the maximum inventory value for a part that is being updated for a Physical Inventory from $99,999.99 to $9,999,999.99.
2012.20
660 - Parts Transfer Routines TMT660 12/03/2012 #3012
We corrected the program to display the actual Quantity on Hand value for a part that is being transferred to another Shop inventory. In previous versions, if the user set the "Update Usage" option to 'Yes', the "Transfer From" Shop would incorrectly display a zero Quantity on Hand for the "Beginning Balance" in the Part Transaction History, (Menu Selection 650 - Part Transactions - View/Print).
66
2012.40
660 - Parts Transfer Routines TMT660 09/16/2013 #2909
New Enhancement 2909 Transfers for Serialized Part Numbers is not supported in this version for Menu Selection 660 - Parts Transfer Routines or Menu Selection 661 - Receive Transfers to Inventory OR when Firmware "Hold
Part Transfers ?" is set to 'Yes', and when using Menu Selection 1042 - Requisition Transfers, or 1043 - Release Requisition Transfers.
2012.10
690 - Component Life Report TMT695P 08/30/2012 #3014
We corrected an overflow error with the program that could occur if the “Component Life” report included over 100,000 records.
67
Warranty Menu
2012.10 700 - Warranty Part Master TMT710 and TMT710H 02/29/2012 #2587
New option 5=Review - Use this option to Review a Warranty Part Master record. (Changes to the record are not allowed with this option). Claim Number - We added the Claim Number to the Warranty Part Master screen. When the current Status of the part is "OFF" - OF, then the Claim Number will be displayed in the lower right hand corner of the screen. F7=Claim - If the current Status is "OF", you may use "F7=Claim" to display the Claim. The claim will be displayed from Menu Selection 720 - Claims - Submit/Receive/Print or Menu Selection 744 - Claims Analysis View/Print, depending on the current status of the claim.
2012.10
700 - Warranty Part Master TMT710H 07/16/2012 #2587
The Part Number field in the Listing Options no longer validates the Part Number to allow searches for Vendor Part Numbers.
There is a "hidden" option to print the Repair Order Section for the claim. Option S=Special Print - Use this option to print a copy of the RO History Workcard that only includes the RO and Section for the Warranty Claim selected.
We changed the entry process when creating a Manual Claim from RO History. You no longer have the option to enter a "Down Date" and if you prompt to select an RO, all completed RO's are displayed, and you may use option 1 to 'Select' the RO, instead of having to manually key the RO Number.
We corrected the program to write the subfolder name correctly when it is added to the IFS root\eWarranty folder for claims submitted to International Corp. In all previous 2010.xx versions, it was including unwanted characters in the 31st and 32nd position of the subfolder name defined the in the Supplier Master eWarranty Export setup.
We changed the program to prevent an error when more than 9,999 Warranty Claims will be displayed based on the selections entered. We also added a new Command Key, F5=Refresh.
68
System Menu
N
2012.40
Mobile Computing app - used for mobile updates
New Enhancement – Mobile Computing We have released a Mobile Computing app available for popular mobile devices.
The new Mobile Computing app provides three functions for the User: Physical Inventory - Allows the user to perform a live real-time update for a Part Physical Inventory
count Yard Check - Allows the User to perform a live real-time update for a Unit Physical Location TMT Dashboard - Provides a selection of reports displayed in a colorful vertical bar-graph format
Open Shop RO Count - Displays the number of Open RO's - by Shop from highest count to
lowest count
Open Vendor RO Count - Displays the number of Open Vendor RO's - by Shop from highest
count to lowest count
Open Call Count by User - Displays the number of Open Road Calls - by User from highest
count to lowest count
N
2012.20
TMT Service Program - TMTSRVPGM 03/08/2013 #3100
We added a function check and a new data area to ensure the programs are compatible with IBM i 7.1 SQL states.
Approximately 96 programs have been updated to accommodate the new IBM I 7.1 SQL states.
Function: CheckSQLState has been added to service program: TMTSRVPGM.
New data area "TMTSQLST".
N
2012.10
800 - Codekeys Master TMT810 05/30/2012 #2884
New Enhancement 2884 We added a new field named "Rpr Days" for System Codes. This field can be used to override the value set in Firmware 12250 - "RO Recent Sys Repair Days".
If this new value is blank or zero, then the value set in Firmware "RO Recent Sys Repair Days" will be used to determine if Recent RO History should be displayed for a user creating Repair Orders. The program will check the Repair Days value first. If the value is zero or blank, then the value in Firmware "RO Recent Sys Repair Days" will be used. We also added a new flag for Codekey Category 600 - RO Templates. When this new flag named "Load All" is set to 'Y', the program will automatically load all sections associated with the RO Template selected while creating a Repair Order or adding sections without requiring any further action from the user. If it is set to 'N', then each section will be displayed in the "Add RO Section" window, allowing the user to change the RO Template section or add it to the Repair Order.
2012.20
800 - Codekeys Master TMT810 04/26/2013 #3095
We changed the program to prevent a System Code from being changed to Inactive status if the System Code is currently in use for an Open Repair Order, a Work Pending, a PM System Master record, or a Component defined in the Unit Component Master. Repair Orders in 'CA' - Canceled status are excluded from this change.
69
2012.10
820 - End of Day Processing 06/12/2012 #2587
We added " - EOD" to the report titles for the End of Day reports to clarify that the reports were generated from the EOD process. TMT125U - PM Update Listing - EOD TMT430 - Fuel Ticket Update Listing - EOD TMT4431 - Vendor Fuel Summary Listing - EOD TMT850 - Completed Vendor Repairs - EOD TMT861 - Completed RO Recap - EOD TMT862 - Completed Repair Orders Listing - EOD TMT901 - Currency Converted Listing - EOD TMT902 - Currency Converted Listing for Indirect Charges - EOD
2012.10
820 - End of Day Processing TMT840B 08/16/2012 #3035
We made a change to the “Base Rule Edit” to prevent Batch and Minor RO's from being processed when the Batch or Minor RO’s are closed automatically during the EOD if a “Base Rule Edit” error exists for the RO and the "Base Rule Edit" Firmware was set to 'Yes'. In previous versions, if the Batch or Minor RO's were automatically closed during the EOD, and a Batch or Minor RO also had a “Base Rule Error”, the EOD would process the RO to RO History if the "Base Rule Edit" Firmware was set to 'Yes'.
2012.10
820 - End of Day Processing TMT700 10/01/2012 #3055
We changed the program to use the RO Charges file to obtain the part quantity when a part that has Part Position Assignments is included on a Warranty Claim instead of the Part Position file.
N
2012.20
820 - End of Day Processing TMT125U 12/05/2012 #3049
New Enhancement 3049 We added a new process and file to keep track of any changes made to Repair Orders with a PM Section. A new program (TMTTPMRO) was created to update a new data file (WK121R) to log any changes made by any program, including any database utility tool. A record will be written to the WK121R file anytime a change is made to a Repair Order PM Section. The record will include the Unit Number, RO Number, RO Section, RO Status, System Code, and the Date and Time any user makes a change, deletes, or adds a PM Section to a Repair Order. We also included the program and transaction type; (Insert, Update, or Delete).
2012.20
820 - End of Day Processing TMT901 12/12/2012 #3071
We modified the program to prevent an error when the Firmware for "Currency Conversion" is enabled, and a Vendor RO Labor Line is being processed with a zero quantity for hours. We also changed the TMT/Innovative AR & Settlements API interface to prevent an error when "Use Innovative Interface" is set to 'Yes', and Firmware "Run AR Export" is set to 'No' and Firmware "Run Settlements Export" is set to 'No', or Firmware "Account Structure A=Acct,S=Sub,C=CCtr" is set to 'blank'. Now, the program will not execute. The program should only run when one of the two export flags is set to 'Yes', and the Account Structure has been entered.
2012.31
820 - End of Day Processing TMT125U 07/23/2013 #3133
We changed the program to use the Repair Order Up Date to update the Last PM Date in the PM Factor Master record file when the RO Up Date is blank in the PM Scheduler record (file PMSCHEDR). This change was added as an additional edit check to ensure that the PM is updated.
2012.31
820 - Work Standards Master TMT151U 07/23/2013 #3146
We changed the program to reconfigure the processing of the Repair Order header file, (ROHEAD) when Work Standards is not in use. We removed SQL updating in favor of line by line processing to update ROHEAD(ROSTAT) and ROLINE(RLSTAT) from End of Day status U5 to U6.
70
2012.41
820 - End of Day Processing TMA895GL 01/07/2014 #3220
We changed program TMA895GL to update the "Posted" fields in the Accounting Export file - ACTXTRAN. We also added a new Data Area "TMARUN" for the TMT / TL2000 - Accounting Interface Run Control. We changed the TL2000 interface programs - (CLTMA895AP, CLTMA895GL, and CLTMA895AR) to set a flag in the new Data Area "TMARUN" while the CL program is running. Each program has its own two digit code: AP (positions 1-2), GL (positions 3-4), AR (positions 5-6). If an error occurs while the interface program is running, subsequent running of the program will send a message to QSYSOPR and end without any changes. This was done to prevent a subsequent run from destroying interface data that has not been fully processed. The new error message sent to QSYSOPR is: "Error running TMT-TL2000 AP Interface. Please contact TMW Support at [email protected]"
N
2012.10
833 - TMT Miscellaneous Menu TMW889 06/29/2012 #2587
New Enhancement 2587 We added a new option to the Miscellaneous Menu that allows you to access the Stored Procedures Master listing. Option 10-Stored Procedure Master will allow the user to Display, Activate, and Inactivate Stored Procedures. In version 2012.10, Stored Procedures for Results Now are included. They are defaulted to 'Inactive' status. If you have the Results Now Module in use, you will need to set the Results Now Stored Procedures you use to 'Active' status after the Upgrade has completed. If you do not have the Results Now Module in use, then no action is necessary. The conversion will set the sub-option rights for MS 833, 8, & 10 to ‘N’ for all Users. Be sure to review Security Rights for Menu Selection 833. We added new sub-option 10, and combined the previous sub-option 8 & 9 for the ATA Import into one sub-option (08). As a result, we felt it was necessary to revoke authority for these options so that you could decide which users should have access to these sub-options.
2012.10
835 - User Profile Master TMT890S 04/16/2012 #2969
We added a new feature for Vendor Security setup. Now the Security ID(*) field has a wildcard function for vendor security. This feature will allow you to setup Vendor Security for multiple vendors using the wildcard value '*' instead of requiring an exact match on the vendor code. The wildcard will match on the characters prior to the wildcard character (*). This will, for example, allow a user to have access to all vendors beginning with "12". This feature saves time when setting up multiple vendors, and does not require each individual vendor to be setup for the user.
2012.40
836 - Menu Security Master TMT890AT 09/11/2013 #3163
We changed the program to prevent the Module Access window for the Web Edition Module from being displayed when User Security Rights are changed. The program was not checking the Web status record to determine if it was Inactive. If the Web Status record is 'Active', and the Web Edition Module "Access Denied" window is displayed, the program will allow a User with the proper Security Access to use Menu Selection 833 - TMT Miscellaneous Menu, option 11 - PUI Configuration to change the status to 'Inactive'. This will prevent the "Access Denied" window from being displayed.
71
2012.31
838 - Firmware Master TMT838M 06/24/2013 #3093
We changed the Description of Firmware 60202 - 'BC Zebra Printer Label Size:1=1x4;2=2x4' to 'BC Printer Label Size:1=1x4;2=2x4'. Barcode label size 1x4 will work with a Datamax or Zebra label printer, label size 2x4 will only work with a Zebra label printer. We also changed the Firmware Maintenance program to process Firmware changes that could result in conflicts within the new database definition using partial Shop Firmware sets, introduced in Version 2010.40. When the new Firmware database definition was introduced, we no longer needed a full and complete Firmware set for each Shop Firmware set a user created. When a Shop Firmware is set differently than the Company Firmware, the program only adds the Shop Firmware that are different than the Company Firmware to the database file, (TMTFIRMW). This allowed the possibility for a limited number of Firmware to exist in conflict with other Firmware. Specifically the BC Printer Type and BC Printer Label Size Firmware could end up in conflict if different printer types and label sizes were desired for the Company and Shop Firmware sets. We updated the subroutine 'EDITFIRMX' to process a COMPANY F/W change differently than a SHOP F/W change.
For a COMPANY F/W change - the conflict protection across Company Firmware values is still in use. For conflicts with Shop Firmware values, the edit does not apply when both Firmware exist at the Shop level. It only applies when the Firmware changed does not exist at the Shop level.
For a SHOP F/W change - the conflict protection is only restricted to the current Shop or Company Firmware set you are working with. If the cross referenced Firmware exists for the Shop, then the edit is applied there. If no Shop Firmware exists, the edit is applied against the Company Firmware.
Changes in the Firmware Deletion program - (TMT838D - All values) Updated EDITFIRMX as related to Firmware deletes
For numeric Shop Firmware values, the program now prevents a delete action if it will expose a conflict with a Company Firmware value.
If the delete action is being performed for a Shop Firmware value, then the only relevant conflict edit is the Company Firmware value.
o Other Shop Firmware values are not considered for a conflict comparison.
N
2012.10
843 - Company Name Master TMT871 08/13/2012 #2587 New Enhancement 2587 We added a new Command Key (F13), to allow the user to display the current version, upgrade date, and other information required to obtain a Security Code. We also modified the program so that Command Key "F10=Enter Security Code" and "F11=Module Security" do not display or function if the user does not have Rights='Y' for these two command keys.
72
2012.30
843 - Company Name Master TMT871 04/03/2013 #2421
The Security Code has been expanded to 44 characters. Other changes:
We changed the length and format of the Security Code.
The Security Code format has been changed to ONLY use letters (upper case & lower case), and numbers, with no spaces or special characters, in the code.
Changed Security Code "use and entry" from 3 to 7 days.
Now we can issue a new Security Code up to 7 days in advance of the date you plan to enter it into the system.
Set expiration interval for DEMO systems to 30 days.
Set expiration interval for TEST systems to 365 days.
Changed DEMO & TEST Security Code expiration warning from 30 to 7 days.
Seven days prior to expiration of the Security Code, (in DEMO or TEST mode only), a message is displayed that includes the number of days left until the Security Code will expire.
We added three new fields to the System Info window, - Data Library, LPAR Number, and Model Type.
The System Info window can be displayed using Command Key F13=System Info. This feature will allow you to display the information needed for Support to create a Security Code for the system.
The System Info window can also be accessed from within the Security Code entry window using F13=System Information, or by using a command line and command: 'CALL TMTCINFO'. To display the System Information window prior to the upgrade to V2012, a user can perform these steps to display the System Information window to obtain the Data Library, serial Number, Partition number etc. prior to the upgrade completion to obtain a Security Code.
1) You must have the V2012 libraries TMTDATA and TMTPGMS in your library list.
You do not need to complete the upgrade, you only need to restore the Version Upgrade objects, and enter those names in your library list if desired. Use the Version Upgrade Installation Instructions to restore the libraries.
2) Use Command CALL TMTCINFO after the V2012 libraries have been restored to display the "System Information" window.
3) This same "System Information" window can be displayed in Menu Selection 843 - Company Name Master, using new Command Key F13=System Information if you wait until after the upgrade has completed to request the Security Code.
4) The information displayed in the "System Information" window is needed for TMW to generate a Security Code for Version 2012.
If you use multiple data libraries, you must specify the allocation of units for each data library when you request a Security Code from Support.
The total number of all units, (excludes Reports Only status), for all data libraries cannot exceed the total number of units you are licensed for.
Data libraries are grouped into categories of Production, High Availability/Disaster Recovery, and Test.
The accumulation of the total number of units applies to all Production libraries as a group.
The accumulation of the total number of units applies to all High Availability/Disaster Recovery libraries as a group.
There is no limit to the total number of units in Test libraries.
We made changes to programs used in the FTP process to capture errors caused by record or file locks to the job so that they will not end abnormally when data is returned.
CLFTPCOQ will attempt three times to create the FTP INPUT & OUTPUT command stream file in QTEMP before it will end the job with an error.
TMT990FTPP was changed to monitor processing of the FTP OUTPUT log file so it’ll not end abnormally while trying to create the QPRINT FTP log and the OUTPUT log file is empty.
TMT990FTPS was changed to monitor processing of the FTP OUTPUT log file so it’ll not end abnormally when the OUTPUT log file is empty –now it’ll return a status of 1 (Error) so the job can start re-try processing.
We changed the Service Program to use PGMSEQ instead of PRFSEQ when getting the "From" address & user name for a program. This was done to prevent the user address from being truncated after the (@) sign in an email address, causing errors when forwarding or replying to messages.
N
2012.10
847 - Import/Export Master TMTDA001 and TMTDA005 10/25/2012 #3038
We corrected the program to display results when Alert program "OTR Repair Over $ Amount", program TMTDA001 is used for the Dawg®. In the previous version, when "Include History" was set to 'No' and the RO Status parameter was set to "blank", the program was not displaying any results, even if there were Repair Orders that fit the condition of the other selections; Shop, Unit, Vendor, System Code etc. We added a new parameter for the "Utilization Errors" Dawg® Alert, program TMTDA005. The new parameter "Include ZERO Ut" will allow units with ZERO utilization to be included in the "Utilization Errors" report. This parameter can be set to 'Y' to include units with zero utilization, or can be set to 'N' to exclude units with zero utilization.
The Dawg for IBM i Alert: TMTDA001 (OTR Repair Over $ Amount) Description: OTR Repairs over $ Amount Purpose: Report ORO charges over a user defined dollar value passed in the 'Amount' parameter. File Name: User defined (suggested name: TMTDF001) Library: User defined (suggested library: QTEMP) Parameters:
Shop 6,0
Unit 12A
Vendor 6A
System 6A
RFR 4A
Amount 11,2
Include History 1 LOGICAL (single value)
Exclude Status 2A
Order By: Shop, RO & Section Primary File: ROHEAD Joined Files: ROBODY Report Fields: Shop, RONumber, Section, Vendor, Unit, Status, System, RFR, Amount, OpenDate and
The Dawg for IBM i Alert: TMTDA002 (Road Calls Open Over # Days) Description: Road Calls Open Over # Days Purpose: Report calls open over a number of days passed in Days parameter. File Name: User defined (suggested name: TMTDF002). Library: User defined (suggested library: QTEMP). Parameters:
Shop 6,0
Unit 12A
Supplier 6A
User Status 4A
Days 4,0
Order By: Call, Unit & RO. Primary File: CALLMSTR. Joined Files: None. Report Fields: Call, Unit, Date, User, Status, Supplier, Type, Order & Shop.
The Dawg for IBM i Alert: TMTDA003 (ROs Closed, Not Processed to History, Over # Days) Program: TMTDA003 Description: ROs Closed, Not Processed to History, Over # Days Purpose: report ROs that have been closed but not cannot be processed by the EOD process due to
one of the following reasons:
Closed/Iv ISystem ?) before
Closed/Tm Time card(s) not posted, active, paused or work assigned (not started)
Closed/$ Waiting on COMDATA
Closed The program will check FW 84105 (Use Invoice System ?)
File Name: user defined (suggested name: TMTDF003) Library: user defined (suggested library: QTEMP) Parameters:
Shop 6,0
Unit 12A
Vendor 6A
Payment Method 10A
Days 4,0
Include IP 1 LOGICAL (single value)
Order By: Shop, RO & Section Primary File: ROHEAD Joined Files: None Report fields: Shop, RONumber, Call, Vendor, Unit, ROType, ROStatus, PayType, PayNumber,
COMDATA (*), PONumber, Amount, OpenDate, CloseDate & CloseUser (lists Last Changed User if CloseUser is blank). Comdata:
N Payment Method is not blank, no COMDATA records exist
Y Payment Method is not blank, COMDATA records found
^ status retrieved from the VTSTS field in file CDVTTRN
The Dawg for IBM i Alert: TMTDA004 (Invoice Change Report) Program: TMTDA004 Description: Invoice Change Report Purpose: report calls open over a number of days passed in Days parameter. File Name: user defined (suggested name: TMTDF004) Library: user defined (suggested library: QTEMP) Parameters:
Shop 6,0 Repair Shop
Unit 12A Unit Number
Customer 10A Customer ID Number
Hours 5,0 Hours to look back (defaults to 1 hour)
NonComp Units?
1L Include Non-Company Units? -> LOGICAL/Single value field requires Y or N (default is Y)
Order By: Call, Unit & RO. Primary File: INVHEAD. Joined files: INVCHGD (ONLY Part & Labor records), ROHEAD Selections:
Repair invoices Closed and/or Printed Closed Date [& Time] are within the hour range passed in the Hours parameter
The Dawg for IBM i Alert: TMTDA005 (Utilization Errors) Program: TMTDA005 Description: Utilization Errors Purpose: Report utilization errors for a period or range of periods. The report will always report
negative utilization in a period, even if the “Over Util Amt.” parameter has a value greater than zero. File Name: user defined (suggested name: TMTDF005) Library: user defined (suggested library: QTEMP) Parameters:
Unit 12 Unit
Period 4,0 Periods to look back (dft is 0 –current)
Over Util Amt. 7,0 Report on negative utilization and amount over the value entered
Domicile 6,0
Cost Center 6A
Fleet 4A
Activity 4A
Make 6A
Model 10A
Equipment Type 10A
Year 4,0 Year of unit manufacture
Order By: Unit, Year & Period. Primary File: UTILZAMT. Joined Files: VHCLMSTR. Report Fields: Unit, Desc, Year, Period, UtilAmt, DomShop, CostCtr, Fleet, Activity, Make, Model,
EquipType, MfgYear.
2012.20
847 - Import/Export Master TMT 11/01/2012 #2958
We made a change for the Decisiv Import program to update the Repair Order "Up Date" with the "Closed" date from the import file, if the Date is included in the file. If the “Closed Date” is not included in the import file, the current date will be used for the “Up Date”.
We changed the program so that it will parse the Up Date/Time only if the repair order being sent by Decisiv is closed. This change will allow Version 2012 to update the Repair Order status using the "Closed" date in the import file. If you import Repair Orders from Decisiv, you will need to make a change in the Cross-Reference Field Setup. After you upgrade to Version 2012, and before any Repair Orders are imported from Decisiv, you will need to use Menu Selection 847, and navigate to Repair Order Import for Decisiv. In the "Import/Export Profile Listing", use option 6=Fields for the Decisiv Profile, and locate the "Repair Status" Field, use option 2=Cross-Reference, and verify if you have a Cross-Reference defined. If you have defined a TMT Value of 'CL' for the Cross-Reference Value of 'CLOSED', replace the TMT Value with 'CN'. Note: Failure to make this change will cause the RO's imported from Decisiv to be created with an RO
Status of 'Not Found' instead of 'Closed'. This will require the RO Status to be changed in the database file - there is no user solution to correct this condition. If the Decisive import file does not contain a Closed Date for an RO, the current date will used instead.
We made several improvements to the Dawg® regarding email notifications. 1) In the Scheduler Record Master, we added a prompt for “Status Notification” below “Job Name”.
Possible values for "Sts Notification are; (Y)es (N)o (E)rror a. When set to 'Y';
I. And, "Job Message Queue" is set to '*USRPRF', a completion message will be sent to the "Scheduled User" and QSYSOPR
II. And, "Job Message Queue" is set to 'QSYSOPR', a completion message will only be sent to QSYSOPR
b. When set to 'N'; I. A completion message is not sent to the "Scheduled User' or the "Job Message Queue"
user c. When set to 'E';
I. And, "Job Message Queue" is set to '*USRPRF', a completion message will only be sent to the "Scheduled User"
II. And, "Job Message Queue" is set to 'QSYSOPR', a completion message will only be sent to QSYSOPR
This will allow the user to determine if the program should send an IBM i message to the Scheduled User when the job completes successfully, and only send a message to the System Operator, (QSYSOPR), when the job fails to run or there is an error message. (This prevents the System Operator from receiving messages when there are no errors). 2) If there are no errors, and the "Status Notification" is set to 'Y', and email message will be sent to the "Scheduled User";
No errors Dawg {dawg name} eMail sent.
3) One of the notification error messages displayed in the list below will be sent if the process fails and the "Status Notification" is set to 'Y' or 'E';
CPF8A82 Dawg {dawg name} eMail failed. Document not found in the folder specified
We changed the program to allow for descriptions in the System Code field, (CompCode), for Order Section, (OrderSec) and Order Line, (OrderLine) nodes in the XML import for Repair Orders. This change requires a System Code Cross-Reference to be setup in the Field Cross-Reference Setup for the Import Profile. The setup would need to include the text Description being passed in on the XML import file to Cross-Reference to the proper TMT System Code. This will allow the Repair Order sections to be created with valid TMT System Codes.
New Enhancement 2960 We created a Web Service that will allow you to import ECM Meters if you are using the PeopleNet PerformX engine monitoring system. Version 2012.20 will add the basic PeopleNet Import/Export setup needed to configure the Import/Export so you can begin importing ECM meters if you are using PeopleNet and the PerformX system. (Import/Export Type - "PeopleNet", Transmission Record, Scheduler Record, Fields, and Properties). This new feature will require you to have the "Mobile Comm - PeopleNet" and "Fuel Import" Module License Codes. (To verify if these two codes are Active, use Menu Selection 843 - Company Name Master and F11=Module Security). You will also need to request the "PerformX Setup Instructions" document from TMW AMS - IBM i Customer Support Department to assist you with the PerformX setup using your PeopleNet account credentials.
We changed the program to prevent an Email from being sent for the DAWG® Alerts when the file is missing or empty and the status notification parameter is set to 'No' in the "Scheduler Record Master".
N
2012.30
847 - Import/Export Master
New Enhancement 3060
Qualcomm VIR Messages Overview
This new Qualcomm VIR Message module will make a Web Service request to Qualcomm to return Vehicle Inspection Requests, (VIR's), that have been queued since the last request. The VIR's are returned in an xml file which will be processed and VIR's will be added to the "Invoice Transfer Header" file, (ITFRHEAD). Program TMT991IR will be called to create the Inspection Tickets for you in Menu Selection 165 – Inspection Tickets. This new program requires your IBM i to be at or above release V6R1M0.
Changes made for both the PeopleNet and Qualcomm eDVIR Import:
Qualcomm VIR ID & PeopleNet MSN are now being stored in File: ITFRHEAD Field: THCMT (used to be in Field: THINV#).
Added logic to determine Inspection Map based on new “Inspection Type” property instead of form ID (Qualcomm does not use Forms).
Added a modification to fix %subst() error on TBCMT when driver enters a blank space for defect Remark.
Added logic to return PeopleNet MSN and Qualcomm VIR ID back to calling program via data structure field: @@msg#.
Updated logic to verify that all labor records are complete, and to use the mechanic from the last labor record.
81
N
2012.30
847 - Import/Export Master
New Enhancement 3060 Qualcomm VIR Mechanic Ack
Overview
This program selects the Mechanic Acknowledgements created since the last Web Service transmission and calls Qualcomm’s Update VIR Web Service to transmit the response back to the Qualcomm unit when repairs have been completed, and the Repair Order has been closed for the eDVIR’s that were reported.
We modified the Repair Order XML Import programs to extract Part Position data for the PART OrderLine nodes. This change will allow RO's you import from the vendors you use to send the Part Positions for parts. Programs TMT991XI & TMT991XP have been changed to look for an OrderLineAct node attached to an OrderLine node with PART in the <LineType> field. If 'PART' is found, the programs will:
Look for POSITION in the <CodeType> field. If found:
extract value from the <Code> field
extract value from the <Qty> field We also added a new file to store the Part Positions for imported RO's - ITFRPTPS.
New file: ITFRPTPS Invoice Transfer Detail Line Positions
Field Name Description
TPID# ID number assigned to the ITFRHEAD record (THID#) when the invoice is imported from the vendor. This same ID is used to link to the body (TBID#), line and [now] position records.
We made several changes to the RO Import program - TMT991.
Changed TMT991 to put the ROID# value in the $@BRND field for the ADD exit, in the EXITDATA file.
Changed the RO Status to 'ER' (Error), and issue “*** Invalid Up Time” on the log report if the Repair Order Down Date and Up Date are equal and the RO Up Time is less than the RO Down Time.
Changed the program to set the RO to 'ER' status and issue “*** Invalid UP Date” if the RO Up Date is less than the RO Down Date, if ITFRHEAD/THSTAT is not set to 'OP'.
Changed TMT991 to leave ITFRLINE/TLQTY as 0 if that's what the vendor sent.
Changed TMT991 to set ITFRLINE/TLAMT to 0 to mimic the "OLD" way the import worked.
Correct parameter name when executing routine CHKWRNT for OEM and AFTER MARKET (Part) warranty.
Created new logical file "LITFRHD3" over file ITFRHEAD by THROID# - (ROID Number). o Logical file LITFRHD3 over ITFRHEAD o Key field: THROID# o Select: THROID <> 0
Set Repair Order header "Completed By" (ROHEAD/ROCMBY) to blank.
Moved the BASE RULE edit so that it follows the WRITE/UPDATE to ROHEAD. The Repair Order header record is needed to perform the BASE RULE edit.
Corrected half-adjust error calculation: the OverFlow function was removing the fraction from Part quantity without recalculating the item cost.
o If a Part Quantity is sent in the Import file by the vendor, the program will calculate the total extended cost, then subtract the fraction amount and divide by the total cost to obtain the item cost.
o This may result in an item cost appearing on the RO part line at a greater cost than the Vendor invoice, however the total amount will match.
o The item amount can be verified in file ITFRLINE. The ROID# will be needed to find the records in file ITFRLINE.
Corrected the half-adjust for the Labor calculation also.
PUI User & Security Updates o User authority from MS 836 is not updating the PUI authority files. o Update process takes up to 15 minutes and almost 50% of system resources
TMTTPWDA o Added MNUAID (from TMTMENU) & USAID (from TMTUSPRF) on the TMT890ATCU
call. o Ignore update when selection is in TMTPSSWD but not in TMTMENU (orphaned
records).
TMT890ATCU o Change ATAUTHP from Output an Update (w/Add) file. o Replaced SQL UPDATE to ATAUTHP with CHAIN and UPDATE. o Added MNUAID (from TMTMENU) & USAID (from TMTUSPRF) to the *entry
parameter list with *NOPASS switch. o When called by trigger (*entry parms passed):
Ignore the FETCH if MNUAID > 0 and MNUAID <> ANITEM (from ATNAVP). Use USAID to SETLL and READE on ATUSERSP so only records for the
We changed the program to prevent an error message and allow the Repair Order import to continue running when a Repair Order section comment exceeds the limit of 7,500 characters for RO comments per section. If an RO is imported with more than 7,500 characters, (about 125 lines), the program will no longer end in error. Any comments that exceed the 7,500 character limit are ignored. The extra characters will not be included in the section comments.
We corrected an issue with node processing caused when a vendor sends incomplete or partial XML nodes. The program did not exit processing the node it was on when a new [child] node began.
We changed the Repair Order Import program to use Firmware "ORO Default Part & Labor Date to Current" - added in Version 2012.10.
If the XML Import file does not contain a charge date value in the <Chg Date> node, the RO Down Date will be defaulted for the Part or Labor charge date.
OR If Firmware "RO Default Part & Labor Date to Current" = 'No' and the Part or Labor line source (ROLINE/RLSRC) = 'S', then use the RO Down Date. OR If Firmware "ORO Default Part & Labor Date to Current" = 'No' and the Part or Labor line source (ROLINE/RLSRC) = 'V', then use the RO Down Date.
If Firmware "RO Default Part & Labor Date to Current" or "ORO Default Part & Labor Date to Current" = 'Yes', then the transaction date in the <ChgDate> Node is used.
The current calendar date is not used for imported ORO's because the imported RO may have an Up Date that is less than the current date.
We updated the Module Security Program for the Qualcomm VIR Import/Export. If the Qualcomm VIR Module is used without a current Module Code, an error message will be displayed alerting the User that the Module Code is no longer active.
We changed the program to prevent it from removing spaces from the Parameter strings, (the data entered in the "Values" field). In previous versions, if a valid value contained a space, the program was removing the space when the report was run. Values that should contain spaces were not included in the report since the program was removing the space. When you are using the Dawgs with Value fields that allow multiple values, each value should be separated by a comma and a space. Example: If a Dawg includes a Value field for "Unit", multiple Units should be entered like this; Unit One, Unit Two, Unit Three
We increased the UserID and Password field length from 15 characters to 20 characters for the Qualcomm import & export profiles.
2012.10
851 - Exits Master TMT840U 06/12/2012 #2587
The program calls for the TL2000 and Innovative Accounting Interface programs are now called from within the End of Day program, (TMT840U). The Exit for TMT840U - "EXT" will be inactivated during the upgrade for 2012.10.
We changed the program to update the meter for Hours and Kilometer based Units in addition to Miles based Units when the PerformX ECM Meter Import is used. We changed the Meter Type description to display "ECM Import" instead of "Fuel Import" in the Unit Meter History Listing screen to identify meters imported from an ECM Meter Import. We accomplished this by changing the value written in the Meter History file (METERHST/MHPGM). The new value used to indicate an ECM Meter Import is "TMT991ECMM". The ECM Meter Import date and time is formatted in Greenwich Mean Time. (GMT) The Timestamp will be converted to your local time zone when the import runs. This may result in a Meter Starting and Ending Date being imported as a different date than the date in the XML file. Example: The Meter Ending Timestamp in the XML file is 06/01/2013 00:30:00. If your local time is using Daylight Savings Time for this date, and you are located in the Eastern Time Zone you are -5 hours from GMT, during Daylight Savings Time this changes to -4 to GMT. The Meter Import Date will be changed to 05/31/2013 since the Time in this example is thirty minutes past midnight, and when four hours is subtracted from 06/01/2013 00:30:00 that changes the date to the previous date.
2012.10
851 - Exits Master TMT991 06/13/2012 #3005
We added a new exit for program "TMT991 - Invoice Transfer Program" that runs in batch for an Order Import, after the Repair Order header record is written in file ROHEAD . Example: You could use this exit to populate fields in the Repair Order header file with other information you may want to have available in the RO.
85
Results Now
2012.20 Results Now
We made several improvements for Results Now Metrics listed below. PM Due Compliance
Replaced the parm named "Only DEPENDENT PMS" with "Select PM TYPE".
If you enter (blank), All PMs will be displayed, (Dependent and Independent)
You may enter a 'D' to only display Dependent PMs
You may enter an 'I' to only display Independent PMs PM Due Compliance Percentage
Changed the Numerator to return a PM count instead of a percentage.
Changed the Denominator to return the total PMs defined that fit the parameter selection criteria.
Replaced the parm named "Only DEPENDENT PMS" with "Select PM TYPE.
If you enter (blank), All PMs will be displayed, (Dependent and Independent)
You may enter a 'D' to only display Dependent PMs
You may enter an 'I' to only display Independent PMs RFR Cost per Utilization
Changed the Numerator to return the Total Cost.
Changed the Denominator to return the Total Utilization.
Changed the parameter "Only METER TYPE" from VARCHAR(255) to CHAR(4)
The default parameter value is '0001' if a blank or NULL (blank) is passed
This is a single entry parameter now, multiple Utilization Types are no longer allowed
Select ONLY valid Units found in the Unit Master file, (VHCLMSTR).
match value passed in parameter "Only METER TYPE" to "VEHUTB"
Select ONLY units with utilization and/or costs in the given date range
Replaced call to TMTUTILS with TMTUTIL
Now the metric will report utilization from the Meter History file, (METERHST) based on FROM & TO date range
The utilization calculations have been replaced from UTILZAMT & MULTUTIL
If the date range includes less than a full period, the program will use the Meter History file to determine the utilization amount to report, beginning on the "FROM" date instead of using the utilization amount for the entire period of the "FROM date.
Shop Labor Hours
Removed TMTCODES from the primary cursor selection and now use a separate SELECT statement, if the user wants detail data returned, to get the PM System description for the report.
Replaced parameter "Include INDIRECT HOURS" with "Labor Type"
If you enter (blank), records for all Labor Types will be displayed, (Shop and Indirect)
You may enter an 'S' to display only Shop Labor
You may enter an 'I' to display only Indirect Labor Shop Report Card
Changed Denominator to show a record count, instead of a Date Range.
2012.20
Results Now - TMT121U & TMT137F 02/11/2013 #3073
We changed the program for two Results Now programs - "RESNOW PMDUE COMPLIANCE" and "RESNOW PMDUE COMPLIANCE PERCENTAGE" to use the value from the PM Scheduler file, (PMSCHEDH), and the Due Utilization field, (DUEUTL) instead of the User Defined field, (UD0111) field when reporting on utilization that caused the PM to become Due. A conversion program will run with the Upgrade to this version to move the data in PMSCHEDH/UD0111 to PMSCHEDH/DUEUTL.
86
New Firmware
Reminder: Beginning with version 2010.40 it is no longer necessary to use Command Key “F10=Add New Values to Shop” if you use Shop Firmware, and you want to set different values for the new Firmware. This command key has been removed, and new Firmware values will automatically be added at the Company Level. Shop Firmware will use the Company value unless they are changed by a user with proper security.
N
2012.10
838 - Firmware Master TMT838i 06/07/2012 #2587
New Enhancement 2587 Added a new Firmware 11007 - "RO Display Header First on Inquiry" on Firmware page 1.
This Firmware allows you to choose if the Repair Order header or Repair Order sections will be displayed first when viewing a Repair Order using Inquiry mode from any Menu Selection that allows RO inquiry. If set to 'Yes' - When Repair Orders are viewed using Inquiry mode from any Menu Selection that allows
RO Inquiry, the Repair Order header screen will be displayed first, followed by the Shop RO Inquiry screen, (RO Sections List). If set to 'No' - When Repair Orders are viewed using Inquiry mode from any Menu Selection that allows
RO Inquiry, the Shop RO Inquiry screen, (RO Sections List), will be displayed first. A command key on the Shop RO Inquiry screen will allow the user to display the Repair Order header screen.
N
2012.40
838 - Firmware Master TMT838I 09/11/2013 #2909
New Enhancement 2909 Added two new User Level Firmware 11038 - "ORO Chgs - Default Part Quantity" and 11039 "RO Chgs - Default Part Quantity" both on Firmware page 1.
These new Firmware will allow you to set a default Part Quantity, by User, for both Standard Shop Repair Orders and Vendor Repair Orders. When the screen value for the Part Quantity is zero, the program will insert the appropriate Firmware value as determined by the Part Source. "ORO Chgs - Default Part Quantity"
Use this User Level Firmware to set the default Part Quantity for a vendor part when the Part Source is 'V' - Vendor. "RO Chgs - Default Part Quantity"
Use this User Level Firmware to set the default Part Quantity for a part when the Part Source is 'S' - Shop.
N
2012.40
838 - Firmware Master TMT838I 09/11/2013 #2909
New Enhancement 2909 Added a new User Level Firmware 60083 – "Maintain Serial Number Location" on Firmware page 6.
This new Firmware will allow you choose whether or not the Location of a Serialized part can be changed by the User. If set to ‘Yes’ – The User is allowed to maintain the Location (Shop Inventory or Unit part is installed on)
for Serialized parts. If set to ‘No’ – The Location field on the Serialized Part Number is protected from changes, and is
maintained by system as the part is purchased for inventory, and then charged out to a Repair Order or Indirect Charges.
87
N
2012.20
838 - Firmware Master TMT838I 01/15/2013 #3083
New Enhancement 3083 Added new Firmware 11048 - "Retain Comments on RO when Creating WP" on Firmware page 1. This
new Firmware allows you to determine whether Campaign & Work Pending comments should be retained on the Repair Order when an RO is being closed, and you need to create a Work Pending for sections without charges. Settings are: 1 = Both
Campaign Sections - Campaign is removed from RO Section, Campaign comments are retained on RO. Campaign is added to Work Pending with Comments. Non-Campaign sections - Comments are retained on RO Section. Work Pending section is
created with the comments from the RO Section. 2 = Campaign <== Default value
Campaign Sections - Campaign is removed from the RO Section, Campaign comments are retained on RO. Campaign is added to Work Pending with Comments. Non-Campaign sections - Comments are removed from RO Section. Work Pending section is created with the comments from the RO Section.
3 = None Campaign Sections - Campaign and Campaign comments are removed from the RO Section.
Campaign is added to Work Pending with Comments. Non-Campaign sections - Comments are removed from the RO Section. Work Pending section is created with the comments from the RO Section.
4 = Work Pending
Campaign Sections - Campaign and Campaign comments are removed from the RO Section. Campaign is added to Work Pending with Comments. Non-Campaign sections - Comments are retained on the RO Section. Work Pending section is created with the comments from the RO Section.
Note: Option 2 = Campaign is the Default Value, and this option will allow the program to function like it has in previous versions.
88
N
2012.10
838 - Firmware Master TMT838i 10/24/2012 #3041
New Enhancement 3041 We changed the description for Firmware 12200 - from "RO Dft Part & Labor Dt to Current" to "RO Default Part & Labor Date to Current" on page 1.
This Firmware allows you to select the default part and labor date when the Source Type is 'S' (Stock/Shop) or 'N' (*NON-STOCK). If set to 'Yes' - The labor entry date will default to the current date (or job date) if the labor charges are
added from the "Shop RO Charges" screen, (TMT115C) and the Source Type is 'S' (Stock/Shop) or 'N' (*NON-STOCK). If you use Source Type 'V' (Vendor), on a Standard RO, then Firmware 12201 - "ORO Dft Part & Labor Dt to Current" is used to determine the default charge date. Labor charges added using the Mechanic Workstation will default the labor date based on this Firmware. Charges added using the Time Card Master in Menu Selection 1110, (TMT134M), will require the user to use a labor charge date that will fit between the Time Card start and end dates. If set to 'No' - All labor charge dates will default to the RO Down Date.
NOTE: This Firmware must be set to 'No' if Firmware "Allow Mechanic to Force Clock Out" is set to
'Yes'. Both Firmware may be set to 'No' at the same time, but they cannot both be set to 'Yes' at the same time. This is necessary to prevent a user from adding labor charge records to the ROLINE file when the F20=Force Out option is used after the desired labor charge date. Example: The Mechanic Workstation Force Out option is used after the previous period end date for a Time Card where work was performed in the previous period. The labor dates written from the Force Out procedure use the current date. When closing the RO, you are required to use an Up Date that is equal to or greater than the labor charge dates for the RO. If the labor charge date from the Force Out procedure is greater than the previous period end date, you would be forced to use an Up Date for the next period. We also added a new Firmware 12201 - "ORO Default Part & Labor Date to Current" on Firmware
page 1. This Firmware allows you to choose the default part and labor date when the Source Type is ‘V’ (Vendor). If set to 'Yes' - The labor entry date will default to the current date (or job date) if the labor charges are
added from the "Shop RO Charges" screen, (TMT115C) and the Source Type is 'V' (Vendor), on a Vendor RO.
If you use Source Type 'S' (Stock/Shop) or 'N' (*NON-STOCK) on a Vendor RO, then Firmware 12200 - "RO Default Part & Labor Date to Current" is used to determine the default charge date.
If set to 'No' - All labor charge dates will default to the ORO Down Date.
89
N
2012.10
838 - Firmware Master TMT838I 04/02/2012 #2984
New Enhancement 2984 Added new Firmware 60202 - "BC Zebra Printer Label Size:1=1x4;2=2x4" on Firmware page 8.
This Firmware allows you to choose between 1" x 4" labels and 2" x 4" labels when using the Zebra GX420t barcode label printer. Both barcode and standard labels (text only), may be produced on either size label. 1=1x4 - Use this option to create thermal bar code and thermal standard labels using the Datamax DMX-
I-4208 or Zebra GX420t barcode printer. Labels are 1" (h) x 4" (w). 2=2x4 - Use this option to create thermal bar code and thermal standard labels using the Zebra GX420t
barcode printer. Labels are 2" (h) x 4" (w). NOTE: This Firmware must be set to '2' when Firmware "BC Printer Type:0=None;1=Datamax;2=Zebra"
is set to '2'. Both Firmware may also be set to '1' at the same time. Two inch high labels are not allowed with the Datamax barcode printer.
N
2012.10
838 - Firmware Master TMT838I 04/18/2012 #2956
New Enhancement 2956 Added new Firmware 84112 - "Use RO Close By for Export Created By" on Firmware page 12.
This Firmware allows you to control the "created by user" ID displayed on REPAIR transactions. If set to 'Yes' - Accounting Export Order Types of REPAIR-PART, REPAIR-PART-V, REPAIR-LABOR, or
REPAIR-LABOR-V will display the USER ID that closed the Repair Order in the Accounting Export record instead of the User ID that is running the EOD job. The USER ID from the Repair Order is contained in the Closed By field, and stored in file ROHEAD/ROUPBY. This USER ID will be displayed in the Accounting Export field; "created by user", and stored in file ACTXTRAN/XTCRTU. If set to 'No' - The USER ID that is running the EOD job will be displayed in the Accounting Export record
as the "created by user". Typically, for other types of transactions like INVOICE, PURCHASE, or FUEL the "created by user" is populated with the USER ID that is performing the act of closing the order.
90
N
2012.10
838 - Firmware Master TMT838I 05/25/2012 #2587
New Enhancement 2587 Added new Firmware 99108 - "InterCompany Account for Multi-Company" on Firmware page 91.
This Firmware causes the accounting export to check for the InterCompany Account setup in the Firmware value, and compares the Repair Shop Company to the Domicile Shop Company for REPAIR | STANDARD | PARTS and REPAIR | STANDARD | LABOR Rules and Subrules. It will allow credits and debits to be written to the General Ledger for each company when units domiciled in one company could be repaired in a shop for a different company. If the two companies are the same, the account setup in the InterCompany Account Firmware will be ignored for the Rule/Subrule found, when Accounting Export transactions are generated. If the two companies are different and the InterCompany Account exists for the Rule/Subrule found, the Accounting Export will create transactions for both companies. The debit and an intercompany credit will be created for the unit's domicile company. The credit and an intercompany debit will be created for the repair shop's company. Recommendation:
Enter an InterCompany account in this Firmware to activate this feature. This Firmware should be setup and used when the TL2000 interface is in use, multiple company General Ledgers are in use, and units Domiciled in one company may be repaired in a shop for a different company.
N
2012.10
838 - Firmware Master TMT838I 05/25/2012 #2587
New Enhancement 2587 Added new Firmware 99129 - "Use Company as Prefix on Vendor" on Firmware page 91.
In TL2000 a customer can set up multiple companies. Each company can have its own set of AP vendors. If set to 'Yes' - This Firmware will allow the TL2000 interface to use a unique vendor number in the
Supplier Master, (Menu Selection 630), to identify the vendors used by each company. The right-most digit of the company number will be added as a prefix on the vendor number in TMT. This Firmware in conjunction with using a Vendor Security wildcard(*) in Menu Selection 835 - User Profile Master, will allow the vendors to be secured for the users using each company's vendor numbers.
N
2012.20
838 - Firmware Master TMT838i 04/16/2013 #3114
New Enhancement 3114 Added new Firmware 96022 - "Mechanic Assign Work - Assigned Only" on Firmware page 11.
This Firmware allows you to choose if the Repair Order Work listing will only display Assigned Repair Order sections, or all Assigned and Unassigned Repair Orders, PM's, Shop Plans, and Work Pending for Employees that access the Repair Order Work listing to select and assign Repair Order sections. If set to 'Yes' - the Repair Order Work listing will ONLY display Assigned Repair Orders for the
Employees Primary Shop setup in the Employee Master in Menu Selection 220 - Employee Master. Users will not be allowed to select Repair Order section work using the Repair Order Work listing, unless the RO section is assigned to another Employee. Users will not be allowed to select Unassigned Repair Orders, PM's, Shop Plans, and Work Pending. Note: These conditions apply to both the Mechanic Workstation and Supervisor Workstation access to the Repair Order Work listing. If set to 'No' - the Repair Order Work listing will display all Assigned and Unassigned Repair Orders,
PM's, Shop Plans, and Work Pending for the Employees Primary Shop.
91
N
2012.40
838 - Firmware Master TMT838I 09/05/2013 #2493
New Enhancement 2493 Added two new Firmware 96031 – “Print RO Comments on Time Card?” and 96032 “Print Indirect Comments on Time Card?” both on Firmware page 11.
These new Firmware will allow you to choose if Indirect or Repair Order Comments should be printed on the Time Card. Print RO Comments on Time Card?
If set to 'Yes' - The RO Comments will print on the Time Card below the line containing the RO,
System and WAC. If set to 'No' - The RO Comments will not be printed on the Time Card.
Print Indirect Comments on Time Card?
If set to 'Yes' - The Indirect Comments will print on the Time Card below the Shop Number. If set to 'No' - The Indirect Comments will not be printed on the Time Card.
N
2012.41
838 - Firmware Master TMT838I 12/11/2013 #3020
New Enhancement 3020 - Web Edition Only Added a new Firmware 96033 – “List Mechanics in Web Edition” on Firmware page 11.
This Firmware allows you to choose if a list of Mechanics will be displayed in the Mechanic Workstation login screen, or only the Employee ID and Password fields. If set to 'Yes' - A list of all Mechanics will be displayed on the Mechanic Workstation login screen.
If the IBM i UserID is secured to a Shop, then only the Mechanics from that Shop will be displayed. If set to 'No' - Only the Employee ID and Password fields are displayed on the Mechanic Workstation
login screen. Note: This feature does not apply to the Standard Edition, and only applies to the Web Edition.
N
2012.41
838 - Firmware Master TMT838I 12/18/2013 #3204
New Enhancement 3204 We changed Firmware 60070 “Wty Box During Part Chgs” to “ORO - Prompt for VMRS Code on “V” lines”.
The default value for records added will be "Y" instead of "N".
If changing an existing record, set the new value opposite of current value.
If adding the Firmware, set the default value to 'Y'. If set to 'Yes' - Allows the User to prompt into the VMRS Code Listing from the Part Number field when
the "Source" is set to 'V' for Vendor parts. When a VMRS Code is NOT given, the program will assume the first nine characters of the Part Number is a VMRS Code, and attempt to validate a VMRS Number. The program will ignore the VMRS Code validation when the first nine characters are the same as a valid VMRS Code and default the matching VMRS Code into the VMRS Code field. If set to 'No' - Prompting for a VMRS Code is not allowed.
Note: This function is useful when warranty tracking on vendor supplied parts is an important issue.
92
Pur/Inv Menu
Purchasing
2012.10
1041 - Parts Requisitioning TMT1041M 04/02/2012 #2935
We changed the program to allow a Part Requisition that contains more than 999 part records. In previous versions, an error message was displayed if the Part Requisition list contained more than 999 records, and the user pressed Page Down.
2012.10
1041 - Parts Requisitioning TMT1041M 05/16/2012 #2918
We corrected an issue that only occurred when multiple users were in the Parts Requisitioning List at the same time for different Shops, and they were selecting parts with option "3=Order Part" to create a Purchase Order. In previous versions when this occurred, parts from the Parts Requisitioning lists of both Shops would be processed together and added to the same Purchase Order. Now, the program only processes the records matching the Shop the user is working with. Recommendation:
Until you can upgrade to version 2012.10 or higher, the only way to prevent this is to ensure multiple users are not attempting to select parts and create Purchase Orders at the same time.
2012.41
1041 - Parts Requisitioning TMT1041L 12/10/2013 #3065
We changed the program to exclude Indirect Parts when the Part Profile option is set to *NONE. When the Part Profile default value (*NONE) is selected, parts with a Bin Location of *INDIRECT, *NON-STOCK, and Inactive parts are excluded from the Parts Requisition. Parts with a Bin Location of *INDIRECT can be included in a Parts Requisition if a Part Profile is selected that includes *INDIRECT parts.
We changed the program to prevent an error ("Attempt to write duplicate record to file DSTMT1042; Record already exists in subfile for file in library"), when an invalid part was entered, and the user prompted into the Part Master using F4 to select a valid part number, then pressed page down after returning to the Part Transfer Request list.
We corrected the program to prevent an error message that was displayed if the "Part Transfer Pick List" report was printed, and no parts existed for the report. Now a message is displayed alerting the user that no parts or data exist for the report - "No data found to display".
We changed the program to prevent an error that was issued when the Receiving Shop has zero Quantity on Hand for a part being transferred.
N
2012.10
1050 - Purchase Orders TMT470P 08/17/2012 #3016
We changed the program to allow the "Reprint FPO" option to print the Fuel Purchase Order for a Fuel PO with any status, and added a new Command Key - "F21=Print" that will also allow you to print the Fuel PO when reviewing the Fuel PO detail. In previous versions, option 43=Reprint FPO was not valid for a Fuel PO when the status was 'CN' or 'CL'.
93
2012.10
1050 - Purchase Orders TMT1050 06/11/2012 #2964
We corrected the program to prevent a calculation error when a credit PO exists for a part, and then is later deleted. In previous versions, when a negative quantity on order amount was cleared or deleted on a PO, the "Quantity on Order" field was reset to zero instead of being recalculated with the new Quantity on Order amount.
We changed the program to ensure the Supplier Number on the Purchase Order Header remains in a "protected" state when a user views the PO in View Mode. In previous versions, when a user viewed the PO Header using option 5=View, then used F8 to display the PO Header, exit then display the PO Header again - the Supplier was displayed in Change Mode instead of View Mode like it should be.
2012.10
1050 - Purchase Orders TMT1050 07/16/2012 #2113
We changed the command keys for the Purchase Order Inquiry Detail window. We removed F12=Cancel, (used to exit the window in previous versions), and replaced it with F3=Exit. You may also press the ENTER key to exit the window. We added F16=Part Info to display the Part Master screen in Inquiry Mode for part selected. (Requires Security Access to Menu Selection 600 - Parts Master).
2012.10
1050 - Purchase Orders TMT1050 07/24/2012 #2982
We corrected the program to prevent a calculation error when a credit PO exists for a part, and the received quantity is changed to a different value than the Ordered quantity. In previous versions, when a negative quantity on order amount was changed during the PO receiving process, the "Quantity on Order" field was reset to the original Quantity on Order amount.
2012.10
1050 - Purchase Orders TMT1050L 07/25/2012 #2991
We corrected the program to allow report printing when a user has been setup in the Remote Print Master, (MS 850) with programs TMT1050L & TMT1050P. In the previous version, the only output that would print for a user with these Remote Print Master programs was part labels if multiple PO's were selected using option 11=Reprint PO.
2012.20
1050 - Purchase Orders TMT1050H 12/03/2012 #2996
We changed to the program to prevent duplicate Purchase Orders from being created when a user displays the PO Header while receiving a Quick PO. In previous versions, when a Quick PO was being received, and the user pressed F8=PO Header, the Shop Number and PO Date allowed changes. If the user changed these fields, a duplicate PO was created for the new Shop or Date. In this version, the Shop and Date are protected to prevent changes, just like a Standard PO.
94
2012.20
1050 - Purchase Orders TMT1050 12/27/2012 #3058
We improved the program with a new feature that will allow the user to update the Item, Description, and G/L Number when the PO Source Type is changed during the "Pay" step of a Purchase Order. When the PO Source Type is changed during the "Pay" step process for a PO, a window will be displayed that gives the user the option to press ENTER to update the Item, Description, and G/L Number, or they may press F12 to Cancel the changes. In previous versions, when the PO Source Type was changed, the Item, Description, and G/L Number required the user to remember to clear the fields or replace the old information with the new information. This option will help to ensure fields are updated when a user makes a change to the PO Source Type code on a PO line. In the example below, the PO Source Type code for Shipping and Handling was changed on the PO, and the new window has been displayed so the user can choose to press ENTER and update the changes, or use F12 to cancel the change.
2012.20
1050 - Purchase Orders TMT1050L 02/01/2013 #3076
We changed the program to prevent a condition that could allow the Purchase Order header status in file POHEADER and the Purchase Order Detail status in file PODETAIL to get out of sync when multiple users are viewing the same PO at the same time, and one user makes changes and exits before the other user. Even if the second user exits without making any changes, the PO Detail records may remain the same as they were before the first user completed their updates. This could result in the POHEADER and POSTATUS records becoming out of sync. In some cases, the part Quantity-on-Order may not update correctly when the part being received has a negative QOH, and a second PO is created for a positive amount, and the second PO is received for an amount greater than the order quantity. Recommendation:
Only one user should display the same PO at any given time. If it is necessary for multiple users to work with the same PO at the same time, the user that will be making updates or changes to the PO should verify all other users have exited the PO without making changes before pressing F6 to save and process the changes.
2012.20
1050 - Purchase Orders TMT1050 02/07/2013 #3082
We changed the program to limit the total quantity that can be received for a single part. The maximum Quantity-on-Hand allowed is 99,999. If the sum of the Quantity-on-Hand and Quantity received will exceed 99,999, a warning message will be displayed so the user can adjust the amount received. The new message displayed is: "On-hand quantity will exceed 99,999. Cannot receive more than '___' parts." (The actual amount that can be received without exceeding 99,999 will be displayed.)
We added the Purchase Order number and the Received Date from the PO to all labels printed from a PO. This includes labels printed during receiving or from the PO after parts have been received.
2012.31
1050 - Purchase Orders TMT1050L 08/12/2013 #3150
We corrected the program to display the correct Outside Repair Order after searching for a PO by Supplier Name, then using option 25=View for the selected OR/PO. In previous versions, if a search was performed by Supplier Name first, then option 25=View was used for an OR/PO, the program did not display the correct OR/PO. An additional attempt to display the OR/PO would result in displaying the correct OR/PO.
New Enhancement 2909 In the Purchase Order Inquiry (TMT1050) - Part Detail Window (Option 5=Display Detail), we added new command keys to display Serial Numbers and Part Information.
We added "F7=Serial Number”
We changed "F16=Rsvd Part Order" to "F10=Part Info" and "F16=Part Info" to "F10=Rsvd Part Order" to be more consistent with other areas in TMT where "F10" is the more common
"Part Info" command key used
We removed "F10=Part Info" when you display this screen via the Part Master using Menu
Selection 600, Option 2=Work With, F8=History, Option 8=View Order, Option 5=Display Detail since the User can simply use "F3=Exit" to return to the Part Master
Purchase Order Entry (TMT1050E) - when adding new parts and the Parts Catalog is in use, the program will load values for the new Part Master fields for PFC Required - (Part Failure Code Required), Expected Life <Mths>, Expected <Util>, and Serialized Part, with values from the Parts Catalog. If the Parts Catalog is not in use or the part is a Non-Stock part, the default values will be set as follows:
PFC Required - (Part Failure Code Required) = 'N'
Expected Life <Mths> = '0'
Expected <Util> = '0'
Serialized Part = 'N'
2012.41
1050 - Purchase Orders TMT1050E 10/28/2013 #3194
We corrected the program to clear the Record ID field (R#1002) in file PODETAIL before each new record is added to PODETAIL. In previous versions the program was using the PODETAIL Record ID from the previous record when a new line was added to an existing Purchase Order. This caused the Accounting Export transactions for these items on the Purchase Order to exclude the items with the duplicate Record ID, resulting in a Purchase Order total amount that was less than actual being exported to accounting.
2012.41
1050 - Purchase Orders TMT1041P 10/25/2013 #0990
We changed the program to display a 'Y' in the Reserved Parts column to indicate the Purchase Order contains Reserved Parts when the PO is created in Menu Selection 1041 - Parts Requisitioning.
2012.41
1050 - Purchase Orders TMT1050 10/25/2013 #3164
We changed the program to prevent two Users from attempting to use the "Pay Inv" or "Receive & Pay" option at the same time. Now the program will verify the option selected by the User(s) should still be allowed after any locks from other Users have been released.
96
2012.41
1050 - Purchase Orders TMT1050 10/25/2013 #3104
We changed the program to prevent a Reserved Part from being created for a Repair Order in a different Shop (or Repair Order Parts Override Shop), than the Purchase Order Shop to prevent a Reserved Part from being received when the Purchase Order Shop and Repair Order Shop or Parts Override Shop do not match. We added an edit to prevent a Reserved Part from being received if the Purchase Order & Repair Order Shop or Parts Override Shop do not match. In previous versions this condition resulted in the Inventory of the Purchase Order Shop being credited (an increase) for the 'RC' - Receipt transaction record, and the Repair Order Shop being debited (a decrease), and the 'RC' transaction displayed a negative Ending Balance for the Repair Order Shop. We added an edit to prevent a Repair Order from being closed if outstanding Reserved Parts exist. This will prevent a Repair Order with un-received parts from being closed, and therefore unbilled parts for Repair Order's with customers. We changed the listing displayed in TMT100U when a Unit Number on a Repair Order is changed to include the Purchase Order Number for any Reserved Parts linked to the Repair Order. Changed program TMT111 to prevent the Shop Number from being changed if the Repair Order has reserved parts when: The Repair Order and Purchase Order Shops don't match The Repair Order and Purchase Order Shops don't have a part override relationship Change the Shop RO Sections screen, (program TMT113) to allow option "9=Reserved Parts" for Non-Company Repair Orders when Reserved Parts exist on a Purchase Order. Changed the program to ensure the PO Detail record is updated if the Unit Number is changed on a Repair Order with Reserved Parts. The Shop Number cannot be changed on a Repair Order with Reserved Parts if the new Shop does not have an override for the Purchase Order Shop. A message will be displayed to alert the User that the Repair Order and Purchase Order Shops must match. Message issued: "RO has Reserved Parts. RO or Override shop must match PO shop." If a Purchase Order with Reserved Parts is cancelled, the Part Order status (PARTORDR/SOSTAT) will be updated to 'CA' status.
2012.41
1050 - Purchase Orders TMT895 01/10/2014 #3211
We changed the program to include the Tax Amounts from the PO Tax Indirect field in the PO Detail file (PODETAIL/PDTIC$), for "Indirect" taxable line charges on items when a Tax Source (V) line is used on a Purchase Order. The Accounting Export Transaction Detail record will now include the tax amount in the total. The result is that the PO amount, including the tax amount for a 'V' line displayed in the "Purchase Order Inquiry" screen will match the amount displayed in the "Export Transaction Detail" screen in Menu Selection 1211 - Export Transaction Listing. We also changed the "Account Export Disbursement Detail Setup". These programs were changed to display the "Use Inventory Account" flag for the following Rule and Subrule pairs
INVOICE | DIRECTISSU
INVENTORY | ADJUSTMENT/TRNSFR-IN/TRNSFR-OUT
INDIRECT | PART We changed the "Account Export Transaction Builder". It was modified to check the Part Master for the existence of a GL Account for the Rule and Subrule pairs listed above
It will now use the Shop Override logic
Previously this logic was only used for REPAIR | STANDARD | PART
97
Invoicing
2012.10 1055 - PO Invoice Listing TMT1050I 07/26/2012 #2999
We changed the program to prevent a lock condition when two users are both active in the "Purchase Order Invoice Listing" and search for the same Invoice Number.
2012.20
1060 - Customer Master TMT172 02/04/2013 #3086
We modified the program so that it would perform an edit if the Customer Number is blanked out when a new Customer Number record is being created. In previous versions, the program was allowing a new Customer Number record to be created if the user left the Customer Number field was blank.
We changed the program to allow a Price Range to be created based on amount only. The program will now allow a blank System Code when setting up a Price Range.
2012.10
1079 - Invoicing TMT1091H 04/06/2012 #2859
A new "Company Unit" field has been added to the Listing Options. You may select both Company and Non-Company Units, only Company Units, or only Non-Company Units. A new "Repair Order" field has also been added in the Listing Options. You may select '*ALL' to list all invoices, or enter a specific Repair Order Number to list the invoice for that RO. Unit numbers displayed in PINK indicate the Unit number on the Invoice is for a Non-Company Unit.
2012.10
1079 - Invoicing TMT1091H 08/23/2012 #2954
We updated the Sub-File Load to use Dynamic SQL to correct an issue with Invoices being read by the process, and then skipping them when attempting to only select Invoices in 'Open' status.
2012.20
1079 - Invoicing TMT1091X 12/07/2012 #3061
We modified the program to check for excessive Charge and Fee amounts to prevent an error when any Part, Labor, Service, or Fee amount is less than $99,999.99-, or greater than $99,999.99.
98
2012.41
1079 - Invoicing CLTMT1091V 12/05/2013 #3201
We changed the program to hold the Invoice Print Detail (PRT1090D) and Invoice Print Summary (PRT1090R) printer output files. When the option to view an Invoice is used (option 5=View), the program produces a printer file used by the Invoice View program to retrieve and display the Invoice. If your IBM i environment is configured to print directly from QPRINT, the output file could be created, printed and deleted before the Invoice View program had a chance to retrieve and display the Invoice. When this happened a message was displayed on the screen informing the User that the Invoice was no longer available to display. This change will allow the Invoice to be viewed, and the User will be able to view the Invoice immediately.
2012.41
1079 - Invoicing TMT1091U 12/16/2013 #3209
We changed the program to enforce the Menu and Submenu Security assigned to a User for Menu Selection 1079 when they are attempting to work with an Invoice in Menu Selection 100 or 180. If the User does not have Security access to use the Close, Change, or Delete options in Menu Selection 1079, then they will no longer be allowed to perform those functions in Menu Selection 100 or 180. For example if the User does not have access to Close Invoices, an error message will be displayed - "Access to close invoices denied to this user." In previous versions, if a User did not have Security access to Change or Close an Invoice using Menu Selection 1079, the User could perform the same function using Menu Selection 100 or 180 to Close or Change an Invoice.
A new "Company Unit" field has been added to the Listing Options. You may select both Company and Non-Company Units, only Company Units, or only Non-Company Units. Manual invoices are only included in the "Customer Gross Profit" report when the Company Unit value is set to all (*). We added the following messages in the "Customer Gross Profit" report to indicate which units (and invoices) were selected :
When all Units are selected: “All Units and DIRECT SALES Included in Gross Profit” When only Company Units are selected: “Only Company Units Included in Gross Profit” When only Non-Company Units are selected: “Only Non-Company Units Included in Gross
We corrected the program to display the correct cost for the last Customer listed on the report. In previous versions, the report was displaying an incorrect amount for the last Customer listed on the report, if the last Customer in the Customer Master has invoices "closed" during the reporting period.
A new "Company Unit" field has been added to the Listing Options. You may select both Company and Non-Company Units, only Company Units, or only Non-Company Units.
New Enhancement 3032 We added a new Menu Selection - "1082 - Invoice Aging Report". This new Menu Selection will allow the User to create an Invoice Aging Report for any unpaid invoices for Past Due dates in increments of 0-30 days, 31-60 days, 61-90 days, or Over 90 days. A View and Print option are also provided. Both options display a Summary Total and Grand Total amount for each Past Due increment. The view option also provides the ability to display the detail of the Summary Total, with additional options that allow the User to print or email the invoice, and an option to review the Repair Order. 1079 - Invoicing
A new field - "Invoice Paid", was added to the "Pay Invoice" window. When this new field is set to 'Y', the Invoice will be excluded from the new "Invoice Aging Report". When the "Amount Paid" field is updated in the "Pay Invoice" window, the "Amount Paid" value will be deducted from the outstanding Past Due amount displayed in the new "Invoice Aging Report". If the "Invoice Paid" flag is set to 'Y', the Invoice is not included in the "Invoice Aging Report", even if there is a partial unpaid balance. (The difference between the "Invoice Total" and the "Amount Paid"). We also added a new field - "Paid Status" to the Listing Options for Menu Selection 1079 - Invoicing. This new field will allow the User to include or exclude any invoices that have not been paid. The three options are: 'All', 'No', or 'Yes'. All - Includes all Paid or Unpaid Invoices No - Only includes Invoices where the "Invoice Paid" option is set to 'N'. Yes - Only includes Invoices where the "Invoice Paid" option is set to 'Y'.
Note: By default, all current Invoices will be set to 'Y' if the "Amount Paid" is greater
than or equal to the "Total Invoice" charges. Otherwise, it will default to 'N'. This new Menu Selection requires the Invoicing Module.
Charging parts with zero Quantity on Hand is no longer allowed from the Mechanic Workstation, regardless if Firmware "Charge Parts with no Qty" is set to 'Yes' or 'No'.
We modified the "Request Parts by VMRS Code" listing so that if the first three digits of the VMRS code on the screen matches the first three digits of the part master VMRS Code and the second three digits of the VMRS Code on the screen are blank, then the part will be included in the listing. In previous versions, all six digits of the VMRS Code had to match even if they were blank or '000', like "017 000".
We corrected the program to display and validate Indirect Codes for the full four digit number when a user enters an Indirect Code in a Time Card or Time Card maintenance, and fails to enter any or all leading zero's. In previous versions, if a user entered Indirect Code 035, and pressed the Tab key instead of Field Exit, the program failed to add the leading zero. Example - 035 should be displayed as 0035.
New Enhancement 3114 We added a new Firmware, "Mechanic Assign Work - Assigned Only". This new Firmware allows you to choose if the Repair Order Work listing will only display Assigned Repair Order sections, or all Assigned and Unassigned Repair Orders, PM's, Shop Plans, and Work Pending for Employees that access the Repair Order Work listing to select and assign Repair Order sections. This new feature is beneficial if you want to allow Employees (mechanics) using the Mechanic Workstation or Supervisor Workstation to select and assign work to themselves from existing Assigned Repair Orders, and also prevent the Employees from selecting work that has not been assigned, or from creating new Repair Orders from PM's, Shop Plans, or Work Pending's. In previous versions, all Assigned and Unassigned Repair Orders, PM's, Shop Plans, and Work Pending's were always displayed. This also allowed Employees to create Repair Orders, even if they did not have security to create Repair Orders using other Menu Selections.
We corrected the program to ensure a User Security Profile with Region or Shop security restrictions will allow the User to view and select Repair Orders in the Repair Order Work Listing. Employees are restricted to only view and select Repair Orders that were created for the Employees Primary Shop setup in the Employee Master.
New Enhancement 2493 We added the ability to allow comments to be added to Indirect Charges entered using the Mechanic Workstation. We added a new label to the Indirect Labor Codes in Codekeys. Indirect Codes are maintained using Menu Selection 800 - Codekeys Master, Category 109 The new Label is: “MWS Comments” - (N)o, (Y)es, (R)equired This will designate whether or not the code prompts the Mechanic to enter comments when finishing Indirect Labor in MWS.
No – Comment window is not displayed
Yes – Comment window is displayed
Required – the Mechanic must enter comments in order to leave the screen. The new flag will be added during the upgrade with a default of 'N'.
The Mechanic Workstation was modified to call the TMT Comments Master program whenever a Mechanic “Clocks Out” of Indirect work.
The Comments window is displayed based on the new Indirect Labor comments flag
The Indirect charge number is passed to the comment program
The Mechanic id is passed to the comment program
TMT Comments Master program modifications
The comments entry window will display the Indirect Labor Code and Description
The comments will be marked with Mechanic id - not the system User name
The comments entry window will enforce the MWS Comments Required flag
Two new Firmware were added that allow you to choose if Indirect or Repair Order Comments should be printed on the Time Card.
Print RO Comments on Time Card?
If set to 'Yes' - The RO Comments will print on the Time Card below the line
containing the RO, System and WAC.
If set to 'No' - The RO Comments will not be printed on the Time Card.
Print Indirect Comments on Time Card?
If set to 'Yes' - The Indirect Comments will print on the Time Card below the
Shop Number.
If set to 'No' - The Indirect Comments will not be printed on the Time Card.
1110 - Time Cards Master
New option '9=Comments' was added to display the comments
Added a “flag” to indicate comments exist for Section Work and Indirect Labor
Time Card Listing - Option 9=Comments will allow the User to view RO or Indirect Comments
Time Card Maintenance - Option 9=Comments will allow the User to display and edit RO or Indirect Comments
Comments entered by the Mechanic will be flagged with the Mechanic id
Comments entered by the Supervisor will be flagged with their User profile - not Mechanic id
New Enhancement 2909 The "Parts Entry" screen (TMT135P) has been replaced with the same screen used when charging parts from Menu 100 - Shop Repairs, "Shop RO Charges". Note: Your UserID’s for the Mechanic Workstation needs to have security to Menu Selection 100,
option 4=Charges if you allow Mechanics to charge parts.
We changed the program to prevent an Employee Time record from being written when an Employee clocks out of an activity before the time defined for Firmware "Minimum SECONDS for Labor Charges" has been exceeded.
We added a new Firmware that will allow you to display a list Mechanics on the Mechanic Workstation login screen.
Changed the Web Edition menu to launch a Menu Selection with one-click instead of double-click.
Changed default Menu title from "Navigation" to "TMT Menu".
Changed Menu style to "Accordion Menu" - (allows user to expand/collapse Menus by Menu Page).
Added an automatic refresh timer to prevent the Mechanic Workstation login screen from a “Time-Out” condition during periods of non-use.
N
2012.40
1110 - Time Cards Master TMT134M & TMT135 08/15/2013 #3112
New Enhancement 3112 We changed the Clock-Out edits to prevent a Time Card from exceeding 100 hours.
The Employee will no longer be allowed to Clock-In if their Time Card has exceeded 100 hours.
The Employee will not be allowed to use "F20=Clock Out" if they have exceeded 100 hours.
A message will be displayed if an Employee attempts to Clock-In and the Time Card has exceeded 100 hours, even if you have Firmware "Allow Mechanic to Force Clock Out" set to 'Yes'.
o The new message that will be displayed for these conditions is: "Time card exceeds 100 hours. Contact Supervisor."
o In previous versions the message displayed was: "Maximum shift hours exceeded, contact shift supervisor"
The Employee will be allowed to use "F20=Clock Out" if Firmware "Allow Mechanic to Force Clock Out" is to 'Yes', and the total time on the current Time Card is greater than the value set for Firmware "Max Shift Hrs Allowed" and less than 100 hours.
o The message displayed for this condition is: "Maximum shift hours exceeded, press F20 to Clock Out"
Firmware "WARNING - Excess Hrs" now has a limit of 99 hours.
Firmware "Max Shift Hrs Allowed" now has a limit of 100 hours. o Recommendation - you should review these Firmware and make sure they are set
within the new limits.
When option 8=Clock Out is selected for a Time Card and the Employee Time Card status is currently Clocked In, on Lunch Break, or on Indirect Work the system will default the Log Out Date/Time values from the current Date and Time and will not allow the Employee to be Clocked Out with more than 100 hours.
When option 8=Clock Out is selected for a Time Card and the Employee is currently Clocked In on Idle Time, the system will default the Log Out Date/Time values from the last record on the Time Card, instead of the current Date and Time.
When option 8=Clock Out is selected for a Time Card and the Employee is currently Clocked In on Section Work, or Pause Mode, the system will not allow the Employee to be Clocked Out with more than the Maximum Shift Hours - OR - allow the Employee to be Clocked Out with more than 100 hours.
N
2012.40
1110 - Time Cards Master TMT134C 08/21/2013 #803
We added the "Posted by" User, Date, and Time to display on the Time Card when displayed in View Mode from the Time Card Listing, or other points of access like the Repair Order or Job Code inquiry reports.
We corrected an error with the program that occurred if you attempted to Clock Out an Employee with over 1,000 hours on the open Time Card, AND the Employee was also clocked into a Section with Job Codes. (Usually a rare occurrence and the Employee left while Clocked In and the Time Card was never Clocked Out).
New Enhancement 3043 We changed subroutine "SR_PROCESS" so that the logic for executing the User Exit 'EXT' for the Time Card selection for Posting or the Time Card Summary Report TMT212K will include all report options (Posting or Summarizing) and all output options (Printing, Emailing and Outfile). The values listed below are now included in the exit data structure: $@SHOP = Repair Shop $@OTHER,8,10 = Shift $@DT1 = Start Date (Low) $@DT2 = Start Date (High) $@EMP = Employee $@OTHER,18,1 = Output Option (Print, Email or Outfile) $@OTHER,19,1 = Report Option (Post or Summary) For copybook TMTBKSRV: 1) increase size of Message Data parameter to 1024a in prototypes QMHRCVPM and QMHSNDPM 2) increase size of Message Data parameter to 1024a in prototypes RCVPGMMSG and SNDPGMMSG For service program TMTSRVPGM: 1) increase size of Message Data parameter in the following procedures: RCVPGMMSG, SNDPGMMSG, TMTMSGS and TMTQSNDPM 2) for procedure TMTMSGS when send to value is *RTVE, use message format RCVM0300.
We changed the program to only display the options and command keys that are allowed for the user based on their Security authority settings in Menu Selection 836 - Menu Security Master. We added option "4=Reset TINA Login" to the Supervisor Workstation to make it more convenient for a Supervisor to reset an Employee. It works just like the option "4=Reset TINA Login" in Menu Selection 220 - Employee Master, and users will have the same Security authority in Supervisor Workstation for this new option as they currently have in the Employee Master when you install this version. Even though by default the Supervisor Workstation and Employee Master Security for the "Reset TINA Login" option will be the same, they can be set differently if desired. We also added sub-option Security for Command Key "F19=Summary" for the Supervisor Workstation. We added a new Command Key "F13=Create RO" to the RO Assignment screen (TMT132R). This will allow the Supervisor to have a convenient new location to create an RO "on the fly" when reviewing or assigning RO's to Employees. This command key works the same way that "F13=Create RO" currently works for an Employee logged into the Mechanic Workstation. The user will have the same Security authority setting that they have for Menu Selection 100 - Shop Repairs.
We changed the program to pass all the required Parms needed to prevent an error that was displayed if the User was attempting to delete a Time Card that had a Repair Order linked to it that was in "Closed" status. The missing parm was used to pass back the RO number so it could be used in the error message. We also modified the messaging in program TMT212K so that the appropriate messages are displayed when deleting a Time Card. The new message displayed is; "Cannot delete Time Card with closed Repair Order 9999999" (The actual Repair Order number is displayed instead of "9999999"). We added a new message when a Time Card is successfully deleted; "Time Card 9999999 has been Successfully Deleted" (The actual Time Card number is displayed instead of "9999999"). In previous versions a message was not displayed when a Time Card was successfully deleted.
105
N
2012.31
1150 - Job Codes Master TMT150H 06/21/2013 #3118
New Enhancement 3118 We added the ability to create and assign Job Codes to Repair Orders created for Non-Company Units. Orders - Shop Plans, Road Calls, Repair Orders
Job Codes may be assigned for Non-Company Units if a Customer Number has been selected for the Repair Order.
Only Non-Company Job Codes will be displayed to select from for an RO with a Non-Company Unit.
Non-Company Job Codes listed will be determined by the value in the "Profile" field for the Job Code Master definition.
All Non-Company Job Codes with a Profile value of '*ALL' will be displayed.
If the Job Code Profile is set to a specific Customer Number that matches the RO Customer Number, then these Job Codes will also be displayed.
If the Job Code Profile is set to a specific Customer Type that matches the Customer Type Code for the RO Customer Number, then these Job Codes will also be displayed.
If the Unit Number, Company Unit flag, or the Customer Number are changed on an Order with Job Codes selected, the Job Codes will be removed, and the user will be prompted to select new Job Codes based on the changes made for the new Unit Number, Company Unit flag, or the Customer Number on the Order.
NOTE: Job Codes are NOT allowed for Non-Company units without a customer number.
Non-Company Units require a Customer Number on the Repair Order. If the Customer Number does not exist on the RO, Job Codes will be removed.
New Listing Option
Non-Company JC -
Yes - Allows the Listing to display both Company and Non-Company Job Codes
No - Restricts the Listing to only display Company Job Codes
Only - Restricts the Listing to only display Non-Company Job Codes
Job Codes for Non-Company Units are displayed in Pink in the Listing.
New flag for Non-Company Unit JC in the Job Code Master record.
Press F4 in the Profile field to display the choices available depending on the current value for Non-Company JC.
Non-Company JC - Yes - Allows the user to select:
1=Job Code Profiles 2=Customer Number 3=Customer Types
No - Allows the user to select a Job Code Profile Only - Allows the user to select:
2=Customer Number 3=Customer Types
Job Codes may be defined to be used for all Customers or a Customer Type.
The "Customer Type" can be defined on the Customer Master record.
The Profile field in the Job Code Master is used to define a Job Code for all Customers (use *ALL), a specific Customer (enter a Customer Number), or the Customer Type (enter a Customer Type code) for Non-Company Job Codes.
When the new flag "Non-Company Unit JC?" is set to 'Y', then the "Profile" field will all you to prompt to select a Customer or Customer Type or enter '*ALL'.
Diagnostics are not specific to Company or Non-Company Units, and any Diagnostics may be used with either Company or Non-Company Job Code definitions.
If the "Non-Company Unit JC?" flag is set to 'Y' for a Diagnostic definition, the Listing Options can be used to filter Diagnostics that have a 'Y' or 'N' set for this field.
We changed the programs to prevent an error that allowed the programs to go into an endless loop adding Indirect Charge records. This resulted in an error message being displayed - "The target for a numeric operation is too small to hold the result."
Yes - Allows the Listing to display both Company and Non-Company Job Codes
No - Restricts the Listing to only display Company Job Codes
Only - Restricts the Listing to only display Non-Company Job Codes
Job Code Reporting - On-Line;
Job Codes for Non-Company Units are displayed in Pink on-line
Job Code Reporting - Printed Reports:
Job Codes for Non-Company Units are displayed with a new legend id on the printed reports that include Job Codes for Non-Company Units.
(*) Non-Company JC with a *ALL profile.
(C) Non-Company JC for a Customer Number.
(T) Non-Company JC for a Customer Type.
2012.10
1170 - Shop Planner TMT145H 04/23/2012 #2587
The Unit Number will be displayed in PINK, if the unit has been flagged as a 'Non-Company Unit' on the Plan. (Reverse Image PINK if there is an Open RO associated with the Plan).
2012.10
1170 - Shop Planner TMT145P 05/29/2012 #2963
We changed the program for the “Shop Planner Listing” report to print a blank line after the last comment line of a Plan, and the label "COMMENTS" will not be repeated for each line of comments per Plan. It will only be displayed once per Plan.
2012.10
1170 - Shop Planner TMT145W 09/09/2012 #3046
We changed the program so that Firmware 15203 - "Auto change Plan work started location" will not be required to have a Location value when Firmware 15202 - "Auto change Plan Status" is set to 'Yes'. When "Auto change Plan Status" is set to 'Yes', and "Auto change Plan work started location" is set to 'blank', the Plan and Unit Location will not be updated when the employee assigned to the RO begins work using the Mechanic Workstation. This feature will allow the current Location to remain on the Plan and Unit until it is changed by a user or the RO Section is updated as "Complete" using the Mechanic Workstation. When the RO Section is updated as "Complete", then the Location value will be updated with the value in Firmware "Auto change Plan work finished location".
2012.20
1170 - Shop Planner TMT150T 02/04/2013 #3079
We corrected an error that could occur when a Repair Order was closed with sections that have Job Codes assigned, and no labor charges have been added to the RO section.
We changed the program to update the Plan Status when an Employee begins work on a Repair Order, logs off, or logs back in when Firmware "Auto change Plan work started location" is blank. In the previous version, when Firmware "Auto change Plan work started location" was blank, the Plan Status was not being updated as the Employee changed status.
N
2012.10
1182 - Parts Workstation TMT690H 04/16/2012 #2919
New Enhancement 2919 We added a new option to the "Request Sts" field. The new option will allow you to select only 'New' part orders. Now you can filter the list of Parts Requests to only display "New" requests. In previous versions you only had the choice of 'All', 'Order', or 'Complete'. The 'Order' status included 'New' and 'Order'. The status of 'New' indicates the part order has not had any items filled. The status of 'Order' indicates the part order is partially filled.
107
2012.10
1182 - Parts Workstation TMT690 10/18/2012 #3019
We changed the program to ensure the new Repair Order ID Number is used in the Part Request Detail file, (PARTREQD), for each item ordered through the Mechanic Workstation. We also added a routine to ensure Warranty Part Labels are generated for parts charged from the Parts Workstation with potential warranty.
2012.10
1182 - Parts Workstation TMT690 10/18/2012 #3010
We corrected the program to ensure all information is included on any Warranty Claims that are generated for any parts charged using the Parts Workstation that have potential warranty. In the previous version, when a claim for non-positional part was created following a claim for a positional part, the vendor information was omitted on the Warranty Claim.
2012.41
1182 - Parts Workstation TMT690 10/14/2013 #3180
We corrected an error with the Part Position logic when processing Repair Order part requests for a Non-Company Unit. The part position logic would return an error that should have been ignored. The error did not identify the condition nor would it permit the User to use "F6=Process".
We added "Field Change History" for the Period Status, Period Begin and End Date fields. We also added a new "hidden" Command Key "F16=History" to display the "Field Change History" for Period Status, Period Begin and End Date fields. The history is displayed by positioning the cursor to the Year and Period you want to display, and then press 'F16=History'. The Year and Period is the key to the TMTFHIST file (YYYYMM) Adds, Changes and Deletes will be tracked
Delete History can be displayed after a Year/Period has been deleted when you position the cursor to the Year/Period or Status field and press F16.
We added the "Customer Number" Subrule option for the INVOICE | DIRECTISSU and INVOICE | DIRECTSALE rules for the Accounting Export module. This feature will allow Subrules to be setup by Customer or Customer Type, the same as the other "INVOICE" rules.
We added the ability to setup the Accounting Export to function in a Multi-Company environment, with the ability to generate Credit and Debit transactions for each company involved in the transaction. For example; Repair Order transactions will use this process when the Repair Order shop and the Unit Domicile belong to different companies. For a Part Transfer, this feature would be used when the sending and receiving shops belong to different companies. New Firmware "InterCompany Account for Multi-Company" must be set to 'Yes'. 1. TL2000 Multi-Company Setup
New Firmware - 99129 - Use Company as Prefix on Vendor - In TL2000 a customer can set up multiple companies. Each company can have its own set of AP vendors. Using this firmware will allow TL2000 customers that have multiple companies to have unique vendor numbers in TMT. The right-most digit of the company number will be added as a prefix on the vendor number in TMT. This firmware in conjunction with using a Vendor Security wildcard(*) in MS 835 will secure a user to one company's vendor numbers. New Firmware - 99108 - InterCompany Account for Multi-Company - In TL2000 a customer can set up multiple companies. When company cross charges occur (repair shop in one company, domicile shop in another company) a second set of debit and credit accounts need to be set up for the cross charges. The value in this firmware represents the cross charge account and allows the accounting export programs to properly account for the cross charges. Changed Programs:
TMASETUP - Create new firmware 99108 - InterCompany Account for Multi-Company - Create new firmware 99129 - Use Company as Prefix on Vendor - Changed TMT Exit for Program TMT183 to TMT117, changed Exit Type from IFE to INV - Removed TMT Exit for Program TMT840U - the TMT-TL2000 EOD programs are called directly from TMT840U CLTMA840U - TMT / TL2000 - EOD Exit (run GL & AP Interfaces) - Program deleted due to direct calls in TMT840U
109
PCR 3001 and 3007 (Continued)
TMAAPI630 - TMT / TL2000 Supplier Master API - Added additional input parameter for TL2000 standard program call parameter. - TL2000 changed their programs that call TMAAPI630 to include use this parameter - If Firmware "Use Company as Prefix on Vendor" is in use, the API will add the rightmost digit of the company to the beginning of the five digit TL2000 vendor code. This allows vendor security to restrict a user to just one company's vendors. TMA895AP - TMT / TL2000 - AP Interface - If Firmware "Use Company as Prefix on Vendor" is in use, the one digit prefix from the TMT Vendor will be removed before passing the vendor to TL2000 AP. TMA895GL - TMT / TL2000 - GL Interface - If Firmware "InterCompany Account for Multi-Company" is in use, the program posts the transactions to the correct company. TMT895 - Account Export Transaction Builder - Checks for Firmware "InterCompany Account for Multi-Company" and compares the Repair Shop company to the Domicile Shop company. If the companies are different and an InterCompany Accounts exists for the Rule/Subrule that is found, it will be used. 2. Modify length of License Weight when calling TL2000 API for Units Changed Program:
TMA310 - increased size of license weight parameter from 5,0 to 6,0
We corrected the program to prevent an overprinting condition for the "Account Export Transactions" report. In the previous version, (2012.10), the report displayed the Supplier, Date/Time, and Program over the Record Type, Transaction Date, Year/Per, and Shop.
We changed the TMT/TL2000 Intercompany GL process to use the Repair Order Shop Company for Non- Company Units. When a Company Unit is repaired, the program normally compares the Unit Domicile Shop Company to the Repair Order Shop Company to determine if it is an Intercompany repair. However, a Non-Company unit does not have a Domicile Shop so the program must use the Repair Shop Company for the Domicile Shop Company. Other Changes:
TMT/TL2000 - GL Interface (TMA895GL)
Added logic to check for Company Unit flag. o If set to 'Y', and the transaction is related to a Unit order, (E.G - REPAIR ORDER,
FUEL TICKET, INVOICE REPAIR), use the Domicile Shop from the unit for Company Units, - otherwise use the Repair Order Shop for Non-Company Units from the transaction (ACTXTRAN/XTSHOP) to determine the correct TL2000 Company to post the transaction to.
TMT895 - Account Export Transaction Builder
Added logic to check for Company Unit flag.
Changed program to ensure that an existing transaction would not be updated if it has been posted.
o The only program available to the user to update an existing transaction is Menu Selection 1211 - Export Transaction Listing:TMT895T, and now it has an edit to prevent Option 8=Recalculate if the transaction has been posted.
o Program TMT895Z can also update existing transactions and is typically used when transactions need to be created due to some sort of issue (E.G. - the EOD User has not been setup in Menu Selection 835 - User Profile Master:TMT890)
o TMT895Z is not available to the user from any Menu Selection. TMT840U - End of Day Processing
We added an edit at the very beginning of the program to ensure that the user submitting the EOD is setup in Menu Selection 835 - User Profile Master.
o When the TMT EOD is run from a scheduled job, the User ID defined in the scheduled job is not set up in TMT, the Accounting Export transactions for Repair Orders do not get created. This is usually not discovered immediately (until month end), and then a special program must be used to create the missing transactions to correct the issue.
o This change will cause the EOD to fail completely, and send a message to the QSYSOPR: "The TMT EOD process for Shop 999999 did not begin because user XXXXXXXXXX is not set up in the TMT User Profile Master."
111
Appendix A - Pre-Conversion Programs
Pre-Conversion Program – Build the RO ID Master
During the conversion upgrade process, a screen will be displayed for the Pre-Conversion program(s) that need to be reviewed before you are allowed to continue.
If you are upgrading from any Version prior to Version 2012, you will be required to complete the “Build ROIDMSTR from ROHDRHST & RPROHEAD” Pre-Conversion program.
The screen below in Figure 1 will be displayed, and you will be required to select the program.
When the conversion upgrade displays the screen below, use option 1=Run to call the program to run.
Figure 1
112
In the next window, type “Y” if you completed all pre-conversion requirements or “N” if you have not completed requirements but will at a later time. Press ‘Enter’.
Note: You can’t move forward with the conversion process until you enter “Y” here.
Figure 2
Once you complete the task, the status column in Figure 1 will change to ‘Completed’. Press ‘Enter’ to continue, (do not press F3=Exit).
113
TMW Systems - TMT Fleet Maintenance™ Technical Support: 919-493-4433
