- Created by Heidi Adams, last modified on Apr 20, 2023
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 55 Next »
Keywords
Ticket Keywords are database fields or command fields stored in the Interact database used for designing printed tickets. These fields are placed on a ticket by enclosing the field keyword in square brackets ([]).
The following is the list of available ticket keywords:
General Fields
Field Keyword | Additional Information |
LOCATION | Show transaction location name. |
TICKET NUMBER | Ticket number assigned to the transaction. |
TICKET NUMBER GROUP | Ticket number group assigned to the transaction. NOTE: Can also use SITE |
TICKET ITEMS | The total number of items on a multiple item ticket. |
TICKET SEQUENCE | The item number on a multiple item ticket. |
CHARGE TYPE | C=charge, R=Receipt, F=finance chg, M=credit, V=Voided |
CASH TICKET | Export value is True or False. (Type=C, Payment=Charge, Charge<> 0) |
CHARGE TICKET | Export value is True or False. (Type=C, Payment=0, Charge<> 0) |
NO CHARGE TICKET | Export value is True or False. (Type=C, Payment=0, Charge=0) |
INVOICE NUMBER | The number of the invoice this ticket appears. |
INVOICE TERMS | The payment terms for this invoice. |
INVOICE DISCOUNT | The amount of the discount for early payment. |
INVOICE DISCOUNT DATE | The discount early payment date. |
INVOICE LESS DISCOUNT | The invoice total less the discount. |
DATE IN | Date only in system's default format. |
TIME IN | Time only in system's default format. Denotes AM or PM |
DATETIME IN | Date and time in system's default format. Denotes AM or PM |
DATE OUT | Date only in system's default format. |
TIME OUT | Time only in system's default format. Denotes AM or PM |
DATETIME OUT | Date and time in system's default format. Denotes AM or PM |
DATE EDITED | Date only in system's default format. |
TIME EDITED | Time only in system's default format. Denotes AM or PM |
DATETIME EDITED | Date and time in system's default format. Denotes AM or PM |
NOTES 1 (2, 3, 4, ... 21,22, 23) | Notes attached to the ticket. |
DAILY NOTE | Exports whatever the daily note value is now. (Not stored with ticket.) |
TIME IN24 | Shows Time In in military time (24 hour format) |
TIME OUT24 | Show Time Out in military time (24 hour format) |
TRUNC X | Truncate output of the command to the specified length. Used INSIDE of brackets. Example: [HAULER DESCRIPTION TRUNC 10]. |
USE REV 6 SPACING | Use with tickets converted from Revision 6 to Revision 7 to closely match line spacing from Interact 6. Optional, will not always be required. This command should be at the very top of the file. |
[Copy Ticket] “0.0” replace 0.0 with the vertical position of the next copy. | Added to Revision 7.#.# - ability to print multiple copies of a ticket on a page when using a Windows printer. |
Hauler Fields
Field Keyword | Additional Information |
HAULER ACCOUNT | The account that owns the truck. |
HAULER NAME | |
HAULER CONTACT1 (2 or 3) | 1st, 2nd or 3rd Hauler contact |
HAULER ADDRESS1 (2 or 3) | 1st, 2nd or 3rd Hauler address |
HAULER ALTADDRESS1 (2 or 3) | 1st, 2nd or 3rd Hauler alternate address |
HAULER CITY1 (2 or 3) | 1st, 2nd or 3rd Hauler city |
HAULER STATE1 (2 or 3) | 1st, 2nd or 3rd Hauler state |
HAULER ZIP1 (2 or 3) | 1st, 2nd or 3rd Hauler zip |
HAULER PHONE1 (2 or 3) | 1st, 2nd or 3rd Hauler phone number |
Bill-To Account Fields
Field Keyword | Additional Information |
ACCOUNT | Bill-to account. |
ACCOUNT NAME | |
ACCOUNT CONTACT1 (2 or 3) | 1st, 2nd or 3rd Account contact |
ACCOUNT ADDRESS1 (2 or 3) | 1st, 2nd or 3rd Account address |
ACCOUNT ALTADRESS1 (2 or 3) | 1st, 2nd or 3rd Account alternate address |
ACCOUNT CITY1 (2 or 3) | 1st, 2nd or 3rd Account city |
ACCOUNT STATE1 (2 or 3) | 1st, 2nd or 3rd Account state |
ACCOUNT ZIP1 (2 or 3) | 1st, 2nd or 3rd Account zip |
ACCOUNT PHONE1 (2 or 3) | 1st, 2nd or 3rd Account phone number |
ACCOUNT EXEMPT | Prints account tax code. |
ACCOUNT NOTE1 (2, 3, 4, or 5) | Customer Specific note fields 1 – 5 |
Job Fields
Field Keyword | Additional Information | |
JOB | Job number. | |
JOB NAME | ||
JOB PO | Job Purchase Order Number | |
JOB ORDER DATE | Provides the order date stored in the Job. Available in 6.1.1990+ | |
JOB RELEASE | Job Release Number | |
JOB INSTRUCTION1 | Delivery instructions, line 1 This field is also used to display update tare information when a ticket is printed after a tare weight has been updated. This field is in the default UPDTARE.GTK file. When used, one of the following lines of information will print on the ticket. Below minimum tare. Update not allowed Above maximum tare. Update not allowed Tare update not allowed! Tare weight updated! | |
JOB INSTRUCTION2 | Delivery instructions, line 2 | |
JOB INSTRUCTION3 | Delivery instructions, line 3 | |
JOB INSTRUCTION4 | Delivery instructions, line 4 | |
JOB NOTES 1 or JOB USER DATA 1 | Custom user field 1 | |
JOB NOTES 2 or JOB USER DATA 2 | Custom user field 2 | |
JOB NOTES 3 or JOB USER DATA 3 | Custom user field 3 | |
JOB NOTES 4 or JOB USER DATA 4 | Custom user field 4 | |
JOB NOTES 5 or JOB USER DATA 5 | Custom user field 5 | |
LOADS | Number of loads for this job item | |
ORDERED optional unit name | Amount ordered of this item | |
DELIVERED optional unit name | Amount delivered of this item | |
REMAINING optional unit name | Amount remaining to be delivered | |
DAILY DELIVERED optional unit name | Amount delivered for the day | |
DAILY LOADS | Number of loads for the day | |
JOB SHIPTO COMPANY | ShipTo Company | |
JOB SHIPTO CONTACT | ShipTo Contact | |
JOB SHIPTO ADDRESS | ShipTo Address | |
JOB SHIPTO ALTADDRESS | ShipTo Alternate Address | |
JOB SHIPTO CITY | ShipTo City | |
JOB SHIPTO STATE | ShipTo State | |
JOB SHIPTO ZIP | ShipTo Zip | |
JOB SHIPTO PHONE | ShipTo Phone | |
JOB SHIPTO FAX | ShipTo Fax | |
JOB SHIPTO EMAIL | ShipTo E-mail | |
JOB BILLTO COMPANY | BillTo Company | |
JOB BILLTO CONTACT | BillTo Contact | |
JOB BILLTO ADDRESS | BillTo Address | |
JOB BILLTO ALTADDRESS | BillTo Alternate Address | |
JOB BILLTO CITY | BillTo City | |
JOB BILLTO STATE | BillTo State | |
JOB BILLTO ZIP | BillTo Zip | |
JOB BILLTO PHONE | BillTo Phone | |
JOB BILLTO FAX | BillTo Fax | |
JOB BILLTO EMAIL | BillTo E-mail |
Truck Fields
Replace TRUCK with the label assigned in Setup | Configure - Trucks, Etc. Example: Truck
Field Keyword | Additional Information |
TRUCK NUMBER | Truck number. |
TRUCK DESCRIPTION | Truck description. |
TRUCK BADGE | Truck badge. |
TRUCK TARE WEIGHT opt unit name | Truck tare weight. |
TRUCK TARE SETDATE | The date truck tare weight was set. |
TRUCK TARE EXPDATE | The date truck tare weight expires. |
TRUCK LOADS | Number of loads of this item hauled today by this truck |
TRUCK DELIVERED opt unit name | Amount delivered of this item today by this truck |
EXPIRED TARE | Prints ‘EXPIRED TARE’ on the ticket when the tare weight of the truck has expired. |
AXLES | Number of axles on this truck |
LICENSE | License number |
TRUCK MAX WEIGHT | Maximum Gross Weight Set for the truck |
TRUCK USER DATA 1 | User Data 1 Field |
TRUCK USER DATA 2 | User Data 2 Field |
TRUCK USER DATA 3 | User Data 3 Field |
TRUCK USER DATA 4 | User Data 4 Field |
TRUCK USER DATA 5 | User Data 5 Field |
TRUCK NOTES 1 | NOTES 1 Field |
TRUCK NOTES 2 | NOTES 2 Field |
Tare 2 Fields
Replace TARE2 with the name assigned in Setup | Configure - Trucks, Etc.. Example: Trailer
Field Keyword | Additional Information |
TARE2 NUMBER | 2nd tared vehicle number. |
TARE2 DESCRIPTION | 2nd tared vehicle description. |
TARE2 TARE WEIGHT opt unit name | 2nd tared vehicle tare weight. |
TARE2 TARE SETDATE | The date tare weight for 2nd tared vehicle was set. |
TARE2 TARE EXPDATE | The date 2nd tared vehicle tare weight expires. |
Tare 3 Fields
Replace TARE3 with the name assigned in Setup | Configure - Trucks, Etc.. Example: Container
Field Keyword | Additional Information |
TARE3 NUMBER | 3nd tared vehicle number. |
TARE3 DESCRIPTION | 3nd tared vehicle description. |
TARE3 TARE WEIGHT opt unit name | 3nd tared vehicle tare weight. |
TARE3 TARE SETDATE | The date tare weight for 3nd tared vehicle was set. |
TARE3 TARE EXPDATE | The date 3nd tared vehicle tare weight expires. |
Material Table Fields
Replace MATERIAL with name assigned in Setup | Configure - Material
program ini file, [Material Settings] section.
Field Keyword | Additional Information |
MATERIAL CODE | |
MATERIAL DESCRIPTION | |
MATERIAL USER DATA 1 | User defined field 1 |
MATERIAL USER DATA 2 | User defined field 2 |
MATERIAL USER DATA 3 | User defined field 3 |
MATERIAL USER DATA 4 | User defined field 4 |
MATERIAL USER DATA 5 | User defined field 5 |
Price Table Fields
Replace PRICE TABLE with name assigned in Setup | Configure - Price Table section.
Field Keyword | Additional Information |
PRICE TABLE CODE | |
PRICE TABLE DESCRIPTION | |
PRICE TABLE USER DATA 1 | User defined field 1 |
PRICE TABLE USER DATA 2 | User defined field 2 |
PRICE TABLE USER DATA 3 | User defined field 3 |
PRICE TABLE USER DATA 4 | User defined field 4 |
PRICE TABLE USER DATA 5 | User defined field 5 |
Location Fields
Field Keyword | Additional Information |
LOCATION | |
LOCATION CODE | |
LOCATION USER DATA 1 | |
LOCATION USER DATA 2 | |
LOCATION USER DATA 3 | |
LOCATION USER DATA 4 | |
LOCATION USER DATA 5 |
Company Data Fields
This data is set in Setup | Configure | Company Data
Field Keyword | Additional Information |
COMPANY NAME | |
COMPANY ADDRESS | |
COMPANY ADDRESS2 | |
COMPANY CITY | |
COMPANY STATE | |
COMPANY ZIP | |
COMPANY PHONE | |
COMPANY FAX |
Category Fields
Replace CATEGORY1 - CATEGORY4 with names assigned in Setup | Configure - Category 1 - 4 section.
Field Keyword | Additional Information |
CATEGORY1 CODE | |
CATEGORY2 CODE | |
CATEGORY3 CODE | |
CATEGORY4 CODE | |
CATEGORY1 DESCRIPTION | |
CATEGORY2 DESCRIPTION | |
CATEGORY3 DESCRIPTION | |
CATEGORY4 DESCRIPTION | |
CATEGORY1 USER DATA 1 | User defined field 1 |
CATEGORY1 USER DATA 2 | User defined field 2 |
CATEGORY1 USER DATA 3 | User defined field 3 |
CATEGORY1 USER DATA 4 | User defined field 4 |
CATEGORY1 USER DATA 5 | User defined field 5 |
CATEGORY2 USER DATA 1 | |
CATEGORY2 USER DATA 2 | |
CATEGORY2 USER DATA 3 | |
CATEGORY2 USER DATA 4 | |
CATEGORY2 USER DATA 5 | |
CATEGORY3 USER DATA 1 | |
CATEGORY3 USER DATA 2 | |
CATEGORY3 USER DATA 3 | |
CATEGORY3 USER DATA 4 | |
CATEGORY3 USER DATA 5 | |
CATEGORY4 USER DATA 1 | |
CATEGORY4 USER DATA 2 | |
CATEGORY4 USER DATA 3 | |
CATEGORY4 USER DATA 4 | |
CATEGORY4 USER DATA 5 |
Tax Fields
Field Keyword | Additional Information |
TAX CODE | Tax code |
TAX DESCRIPTION | Description of tax code |
Freight Fields
Field Keyword | Additional Information |
ZONE CODE | Delivery zone code |
ZONE DESCRIPTION | Delivery zone description |
DISTANCE | Distance or time hauled |
User Fields
Field Keyword | Additional Information |
USER NUMBER | System assigned user number for weigh in operator |
USER LOGIN | User's eight character login name for weigh in operator |
USER NAME | User's full name for weigh in operator |
USER NUMBER OUT | System assigned user number for weigh out operator |
USER LOGIN OUT | User's eight character login name for weigh out operator |
USER NAME OUT | User's full name for weigh out operator |
USER NOTE1 | User Note 1 for the weigh out operator |
USER NOTE2 | User Note 2 for the weigh out operator |
USER NOTE3 | User Note 3 for the weigh out operator |
USER NOTE4 | User Note 4 for the weigh out operator |
USER NOTE5 | User Note 5 for the weigh out operator |
Weight Fields
Field Keyword | Additional Information |
WEIGHT IN optional unit name | Incoming weight |
WEIGHT OUT optional unit name | Outgoing weight |
NET WEIGHT optional unit name | Absolute value of weight in less weight out. |
GROSS optional unit name | The greater of weigh-in and weigh-out. |
TARE optional unit name | The lesser of weigh-in and weigh-out. |
ADJ WEIGHT optional unit name | Net weight less adjustments |
GRAND TOTAL ADJ WEIGHT required UOM name | Total adjusted weight for all items in a multiple item ticket. One additional keyword UOM must be used. Valid UOM keywords are; POUNDS, TONS, KILOGRAMS, METRIC TONS, YARDS, and COUNT. Keyword is only valid in the Footer (F) lines of the ticket format file. The keyword can be used multiple times to print each possible UOM. For example, the footer of the ticket format file may contain keywords for both [GRAND TOTAL ADJ WEIGHT TONS] and [GRAND TOTAL ADJ WEIGHT COUNT], perfect for a multiple item solid waste ticket. |
CONV WEIGHT1 | Scale weight converted to user units 1 as defined in material table. This will use the Adjusted net weight (TransWeightAdj).. Notes on CONV WEIGHT1/WEIGHT2: if you use an additional keyword CONV WEIGHT1 UNADJ, This will use TransWeightNet weight for the calculation rather than the adjusted net weight. If you use CONV WEIGHT1 DISC, this will give you the difference between Net and Adjusted Net converted. |
CONV WEIGHT2 | Scale weight converted to user units 2 as defined in material table. See additional notes on CONV WEIGHT1 |
CONV WEIGHT1 UNITS | Converted scale weight plus description. Example: 7200 Gallons |
CONV WEIGHT2 UNITS | Converted scale weight plus description. Example: 3200 Barrels |
TICKET WEIGHT | Scale weight converted to ticket unit of measure (See UNIT keyword). |
SCALE IN | Weigh-in scale (1 or 2). |
SCALE OUT | Weigh-out scale (1 or 2). |
ADJUSTMENT1 | % of load, Adjusted = Net x Percentage |
ADJUSTMENT2 | % deducted, Adjusted = Adjusted - (Adjusted x Percentage) |
SCALE IN NAME | Weigh-in scale (1 or 2) = name of scale. |
SCALE OUT NAME | Weigh-out scale (1 or 2) = name of scale. |
UNIT NAME | Ticket Unit text value (Pounds, Tons, etc.) instead of numeric value |
AXLE1 | First axle weighment, not NTEP compliant |
AXLE2 | Second axle weighment, not NTEP compliant |
AXLE3 | Third axle weighment, not NTEP compliant |
AXLE4 | Forth axle weighment, not NTEP compliant |
AXLE5 | Fifth axle weighment, not NTEP compliant |
PO | Transaction PO |
Unit of Measure Fields
Field Keyword | Additional Information |
SCALE UNIT | The unit displayed on the scale indicator (pounds = lb. kilograms = kg) |
UNIT | Adding this unit name keyword within the square brackets of any weight keyword will make the ticket unit print with the weight. The unit printed on the ticket (pounds = lb, yards = Yd, unit count = Un, kilograms = kg, tons = Ton, metric tons = Metric ton). |
UNIT1 | Prints "Load" if price component 1 is a per load charge, else prints the ticket unit of measure. |
UNIT2 | Prints "Load" if price component 2 is a per load charge, else prints the ticket unit of measure. |
UNIT3 | Prints "Load" if price component 3 is a per load charge, else prints the ticket unit of measure. |
UNITS | Same as UNIT except plural (appends the letter s). |
UNITS1 | Same as UNIT1 except plural (appends the letter s). |
UNITS2 | Same as UNIT2 except plural (appends the letter s). |
UNITS3 | Same as UNIT3 except plural (appends the letter s). |
POUNDS | Adding this unit name keyword within the square brackets of any weight or rate keyword will convert the weight or rate to pounds. |
TONS | Adding this unit name keyword within the square brackets of any weight or rate keyword will convert the weight or rate to tons. |
KILOGRAMS | Adding this unit name keyword within the square brackets of any weight or rate keyword will convert the weight or rate to kilograms. |
METRIC TONS | Adding this unit name keyword within the square brackets of any weight or rate keyword will convert the weight or rate to metric tons. |
2Decimals | Adding this keyword with the Net Weight within the square brackets will format the field to contain two decimal places; 0.00. It will work when used with other Unit Name Keywords; but must be placed before the unit name i.e. [Net Weight 2Decimals Pounds]. |
SUPPRESS_CR | Can be appended to the //xxx// line to suppress the CR of a line when sent to the “Serial” printer definition. |
Variables, Calculations, and Strings
The VAR1 and VAR2 ticket keywords are used to store numeric values for simple calculations. More information and examples can be found in Utilities | Ticket Editor - Variables and Calculations.
The STR1 string command can be used with VAR commands to create simple IF statements. More information and examples can be foud in Utilities | Ticket Editor - Using Strings for Simple IF Statements.
"IMPORTANT: The VAR and STR1 commands must be in ALL CAPITALS"
Field Keyword | Additional Information |
VAR1 | Set VAR1 to a database field value or constant. Database fields must be surrounded by square brackets [ ]. Constants must be surrounded by double quotes " ". A space must separate the VAR1 from the command. |
VAR2 | Set VAR2 to a database field value or constant. Database fields must be surrounded by square brackets [ ]. Constants must be surrounded by double quotes " ". A space must separate the VAR2 from the command. |
VAR ADD | VAR1 + VAR2 |
VAR SUB | VAR1 - VAR2 |
VAR MULT | VAR1 * VAR2 |
VAR DIV | VAR1 / VAR2 |
VAR DIV0 | Characters 0,2,4,6 are allowed after the math type [VAR DIV2] to define the number of places after the decimal point to be printed |
IF STR1 EQ "value" | Choose text to output to ticket line based on string value |
IF STR1 NULL | Choose text to output to ticket line if string is NULL |
If VAR1 EQ "value" | Choose text to output to ticket line based on variable value |
Charge Fields
Field Keyword | Additional Information |
BASE CHARGE | BASE CHARGE1 + BASE CHARGE2 + BASE CHARGE3 |
GRAND TOTAL BASE CHARGE | Total base charge for all items in a multiple item ticket. |
BASE CHARGE1 | Adjusted Weight x Rate 1. |
GRAND TOTAL BASE CHARGE1 | Total base charge 1 for all items in a multiple item ticket. |
BASE CHARGE2 | Adjusted Weight x Rate 2 |
GRAND TOTAL BASE CHARGE2 | Total base charge 2 for all items in a multiple item ticket. |
BASE CHARGE3 | Adjusted Weight x Rate 3 |
GRAND TOTAL BASE CHARGE3 | Total base charge 3 for all items in a multiple item ticket. |
BASE CHARGE12 | BASE CHARGE1 + BASE CHARGE2 |
BASE CHARGE13 | BASE CHARGE1 + BASE CHARGE3 |
BASE CHARGE23 | BASE CHARGE2 + BASE CHARGE3 |
FREIGHT CHARGE | Freight Charge |
BASE + FREIGHT CHARGE | Total BASE charge + Freight Charge |
ADDED + FREIGHT CHARGE | Added Charge + Freight Charge |
GRAND TOTAL FREIGHT CHARGE | Total freight charge for all items in a multiple item ticket. |
GRAND TOTAL BASE + FREIGHT CHARGE | Grand total base charge plus grand total freight charge for a multiple item ticket |
GRAND TOTAL ADDED + FREIGHT CHARGE | Grand total Added Charge + Freight Charge for a multiple item ticket. |
FREIGHT CHARGE PAYABLE | Freight Charge payable to hauler |
GRAND TOTAL FREIGHT CHARGE PAYABLE | Total freight charge payable for all items in a multiple item ticket. |
ADDED CHARGE | Added Charge |
BASE + ADDED CHARGE | Total BASE charge + Added Charge |
GRAND TOTAL ADDED CHARGE | Grand total of added charges for all items in a multiple item ticket |
GRAND TOTAL BASE + ADDED CHARGE | Grand total base charge plus grand total added charge for a multiple item ticket |
CHANGE DUE | Change due customer in cash transaction |
AMOUNT TENDERED | Calculated from total charge + change due |
CHARGE | Total charge |
GRAND TOTAL CHARGE | Grand total of charges for all items in a multiple item ticket |
CHARGE NOTES | Add all the following values that apply to this ticket 1 - Minimum charge applied 2 - Weigh-in is a stored tare 4 - Weigh-in was keyed 8 - Ticket was edited 16 - Reprinted ticket 32 - Imported ticket 64 - Charge has been imported 128 - Weigh-out is a stored tare 256 - Weigh-out was keyed 512 - Weigh-in occurred on scale 2 1024 - Weigh-out occurred on scale 2 2048 - Axle weighment |
Sales Tax Fields
Field Keyword | Additional Information |
SALES TAX | Total sales tax |
GRAND TOTAL SALES TAX | Grand total of sales tax for all items in a multiple item ticket |
FREIGHT TAX | Freight Tax |
GRAND TOTAL FREIGHT TAX | Grand total of freight tax for all items in a multiple item ticket |
SALES TAX1 | Sales tax (dollar amount) associated with taxing authority 1 of tax code |
GRAND TOTAL SALES TAX1 | Grand total of sales tax 1 for all items in a multiple item ticket |
SALES TAX2 | Sales tax (dollar amount) associated with taxing authority 2 of tax code |
GRAND TOTAL SALES TAX2 | Grand total of sales tax 2 for all items in a multiple item ticket |
SALES TAX3 | Sales tax (dollar amount) associated with taxing authority 3 of tax code |
GRAND TOTAL SALES TAX3 | Grand total of sales tax 3 for all items in a multiple item ticket |
SALES TAX4 | Sales tax (dollar amount) associated with taxing authority 4 of tax code |
GRAND TOTAL SALES TAX4 | Grand total of sales tax 4 for all items in a multiple item ticket |
SALES TAX5 | Sales tax (dollar amount) associated with taxing authority 5 of tax code. |
GRAND TOTAL SALES TAX5 | Grand total of sales tax 5 for all items in a multiple item ticket |
SALES TAX12 | SALES TAX1 + SALES TAX2 |
SALES TAX13 | SALES TAX1 + SALES TAX3 |
SALES TAX14 | SALES TAX1 + SALES TAX4 |
SALES TAX15 | SALES TAX1 + SALES TAX5 |
SALES TAX23 | SALES TAX2 + SALES TAX3 |
SALES TAX24 | SALES TAX2 + SALES TAX4 |
SALES TAX25 | SALES TAX2 + SALES TAX5 |
SALES TAX34 | SALES TAX3 + SALES TAX4 |
SALES TAX35 | SALES TAX3 + SALES TAX5 |
SALES TAX45 | SALES TAX4 + SALES TAX5 |
GRAND TOTAL TAX | Grand total of SALES TAX + FREIGHT TAX for all items in a multiple item ticket |
Payment Fields
Field Keyword | Additional Information |
TAX CODE | Tax code |
TAX DESCRIPTION | Description of tax code |
PAYMENT | |
GRAND TOTAL PAYMENT | Total payments for all items in a multiple item ticket |
CHECK NUMBER | Grabs the input value from either the Check# or Slip# field |
Price Fields
Unit of Measure Fields
Go to the Unit of Measure Fields section of this document to view valid 'optional unit name' UOM additions.
Field Keyword | Additional Information |
RATE optional unit name | Total price excluding per load prices |
RATE PER LOAD | Total per load price |
RATE1 optional unit name | Price component 1 |
RATE2 optional unit name | Price component 2 |
RATE3 optional unit name | Price component 3 |
RATE12 optional unit name | RATE1 + RATE2 (excludes per load prices) |
RATE13 optional unit name | RATE1 + RATE3 (excludes per load prices) |
RATE23 optional unit name | RATE2 + RATE3 (excludes per load prices) |
RATE1 PER LOAD | Is RATE1 a per load charge? (0 = false, -1 = true) Can be exported as a boolean field |
RATE2 PER LOAD | Is RATE2 a per load charge? (0 = false, -1 = true) Can be exported as a boolean field. |
RATE3 PER LOAD | Is RATE3 a per load charge? (0 = false, -1 = true) Can be exported as a boolean field |
FREIGHT RATE | Freight price |
FREIGHT RATE PAYABLE | Freight price payable to hauler |
FREIGHT RATE PER LOAD | Is FREIGHT RATE a per load charge? (0=false, -1=true) |
FREIGHT RATE PAYABLE PER LOAD | Is FREIGHT RATE PAYABLE a per load charge? (0=false, -1=true) |
CONV RATE UNIT | Prints the converted rate unit (e.g. "Gallons" or "Barrels") |
UNITS FOR CHARGE | Prints the name of the user-defined unit if it is used to calculate the charge, will otherwise print the transaction unit. |
CONV RATE | Prints the total price per user unit (3/3/22 - Not available) |
CONV RATE1 | Prints price component 1 per user unit (3/3/22 - Not available) |
CONV RATE2 | Prints price component 2 per user unit (3/3/22 - Not available) |
CONV RATE3 | Prints price component 3 per user unit (3/3/22 - Not available) |
CONV RATE12 | CONV RATE1 + CONV RATE2 (3/3/22 - Not available) |
CONV RATE23 | CONV RATE2 + CONV RATE3 (3/3/22 - Not available) |
CONV RATE13 | CONV RATE1 + CONV RATE3 (3/3/22 - Not available) |
FIXED CHARGE MULT | Fixed Charge Multiplier value (Setup | Configure | Prices | Added Charges) |
Credit Card Printed Ticket Keywords
Go to the Electronic Credit Card Processing - Printed Ticket Requirements page for additional information.
Static Images
Before an image can be printed on a ticket the image must be uploaded to the database. To add or delete images to a database, select Setup | Configure - Static Images.
Static Images are considered a flag field and therefore enclosed in curly brackets ({}). Images can be added to a ticket design using the following command: {IMAGE "filename,Horizontal,Vertical,Width,Height"}. The following example will print the Bedrock SGLogo image in the top left corner of a ticket.
{IMAGE "filename,Horizontal,Vertical,Width,Height"}
Command - IMAGE
Filename - Name of image in static images table
Horizontal Position (X) -in inches @ 90 DPI
Vertical Position (Y) - in inches @ 90 DPI
Width of Image - in inches @ 90 DPU
Height of Image - in inches @ 90 DPI
{IMAGE "Bedrock SGLogo,0,0,2.75,1.0"}
Command - IMAGE
Filename - Bedrock SGLogo
Horizontal Position (X) - 0.0 Inches
Vertical Position (Y) - 0.0 Inches
Width of Image - 2.75 Inches
Height of Image - 1.0 Inches
Image Name
Use only the filename. The file extension (JPG, PNG, or BMP) is not required. The image will not appear if the file extension is included.
Multiple images can be printed on a ticket. Simply add another command line and ensure the size and position of the additional image or images do not overlap with other images. The following is an example with two command lines to print two different logos.
H {IMAGE "Bedrock SGLogo,0,0,2.75,1.0"}
H {IMAGE "awslogo,0,4.0,2.75,1.5"}
The first image is the same as the above example. The second image uses the following parameters
{IMAGE "awslogo,0,4.0,2.75,1.5"}
Command - IMAGE
Filename - awslogo
Horizontal Position (X) - 0.0 Inches
Vertical Position (Y) - 4.0 Inches
Width of Image - 2.75 Inches
Height of Image - 1.5 Inches
The awslogo will be a little taller than the Bedrock SGLogo, 1.5 inches vs. 1 inch. and will print four (4) inches (vertical position) from the top of the page. The Bedrock SGLogo is set to print a the very top.
A sample ticket using this format can be found in Sample Ticket Designs page.
Dynamic Images
Create filename
A dynamic image is any image captured by one of our hardware devices such as cameras or a signature capture device. All captured images are stored in C:\ProgramData\AWS\Interact\Images folder. Up to nine (9) different images can be captured for each transaction ticket.
The following information from Interact is used to create the image filename when the image is captured and the transaction stored in the database. This structure ensures the file will have a unique name.
- Ticket Number Group_Ticket Number_Sequence Number_TImage Number.jpg
When the DYNAMICIMAGE command is called, Interact will search for all images that match the above information to know which images are to be printed on the ticket.
Setting the Image Number
As mentioned above, up to nine (9) different images can be captured for each transaction. The image number is assigned when unattended prompting is configured. To learn more about configuring unattended prompts, go to the Setup | Unattended page.
Command Syntax
Dynamic Images are considered a flag field and therefore enclosed in curly brackets ({}).
- {DYNAMICIMAGE "Image Number 1 - 9,Horizontal,Vertical,Width,Height"}
- Command - DYNAMICIMAGE
- Image Number - Valid numbers are 1 - 9 to accommodate the nine image limit
- Horizontal Position (X) -in inches @ 90 DPI
- Vertical Position (Y) - in inches @ 90 DPI
- Width of Image - in inches @ 90 DPU
- Height of Image - in inches @ 90 DPI
The following is a sample filename created by Interact during an unattended transaction where a prompt has triggered the system to capture an image from a camera. The filename follows along with most of the samples throughout this documentation.
- Scale_700_0_T1.jpg
- Ticket Number Group - Scale (To learn more about Ticket Number Groups go to the Ticket Number Groups page.)
- Ticket Number - 700 (To learn more about Ticket Numbers go to the Ticket Numbers page.)
- Sequence Number - 0 (Represents the item number on a multiple item transaction. As of January 2022, Interact 7 is not configured to process unattended multiple item transactions and the sequence number should always be 0)
- TImage Number - The number assigned when unattended prompting is configured, 1- 9.
The command line to print image number 1 on a ticket will look similar to the following.
- {DYNAMICIMAGE "1,0,0,2.75,1.0"}
- Command - DYNAMICIMAGE
- Image Number- 1
- Horizontal Position (X) - 0.0 Inches
- Vertical Position (Y) - 0.0 Inches
- Width of Image - 2.75 Inches
- Height of Image - 1.0 Inches
The image will print in the top left corner of the ticket. It will be 2.75 inches wide and 1.0 inch tall.
Dynamic Image
There are no spaces after the commas in the command line.
Flag Fields
A flag is set in the database whenever a special condition has been met by a transaction. These conditions are:
Field Keyword | Additional Information |
Minimum Charge | A minimum charge has been applied to this transaction |
Keyed Weigh In | The weight on a weigh-in has been manually entered |
Keyed Weigh Out | The weight on a weigh-out has been manually entered |
Keyed Gross | Gross weight has been manually entered |
Keyed Tare | Tare weight has been manually entered |
Recalled Weigh In | Weigh-in weight has been recalled |
Recalled Weigh Out | Weigh-out weight has been recalled (stored tare) |
Recalled Gross | Gross weight has been recalled |
Recalled Tare | Tare weight has been recalled |
Cash | This is a cash transaction (amnt paid = charge) |
Cash By Check | This is a cash transaction paid by check (check number is not blank) |
Cash By Money | This is a cash transaction paid by cash (check number is blank) |
Cash By CreditCard | This is a cash transaction paid by credit card (credit card radio button is selected during transaction) |
Charge | This is a charge transaction (paid = 0 and charge > 0) |
No Charge | This is a no charge transaction (paid = 0 and charge = 0) |
Edited | The transaction has been edited |
Reprint | The ticket for this transaction is being reprinted (i.e. from the Quick Scan form) |
Incoming | This is a incoming transaction (weigh-in > weigh-out) |
Outgoing | This is a outgoing transaction (weigh-out > weigh-in) |
A user defined static text field can be associated with each of these conditions. A flag field is enclosed in curly brackets ({}). The example below assigns the static text, "Keyed", to the Keyed Weigh In flag. This text will be printed on the ticket whenever the Keyed Weight flag is set for a transaction.
- {Keyed Weigh In "Keyed"} - assigns the static text, "Keyed" to the Keyed Weigh In flag. When this condition is met by manually entering a weight in the weight in field, the text 'Keyed' will print on the ticket.
- {Reprint "Ticket Reprinted"} - assigns the static text, 'Ticket Reprinted' to the Reprint flag. When this condition is met by selecting Reprint Ticket from the Weigh form or the transaction editor, the text 'Ticket Reprinted' will print on the ticket.
- {Edited "Edited Ticket"} - assigns the static text, 'Edited Ticket' to the Edited flag. When this condition is met, by editing a ticket in the transaction editor the text 'Edited Ticket' will print on the ticket.
- Ticket Configuration and Overview
- How to Design a Ticket Ticket Design
- Font and Positioning Commands
- Ticket Extensions
- Static Images
- Using Strings
- Variables and Calculations
- Ticket Priority and Custom Ticket Designs
- Ticket Emailer
- Printer Setup
- Sample Ticket Designs
- Assigning ticket formats; system default, account specific, truck specific, or truck type
- Import an existing ticket
- Added Charge Multiplier
Table of Contents
- No labels