Many of Mango's processes are integrated into your Eagle system and Acenet. It's quick and simple to set up your Eagle system! An API (application programming interface) allows different systems to communicate information with each other and will save your store a lot of keyboard labor!

1-Time Setup

1. Open Network Access or Secure Access.
2. In the function line, type OSPREY and press Enter.
3. Enter the password (if you don't know the password then contact your system administrator) and press Enter
4. In the Selection line, type ACEQMNGO and press Enter.
5. Run ACEQMNGO Utility? Press Y on the keyboard.
6. For a time to run the job, select the time between noon (12:00) and 4:55 p.m (16:55) with the time ending in a 0 or 5 (e.g. 13:15, 14:40, 15:10). Times like 12:23 or 14:09 will NOT work. We suggest using a random time (not on the hour) this helps spread out Eagle server requests to Mango.
   
   Here's a table to help determine a good time to select.
   
   
   
7. In the Action line, press E on the keyboard and then press Enter.
8. A message will display, "Running ACEQMNGO to create SEQ ...." Press Enter.
9. You can now close out of Network Access/Secure Access.
10. Once this job is run, a new row ‘MANGOAPI’ is added to SEQ of Store 1. This is a multi-store function so if you have multiple stores you'll only need to do this once. This job will contact Mango at the specified time to perform the duties of the API.

• Does this cost money to enable?
  No! This is completely free to set up and use.

  I'm multi-store, do all stores set this up individually or just the main store?
  This only needs to set up by the main store. The system will automatically provide lists for all stores in the organization.

  This helps for 100% CS Completion, is there anything else this will help with?
  Currently it's for helping with completion but it has laid the groundwork for future integrations.

  Do you have to set up who can and cannot view the list?
  The Eagle system automatically assigns the list to anyone with enough security to make changes in PIP/IMU.

  Will stores continue to get Count Sheets included in the monthly email?
  Yes, they will still get the Count Sheet.pdf. The Mango CSV file (Excel email) is discontinued because this integration replaces everything that file was used for.

• Your Eagle system can be set to automatically receive Mango's Count Sheets and display them in the LISTS screen. This increases the visibility of Count Sheet Completion and is a better alternative to manually loading Count Sheets into a viewer. This has no impact on any additional counting you do beyond Mango. 

  
  More information about checking Count Sheet completion with integration can be found here.

  
  When your Eagle server contacts Mango and finds a new Count Sheet, the following happens:  

  1. The new count list will be pulled into your Eagle system and loaded as a count list in LISTS. This list will also be assigned as a directed count list to users who can perform RF counts or modify PIP. This is controlled by security bits 423 'Add/change/delete physical inventory counts' or bit 863 'Mobile Inventory: Access/Update Mobile Physical Inventory' being turned on. The count list will be named with ‘MANGO’ as part of the title, so they can easily be located when clicking on the item list dropdown in LISTS.
     
     
  2. On the first of each month, the Mango count list will be deleted until the new list is ready (usually by the 4th of the month).
     
     
  3. Any uncounted items from a prior Mango list, those will be included on the new count list provided by Mango.

• When your Eagle server contacts Mango and finds a new Promo File, the following happens: 

  1. The new promo file will be added to MIP with Start Date and End Dates many years in the future (12/31/30). This prevents the promo from going live without anyone knowing.
  2. Any SKUs that sold to zero or PIP'd to zero will have the MDR removed from Location 2 and replaced with MDONE. This stops seasonal items or special orders in the future from going back on Closeout Management.

  If you process and submit SKUs from the Closeout Management grid of Acenet, your Eagle server will do the following:

  1. If you selected Start COM for a SKU the system sets Location 2 = MDR and Store Closeout Flag = Yes.
  2. If you selected Exclude COM SC=Y for a SKU the system set Location 2 = XDR and Store Closeout Flag = Yes.
  3. If you selected Exclude COM SC=N for a SKU the system  set Location 2 = XDR and Store Closeout Flag = NO.
  4. If you selected No Change for a SKU no action is committed to the SKU.

  
  MDR - indicator in Location 2 to include a SKU in Closeout Management (Store Closeout = Y is also needed).

  MDRPC - the byproduct of using Ace's Planogram Change Management tool to closeout a SKU and add to Mango COM.

  MDONE - location 2 given to a SKU automatically by Mango Report after it's completed its lifecycle on COM and QOH = 0. Prevents the SKU from being readded to COM in the future if special ordered or brought back into inventory.