55 Transaction Services

Transaction Services is a web service that allows Simphony to interface with third-party applications (for example, hotel self-service kiosks or room service devices, menu boards, and Enterprise online ordering). Transaction Services is commonly installed in stadiums that use self-ordering devices. Guests can place orders using a third-party application that interfaces with a Transaction Services client. The client then sends the guest checks to Simphony. To configure Transaction Services, EMC user access privileges are required.

Beginning with Oracle MICROS Simphony version 19.2, there are two types of Transaction Services available for use.

  1. Transaction Services Gen 1

    Transaction Services Gen 1 is the legacy version of the product that is typically deployed at a local Property and supports a single revenue center (RVC) or group of RVCs.

  2. Simphony Transaction Services (STS) Gen 2

    The use of STS Gen 2 is supported for Simphony Standard Cloud Service customers (those hosted on the Oracle Hosting Center). Oracle Hosting must complete configuration tasks to enable this functionality. This access is required to support uploading images to a storage service named Oracle Cloud Object Storage. Once your OCI and cloud object storage access has been configured by Oracle Hosting, you can upload images from the Simphony EMC for display on POS workstations or other integrated solutions. STS Gen 2 is optimized for the Simphony product and lets users better handle digital transactions. It does so by being deployable on either an Enterprise (supports multiple tenants) or a property location (supports a single revenue center or group of revenue centers), similar to the way Transaction Services Gen 1 operates.

    If you are using the STS Gen 2 API cloud offering and have more than one POS API Client workstation type available in a revenue center, Oracle Food and Beverage recommends enabling at least two workstation devices which can receive checks and orders as this provides resiliency should one of the workstations become unavailable.

    Tip:

    Your STS Gen 2 services URL and the OpenId Connect server endpoint values are located on the Applications subtab on the Enterprise Parameters tab in the EMC. The STS Gen 2 URL represents the base URL for the services exposed in your environment. The remainder of the URL for each of the service endpoints in a given version is consistent regardless of the environment they are deployed in. The OpenID Connect URL represents the base URL for the OpenID Connect endpoints that are used to acquire tokens for use with STS Gen 2. See the Oracle MICROS Simphony Transaction Services Generation 2 API Reference Guide for more information on service endpoints and authentication and authorization for STS Gen 2.
    The following EMC modules have consumer-facing content fields:
    • Menu Item Definitions

    • Family Groups

    • Condiment Group Names

    • Discounts

    • Service Charges

    • Tender/Media

      See Configuring Menu Item Definitions, Family Groups, and Condiment Group Names Consumer-Facing Settings for more information about configuring these specific modules.

      See Configuring Discounts, Tender/Media, and Service Charges Consumer-Facing Settings for more information about configuring these specific modules.

    Some examples of consumer-facing content includes such information as:

    • Consumer Facing Name

    • Consumer Item Name

    • Consumer Item Description

    • Consumer Image URL / Consumer Image Description

    • Consumer Family Group Name / Consumer Family Group Description

    This content can then be exposed to users during point-of-sale transactions via STS Gen 2.

    Additional consumer-facing content can be found and configured in the modules listed below. Each of these modules contain specific Property and Revenue Center location and contact information:
    • Enterprise level Properties

    • Property level RVC Configuration

      See Adding a Property and Adding a Revenue Center for information about configuring these modules.

    For Oracle-hosted customers (only), image URLs stored on Cloud Storage should not be distributed and utilized directly by downstream applications. Image URLs are provided to give external systems access to pull images associated with Oracle configuration and then cache those images in a performance appropriate environment for their consumption.

    Note:

    The Simphony Web Portal’s (SWP) Import/Export utility supports accessing all EMC consumer-facing field data.

    See the Simphony Transaction Services API Reference Document for more information about Transaction Services.