Home › Forums › Knowledge Base › Legacy Applications › TraPr › TraPr styling module for Table Service
- This topic has 0 replies, 1 voice, and was last updated 19 years ago by
Rob.
-
AuthorPosts
-
April 13, 2006 at 3:57 am #1432
Rob
MemberTraPr styling module for Table Service
Last edited: April 27, 2004 11:14 PM
This document explains how to add the TraPr styling into the Hospitality Data Systems Inc. table service application for use with the 32-bit TraPr credit card authorization program. The TraPr styling module is optimized for former Touch Menus applications using keyboard port input magnetic stripe readers. There are calls to components that exist in all former Touch Menus applications that would need their functionality replaced if you do not have those components. It is beyond the scope of this document to explain all the styling variations and modifications that can be done, but this document should give you a good start. Contact tech support if you want more advanced information than is provided in this document.
Installation
Step 1 – Install the TraPr moduleSimply unzip TrprSty.zip in your application directory. All the files contained within are named with the prefix TrPr. There shouldn’t be any problems with overwriting one of your existing files. If you run into that, try to rename your existing file rather than the TraPr file.
Step 2 – Add Employee Functions
Employees generally need the ability to run their credit card report, add a tip to a closed check, and reprint a credit card draft, in addition to accepting a credit card. Assuming you are working with one of the standard Touch Menus applications, follow the steps below:
Adding Tips to a Closed Check
1. Add a button to your Employee Functions Page (or equivalent) to add a credit card tip to a closed check. Make the instructions in the button’s zone:
1. Pointer = 7
2. Page = TrPrSeq
3. Margin = TrPrSeqInstruction 1: “Pointer = 7”
Touch Menus’ applications are built from one of six standard applications and they all use the similar chains and logic. We set the value of POINTER to provide the RETURN chain with a “pointer” to determine which page/margin/control page to “return” to if the EXIT button is depressed on the TrPrSeq page. (You’ll have to modify your RETURN chain to do this later.)
Instruction 2: “Page = TrPrSeq”
Instruction 3: “Margin = TrPrSeq”These two instructions draw the UI used to enter the TraPr sequence number for which you wish to add a tip to. There is a 10-key pad and some brief instructions on what to do. The user will stay on this page/margin until the EXIT button is touched.
To add a tip to a closed check, the user will enter the TraPr sequence number (from the original TraPr transaction) and then an amount.
The user will have to touch EXIT to return back to the origination point. The origination point in the standard applications will be the Employee Functions page/margin. (Your origination point may be different.)
2. Add support for returning from Closed Check Gratuity function. This step will add support for the EXIT button on the TrPrSeq page. This button was discussed above and let’s the user back out from the Adding a tip to a Closed Check function back to the origination point.For Touch Menus standard applications you will edit RETURN chain and add the following lines:
If Pointer = 7
Page = Employee
Margin = Employee
Jump to ‘END’
End IfRunning Credit Card Reports
1. Add a button on the Employee functions page to generate a server credit card report. You’ll only need one instruction:
TraPr:Server Report
This instruction functions much like the REP:CashierServer instruction. It will print a 40 column report for the logged employee on the defined report printer for the node being used.
Reprinting a Credit Card Draft
1. Add a button on the Employee functions page to reprint a TraPr draft. This function will only work until the employee runs a “Z” report.
Make the instructions in the button’s zone:
1. Pointer = 7
2. Page = TrPrRprt
3. Margin = TrPrRprtInstruction 1: “Pointer = 7”
Touch Menus’ applications are built from one of six standard applications and they all use the similar chains and logic. We set the value of POINTER to provide the RETURN chain with a “pointer” to determine which page/margin/control page to “return” to if the EXIT button is depressed on the TrPrSeq page. (You’ll have to modify your RETURN chain to do this later.)
Instruction 2: “Page = TrPrRprt”
Instruction 3: “Margin = TrPrRprt”These two instructions draw the UI used to enter the check number for which you wish reprint a TraPr draft. There is a 10-key pad and some brief instructions on what to do. The user will stay on this page/margin until the EXIT button is touched.
To reprint a TraPr draft, the user will enter the check number.
The user will have to touch EXIT to return back to the origination point. The origination point in the standard applications will be the Employee Functions page/margin. (Your origination point may be different.)
Step 3 – Add support for Credit Card tendering
Here’s where you’ll add the main code for actually receiving/processing a credit card payment.
1. Add a button on the TENDER control page (wherever you apply medias) that will start the TraPr process. Make the first instruction on this zone:
Chain to: TrPrInit
2. Decide whether your application should ask the user to: “Store the check” OR “Wait for approval” OR “Ask each time”. The styling is set up to “Wait for approval” by default.“Store the check”
This means that once the TraPr transaction is submitted to TraPr for approval, the check is stored and the order process reinitializes (Chain to Startup)
“Wait for approval”
After submitting the check to TraPr, the system will wait for a reply. After the reply is displayed, the system will return to the TENDER control page.
“Ask each time.”
Each time the user submits a check to TraPr they will be asked “Wait for approval or store the check?”
To change the default styling you’ll need to edit the TrPrSubm chain. It is well commented, and tells you exactly what to delete in order to enable the option of letting the user choose whether to “Store the Check” OR to “Wait for approval”.
NOTE: enabling this option means that each time a check is submitted to TraPr, the user will be asked this question.
Step 4 – Add support for tips on open checks
Sometimes employees will add the credit card gratuity on to the check prior to closing it.
1. Add a button on the TENDER control page to add a tip on an open check. The first instruction of this zone should be:
Chain to: TrPrTip
You shouldn’t have to do anything else.
Step 5 – Adding support for “Storing the check”
When the check is stored after submitting to TraPr for authorization, (either by user choice or forced) you’ll need to deal with it when you recall the check.
1. Edit the RECALL chain to look like this. New commands are in red and marked with an asterisk.
Index = Pointer *’Remember value of Pointer for later, it is
*’used to determine where to go after a check
*’is recalled.
If Order Exists ‘If check in memory when called, ensure it is
Chain to: SENDCHK ‘sent and store it.
Store current check
End If
Retrieve (Fine Dine) ‘Retrieve a check
If Order Exists ‘If check is retrieved
If T:Result > 0 *’If some TraPr result exists
If T:Result = 3 *’If TraPr approved the request, then print
Do Template TRPR *’the receipt to the local printer
Chain to: PRTLOCAL *
End If *
Chain to: TRPRANSW *’Show results of TraPr answer and ask user
*’to choose Close, Modify or Store, check
*’options.
If Pointer = 1 *’If user selected STORE THE CHECK, then
Pointer = 0 *’store the check and start order process over.
Store current check *
Chain to: STARTUP *
Stop-Ignore Rest!! *
End If *
If Pointer = 2 *’If user selected CLOSE THE CHECK, then
Pointer = 0 *’take user to TraPr Tender page which is
Chain to: TRPRTNDR *’missing the check and other media buttons.
Stop-Ignore Rest!! *
End If *
If Pointer = 3 *’If user selected MODIFY THE CHECK, then
Pointer = Index *’return Pointer to the value passed to it,
End If *’and continue normally.
End If *
Cus Display Totals
If Pointer ~ 1
Control = SERVER
Jump to ‘END’
End If
Auto PLU=MnuGrp 99
Page = SPEEDBAR
Margin = SPEEDBAR
End If
‘END’
Pointer = 0Step 6 – Add Manager level controls
TraPr provides several manager level controls.
1. Make a button on the MANAGER, ASSTMGR and/or BARTENDR control pages.
Make two instructions in this zone:
1. Pointer = x
2. Control = TRPRCTLThe first instruction: Pointer = x is used by the RETURN chain to return to proper origination point. Valid values for x are:
1 = Manager control page
2 = Assistant Manager control page
6 = Bartender control pageThe second instruction: Control = TRPRCTL draws the Manager level controls, they are as follows:
1. Void a TraPr Transaction
2. Enter a tip on a closed check
3. Run a TraPr server report
4. Run a TraPr batch reportStep 7 – Add support for Voiding Transactions
You’ll need to add code to existing chains to void TraPr medias off the check when the user is Voiding the entire check.
1. You’ll be editing the VOIDCHK chain to look like the following. This chain asks the user for confirmation prior to voiding the check. New commands are in red and marked with an asterisk.
Number 1 = HI:Pos ;Is there a check to void?
HI:Pos =1 ;If no items are on the check
IF HI:PLU=0 ;then exit this chain.
Jump To ‘END’
END IF
HI:Pos = Number 1
Window = VD_RUSUR ;Ask user ‘Are you sure?’
Accept Touch
Close 1 Window
If Pointer = 1
TraPr:Void All Media *
If Status = 1 *
Window=TRPROFF *
Accept Touch *
Close 1 Window *
Jump to ‘END’ *
End If *
Status = 0
Shell to VoidCHK
If Status > 0
Hi:Pos=1
‘LOOP’
Number 1 = Hi:Pos
Chain to:SP_VD
Void Item
If Hi:Pos~Number 1
Jump to ‘LOOP’
End If
Do Template VOIDCHK
Chain to:PRTLOCAL
Word 1=VOIDED
Word 2=CHECK
Clear ALL Media
Close Check
End If
End If
‘END’Step 8 – Configure Credit Card Medias
For TraPr to assign payment to the correct media, they must be defined in Media Definitions with the TraPr Media number set per the following table. Only credit card types accepted by the customer need to be defined in Media Definitions. If the media type for an authorization is not defined, TraPr will allocate it to Cash Tendered.
1
Checks2
AMEX3
Visa4
Master Card5
Discover6
Private7
Diners Club8
JCB9
DebitStep 9 – Load KBMSR
This module uses the KBMSR utility which interprets the credit card swipe information from keyboard input magnetic stripe readers. KBMSR.EXE must be in the Tools directory or a directory that exists in the workstation’s Path statement.
Revisions
6/12/98 Version 6.001. Initial release
9/02/98 Version 6.01
1. Updated documentation.
9/02/98 Version 6.02
1. Fixed overlapping zones in TraPrKnd window.
2. Updated documentation.5/16/02 Version 6.03 rw
1. Removed obsolete files from zip and corrected some minor styling errors.
2. Added programming of TraPr medias to documentation.
3. Converted TrPrSwip chain to use KBMSR utility instead of Touchnet to read the card.
4. Removed UDM support, as it was incompatible with KBMSR. -
AuthorPosts
- You must be logged in to reply to this topic.