This page details the approach to Oracle configuration in both the RBI platform and the POS.
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.
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.
PLU, Definition Sequence and Price Sequence are the 3 Oracle attributes which we will use to distinguish across different structures, service modes and modifier quantities.
The logic behind the menu configuration is that the combination of these 3 attributes will always lead to a unique PLU for each menu structure. For example, a single Whopper for delivery will have a unique PLU.
These are the 3 Oracle attributes:
Attribute | Description | Oracle’s Enterprise Management Console (EMC) Image |
|---|---|---|
Oracle PLU | The Oracle PLU (Price Look-Up codes) is the unique record number that identifies each Menu Item Master. |  |
Definition Sequence ( | Definition sequences are defined in each Menu Item Master and they can change the behavior of the item they’re connected. For example, the same Menu Item Master can be displayed differently in the POS touchscreens and receipts using different definition sequences. Each Menu Item Master can have up to 64 menu item definitions. | |
Price Sequence ( | Price sequences are defined for each definition sequence. Definition sequences can have multiple prices. |  |
In summary, Menu Item Masters contain the Oracle PLU. Each PLU has one ore more definition sequences, and each definition sequence has one or more price sequences.
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.
For example, for an item with Menu Item Master ID 200137, definition sequence 1 and price sequence 2 (Delivery), the following PLU will be generated: 200137-1-2.
Our recommendation is to use:
For menu items:
Price Sequence to distinguish between service modes, where 1 is Pickup and 2 is Delivery. It is also possible (but not recommended) to use Definition Sequence to distinguish between service modes.
Definition Sequence to be always 1.
For modifiers:
Price Sequence to distinguish between service modes and Add/No modifiers (details here). It is possible (but not recommended) to use different Menu Item Master ID’s than those mentioned in the linked documentation. It is also possible (but not recommended) to use Definition Sequence instead.
Definition Sequence to be always 1.
More details can be found in each sub-section of the Oracle Config - Menu documentation.
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.
Deviations from the proposed structure are not recommended. The recommended approach will results in a faster rollout and less issues, and new features will be built based on the recommended structure.