Terminal Alias File (#72, August 2006)

Carriers may set up terminal codes internally for uses not consistent with shipment costing.   The Cost Information System has a terminal alias file, CONVERT.TRM, to convert such terminals to the "real" terminal that they represent in the cost model.   The most common uses of the terminal alias file are for:

1. Terminals that have changed codes mid-period.

2. Terminal codes set up internally to segregate certain freight.

3. Terminal codes representing a specific P&D run or cartage area from a terminal.

4. Accounting codes for freight terminals in the general ledger, if not the same as those used in the model (such as Numeric vs. Alpha).

The conversion file is maintained using the "Terminal Aliases" item under "Service Points" in CIS Profile Maintenance.   Besides the fields for "Non-CIS Terminal" and "CIS Terminal" codes, there is an optional run number / SCAC code that can be specified as well.

In CIS Profile Maintenance, aliases are applied to terminal codes in the General Ledger file, to the Points List file processing, to the Load Plan file processing, if so stated in the file import settings, but only for the linehaul data processing if so requested.

In the Traffic/CIS Database, alias conversions are applied only for the origin and destination terminals in the freight bill record, and not for intermediate terminals unless requested.   They are also applied to the Customer Profile when the edit check is run.

Some examples of entries in the Terminal Alias file:

1. ABC is used internally as the destination terminal for freight given to interline carrier ABC Express at our Chicago Terminal:

Non-CIS Terminal:  ABC
CIS Terminal Code: CHI
Run Number: ABCX (the interline carrier SCAC)

2. Our accounting system uses two-digit numbers for each freight terminal in CIS:

Non-CIS Terminal:  01
CIS Terminal Code: JAX
Run Number:

Non-CIS Terminal:  02
CIS Terminal Code: ATL
Run Number:

etc...

3. Terminal ROC is actually just a long peddle run to Rochester, NY, out of our Buffalo terminal:

Non-CIS Terminal:  ROC
CIS Terminal Code: BUF
Run Number: (specific run set in the system, or 0 if data provided by ZIP Code)

4. Terminal WAL is actually a major shipper picked up via trailer spot by our LAX terminal:

Non-CIS Terminal:  WAL
CIS Terminal Code: LAX
Run Number: (only if a specific run for the shipper is set up)

When used in CIS, aliases are NOT retained, once converted to the real terminal code.   In each routine that uses the alias file, the file is searched for a match to an alias code, and then the terminal, and run number if applicable, are replaced.

User Notes | Home

Contact TCG:
Phone: 800-328-9700
E-Mail: kmm@tcgcis.com
Address: 1355 Piccard Drive, Suite 310, Rockville, MD 20850
This site best viewed with: