| Note |
|---|
This page is a draft. |
| Info |
|---|
This page details the approach to Oracle configuration in both the RBI platform and the POS. |
Content
Contents
| Table of Contents | ||
|---|---|---|
|
Oracle POS Technical Requirements
Oracle is one of the RBI-approved POS that our franchisees can use in their markets. The following requirements apply:
Uses Oracle Symphony version 19.7 or above.
Uses Simphony Transaction Services Gen2 (STS Gen2) as the cloud service.
Symphony runs locally on the restaurant POS, while STS Gen2 is the cloud component that the POS connects to. STS Gen2 allows orders from the RBI platform to be sent to restaurants.
...
Overview
This page summarises the menu structure and identifier standard that must be followed by Franchisees to make the Oracle configuration compatible with the RBI Digital Platform.
Menu Configuration
Oracle Symphony offers multiple ways of configuring a menu. The following guides detail how a menu must be configured to be RBI-compliant.
...
You can find the menu configuration guides here: Oracle Config - Menu.
Unique Identifiers
The reason we use a unique PLUs for the menu structure (by combining PLU, Price Sequence and Definition Sequence attributes) is that the RBI Platform needs unique PLUs internally to function as expected. Internally, the RBI Platform will concatenate each attribute, separated by a dash, to create a unique PLU.
...
More details can be found in each sub-section of the Oracle Config POS - MenuConfiguration documentation.
| Note |
|---|
The approach above needs to be the same for all structures – i.e. you can’t use PLUs to distinguish service modes for items and definition sequences for combos. |
...