Migrate from OXI to OHIP integration
This migration guide assists properties transitioning from Oracle's OXI interface to OHIP (Oracle Hospitality Integration Platform) while preserving connections to SHR applications. The migration involves technical integration changes, mapping requirements, and operational considerations to ensure seamless data flow between your Opera Cloud PMS and SHR systems.
Oracle manages the core migration of your PMS data while SHR handles the integration connectivity updates. Understanding both processes helps ensure smooth operational continuity throughout the transition.
📌Note: The SHR team provides updated Opera Cloud (OHIP) Hotel Migration Guide and OHIP Certification Guide documents specific to your migration timeline and the latest supported features.
OHIP connection architecture
Outlined below is information regarding OHIP connection architecture.
API connectivity structure
SHR connects to OHIP through both Streaming API and Property APIs. This dual connection approach ensures comprehensive data exchange for different operational requirements:
Streaming API functions:
Real-time rate, inventory, and restriction updates.
Reservation data transmission and confirmation.
Business event notifications for operational changes.
Property API functions:
Specific operational actions and data retrieval.
Configuration updates and system synchronization.
Custom integration requirements based on property needs.
Event subscription process
During your property's OHIP connection setup, SHR requests Oracle to enable streaming for your property or chain. Once Oracle enables streaming, SHR subscribes to the required events for your specific SHR applications. You must approve these event subscriptions before they become active.
Streaming events by application:
CRS applications: Reservation data, rate updates, inventory changes, restriction modifications.
Additional SHR systems: Configuration-specific events based on your integrated applications.
⚠️Important: Event approval is required from your side to activate the streaming functionality for each connected SHR application.
Prerequisites and requirements
Outlined below is information regarding prerequisites and requirements.
Oracle Cloud Foundation requirements
Before requesting CRS and PMS integration via OHIP, ensure your property meets these Oracle prerequisites:
Essential requirements:
Purchase of Opera Cloud Foundation SKU.
Chain onboarding with OHIP for properties using Opera Cloud Foundation.
Migration to Oracle Cloud Infrastructure (OCI) - legacy data center environments are not supported.
Streaming Business Events capability for reservation and availability data exchange.
Minimum Opera Cloud version 22.3.0.1 or higher.
Business event activation
The OPP_BSEV (Business Event) functionality must be activated to enable external system connections. This activation allows OHIP to communicate with SHR systems for ongoing operational data exchange.
Required property information
Prepare this information for SHR to facilitate your integration user setup or Developer portal access:
Technical identification details:
Tenant or Chain Code: Your hotel's tenant identifier for multi-tenant Opera Cloud environments.
Hotel ID: Opera's internal property identifier within your tenant.
SSD URL: Opera login page URL (required unless using OCIM).
Enterprise ID: Required only when using OCIM functionality.
Region: Geographic region hosting your Opera Cloud environment.
Mapping requirements and system alignment
Outlined below is information regarding mapping requirements and system alignment.
Code synchronization approach
Unlike legacy OXI connections, Opera Cloud eliminates mapping tables between systems. Room codes, rate plans, service items, and policy codes should be built in your CRS to match Oracle's configuration, or use CRS mapping tables when variations are necessary.
Critical mapping tables for CRS clients
Complete these mapping configurations before migration. If you lack access to the CRS PMS Management section, provide mapping values to your onboarding specialist:
Required mapping categories:
Room type codes and descriptions.
Rate plan codes and category assignments.
Service item codes and revenue classifications.
Policy codes for cancellation and guarantee requirements.
Additional operational codes specific to your property configuration.
Warning system changes
OXI provided message warnings while still allowing reservation posting. OHIP lacks this warning system, making accurate mapping values and matching codes essential for preventing reservation delivery failures.
⚠️Warning: Incorrect mapping can cause reservation failures without advance warning notifications.
Additional configuration fields
The CRS contains single mapping codes for specific operational requirements. Review the migration guide for detailed information about these fields, their usage scenarios, and where to locate appropriate mapping values.
This includes configurable options for property or group-specific operational decisions that require review and activation choices during migration.
Migration process and data handling
Outlined below is information regarding migration process and data handling.
Oracle's migration responsibility
Oracle manages all data migration from your on-premise servers to Opera Cloud, including existing reservations, groups, rates, and inventory. SHR does not participate in this PMS data migration process. Contact Oracle directly for questions or concerns about internal PMS data migration.
SHR data continuity
If you currently connect to SHR via OXI, your rates, inventory, restrictions, and reservations remain as last received through the OXI connection. During any downtime between disabling OXI and enabling OHIP, trigger simple syncs from your CRS to refresh availability and rate information as needed.
Business event backfill
When OHIP activates with streaming capabilities, your CRS receives business events for all activities occurring within the seven days prior to connection establishment, providing recent data continuity.
Post-migration verification
Conduct spot checks on bookings created or modified during your OXI to OHIP transition to ensure record consistency across both systems:
Verification procedures:
Missing CRS bookings: Trigger reservation syncs by date range or specific PMS identifiers.
Missing PMS bookings: Work with Support to retrigger bookings under the new OHIP interface.
Data discrepancies: Compare reservation details and resolve inconsistencies promptly.
Key considerations and common challenges
Outlined below is information regarding key considerations and common challenges.
Feature compatibility review
Review the OHIP-supported features document for your SHR applications before migration. If you require features not currently listed as supported, raise these requirements with SHR immediately for review and planning.
Prepare to connect your Oracle OHIP UAT environment to SHR for testing unsupported features or custom functionality requirements.
Rate synchronization requirements
When syncing rates from CRS to PMS, ensure assigned rate categories (Rate Code Groups in CRS) exist in your PMS with valid active date ranges. Rate records falling outside Oracle Rate Category date ranges will fail processing.
Payment processing considerations
Oracle Cloud does not accept plain text credit card numbers. Choose one of these payment processing approaches:
Payment processing options:
Payment gateway integration: Enable with SHR for credit card tokenization before PMS transmission.
Cloud OPI implementation: Use Oracle's cloud payment interface for token requests.
No card transmission: Bookings post to PMS without payment information (accessible via CRS based on user permissions).
Custom development requirements
OXI customizations such as User Defined Field (UDF) data passing require redevelopment for OHIP compatibility. Raise customization requirements immediately for SHR discussion and redevelopment planning.
📌Note: OHIP UAT environment configuration is recommended for testing, as UDF fields may differ between OXI and OHIP implementations.
Testing and validation
Utilize Oracle's OHIP UAT environment for thorough testing of:
Custom field mappings and data flows.
Payment processing configurations.
Rate synchronization accuracy.
Reservation delivery and confirmation processes.
Operational workflow validation.
This comprehensive testing approach helps identify and resolve integration issues before production deployment, ensuring operational continuity throughout your migration process.