A. Records need to be set up in the Edit Ticket Charge Codes file. This file allows the user to configure how this program will work for the various types of vendors that charge for EV recharging.
B. A Ticket Charge Codes (previous step) must be assigned to each vendor in the Vendor file whose EV charges are to be processed by this program.C. For all EV Charging Stations, a Vendor type code must be assigned to each vendor in the Vendor file. This will allow for the EV Charging Processing Program to be run by Vendor Type.D. Hertz users only: the following steps 1 and 2 may be skipped by all other users,
1. The Edit TICGAR Control Record should be set up . Refer to the chapter Edit TICGAR Control Record for more information.2. Prior to using this program, the next "ticket reference number" must be defined. This is done using the program Edit Next TICGAR Number. Since this is typically a "run once" program, it is not on a menu. It can be accessed by typing RUN and any menu "OPTION" field, then typing EDNTGR in the "Name of Program" field. (Note: The user's menu security level must include the "Run A Program" item on the System Management Menu in order to perform this step.) The screen will then display:
OPTION: __ EDIT NEXT TICGAR NUMBER
1 Next TICGAR #
1SAVE 2 3 4 5BACKUP 6 7HELP 8Enter the next reference number into field 1.
Press enter to return to the OPTION field, then press F1 to save the record.
F. There are three methods for obtaining the location and cash drawer to be used for the Invoice and corresponding payments:
1. The owning location of the vehicle on the RA and the lowest-numbered cash drawer for that location. (This is the default).2. The current location and cash drawer of the user running this program (as seen on the Change User Environment Screen).3. The opening location and cash drawer of the RA.Note: Options 2 and 3 require GVT code TKTLOC to be set up. Please contact Thermeon Customer Support for this. Option 3 also requires "RA" to be in the Alpha field of the GVT record.
A. Create the spreadsheet on a PC or computer that is also used to access CARS+.
Click here to download a template file with the header row already completed.
B. Entering data in the spreadsheet
Although the link above provides a template, the columns for the spreadsheet do not need to be in any particular order, and all columns need not be present. For your own purposes, the spreadsheet can contain additional columns unknown to CARS+. What is required is that the columns that contain data to be merged MUST have the column header specified in the chart shown at the end of this chapter.
- Create a row for each Model Code record that should be imported or updated.
- Enter the data to be added or changed in the appropriate column(s). (See the "User Tip" below regarding the date format.)
- A blank field in the spreadsheet will cause the corresponding field in CARS+ to be cleared. This means that when entering a record into the spreadsheet, the complete record needs to be entered, not just the fields that are being changed.
User tip: Date format can be either:
YYYYMMDD (Example: 20150927 for September 27, 2015)
The local date format of either: MM-DD-YY or DD-MM-YY (This is specified in Edit Misc Control Record.)
C. Naming the spreadsheet file.
When saving the spreadsheet, the name assigned to it should follow Unix file name conventions which are:
- Maximum of 10 characters for example 20150930DC.csv for September 30, 2015, and EV for (E)Electric (V)Vehicle
- No spaces or slashes in the name
D. Saving the spreadsheet.
First save it in your spreadsheet program's native format (for example if using Microsoft's Excel program, save it as .xls).
Re-save a copy in .csv format.
If an error in the data is discovered by the merge program, go back to the file in the native format and easily make any corrections. Then re-save it again as a comma delimited file (.csv format).
It is the copy saved in .csv format that will be used for the import. The first row of column headers must be included.
The following table lists the required column headers to be used in the spreadsheet. After entering data, export the data as a comma delimited file and place it on your CARS+ server for processing. Warning: The column headings must be character by character as they are illustrated in the chart below and the format instructions must be followed. Additional columns may be added to the spreadsheet but they will be ignored by the processing program.
The screen will then display:
| OPTION: ____ IMPORT ELV CHARGES 1 Batch file name 2 Payment Date 2 Ticket Received RA/NRV# 3 Ticket No. 11 Last Name 4 Ticket Issuer 12 First Name 5 Ticket Date 13 Address1 6 Ticket Time 0000 14 Address2 7 Offense Type 15 City 8 Ticket Amt 16 State 9 License No. 17 ZIP NOTE: DATE FORMATS HAVE CHANGED. ACCEPTABLE FORMATS ARE: MM-DD-YY YYYYMMDD 1SAVE 2SKIP 3ERASE 4UPLOAD 5 BACKUP 6 HELP 8 |
Enter data as follows:
|
1. BATCH FILE NAME |
Enter the name of the ascii comma delimited file containing the toll data. Press F1 to begin processing the records. |
| 2. PAYMENT DATE |
This field displays the Payment Date. |
|
3. TICKET RECEIVED |
This field displays the date the toll was received. |
|
4. TICKET NO. |
This field displays the toll number of up to 20 alphanumeric characters. |
|
5. TICKET ISSUER |
This field displays the Vendor number of the entity that issued the ticket.A valid Vendor number must be used. |
|
6. TICKET DATE |
This field displays the date the toll was issued. |
|
7. TICKET TIME |
This field displays the time the toll was issued. |
|
8. OFFENSE TYPE |
This field displays the Ticket Charge Code from the vendor record. |
|
9. TICKET AMT |
This field displays the amount of the toll. |
|
10. LICENSE# |
This field displays the license number of the vehicle stated on the ticket. |
|
10. ADDRESS 1 11. ADDRESS 2 12. CITY 13. STATE 14. ZIP |
If the customer’s address needs to be updated (obvious typographical errors done at the counter), enter the new information in these fields. Upon pressing F1 to save, the data entered will update the customer record. |
OPTION: __ IMPORT ELV CHARGES
1 Batch file name
2 Ticket Received RA/NRV#
3 Ticket No. 10 Last Name
4 Ticket Issuer 11 First Name
5 Ticket Date 12 Address1
6 Ticket Time 13 Address2
7 Offense Type 14 City
8 Ticket Amt 15 State
9 License No. 16 ZIP
/dev/tty
Option: _ IMPORT ELV CHARGES FILE SEARCH
F2=NEXT 8 F4=PREV 8
File Name Create Date
1 ev_charge-101112.csv Oct 11 12:00
2 ev_charge-100312.csv Oct 3 14:20
** No More Records **Select the appropriate file by typing the row number.
After loading the name of the file to be processed, place cursor back in the "OPTION" field and press F1 to begin the import process.
A table listing the required column headers of the data in the spreadsheet is shown below:
| Required Column Header |
Format |
Notes |
| Date |
See note on acceptable date formats above | Transmission file date. |
| Vendor-no |
8 character Vendor number |
This is the Vendor number from the Vendor File for the entity that is doing the battery charging. |
| Offense-type |
2 character code |
Leave this column blank. The Ticket Charge Code record that is to be used for the admin fee and taxes charged comes from the Charge Code on the Vendor in the previous field will be used. |
| Charge-ID |
up to 20 characters alphanumeric |
EV Recharge citation number. |
| Chg-Amount |
nnnnnn.nn |
The amount of the EV recharge. |
| Park-Amount |
nnnnnn.nn | The charge amount for leaving the car attached in parking space after full charge. |
| VIN |
up to 17 characters |
Vehicle VIN number |
| Charge-date |
See note on acceptable date formats above | Date of the EV recharge occurred. |
| Charge-time |
HHMM (using a 24 hour clock [2pm = 1400)) | Time of the EV recharge occurred. |
| Description |
up to 20 characters alphanumeric |
Enter name of the EV Charging station/location |
| Chg-kwh |
nnnnnn.nn | Number of kwh charged. |
| Park-min |
nnnnnn.nn | Number of Parking minutes the vehicle was still attached after full charge. |
The Import ELV Charges program works as follows:
A. All records in the spreadsheet are sorted by Vehicle VIN number and then citation issue date/time (this is to discover if multiple tickets were written for a single rental). As a result, they may be processed on the screen in a different order than the order expected.
For each line in the spreadsheet:
B. If the vendor number doesn’t match an existing vendor record in CARS+, an error is displayed and the record is skipped.
C. If the vendor does not have a Ticket Charge Code assigned to it and the Offense Type column in the spreadsheet is blank, an error is displayed and the record is skipped.
D. If the vehicle vin number doesn’t match an existing vin number in the Vehicle file, an error is displayed and the record is skipped.
E. Next, the Vehicle History file is checked to see if this ELV has already been processed. If a ELV record (Service Code "X7") is found, an error is displayed and the record is skipped.
F. If the vendor number and vehicle VIN number are validated, the RA file (and optionally the Non-Rev file) are examined for records in accordance with the date and time of the EV recharge.
When only one transaction involving the cited vehicle is found, and the GVT record “QUICKTKT” exists, the ticket is processed and nothing displays on the screen. Otherwise, the RA and/or NonRev is displayed on the main window for editing by the user.
Press F1 to proceed with processing.
When more than one record is found, the possibilities are displayed in the subwindow on the screen. The user must then select the line number for the correct record, or the user may press ESC to exit the subwindow without selecting a line.
If no records are found in the RA or Non-Rev files, the vehicle history file is examined for Service Code records number 00 (RAs) and 93 (Non-Revs) in case the RAs or Non-Revs have already been purged off the system.G. Once all records have been processed, two audit files are produced:
- The first lists all toll charges which were successfully matched to a vehicle VIN number and were processed.
- The second lists all charges that errored out.