Overview

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 ran hourly.

Requirements

Yellow Dog Requirements

In order to push items to and pull code data from the API, we require the following:

  • Security Service URL
  • Data Service URL
  • EMC User
  • EMC Password
  • 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.

Prerequisites

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.

Servers

Net 4.6.2 must be installed where the sync will run.

Data Exchange

Exporting Item Data

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
HierarchyID Revenue Center
FirstName POS Description 1
SecondName POS Description 2
MenuItemClass Micros Class
SLU Micros SLU
NLU SKU
NLUGroup Micros NLU Group
HierarchyID Revenue Center
PriceSequence Retail 1
PrepCost Calculated Cost
ObjectNumber Item Number (Micros Number)
Code UPC, else 0
MasterObjectNumber Item Number (Micros Number)
DefinitionSequence Retail

Importing Sales Data

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).

Importing Code Data

Our sync pulls the following code data from Micros SImphony 2.9 via the API:

  • Major Group
  • Family Group
  • Menu Item Class
  • Menu Item Numbers

Implementation

Installation

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.

Additional Information

Limitations

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.