Confirmation letters
Confirmation layouts are Graphic layouts (used with the Salesware Reservations module) that are saved in a special directory: Siriusware\Layouts\CONFIRMS. This is done for ease of selection by the Sales operator.
All tables in the local Data folder are open and may be referenced, but they may not be synched. To print confirmation letters, PrintEZ application creates several temporary tables. These tables are actually left on disk after the confirmation letter has printed, so you can close Sales and use Helper utility to view their contents. They are created in the Sales\Data folder. csrTrans is the primary (selected) table. The following tables are used.
Table | Sync field | Notes |
csrTrans | | Table created and left on disk for each confirmation letter – holds all the tr_save records for the reservation. |
csrSaleHdr | Not synched | Contains sh_save and sale_hdr records for the reservation. |
csrResGuest | N/A | Single record table. Contains guest record (with address information) for guest attached to Reservation Header. |
csrUtility | Not synched – only top record | Contains utility records for all sales in csrSaleHdr |
csrSaleGuest | Not synched | All guests attached to transactions in the reservation with address information |
resrvatn | reserv_no | |
utility | printing.sale_no | Has totals for a reservation and is invaluable in creating confirmations. Fields include Sale_no, Sale_sub, Sale_disc, Sale_fee, Sale_ext, Sale_taxa, Sale_taxb, Sale_tax, Change, Acct_tot, Inv_tot, Acct_chg, Acct_pay, Pms_lookup, Pms_select, Saved_sale, Admissions, Dw_swipeno, Dw_cr_lim, Dw_cr_rem, Sp_lim, Sp_rem, Sp_lim_dy, Sp_rem_dy, Guest_no, First_name, Last_name, Phone, Descript1, Descript2, Salespoint, Operator, Date_time, Res_total, Bal_due, Amt_paid |
csrResDWCards | N/A | Single record table with In-House Cards info |
accomdtn | resrvatn.accommodat | |
baselodg | resrvatn.base_lodge | |
mktgcode | resrvatn.mktg_code | |
pkup_loc | resrvatn.pickup_loc | |
srcecode | resrvatn.srce_code | |
usercod1 | resrvatn.user_code1 | |
usercod2 | resrvatn.user_code2 | |
usercod3 | resrvatn.user_code3 | |
wrapcode | resrvatn.wrap_code | |
accounts | csrSaleHdr.acct_name | |
invoices | csrTrans.invoice_no | |
guests | csrTrans.guest_no | |
gst_pass | csrTrans.type20num | |
bookinfo | csrTrans.type40num | |
res_schd | csrTrans.type60num | |
access | csrTrans.type70num | |
meet_loc | csrTrans.meet_locat | |
template | items.DCI | |
items | csrTrans.DCI | |
alladres | csrSaleGuest.guest_no_a | However, csrSaleGuest is not synched |
Multi-page Confirmation layouts
Sometimes you need to get a vast quantity of text on a page but problems may occur when you get to the page breaks. To mitigate this, you can use “fake groups.” In the Confirmation layout available from http://portal.siriusware.com/docs/kb-data/multipagefakegroupdemo.zip, fake groups were added to break up the one or two very large text blocks. Each of the chunks prints entirely on a page or is moved to the next page – they are not split up. This is the problem with very large blocks of text – they don’t split between pages. If you make the blocks small enough, though, then they break up in a more desirable way. T
his trick has the added headache of maintaining more individual chunks of text, but has the advantage of working better in multi-page layouts. When you create fake groups you also need fake group variables (this is what the fake groups group on).
To create the layout, follow these steps:
1. From the layout editor, click Report > Data Grouping.
2. Add as many fake groups as you think you might need. Use the expression FakeGroup1, FakeGroup2, etc.
3. On that same Data Grouping dialog box, change the nesting order of the groups so that the real groups are at the bottom and the fake ones are at the top.
4. In Reports > Variables create the same number of variables to match the expressions you used in step 2 (FakeGroup1, FakeGroup2, etc.). Leave the Value to store, Initial Value, Reset Value and Calculation on their defaults.
5. Start filling up the group footers.
You may have some problems if you are using a summary band – but that can usually be solved by moving that information into one of the FakeGroup footer bands.