Overview

Yellow Dog Inventory synchronizes data with Micros. This document outlines requirements necessary to ensure a clean sync.

Once each hour, Yellow Dog Inventory will push all new item definitions into the Micros database as well as pull all sales and returns. Various other codes are also pulled from Micros.

Requirements

Yellow Dog Requirements

The following information is necessary in order to fully configure Yellow Dog Inventory to interface with Micros:

  • A complete list of revenue center names and numbers that will contain retail inventory.
    • Parent/Child setup? Please let us know if the retail RVCs will be part of a Parent/Child setup in Micros. Note: In a Parent/Child configuration any items shared between stores will also need to share all Micros codes (Major, Family, etc).
  • 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 (see below). In the past, Yellow Dog Inventory always used NLU Group 32. It is now soft-settable.

Please provide this information to Yellow Dog Software.

Back Office Setup Requirements

  • 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.
  • NLU group 32 is used by Yellow Dog Inventory and should be labeled "BARCODES". This needs to be programmed for each retail revenue center. All inventory items will use this group. Note: 32 is no longer required.
  • Barcode NLU Help Screen must be disabled.
  • Barcode Menu Item NLU Group must be set to 32.

Servers

While we do not need access to the EMC, we will need the following:

  • The Micros database server will need to be able to communicate with the Yellow Dog Inventory application server via port 1433. 
  • The sync application will need a SQL login to the Micros database (typically MCRSPOS). This login only requires read and write access to the database. We can set up the login by being given access to the Micros database server.

Sharing the Micros Database Server

Sometimes the customer chooses to use the Micros database server to house the Yellow Dog Inventory database. In this case, the following is required:

  • Yellow Dog Software requires permission from your Micros representative to install our database.
  • Yellow Dog Inventory requires Microsoft SQL Express 2005 or higher. A single database will be created. This database will be given its own SQL login that only has access to this database. All programs connecting to the Yellow Dog Inventory database will use this login. If the database server is running Microsoft SQL 2000, we will need to either:
    1. Upgrade SQL Server.
    2. Install SQL Server 2005 beside SQL Server 2000 as a named instance. Technically, this poses no problems. It will use up additional resources on the server.

Data Exchange

While syncing data between Yellow Dog Inventory and Micros, Yellow Dog Inventory reads and writes data from the MCRSPOS database using a stand-alone executable named SyncYdiWithMicros9700.exe. 

The sync application connects directly to the Micros database (typically MCRSPOS) in order to both read and write data. In the past we used Micros' 8700sql.exe tool to read/write data, but we are not supporting this in new installs.

Exporting Item Data

The following tables are written to by SyncYdiWithMicros9700:

  • BARCODE
  • MENU_ITEM_DEFINITION
  • MENU_ITEM_DEFINITION_MAIN
  • MENU_ITEM_DEFINITION_SUB
  • MENU_ITEM_MASTER
  • MENU_ITEM_PRICE
  • STRING_NUMBER_PARAMETER
  • STRING_NUMBERS
  • STRING_TABLE

Importing Sales and Code Data

The following tables are read from by SyncYdiWithMicros9700:

  • BARCODE
  • CASHIER
  • CHECK_DETAIL
  • CHECKS
  • DISCOUNT
  • DISCOUNT_DETAIL
  • DISCOUNT_ITEMIZER
  • DISCOUNT_ITEMIZER_DISCOUNT
  • EMPLOYEE
  • FAMILY_GROUP
  • HIERARCHY_STRUCTURE
  • HIERARCHY_UNIT
  • MAIN_MENU_LEVEL
  • MAJOR_GROUP
  • MENU_ITEM_CLASS
  • MENU_ITEM_DEFINITION
  • MENU_ITEM_DEFINITION_MAIN
  • MENU_ITEM_DEFINITION_SUB
  • MENU_ITEM_DETAIL
  • MENU_ITEM_MASTER
  • MENU_ITEM_PRICE
  • NUMBER_LOOKUP
  • REVENUE_CENTER
  • SCREEN_LOOKUP
  • STRING_NUMBERS
  • STRING_TABLE
  • SUB_MENU_LEVEL
  • TENDER_MEDIA
  • TENDER_MEDIA_DETAIL

Implementation

Installation

SyncYdiWithMicros9700 can connect to the database using either a trusted connection or a SQL login. SyncYdiWithMicros9700 can run on any server (unless the Yellow Dog Inventory server is hosted); it doesn't necessarily have to run from the Micros database or application server.

Additional Information

Limitations/Known Issues

When using SAR (Stand Alone Resiliency) Workstations, make sure to run the initial sync during an off time. The first sync handles a lot of information, and the SAR Workstations process more slowly, so it takes a much longer time. Following the first sync, it can be scheduled to run hourly as normal.