X+ Table - Additional Security Options

The X+ table provides additional security to RDP features which do not display as sub-records accessible in option “090” - “Update System Tables”. For example, it is possible to invoke a sub-record in the X+ table which allows users to toggle the “Allow Move” flag from the tape chart. In addition, certain properties may allow supervisors to only update non-critical system tables. This section will detail several X+ table options, including:

Sub-record	Description
090??	Provides security on any 090 table (where "??" is the table). For example, adding sub-record 090PW to table X+ will force the system to check a user's power level prior to providing access to the PW table.
120E62	By adding sub-record 120E62 to table X+, users can be restricted from changing the owner paycode in field # 62 of a reservation. For example, with a power level of 100 assigned to X+ sub-record 120E62, users with a power level of 60 are not allowed to change the owner paycode on a reservation.
120FF8	By adding sub-record 120FF8 to table X+, users can be restricted from ALL <F8 - CHANGE> features. For example, with a power level of 100 assigned to X+ sub-record 120FF8, users with a power level of 60 are not allowed to use the <F8- CHANGE> features.
120FC	By adding sub-record 120FC to table X+, users can be restricted from changing the "Price" and "Quantity" fields while using <F8 - CHANGE>.
120FD	By adding sub-record 120FD to table X+, users can be restricted from deleting transactions with <F8 - CHANGE>.
120FP	Only active on systems that do NOT have "RN" - "Enhanced Rates and Packages" installed. By adding sub-record 120FP to table X+, users can be restricted from changing the Package Master Flag.
120FT	By adding sub-record 120FT to table X+, users can be restricted from transferring transactions through <F8 - CHANGE>.
140AM	By adding sub-record 140AM to table X+, users can be restricted from toggling the "Allow Move" flag (<F7>) in the reservation tape chart.
140F9	By adding sub-record 140F9 to table X+, users can be restricted from using the <F9 - CAPTURE> feature in the tape chart. By restricting the <F9> key, users are unable to make reservation changes from the tape chart (i.e. - changing arrival/departure dates, performing room moves).
140F10	By adding sub-record 140F10 to table X+, users can be restricted from making new reservations from the tape chart (<F10 - NEW RES> option). In addition, the 140F10 sub-record holds the "Program Option Code" that holds the default reservation type when using <F10 - NEW RES> from RDP142. Enter the reservation type in field #6 (Program Option Code) in table X+.
140F11	By adding sub-record 140F11 to table X+, users can be restricted from the <F11 - CHANGE> feature in the tape chart. <F11 - CHANGE> brings the user to the 120 screen where any reservation field may be changed.
184?	By adding sub-record 184? to table X+, users can be restricted from specific options in "184" - "Inquire on Totals File" found on the System Manager menu. The "?" is replaced with the number 1 - 9, which correspond directly with the options found in RDP184. For example, adding sub-record 1845 to table X+ prevents users from making adjusting entries to the totals file (option #5 in RDP184 is "Adjusting Entry for Totals File"). The only required field in X+ sub-record 184? is the Program Fence Level (#3).

322?	By adding sub-record 322? to table X+, users can be restricted from specific options in "322" - "Print & Maintain Checks" on the Check Maintenance menu (80). The "?" is replaced with the number 1 - 5, which correspond directly with the options found in RDP322. For example, adding sub-record 3223 to table X+ prevents users from printing new checks (option #3 in RDP322 is "Print New Checks").
362F8	Table X+ sub-record "362F8" holds the description for the <F8> key in option 362. For example, if a property makes walk in reservations from RDP362, enter the text "Walk-In" in field #1 of sub-record 362F8. The text in field #1 displays on the 362 screen to the right of the <F8> key. Additionally, enter the default reservation option (R - Room Availability, P - Preassign, etc.) in field #6, Program Option Code. If the property wants to restrict the <F8> key in RDP362, enter the appropriate security level in field #3, Program Fence Level.
500C	By adding sub-record 500C to table X+, users are restricted from making changes to owner transaction totals in option "502" - "Inquire on Owner History". If a user does not have a sufficient power level, the option "C" - "Change Monthly Total for this Owner" does not appear as a menu option.
PAY1 - PAY7	By adding sub-records PAY1 - PAY7 to table X+, users can be restricted from taking payments using specific payment types, as seen below.
	PAY1	Cash
	PAY2	Check
	PAY3	Credit Card Manual
	PAY4	Credit Card Auto
	PAY5	Miscellaneous
	PAY6	Wire
	PAY7	Transfer
	The only field required in table X+ when adding sub-records PAY1 - PAY7 is #3, Program Fence Level.
130BQ	By adding sub-record 130BQ to table X+, users are restricted from using the RDP131 power user option "Q" - "Invoice Group Master Now" feature. This security feature only applies to properties with switch #422-14 set to NO. With switch #422-14 set to NO, group master reservation balances are not automatically transferred by the RDP system at checkout. The only required field in X+ sub-record 130BR is #3, Program Fence Level.
130BR	By adding sub-record 130BR to table X+, users are restricted from using the RDP131 power user option "R" - "Bill to Group Leader" feature. This security feature only applies to properties with switch #422-14 set to NO. With switch #422-14 set to NO, group leader reservation balances are not automatically transferred by the RDP system at checkout. The only required field in X+ sub-record 130BR is #3, Program Fence Level.

There are four X+ sub-records used for restricting various functions of the <F8 - CHANGE> key. They are:

All X+ sub-records are accessed through option 090 on the System Manager menu using option “U” - “Update Table Records”. Enter table “X+” at the Table Number prompt and add the above sub-records, with only the power level required for restricting access.

Use the X+ table to make the tape chart a read only feature , available for housekeepers and management personnel who do not need access to moving reservations. For example, housekeepers like to use the visual features of the tape chart for charting clean rooms and scheduling, however they should not have access to the <F9 - CAPTURE> feature which allows room moves to be performed from the tape chart. To implement the feature, add the following sub-record to the X+ table:

With this feature turned on, the system displays the following warning if a user with an insufficient power level attempts to perform a room move with the <F9 - CAPTURE> key:

It is also possible to restrict users from making a reservation from the tape chart by adding X+ sub-record 140F10, similar to the following:

The 140F10 sub-record also controls the default reservation type from the tape chart. For example, if the property always makes inventory reservations, enter an “I” in field #6, Program Option Code. With the “I” entered in field #6, the system defaults to an inventory reservation, bypassing the following reservation type option screen:

When accessing a reservation in the tape chart, guest information is displayed in the reservation information box, seen below:

Reservations with the “Allow Move” flag set to NO (N) cannot be moved from the tape chart. However, by adding X+ sub-record 140AM with the proper security level, similar to the following, the <F7> key is active in the tape chart for toggling the "Allow Move" flag.

With sub-record 140AM added, the ability to toggle the “Allow Move” field through the <F7> key is added to the reservation tape chart.

Using the X+ table it is possible to restrict certain tables within option “090” - “Update System Tables”. For example, assume a property allows supervisors to update market codes, source of business codes, and guest types but does not want them to have access to the PW (System User) and C1 (Program Control Table) tables. In order to restrict these tables, add two sub-records to the X+ table: (1) 090PW and (2) 090C1. The sub-records appear as:

With the sub-record added, supervisors with insufficient power levels receive the following error message when attempting to access the PW table :

Use the same sub-record naming convention in order to restrict any system table, i.e. - 090??, where ?? is the table number (CD, CF, C1, etc.).

In order to restrict payment types , add the following sub-records to the X+ table:

Sub-Record	Description
PAY1	Cash payment option
PAY2	Check payment option
PAY3	Manual Credit Card payment option
PAY4	Scan Credit Card option
PAY5	Wire Transfer option
PAY6	Miscellaneous option
PAY7	Transfer option

All of the above options display when taking a payment in RDP120 using power user option “D” - “Deposit or Guest Payment”.

With sub-record PAY6 added with a power level of 100, users cannot access the miscellaneous option:

A user without a power level of 100 receives the following error message if payment option 6=Misc is chosen:

By restricting the seldom-used payment options (Wire, Miscellaneous, and Transfer), general ledger mistakes are avoided.

The In-House status screen allows users to adjust group allocations using the <F9 - ADJ GRP BLOCK> feature. Many properties do not want all personnel to have access to this powerful feature. In order to restrict access to group block adjustments , add a fence level to menu X6, sub-record “551” - “Group - Adjust Room Block”. The system checks this fence level and the user’s power level prior to allowing access to the group allocation screen with the <F9 - ADJ GRP BLOCK> feature. A clerk with an insufficient power level receives the following error message when using the <F9> feature:

Ä See the Front Desk chapter in the User’s Manual for a complete explanation of the In-House status screen.

Home	RDP Sales	Contact Us	Training
RDP Support		Open a Web Support Ticket
RDPWin Knowledge Base	RDP-DOS Knowledge Base	IRM and IRM.Net Knowledge Base	Crystal Knowledge Base

Supported Environments as of10/15/08 See Hardware Requirements for an entire list.
Workstations	All workstations must use either Windows XP Professional or Windows Vista (Business or Ultimate) 32-bit only (not 64 bit on workstations) with all service packs installed . RDP no longer supports Windows 95, 98, ME, or 2000 Workstations. For RDPWin, a minimum of 1 GB of RAM and a dual core processor or faster are required. See Hardware Requirements for an entire list.
Servers	The data server must be Windows 2003 or 2008 32 or 64 bit with all service packs installed and at least 4GB of RAM (16 for customers with 20 or more workstations). RDP no longer supports Novell Netware Servers. Feel free to call RDP Support at 970- 845-7108 with any hardware questions.
Pervasive	The Pervasive database must be Version 9.52 or higher with all Service Packs installed. See Pervasive Overview.
Printing Issues	RDPWin supports all standard Windows Printing environments. Our legacy RDP-DOS system may not be able to print if the printer is USB, TCP/IP or wireless. Additionally, printing remotely with Terminal Services or Citrix may not work with RDP-DOS.
NetMeeting or Remote Desktop	To provide the highest level of support, RDP requires access to your system with Remote Desktop or Microsoft NetMeeting. Carbon Copy and other remote tools are not supported. See Hardware Requirements for more details.
RDPWin	RDPWin is our Microsoft .Net Windows-based software. It accesses the same database at the same time as your existing RDP-DOS and Internet Reservation Module (IRM). Please review: RDPWin Overview. Adding RDPWin to an Existing Legacy RDP-DOS System.
For more information see Hardware Requirements.

Home	RDPWin	RDP-DOS	IRM/IRM.Net	Open A Web Support Ticket
	Version 2.xxx	Upgrade to RDPWin	Link to Marketing Site	Contact Us
	Training	Vendor Interfaces	Troubleshooting	RDP Sales Website

X+ Table - Additional Security Options

Overview

Restricting <F8 - CHANGE>

Tape Chart Security

Restricting System Tables and Payment Types

In-House Status Screen and Group Allocations (362)