Enroll Profile Message

The EnrollProfile Message functionality is available with the following license codes:

• OPX_GA2
• OPX_BALL
• OPX_ACSC  
• OPX_ARIS

Purpose

The Profile Enrollment Message permits OPERA to create a profile in the PTS. In installations, where all profiles are automatically enrolled, this function is unnecessary and can be disabled via OPERA application settings.

To invoke enrollment, a player ID cannot exist on the guest profile. Procedures require that the guest presents a government issued picture ID in order to be enrolled as a casino player. Operationally, the property will not utilize the enrollment functionality unless the guest is in house or arriving.

Underlying Assumptions

PTS needs to store the OPERA profile ID and property code to identify the right profile when changes are made in OPERA.

Scenario

Hotel registration information is already known, the guest does not have a PTS account and wants to enroll.

Business Rules

Once the enrollment request has been sent to PTS, based on received minimum required information, the PTS will verify if the player does already exist in its system. If a match of player profiles exists, a response with multiple matches will be returned, prompting the user to select one of these existing players. In case none of these profiles applies to the guest to be enrolled, the user will be able to proceed with the new enrollment and ignore the choices presented from PTS. If no matches are found for the enrollment request in PTS, a successful response with the newly issued player ID for the guest will be received. The profile will be created or updated with the information sent by PTS.

The player ID is constant per individual guest and will be stored as a membership number in the OPERA profile. The membership type will be determined based on a PTS configuration parameter and belong to a separate membership class. Entry points for profile enrollment are the Profile search screen, the Profile membership screen and the Miscellaneous Menu.

PTS will reply with either a MatchCompare Response prompting the user with a selection of existing players that match the request details, or an EnrollProfile Response containing the new player ID that must be stored as membership in the guest profile.

OPERA Requirements

The functionality for enrollment is controlled by two OPERA settings. These are the OPERA OXI add-on gaming license code (e.g., OPX_GA2), and the OPERA application setting in the memberships section for ENROLLMENT.

• A possibility exists that the same property may have an alternate loyalty and PTS enrollments.
• If OPX_GA2=Y and ENROLLMENT=Y, a form requests the user select which type of enrollment (loyalty or gaming) is being done (same form as described in Lookup, except change the title bar).  
• If OPX_GA2=N, and ENROLLMENT=Y, when the user selects the Enrollment button, the GUEST_SEARCH_GEN form (or the form based on config mode) will automatically show (same as current).
• If OPX_GA2=Y and ENROLLMENT=N, the enrollment button is not available.
• 'ENROLLMENT' ='Y', Gaming is on and 'AUTO ENROLL PLAYER' IN ('PROMPT','NEVER'), then show the gaming button.
• 'ENROLLMENT' ='Y' and 'AUTO ENROLL PLAYER'='ALWAYS' and Enrollment Type in ('LOYALTY','GAMING'), OR OPP_GCA=FALSE, then do not show the gaming button. Go directly into enrollment form when the enrollment button is pressed
• 'ENROLLMENT' ='Y' and Enrollment Type is null, gaming is OFF, then do not show the enrollment button, and go directly into the enrollment form.
• If OPX_GA2=Y and ENROLLMENT=Y, when the user selects the Enrollment button, the screen below will show:

  

• The Gaming button will be grayed out if the guest is not in-house, departed today or arriving today or in the future.
• The Gaming button is grayed out if the profile has a player ID attached to the profile (looking at membership type defined in PTS_MEMBERSHIP_TYPE).
• The Loyalty button is grayed out if the profile has the loyalty membership id already attached to the profile.
• If both loyalty membership and gaming membership exist on the profile, the Enrollment button is grayed out from all places.
• When the Loyalty button is selected, the enrollment form is displayed.
• When the Gaming button is selected, the system will display the Gaming Enrollment screen:
• The Type/Keyword field will only show if the function KEYWORD=Y is set in application settings for profiles. This will default to blank. The LOV will show all keyword types on the profile. The user can select an existing one or create a new one.
• When Enrollment is complete for Gaming, OPERA prompts, “Would you like to create a player card?” if Yes is selected, OPERA prompts, “Player ID XXX has been created” when complete. The Player ID number will be stored on the profile. This message will only show if parameter GAMING_PTS_CARD = Y, and the parameter Create Player Card is active’.
• The Enrollment button is called from the following places.
  • Miscellaneous > Enrollment
  • Reservations > New Reservation > Search
  • Reservations > Profiles
  • Reservations > Profiles > Edit > Options
  • Reservations > Profiles > Edit > Options > Memberships

OPERA Gaming Requirements

OPERA will send an EnrollProfileRequest with all the profile data that was entered into the enrollment screen to PTS.

Messages

EnrollProfileRequest (OPERA to PTS)

This message will be sent from OPERA to the PTS and will contain all the mandatory information necessary to enroll a profile in the PTS. PTS sends back an EnrollProfileResponse message that contains the player ID from which a new player card could be created. In case one or multiple existing players are found matching the enrollment criteria, the PTS may respond with a MatchCompareResponse message. The OPERA user will be prompted with this list to select a player or otherwise to abort the enrollment process.

See Also How the Gaming Interface Functions with PTS