Pitney Bowes Interface Program
Version 3.5
Overview
The PITNEY interface program is a DOS program. It is used to convert expense transactions from a Pitney Bowes system to be compatible with the TABS III Merge Data Capture Transactions program. The PITNEY interface program works with the following Pitney Bowes systems:
1) A120, A130, G120, G140, G150, or G170
2) A-10000, Star 190 Carrier Management System, or G-300 series
3) J-700 or Star 700
4) Ascent/Solo
5) Accutrac
If you are using the J-700 or the Ascent/Solo systems, this program can also create a client validation file that can be used by Pitney Bowes. This file will contain a record for each active client/matter that exists in the TABS III Client file.
Note: The Create Validation Files program must be run before you can successfully use this data capture device interface program. The Create Validation Files program is found in TABS III by selecting the following menu options Maintenance|Integration|Create Validation Files. When creating validation files, select a Validation File Type of Data Capture Device.
If you are using the J-700 or the Ascent/Solo systems software, the Create Validation Files program in TABS III must also periodically be run before using the "CV" option so that new clients can be included in the client validation data file (step 4 under Executing the Pitney Bowes Interface Program).
Note: If you previously used the PITNEYA interface program to convert Pitney Bowes transactions, the PITNEY interface program replaces all versions of the PITNEYA program. The PITNEYA program provided compatibility for the AMS 24 system as well as various Pitney Bowes formats. However, this program does not support the AMS 24 system. If you previously owned the PITNEYA program specifically for the AMS 24 system, we will provide you with an upgrade to an interface program specifically written for Ascom Hasler systems.
Specific Systems Notes
A120, A130, G120, G140, G150, or G170: It is assumed that the Pitney Bowes remarks field contains the TABS III client/matter number. Numbers including a decimal separator between the client and matter numbers will be converted as they are. Numbers without a decimal separator will be converted as client numbers appended with zeroes for the matter number. For example, 200.03 would be converted as client 200 and matter 03, while 20003 would be converted as client 20003 and matter 00 (assuming your TABS III key length is 8.2).
A-10000, Star 190 Carrier Management System, or G-300 series: It is assumed that the fields are defined for the following information:
| Translation Date: | Date used for the transaction in TABS III. |
| Charge Field: | Total amount charged for a transaction (surcharges and discounts are ignored). |
| Custom Field: | TABS III Client/Matter Number, which can include or exclude the decimal. For example, 200.03 and 20003 represent the same client 200 and matter 03. |
J-700 or Star 700, Ascent/Solo, and Accutrac systems: Both systems have predefined client/matter fields. They are converted with the same assumptions used with client/matters for the A-10000 system.
Installation
The Pitney Bowes interface program (Pitney.EXE) must be transferred to the directory on your hard disk where the TABS III program files reside. This is done by using the INSTALL program on the Pitney Bowes interface program disk.
To install the Pitney Bowes interface program on your hard disk:
A:
INSTALL
Note: The INSTALL program has a built-in search feature that will find where your TABS III program files reside. On larger network hard drives, this search feature can take quite a bit of time. If you know where the TABS III program files reside, you can bypass this search feature by entering the path following the install command. For example, if the TABS III program files reside on drive F: in a directory named "STI", you would enter: INSTALL F:\STI
Executing the Pitney Bowes Interface Program
Use the following procedure for conversion:
PITNEY
Note: If you want to use a different data file name other than TRAN_CMS.TXT, you can specify that name when executing PITNEY. For example, if your data file name is DATA.TXT, you would enter: PITNEY DATA.TXT
1) A120, A130, G120, G140, G150, or G170
2) A-10000, Star 190 Carrier Management System, or G-300 series
3) J-700 or Star 700
4) Ascent/Solo
5) Accutrac
Next, you will be asked to enter the TABS III transaction code number that you use for
shipping cost transactions.
Note: Both the options entered in Step 3 are stored in a parameter file named PITNEY.PRM. Each time the PITNEY program is executed, it will read the PITNEY.PRM file and use those options automatically.
If you enter "CV" (for Create Validation File), and you are using TABS III version 3.4 or later, this routine will create a client validation data file named CLIENT.DAT in the TABS III program directory. This file will contain a record for each active client/matter that exists in the TABS III Client file. You will be prompted to choose from two available client validation methods. They are as follows:
|
Method |
File Name |
Format |
|
1 |
CLIENT.DAT | Client/Matter Number, Client Name |
|
2 |
CLIENT.DAT | Client/Matter Number, Client Name Search |
If you enter "CD" (for Convert Data), the program will look for the TRAN_CMS.TXT file containing the Pitney Bowes data. If the TRAN_CMS.TXT file is found to contain data, the program will display the message "Converting Transactions" followed by a counter as each transaction is read from the file. The files T3EXPKEY.REM, T3EXP.REM, and T3EDESC1.REM will be created which can be merged with the main TABS III data files. You must then start TABS III and run the Merge Data Capture Transactions program.
Note: If you are running TABS III Version 9, you must first run the Create Validation Files program in TABS III with the Data Capture Device option selected and the Client check box selected before using the "CV" command. If new validation files are not created in TABS III before creating validation files in PITNEY, current client information will not be included in the new validation files for J-700 or the Ascent/Solo systems.
Note: If you are not using a demo version of the program, the data file will automatically be deleted when the conversion is complete to avoid double posting the data.
Note: If any records in the TRAN_CMS.TXT file are rejected for any reason, they will be noted in the PITNEY.ERR file. You can look at this file after the PITNEY program executes to see which records (if any) were not converted. If no records are rejected, the PITNEY.ERR file is not created.
Note: You may change default system type or the cost transaction code used by the Pitney Bowes interface program by deleting the PITNEY.PRM file which is created in your TABS III directory. This will enable you to go through the setup procedure described above in Step 3 as a first time user of the program.