Oracle hotel interface setup

Tapa

  • Add or edit a tender
  • Choose tender type Room Charge (Hotel Interface)
  • In the EFT section choose Provider Oracle
  • Hotel ID is the internal ID of the hotel in Oracle. This should be obtained from the customer.
  • Endpoint is the Gateway URL of the environment configured in the Oracle Developer Portal.
  • All other credentials must be obtained from the Oracle Developer Portal.

If the customer has a test non-production environment set up in Oracle Cloud and wants to use it for testing, set the Port to 1. Otherwise leave it blank.

Oracle

To communicate with the hotel’s Oracle interface, the customer must provide either:

  • Integration Username and Region
  • Enterprise ID, Chain Code and Region

After that, contact either Ryan or Daniel to set up the integration in the Oracle Developer Portal.

It is suggested that the customer’s transaction codes match product groups. We do this by matching the transaction code, for example 1000, to the Group cust_ref. The default cashier we use is ID 1473. Tender cust_ref will need to match the Payment Method Code, for example CA for Card. For PF Room mapping, use Custom Field 1 in tenders to enter the PF Room number, for example 8000.

Troubleshooting

Query the Tapa logs for hotel to investigate any issues.

FAQ

Which Oracle details must the customer provide?

The customer must provide either Integration Username and Region, or Enterprise ID, Chain Code and Region, along with the Tapa tender settings and Oracle Developer Portal credentials.

When should Port be set to 1?

Only set Port to 1 when the customer wants to use a non-production Oracle Cloud environment for testing. Otherwise leave it blank.