Yellow Dog/Simphony2 w/Oracle Integration Overview

Yellow Dog/Simphony2 w/Oracle Integration Overview

This document will provide an overview of the Yellow Dog /Simphony 2Way integration 

Integration Approach

The Yellow Dog/Simphony integration is a 2Way integration
  1. Sales – pulled in from files provided by Oracle once per day 
  2. Codes – pulled from the Simphony API
  3. Items – pushed to the Simphony API 

Requirements for Items to Push to Simphony 

  1. The item must be active 
  2. The item must be available to the store 
  3. The item must not be POS Blocked - this can be checked in the interface codes as of sync view. From this view, users can also quickly identify that Publish is enabled, and that the item is available to the store in question.

  1. The item must be set to publish

  1. The item must have a Major Group set in interfaces
  2. The item must have a Family Group set in interfaces
  3. The item must have a Menu Item Class set in interfaces

Best Practices for Managing Items

Updates and edits to items should be made in Yellow Dog and allowed to push to Simphony. If updates are made directly in Simphony it will be overwritten by Yellow Dog the next time the integration runs.

What to check before calling support:

  1. Check that your items have all requirements set
  2. Confirm your scheduled sync time has passed, feel free to ask support when your sync times are or refer to the scheduled apps report in YD’s Standard Report section to review your sync times.
  3. Note any errors appearing at the POS when you try to scan. If your items are still not able to be rung up at the POS, these errors can help support identify the issue.

Limitations 

  1. Sales are only provided once per day
  2. Sales do not contain transaction specific details such as check closed or transaction numbers
  3. Before removing items from Simphony, users will need to turn the item to “No, push nothing” in the publish field to prevent errors in the sync
  4. This integration does not delete barcodes from Simphony, any barcodes deleted in YD will need to be removed in Simphony manually
  5. There is a 13 digit limit for all barcodes 

For additional information on the Yellow Dog/Simphony Integration visit https://help.yellowdogsoftware.com/micros-simphony-2x-oracle-hosted/



    • Related Articles

    • Yellow Dog/Roller Integration Overview

      This document will provide an overview of the Yellow Dog Roller Integration Integration Approach This integration can be set up as a 2Way - Pull sales & Push items or a 1Way - Pull sales Sales – Pulled from Roller Webhook Codes – Pull from Roller API ...

    • Yellow Dog/Resort Suite Integration Overview

      This document will provide an overview of the Yellow Dog Resort Suite Integration Integration Approach This is a two-way file exchange integration – we pull sales and push items Sales – pulls sales from a CSV file Summary: will provide sales as a ...

    • Yellow Dog/Toast Integration Overview

      This document will provide an overview of the Yellow Dog Toast Integration Integration Approach This is a 1Way Integration – Pull sales only Sales – Pulled from the Toast API Items – Can be matched on SKU Item management best practices Yellow Dog ...

    • Yellow Dog/Silverware Integration Overview

      This document will provide an overview of the Yellow Dog Silverware Integration Integration Approach This can be setup as a 2Way – Push items and Pull sales or a 1Way – Pull sales Sales – Pulled from the Silverware API Codes – Pulled from the ...

    • Yellow Dog/Revel Integration Overview

      This document will provide an overview of the Yellow Dog Revel Integration Integration Approach This can be set up as a 2Way – Push items and Pull Sales or a 1Way – Pull Sales Sales – Pull from Revel Webhook Codes – Pull from Revel API Items – Push ...

    • Recent Articles

    • Yellow Dog Inventory Troubleshooting: Unable to start Auto-Restock for upcoming event

      This article will help you identify and resolve why you are unable to create an ‘Auto-Restock’ Issue The ‘Create New Auto-Restock’ button is greyed out, cannot be clicked on and a new auto restock cannot be created. Causes The event has not been ...

    • How To: Import Interfaces by Level using Balto

      This document will review how to import interface settings for a level using the Balto import tool. Prerequisites Items are required to exist in YD already Items cannot be marked as removed. The stores must also exist in YD Yellow Dog user with ...

    • How To: Update Par & Re-Order Points via the Balto Import Tool

      This document will review how to update Par & Re-Order Points via the Balto import tool With all Balto imports, be sure not to change any of the column headers in the template. Unused columns can be removed, but the headers should not be edited in ...

    • How To: Update Items Store Availability via the Balto Import Tool

      This article will review how to update items store availability with the Balto Import Tool With all Balto imports, be sure not to change any of the column headers in the template. Unused columns can be removed, but the headers should not be edited in ...

    • Yellow Dog/Jonas File Exchange Overview

      This document will provide an overview of the Yellow Dog Jonas File Exchange Integration Integration Approach This is a 2Way integration – pull sales and push items • Sales – pulled from a file • Items – pushed to .csv file • Codes – Inserted into ...