Micros Simphony - Oracle Hosted
Yellow Dog Inventory can provide a 2-way integration (push in items and process sales) with Oracle Hosted Simphony 2.9+ Premier or Standard.
This document outlines requirements necessary to ensure a clean sync.
Simphony exports a sales file once a day that Yellow Dog can then consume and update inventory. The Yellow Dog Sync itself can push item changes to the API at any point and is generally run hourly.
To see the specifications for other versions of Micros, use the links below:
Net 4.6.2 must be installed where the sync will run.
Each Simphony database location will have to be configured to generate the standard daily GLID file and publish to an ftp location. This location, agreed upon by Oracle/Micros, Yellow Dog Software, and the customer, is where the GLID will be picked up by the sync application. In most cases, Yellow Dog Software can provide this ftp location.
In order to push items to and pull code data from the API, we require the following:
Security Service URL
Data Service URL
User must have a minimum of the permissions selected below:
Revenue Center Codes: This will be 3 separate numbers separated by a space, for example "14 1 10": 14 is the Enterprise, 1 is the Property, and 10 is the Revenue Center.
A list of all Reporting Groups and NLU Groups.
The Yellow Dog interface can be configured to push menu items into Simphony in a variety of combinations. Please review these configuration options below with your Oracle team and Yellow Dog Implementation Guide:
Pushing Menu Items to Enterprise or Property.
Pushing Menu Item Definitions to Enterprise, Property, or Revenue Center.
Pushing Menu Item Prices to Enterprise, Property, or Revenue Center.
Data Exchange and Mapping
The standard GLID export files are .txt files within a .zip folder and are exported from Micros to an ftp location once a day.
Note: The Simphony sales files do not contain transaction level detail: no Transaction Numbers or transaction Check Closed DateTimes (all items in the file share the same CheckClosed DateTime based on the date provided in the header).
We export the following item details to Simphony 2.9:
|File Field||Yellow Dog Field|
|ObjectNumber||Item Number (Micros Number)|
|MenuItemName||POS Description 1|
|MajorGroup||Micros Major Group|
|FamilyGroup||Micros Family Group|
|ReportGroup||Micros Reporting Group|
|FirstName||POS Description 1|
|SecondName||POS Description 2|
|NLUGroup||Micros NLU Group|
|ObjectNumber||Item Number (Micros Number)|
|Code||UPC, else 0|
|MasterObjectNumber||Item Number (Micros Number)|
If an item is made inactive or deleted in Yellow Dog, the sync will remove the barcode from the item in Simphony, so it can not be scanned to add to a ticket.
Our sync pulls the following code data from Micros SImphony 2.9 via the API:
Menu Item Class
Menu Item Numbers
Yellow Dog Software is not provided any free support from Oracle. Any support that we need requires a Service Request submission (SR). Each SR will cost the client $75. Yellow Dog Software will present the SR request to each client for approval. Yellow Dog Software will always attempt to resolve an issue without an SR submission.
Requires 2.10.1 Hot Fix 5 or newer. This hot fix along with per system configuration updates are required.
Yellow Dog support will need to be provided an EMC password every 90 days in order for the sync to continue to operate.
The import of new items can take a considerable amount of time. Initial loads need to be carefully scheduled and planned.
The Simphony sales files do not contain transaction specific details like Transaction Numbers or Check Closed Date Time.
The sales files are only provided ONCE per day.
The sales files are generated by a process that is controlled by Oracle. They will need to provide the information regarding when these files will be generated and if they can be delivered by a certain time after an end of day process has occurred.
The export of the sales files needs to be configured on the primary server provided by Oracle. It cannot come from any redundant servers.
Yellow Dog does not currently support Zone configuration.
The sync can be run from any location where it can reach the agreed-upon ftp location and the API, if it is being used as a two-way sync).
.Net 4.6.2 will need to be installed wherever the sync is run.
We will install our sync application along with NewtonSoft.Json.dll.