Skip to main content

Opera PMS Integration (OHIP)

Connect AVA to Oracle's Opera Cloud property management system via OHIP (Oracle Hospitality Integration Platform). Once configured, AVA syncs reservations, room inventory, and guest information directly from Opera. Guest profiles now open in AVA's shared profile layout.

Quick Setup

Most hotels finish this in 10 to 15 minutes. If you use OCIM, ask Oracle for enterpriseId first.

Where to Find It

Settings → Essentials → Property Management System (PMS) Integration

Before You Start

Get these credentials from your IT team or Oracle/Opera administrator:

CredentialDescription
OHIP Host NameAPI base URL (e.g., ohip.oraclecloud.com)
OHIP Application KeyApplication key for API access
OHIP Hotel IDYour property identifier in Opera
OHIP Client IDOAuth client identifier
OHIP Client SecretOAuth client secret
enterpriseIdOracle's OCIM enterprise identifier. Required when OHIP Identity Management is OCIM.
warning

Opera OHIP integration requires technical setup by Oracle or your IT team. They will provide the API credentials after enabling OHIP access for your property.

OCIM requires one extra value

If you select OCIM, AVA now needs enterpriseId before it can request tokens. Keep that value with the rest of your OHIP credentials.

Configuration Steps

Step 1: Select Opera as Your PMS

  1. Go to Settings → Essentials
  2. Scroll to PMS Integration
  3. Click the Opera card
  4. A checkmark (✓) appears to confirm selection

Step 2: Enter OHIP Configuration

Fill in each field:

  • OHIP Host Name: The base URL of your OHIP API instance (e.g., ohip.oraclecloud.com)
  • OHIP Application Key: Your application key for API access (click Edit Secret to update)
  • OHIP Hotel ID: Your property's Opera hotel code
  • OHIP Identity Management: Choose OCIM (Oracle Cloud Identity) or SSD (Direct Credentials)
  • OHIP Client ID: OAuth client identifier
  • OHIP Client Secret: OAuth secret key (click Edit Secret to update)
  • enterpriseId: Oracle's OCIM enterprise identifier. Use this only when OHIP Identity Management is OCIM.

If you selected SSD for identity management, also enter:

  • OHIP Username: Direct login username
  • OHIP Password: Direct login password

Step 3: Save and Verify

  1. Click Save
  2. Check the status indicator:
    • 🟢 "Opera Integration Configured" = All required fields are entered
    • 🟡 "Opera Integration Not Configured" = Missing required fields

What Syncs from Opera

Once connected, AVA receives:

  • ✅ Guest reservations and folios
  • ✅ Room availability and status
  • ✅ Guest profile information in the shared AVA format
  • ✅ Check-in/out transactions
  • ✅ Room blocking information
  • ✅ Do Not Move room-lock status
  • ✅ Reservation ETA updates through the standard reservation flow

Guest & Staff Impact

  • Guest forms adapt to Opera rules. Required fields and hidden fields change based on Opera configuration, so guests only see what is needed.
  • Guest profiles use the shared AVA layout. Opera guest details now open in the same field structure as AVA v2.
  • Reservation lookup uses Opera. If Opera is not configured, the guest lookup step will fail.
  • Active reservations appear by default. Cancelled reservations stay out of normal lookup results unless a workflow explicitly requests them.
  • Multi-room reservations keep the searched room on the right card. AVA preserves the confirmation you looked up, even when Opera normalizes the family to the main confirmation or uses different internal IDs.
  • Charged room type stays stable. When AVA assigns a room in Opera, it keeps the charged room type unchanged, even if the physical room has a different type.
  • Adding guests to a room stays synced. If staff add another guest during check-in, AVA updates Opera so the extra guest stays attached to that room.
  • Assisted check-in can show rate codes. When Opera sends a rate code, AVA shows it on the selected reservation card during staff-assisted check-in.
  • Travel-agent labels stay visible. Opera can pass the agency name into sourceName. That lets waiver matching see labels like Booking.com (VCC).
  • Payment posts can add comments. After a successful Opera payment or deposit, AVA adds a reservation comment in Opera. It uses your configured Default Comment Type / Location from Settings → Payment.
  • Reservation ETA stays in sync. AVA writes estimated arrival time back to Opera and reads it into Streamliner. You can see the PMS-backed ETA on reservation cards and rows.
  • Billing rules can shape the guest bill. Opera is the first PMS to hide guest-only rows.
  • Waived room and tax rows stay visible. AVA then recalculates the payable total.
  • Locked rooms stay locked in AVA. If Opera marks a reservation Do Not Move, Streamliner shows the lock icon in room-change views.

Troubleshooting

"Integration Not Configured" Status

Required fields missing. Ensure you have entered:

  1. OHIP Host Name
  2. OHIP Application Key
  3. OHIP Hotel ID
  4. OHIP Client ID
  5. enterpriseId if you selected OCIM

API Connection Errors

  1. Verify OHIP Host Name is correct
  2. Check that your OHIP subscription is active
  3. Confirm enterpriseId is saved when using OCIM
  4. Contact IT to confirm firewall/network access
  5. Verify credentials with Oracle support

OCIM fails as soon as you save

What you see: AVA rejects the connection right away when you choose OCIM.

Fix:

  1. Ask Oracle for the correct enterpriseId.
  2. Re-enter the OCIM credentials in AVA.
  3. Save again.
  4. If it still fails, confirm the client ID and client secret with Oracle.

No Reservations Appearing

  1. Wait 15-30 minutes for initial sync
  2. Verify OHIP user permissions in Opera
  3. Check that reservations exist in Opera
  4. Contact support with error logs

ETA does not update

What you see: The reservation still shows the old arrival time in Streamliner.

Fix:

  1. Confirm the ETA is saved on the reservation in Opera.
  2. Refresh Operations View after the update syncs.
  3. If it still does not appear, check the Opera connection and retry after a few minutes.

A multi-room room card looks empty

What you see: A room card opens, but the main guest is missing.

Fix:

  1. Confirm you loaded the reservation by confirmation number.
  2. Refresh the check-in screen and open the room again.
  3. If the guest is still missing, contact support with the confirmation number and arrival date.

A room does not appear in room changes

What you see: The room is missing from Allow move room.

Fix:

  1. Check the reservation in Opera.
  2. Remove the Do Not Move lock if the room should be movable.
  3. Refresh the reservation in AVA.
  4. Try the room change again.

Security Best Practices

  • 🔒 Store credentials securely (they're encrypted in AVA)
  • 🔒 Use OCIM when possible for better security
  • 🔒 Keep enterpriseId with the rest of your OCIM credentials
  • 🔒 Rotate client secrets periodically
  • 🔒 Limit OHIP user permissions to minimum required

Getting OHIP Credentials

If you don't have credentials:

  1. Contact Oracle Hospitality Support or your Opera system administrator
  2. Request OHIP API access for AVA integration
  3. They will provide:
    • OHIP Host Name
    • Application Key
    • Client ID and Secret
    • Hotel ID
    • enterpriseId for OCIM
  4. Document received credentials securely

Still Stuck?

Contact success@vouch-technologies.com if:

  • ❌ The OCIM connection still fails after you add enterpriseId
  • ❌ Reservations do not appear after the first sync window
  • ❌ Oracle says the credentials are valid, but AVA still rejects them

Include:

  • Screenshot of the error
  • Your Opera identity management mode
  • Time the problem started
  • Steps you already tried