How can we help? 👋

Opera (OHIP)

Learn how to connect Akia to Opera OHIP


Enabling OHIP integration

  1. Please provide the following information to your Akia’s Customer Success Representative
      • Region: The region in which the hotel’s OPERA Cloud environment is running.
      • Tenant / Chain Code: The hotel’s tenant code used to target the right tenant especially in OPERA Cloud environments that host multiple tenants.
      • Hotel ID: The OPERA internal ID of a hotel in the customer’s tenant.
      • SSD URL: The URL on which to create an integration user. This is your OPERA login page URL.
      💡
      Please refer to this PDF for guidance on locating the above information in your portal: https://amenable.s3.us-west-1.amazonaws.com/attachments/15-7ba69b9b.pdf
       

      If you have an OCIM environment, please provide the following instead:

      • Enterprise ID: This is a unique identifier for the enterprise.
      • Chain Code: The hotel’s chain code is used to target the right account especially in OPERA Cloud environments that host multiple accounts.
       
  1. A new integration user will be created on your behalf. The Opera hotel administrator will need to approve this request.
  1. Please let your representative know upon completion of the approval
 

Enabling Business Events (for Near Real-Time Updates)

By default, Akia receives new bookings when they are made and continuously syncs with Opera 3 days before the guest’s arrival. For Akia to receive reservation updates when they happen (e.g. reservation date changed or room update), you will need to enable business events in Opera.

 

1. Create a New External System

  • Go to ADMINISTRATION > INTERFACES > BUSINESS EVENTS > EXTERNAL SYSTEM.
  • Create a New External System named [Your Hotel ID]_AKIA, so if your Hotel ID is CALIF your External System would be named CALIF_AKIA
    • For hotel groups, have only one External System per Chain code.
    • Register events from other connections separately.
      • Notion image

        Specify the Code as the External System Name (CALIF_AKIA)

  • Add 999 in the Sequence field (if already in use, choose another/any number)

Click on the Three dots icon and go to Publishers

Notion image
Notion image

Create a new Publisher.

Notion image

Add only publishers that are related to reservations or rooms, other publishers available in OHIP are not relevant for the Akia integration

Notion image

If you are setting this up for multiple properties, do this for each property.

Notion image
 

2. Create a New External Database per Hotel

  • Go to TOOLBOX > SYSTEM SETUP > EXTERNAL DATABASE.
  • Create a New Database with code [HOTEL_CODE]_AKIA. If your Hotel Code is CALIF, the Database would have the code CALIF_AKIA.

In order to create a new database please follow the Oracle guide below

Make sure you have “Database Task” Enabled

 

Business Event Configuration

  • Navigate to ADMINISTRATION > INTERFACES > BUSINESS EVENTS > BUSINESS EVENTS CONFIGURATION.
  • Create new business events based on the Reservation Module
    • Business Events:
      • Cancel
      • Check in
      • Check out
      • Delete reservation
      • Join guest
      • New Reservation
      • No Show
      • Reactivate No Show
      • Reactivate waitlist
      • Reverse check in
      • Update reservation
      • Turnaways
      • Notion image

      You're Done!

Enable Pre Registration Check-in

  1. Go to ENTERPRISE > OPERA CONTROL
  1. Make sure the Pre-Registration Check in is ACTIVE
 
Did this answer your question?
😞
😐
🤩