Oracle Simphony
DLH.io documentation for Oracle Simphony
Oracle Simphony is a cloud based point-of-sale platform for restaurants and hospitality groups that handles order entry, kitchen display, payments, and labor across single locations and large multi-location enterprises.
Use the DLH.io connector to retrieve data about locations, menu items, guest checks, payments, and labor and sales totals from the Simphony Business Intelligence (BI) API. To learn more about Oracle Simphony, visit their page (https://www.oracle.com/food-beverage/restaurant-pos/simphony-pos/).
Setup Instructions
Follow the setup steps guide for configuring your Oracle Simphony connection to enable data to flow into your destination via DLH.
Supported Features
Here are key features supported for this connector.
| Sync Feature | Supported | Details |
|---|---|---|
| Custom Data and Development | ✓ | Ability to enhance connector upon request |
| Historical Re-Load/Load | ✓ | Defaults to 365 days of transactional history on the first sync |
| Incremental/Delta Load | ✓ | Gets most recent records and changes |
| Column Selection | ✓ | |
| Column Hashing | ✓ | |
| Re-Sync Table/Entity | ✓ | Select at the table level to reload data history (on next Sync Bridge run) |
| Custom Queries | Utilizing SQL Data Query Connector | |
| Custom Data | ||
| Captures Deleted Rows | Guest checks expose a cancel flag; most tables have no delete marker | |
| API Sync Bridge Initiation | ✓ | |
| Priority Scheduling | ✓ | |
| Private VPC/Link | ☂ | |
| DLH Data Model Available | - |
If you have any questions about these supported features please reach out to our Customer Support team.
Details on Sync Processing
For this connector, we believe the sync processing is straightforward. We've provided a number of details, steps, and other guidance here and in the setup steps guide. Be sure to also check the change log and notes page from time to time for any changes.
DLH.io connects to the Simphony BI API using OAuth 2.0. This connection is read only and never writes data back to Simphony.
Reference/dimension tables such as locations, employees, menu items, discounts, and taxes are fully reloaded on every sync since Simphony does not expose a changed-since marker for them. Transactional tables (guest checks, payments, journal entries, KDS orders) and the daily and quarter hour total tables use a rolling changed-since window and also re-check the last two days of business dates on every run to catch any late updates or closed-out checks.
Connecting to Your Oracle Simphony Account
This section enumerates the options in the Credentials and Details panes in the Oracle Simphony Connector page within DLH.io.
Credentials Pane
This pane contains fields for entering credentials to connect to your Oracle Simphony account. The following table describes what is needed for each field:
| Field | Description |
|---|---|
| Application Server URL | The Simphony data host, for example https://simphony-home.yourcluster.oraclerestaurants.com. |
| Authentication Server URL | The Simphony OIDC identity host, for example https://ors-idm.yourcluster.oraclerestaurants.com. This is a different host from the Application Server URL. |
| Enterprise Short Name | The three character organization identifier for your Simphony enterprise. |
| Client ID | The Client ID issued for your Business Intelligence (BI) API account. |
| User Name | The user name for your BI API account. |
| Password | The password for your BI API account. |
If you have any issues obtaining these values, reach out to your Simphony administrator or Oracle representative, since the BI API account is created and permissioned inside the Enterprise Management Console (EMC), not inside DLH.io.
Replicated Entities
The following Oracle Simphony entities are replicated to your target destination. These are the table names you will see:
- LOCATIONS
- LOCATION_WORKSTATIONS
- REVENUE_CENTERS
- EMPLOYEES
- JOB_CODES
- CASHIERS
- CASH_MANAGEMENT_ITEMS
- MENU_ITEMS
- MENU_ITEM_PRICES
- DISCOUNTS
- SERVICE_CHARGES
- TAXES
- TENDER_MEDIA
- ORDER_TYPES
- ORDER_CHANNELS
- REASON_CODES
- PAYMENT_ACCOUNT_HOLDERS
- PAYMENT_ACCOUNTS
- GUEST_CHECKS
- GUEST_CHECK_DETAIL_LINES
- GUEST_CHECK_TAXES
- POS_JOURNAL_LOG
- POS_WASTE_DETAILS
- NON_SALES_TRANSACTIONS
- SPI_PAYMENTS
- KDS_ORDERS
- OPERATIONS_DAILY_TOTALS
- CONTROL_DAILY_TOTALS
- EMPLOYEE_DAILY_TOTALS
- MENU_ITEM_DAILY_TOTALS
- DISCOUNT_DAILY_TOTALS
- ORDER_CHANNEL_DAILY_TOTALS
- ORDER_TYPE_DAILY_TOTALS
- SERVICE_CHARGE_DAILY_TOTALS
- TAX_DAILY_TOTALS
- TENDER_MEDIA_DAILY_TOTALS
- OPERATIONS_QTR_HOUR_TOTALS
- MENU_ITEM_QTR_HOUR_TOTALS
- DISCOUNT_QTR_HOUR_TOTALS
- ORDER_TYPE_QTR_HOUR_TOTALS
- SERVICE_CHARGE_QTR_HOUR_TOTALS
- TENDER_MEDIA_QTR_HOUR_TOTALS
- CASH_MANAGEMENT_DETAILS
Locations and Enterprise Wide Data
Most Simphony entities are pulled per location using each location's LOC_REF. A few entities, such as LOCATIONS itself and PAYMENT_ACCOUNT_HOLDERS, answer for the whole enterprise in a single call, so the same enterprise wide result is not repeated for every location.
Schema Details (ER Diagram)
This entity relationship diagram (ERD) provides you with information about what entities/tables DLH provides for you out-of-the-box and how they are related to one another.
Common Issues
If any issues occur with the authorization, simply return to the sources page in DLH.io, edit the source details and click the Save & Test button to confirm connectivity. A newly issued BI API account will reject sign-in until its first-time password has been changed once in Simphony, so confirm that step was completed if authentication keeps failing.
If any issues persist please contact our support team via the DLH.io Support Portal.