Micros Simphony (First Edition) - Oracle Hosted Interface
NOTE: This document applies only to First Edition versions of Simphony. If you have a different version, please contact Yellow Dog for more information.
Yellow Dog Inventory synchronizes data with Micros Simphony. This document outlines requirements necessary to ensure a clean sync.
Once each hour, Yellow Dog Inventory will push all new item definitions into Micros Simphony as well as pull all sales and returns. Various other codes are also pulled from Micros.
DO NOT insert inventory items into the Micros database. Yellow Dog Inventory will push items in automatically. If they are pre-loaded there will be problems.
If inventory items are already existing in the Micros database and cannot be cleaned out, please let us know ahead of time.
Existing POS items and modifiers may need to be reconfigured so that the proper item is listed in the sales information and can be mapped to reduce the correct inventory items. Yellow Dog can review your setup prior to your acceptance of the proposal to identify what you and your POS team will need to do to allow our inventory system to work properly.
DO NOT create blank records for inventory items. Yellow Dog Inventory will insert records as needed.
The following business information is necessary in order to fully configure Yellow Dog Inventory to interface with Micros:
Upgrading From Micros 9700?
Please let us know if there will be data changes (number ranges, revenue centers, major or family groups, etc), or if it will be a straight upgrade. Straight upgrades are easier for Yellow Dog, because we can convert all existing 9700 setups directly to Simphony setups.
Micros Simphony Codes
A complete list of revenue center names and numbers that will contain retail inventory.
All major group codes that will be used for retail items.
All family group codes that will be used for retail items.
All menu item classes that will be used for retail items. This will need to be provided per revenue center.
Starting item number range. By default, all inventory items will be placed in the Micros database starting at item number 8500000.
Reporting codes that will be used for retail items.
SLUs that will be used for retail items.
NLU group to use. This must be configured correctly, otherwise item lookups will not work correctly at the Micros Register.
The EGateway URL. This will look something like this:
Replace "simphony" with the app server name or IP, and port 8080 if necessary.
Access to a computer with the ImpExp.exe Micros utility installed. This will typically be the Micros Simphony application server. This is where we will install our sync application.
A non-expiring EMC username/password. ImpExp.exe requires an EMC username/password with Property Manager permissions to function. Notes:
Be aware that this password is often shown in plain text (because ImpExp.exe is a command-line utility).
Only use alpha-numeric characters. Otherwise ImpExp will fail and the EMC account may be locked.
We do not need access to EMC itself, although that might be helpful for troubleshooting.
NOTE: If your EMC user configuration requires automatic password expiration (i.e. every 60 days) it is your (the customer) responsibility to change it in the sync configurator. ImpExp.exe will not work without a valid EMC username/password, which means that sales and item changes will not sync if the password in our sync configurator has expired.
Data Exchange and Mapping
Micros Simphony typically generates a daily sales export at the end of each business day. This file is generally sent to an ftp location, agreed upon by Oracle/Micros, Yellow Dog Software, and the customer, where it will be picked up by the sync application. In most cases, Yellow Dog Software can provide this ftp location.
Data is written to Micros using Simphony's ImpExp.exe tool. (This tool is not adequate for pulling sales.)
New or updated inventory data is pushed into Micros Simphony using multiple steps.
SyncYdiWithMicrosSimphony.exe writes import files and command files to a shared folder on the Simphony application server. Only between 10 and 100 items are written at a time.
SyncYdiWithMicrosSimphony.exe launches ImpExp.exe against the command file and waits for it to finish.
If ImpExp.exe generates errors, those errors are forwarded to YDI and the items are slotted to sync again.
If ImpExp.exe is successful, the items are marked as synced and a new batch of items is started (Step 1).
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.
SyncYdiWithMicrosSimphony.exe should be installed and run from the Micros application server as best practice. If necessary it can be run from the Yellow Dog application server, but this requires the ImpExp.exe to be properly installed there.