OVERVIEW:

The one-way process is really a uucico command combined with a CARS+ merge program similar to the RESINT programs. The getoneway script in the /usr/bin directory executes a uucico command to the hpux14 machine. It then takes the file(s) from the uucppublic directory, merges them into CARS+, generating a merge report, and moves them to the /usr/carsplus/htzspool directory. Copies of the merge reports are held in the /usr/carsplus/oneway directory. The getoneway script is called at certain times during the day from crontab if the user has a dedicated modem. If not, the files are retrieved during the EDRB process and merged at the next interval in the crontab.
Below are some of the basic questions asked by the user that are not listed in the manual pages.

Q: One of my contracts was closed at an ASAP location, and now the vehicle has no status.
A: The system has no way to know that the closing location is within return-rent distance, so no status is applied. This allows the user to either set the status as "A" if the vehicle is to be rented back, or "N" indicating that the vehicle will be brought back as a Non-Rev vehicle. Here is an example:
A vehicle is rented in Los Angeles and the renter says he will return it to LA. Her returns the car instead to Seattle. This vehicle will never be rented back to LA, and will be transported back. The status should be "N".

Q: One of my RA's was closed at an ASAP location, and shows no payment at all.
A: This indicates the FOP was changed at close to something other than cash. If the FOP is changed to cash, a payment will appear indicating the closing location as the FOP. Contact the closing location for payment detail.

Q: The message "RA not open" appears on the merge report.
A: This RA was closed in Foreign RA entry prior to the ASAP file being merged. Do nothing.

Q: The message " RA MERGED TO ONEWAY FILE" appears on the merge report.
A: This RA was merged in the one-way file. Do nothing.

Q: The message " RA RECORD NOT FOUND IN CARS+ RA FILE" appears on the merge report.
A: This is a local RA closed at an ASAP location. The RA could not be found in the RAFILE. Either the location that opened the RA is a manual location and had not batch opened the RA yet, or the RA was deleted.

Q: The message " CARS+ RA RECORD NOT OPEN " appears on the merge report.
A: This is a local RA closed at an ASAP location. The RA was found, but was not "O" status.

Q: The message " CUSTOMER RECORD FOR CLOSING LOCATION NOT FOUND " appears on the merge report.
A: This is a local RA closed at an ASAP location. The closing location (indicated on the printout) either does not exist in the customer file, or there is no conversion record mapping what Hertz sent to the correct customer record.

Q: The message " RA CLOSED: RA EXCHANGED, NEEDS REVIEW " appears on the merge report.
A: This is a local RA closed at an ASAP as an exchange. Another RA was opened. Contact the closing location and review the charges on the RA with them directly.

Q: When I run my DBRA, all of my contracts that closed at ASAP locations with a foreign vehicle are showing 100% of revenue owed to the owning location.
A: Since the system can't know if a location is closer or farther from the owning location, it defaults to 100% to owner. The user must pull these RA's up on the close/edit close screen & re-save the contract. The user will be prompted with the question "One Way Towards Owner?", and depending on the answer, the correct split will be applied. NOTE: Since an EDRB'd RA cannot be edited, the user must run the DBRA BEFORE running a real EDRB run. This is a change in normal procedure.

Q: I manually closed a foreign RA that was not in the ONE-WAY file. The RA was then received. How do I close this RA?
A: If you do not have the RA in the ONE-WAY file, you can close the RA in Foreign RA Entry. If you have not closed the RA in the system, and the RA is then received, you can go to the ASAP Close program thru the Hertz/ASAP menus. By accessing the program this way, the user can access the date/time fields to batch close the RA.