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:

Credential	Description
OHIP Host Name	API base URL (e.g., ohip.oraclecloud.com)
OHIP Application Key	Application key for API access
OHIP Hotel ID	Your property identifier in Opera
OHIP Client ID	OAuth client identifier
OHIP Client Secret	OAuth client secret
enterpriseId	Oracle'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.

Room key validity uses local time

Set the property's IANA timezone in Settings → Essentials → Hotel Basic Details. AVA uses it to format Opera room-key validity in local wall-clock time.

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

Step 4: Configure Sharer Payment

Use this setting when AVA creates a separate sharer reservation for an additional guest.

1. Go to Settings → Check-In → Check-In Policy

2. In Registration, set Additional Guest Under to Sharer Reservation.

3. Find Sharer payment method, then click Configure.

4. Choose how Opera should set the sharer's payment and guarantee codes:

   Option	Use it when	Result
   Same as main reservation	The sharer should match the main booking	AVA uses the main reservation payment method.
   Specific OPERA method	The sharer needs an independent payment method	AVA uses your selected payment and guarantee codes.

5. For Specific OPERA method, select an eligible OPERA payment method and OPERA guarantee code.

6. Click Apply, then click Save Check-In Policy.

   ✓ The saved pair is used for generated sharer reservations, even when the request has no override.

When you save the guest-placement or sharer-payment settings, AVA syncs them to Vouch Core for Opera. This keeps generated sharer reservations aligned with your saved policy.

Confirm Opera settings before deployment

AVA no longer applies a property-specific sharer payment code. Confirm your intended setting is saved before deploying an Opera integration change. For an independent cash sharer, select CA and NON only when Opera lists both as eligible.

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
• ✅ Group Checkout capability for linked reservations

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.
• External-reference lookup verifies the full reservation. AVA checks the requested external reference and arrival date on the full Opera record before selecting it. If the values mismatch or results are ambiguous, AVA does not select a reservation.
• OTA references can use different letter casing. If an exact external-reference lookup returns no result, AVA retries once with the reference in uppercase. It then compares the reference without case differences on the full reservation record. Confirmation-number lookup behavior is unchanged.
• Checkout lookup follows Opera's PMS business date. After midnight, AVA limits checkout lookup to departures due on Opera's current PMS business date. AVA also checks the departure date itself. A calendar-date departure may remain unavailable until Night Audit advances the business date.
• ACI name searches use Opera profiles. Staff Access searches the Opera guest profile directory, then shows active reservations tied to matching profiles.
• Same-name reservations can be grouped in ACI. A verified kiosk staff credential is required. One-device ACI uses its existing credential without starting the two-device runtime.
• The primary reservation stays primary. AVA waives main guest registration only for selected additional reservations.
• Additional guest updates do not overwrite the primary guest. Name-bearing updates create an additional guest on the selected reservation.
• Accompanying profiles use authoritative main-guest context. Before creating an accompanying profile, AVA refreshes the Opera reservation and requires exactly one explicit main guest with a usable profile ID. Missing, blank, mismatched, or ambiguous identity context stops the action before profile creation.
• Manual grouping changes AVA's ACI journey only. It does not create or change a reservation group in Opera.
• 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.
• Two-device ACI supports room operations on the verified staff device. Staff can view room condition and occupancy, refresh the Opera assignment, and choose a ready replacement room.
• Room refreshes fail closed. If Opera returns no room or an ambiguous multi-room result, AVA keeps the stored room instead of choosing another one.
• An empty Opera out-of-service result is valid. When Opera returns no out-of-service rooms, AVA treats the result as empty. Room assignment can continue. A missing or malformed result still shows a PMS-unavailable error.
• Component suites check every linked room. If Opera represents a suite with component rooms, AVA checks each member's occupancy and readiness before assignment.
• Occupied component rooms keep priority. If one member is occupied, AVA preserves that occupied reason instead of selecting another unready status.
• Unverified auto-selected suites stay blocked. If AVA cannot verify an automatically selected component suite, it blocks the assignment request.
• Ordinary rooms keep the existing path. These extra component-room checks do not apply to ordinary rooms or unrelated auto-selected rooms.
• One-device ACI does not show these room-operation controls. Use the PMS for room changes in one-device ACI.
• Group Checkout is available when Opera reports support. Turn it on in Settings → Check-In → Check-In Policy after the connection is active.
• Partial multi-room check-in survives a refresh. After the registered main room checks in, a refetched booking keeps an empty subsequent room eligible. AVA matches the room to the same booking family, so an unrelated checked-in room cannot unlock it.
• Empty subsequent-room actions remain available. After you select and check in an empty subsequent room, AVA sends only that room to Opera. For an already checked-in empty room without its own access payload, AVA checks the merchant Keycard setting. If unavailable, AVA checks explicit Keycard access from an in-house sibling in the same reservation. Room Information and Create Keycard then appear.
• Sharer reservations stay separate. If Opera uses one confirmation number for multiple reservation IDs, AVA keeps each reservation as its own check-in target.
• Sharer payment settings control generated reservations. A specific payment-and-guarantee pair takes priority over Opera's cash-method lookup. Without a specific pair, AVA uses Opera's eligible cash payment method.
• Guest-placement settings sync with Vouch Core. Saving Additional Guest Under or sharer-payment settings forwards the saved values for future Opera guest actions.
• 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.
• Payment amounts should match the property currency. Opera can return an internal error when currencies do not match.
• Uploaded documents can appear in Opera attachments. After sync, you can verify travel document and registration card uploads from the reservation.
• 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.
• Special codes stay aligned across settings pages. AVA reads the flat Opera special-code fields as the saved source of truth in Settings → Essentials → PMS Integration and Settings → Check-In. Nested specialCode and specialCodes objects may still appear on the wire for legacy readers, but AVA does not use them. If you edit a code in one place, the other view shows the same saved flat values after refresh. If you clear a code, the change stays saved too.
• Optional checkout special codes retry transient Opera failures. AVA retries once after a short-lived OHIP error. It checks Opera before retrying, so an uncertain response does not create a duplicate code. Checkout still completes if the optional update fails.
• Opera billing policies shape the guest bill. Hide and waive rules have different effects.
• Payment policy controls appear in Settings → Payment. Capability data controls which accommodation and Opera-specific controls you see.
• Waive policies reduce room-package charges and identified room-package components. For pre-arrival reservations, projected Opera rate-info room charges and their tax are waived together.
• Separately posted extras and their taxes can remain payable. They are not part of the booked room rate.
• Hide policies mask room and tax rows. The balance due stays unchanged.
• Evaluated payable billing controls checkout payment. AVA uses that amount instead of the display summary.
• An explicit Opera zero balance stays authoritative. AVA does not rebuild a positive balance from visible room, tax, or service rows. This applies when routed or settled counterparts are not visible. AVA trusts that zero only when the amount and currency match the normalized Opera bill. A mismatch remains unconfirmed.
• Payment reversals keep their sign. An Opera payment and equal negative reversal net to zero in AVA's folio and billing review.
• Selective billing stays within the guest's folio window. Routed charges from other windows do not increase the balance.
• Incomplete folio data stays unconfirmed. AVA avoids showing a false zero when the guest window is incomplete.
• Projected invoice lines can remain visible. Compare unexpected charges with Opera before collecting payment.
• If no policy matches, AVA uses the billing response it receives.
• 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

Opera authentication is rejected during an action

What you see: An Opera action briefly pauses or shows an authentication or timeout error.

Why this happens: Opera may reject cached credentials or briefly delay its OAuth service. AVA handles each case with one automatic retry.

Fix:

1. Wait up to 30 seconds for AVA to finish its automatic retry.
2. Try the action again only if the error remains.
3. If the error returns, verify the Opera environment and credentials.
4. Re-enter the credentials in AVA, then click Save.
5. Contact Oracle or Vouch support if the error continues.

One automatic retry

AVA refreshes Opera configuration after cached credentials fail. It also retries one transient OAuth timeout or gateway error. Invalid credentials and rate limits do not trigger this retry.

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

Checkout completes, but the Opera report misses the special code

What you see: AVA completes checkout, but the configured checkout special code is missing in Opera.

Why this happens: The optional Opera update can fail after checkout. AVA retries transient OHIP errors once.

Fix:

1. Wait briefly, then refresh the reservation in Opera.
2. Confirm the Specials code for check-out is saved in Settings → Check-In.
3. Check the Opera reservation again.
4. Contact support if the code remains missing.

Checkout is not blocked

A failed optional special-code update does not undo or block checkout. AVA does not retry non-transient errors.

Extras remain payable after an accommodation waiver

What you see: AVA shows a positive balance after room-package rows are waived.

Pre-arrival Opera rate tax

AVA treats projected Opera rate-info room charges and their tax as one room-package amount. A matching rate-code waiver should not leave projected room-rate tax payable. Only separately posted extras and their taxes should remain collectible.

Fix:

1. Review the balance and extra GST in Opera.
2. Confirm the remaining charges are correct.
3. Refresh the reservation in AVA after Opera finishes syncing.
4. Select Pay when the positive balance matches Opera's outstanding balance.
5. If Opera reports zero, refresh AVA and confirm the balance is zero.

Opera folio data is incomplete

What you see: AVA cannot confirm the balance after an Opera folio update.

Fix:

1. Confirm that Opera returned the guest's primary folio window.
2. Check that the folio window includes a balance or usable postings.
3. Refresh the reservation in AVA.
4. Wait for Opera to finish updating the folio.
5. Contact your front desk or support team if the balance stays unconfirmed.

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.

An Opera component suite is not ready

What you see: Check-in stops because an Opera suite is not ready, or the room assignment is unavailable.

Why this happens: Opera represents the suite with linked component rooms. AVA checks every linked room before assigning the suite.

Fix:

1. Open the suite in Opera.
2. Check every component room for occupancy and readiness.
3. Resolve any occupied, dirty, or unavailable component room in Opera or Housekeeping.
4. Confirm the suite's room configuration lists the exact component members.
5. Return to AVA, click Refresh, and retry check-in.

If AVA selected the suite automatically but cannot verify its exact configuration, ask your Opera administrator to correct the mapping.

Ordinary rooms are unchanged

AVA uses the existing room-assignment path for ordinary rooms and unrelated automatically selected rooms.

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

Related Guides

• PMS Connection
• PMS Connection Errors
• Sync Issues