Creating new stores with EEE

From EnablerWiki

Jump to: navigation, search

Created: 14 October 2009. Last Reviewed: 14 January 2011


Process for creating new stores with EEE & Enabler


The following process should be followed when creating new stores when you are using both EEE and Enabler. This process doesn't include installing Enabler on the store computers and getting the store ready for trading. For information about Staging a new store, refer to the document “Staging and Support”.

The store should be initially created in EEE and then exported from EEE to Enabler HO. Once the store is in Enabler HO, you can then clone a Store Server and Tills from another store.


  1. The new store should be initially created in EEE from Location Management->Branch. As all branches must have a unique branch code and logical address, you can use the Branch browse screen to determine whether a branch code has already been used. Till Maintenance (Point Of Sales->Pos Till Maintenance) can be used to identify what logical addresses have been used. As an example, if you are adding a branch and that branch is in a region whose logical address is 02, you could search in Till Maintenance for all tills than contain 02, including those starting with 02.
  2. When creating a new branch in EEE, the Logical Address and Directory must be the same. When you populate the Logical Address field, this value will also be placed in the Directory field. All Mandatory fields are marked with an *.When a new store is created the following fields are ticked by default. If they don't apply, you should remove the ticks where applicable.(i) Consider Branch when re-ordering(ii) Consider branch when replenishing(iii) Allow purchase ordering for this branch(iv) Maintain Costs(v) Maintain Prices(vi) Maintain Min Max
  3. If the Enabler machines are not being setup at the same time as the branch is being created, you should turn on the flag “Do not export data to this branch”, otherwise Data exporter will export data and continue to re-export data as it won't be receiving an acknowledgement for the exported data.
  4. After clicking on SAVE to create the branch, you are then prompted whether to clone Prices, Costs, Branch Purge Parameters and Min/Max from another branch. You also have the option of skipping the cloning process. To clone, from another branch, enter a branch code beside each option and then press OK to proceed with cloning. If you don't clone data here, you must populate at least costs and prices from another method otherwise when data is exported to the store, products will have no prices or costs.
  5. If the option “Do not export data to this branch” was not ticked, you will be prompted to set the last export date for stores. If you want all master file data exported from Enabler, then select the option “Leave Last Export Date/Time Unchanged”, otherwise you can specify an date and all data modified since that date will be exported to Enabler.
  6. The creation of the branch in EEE is now complete. To get the branch details into Enabler HO so that you can create the tills, perform an export of new data from EEE to Enabler HO using EEE Data Exporter.
  7. From Enabler HO, if you are configured to import ISL-FILE.zip immediately when found, the branch will have been imported into Enabler, otherwise you will need to perform a Host Import to import the branch.Add Store Server
  8. Highlight an existing store server then click on the clone button (make sure you clone off a store server that has Enabler installed on the same drive as the new branch. Always clone a store server from a store server and a till (node) from another till (node)
  9. Click on the name of the Branch where you are adding the new store server
  10. Key in the branch code, press Tab then key in the 2 digit till number, press Tab then key in the name/location of the till, press enter.
  11. Highlight the new branch name on the left hand side then select System Parameters
  12. Key in the new branch details, press enter.
  13. Select Sales, Docket Setup then key in the correct header details, press enter.
  14. Select Transaction Processing / Comms, Communication then replace the machine name with the store servers machine name in the following fields: Database server (UNC name) \\servername Time Server (UNC name) \\servername
  15. If you have multiple tills and wish to backup your Enabler databases and configuration to another machine on the local network, follow this step.Select Transaction Processing / Comms, Backup Options Setup then replace the backup path with the path to another machine on your local network, e.g. \\tillname\en\enabler\backup
  16. If there is only one machine (store server) in the new branch, skip to “export the configuration”.
    Add Any Tills (nodes)
  17. Highlight a till(node on an existing branch then click on Clone.
  18. Click on the name of the Branch where you are adding the new till, then key in the 2 digit till number, Press Tab then key in the name/location of the till, then press Enter.
  19. Highlight the new till on the left hand side
  20. Select Sales, Docket Setup then key in the correct header details, then press Enter.
  21. Select Transaction Processing / Comms, Communication then replace the machine name with the store servers machine name in the following fields:-Database server (UNC name) \\servernameTime Server (UNC name) \\servernameConfiguration Base directory \\servername\enserver\enabler\comms\config
  22. Select Database Setup then replace the machine name with the store servers machine name in the following fields:-Lan Transactions [file://servername/enserver/enabler/lantran \\servername\enserver\enabler\lantran]Lan Master Files [file://servername/enserver/enabler/local \\servername\enserver\enabler\local]Lan Maintenance files [file://servername/enserver/enabler/lanmnt \\servername\enserver\enabler\lanmnt]
  23. Select Transaction Processing / Comms, Version Control Setup then replace the machine name with the store servers machine name:Upgrade Package Path [file://servername/enserver/enabler/comms/upgpack \\servername\enserver\enabler\comms\upgpack](if the upgrade path refers to a central location rather than the store server, then leave this setting unchanged)Export the Enabler Configuration
  24. From Back Office select Global Setup
  25. Highlight the Store Branch Name
  26. Specify a shared folder location
  27. Click on the Export button
  28. Type in the shared path name when prompted for a path
  29. You will receive a message “Include Data common to all stores but maintained by EEE”. As you have EEE installed, select NO to this option
  30. You should see a configuration successfully exported message when finished

For further information, see the Magenta document “Staging and Support”

Retrieved from "http://theoracle.magentaretail.com.au/Creating_new_stores_with_EEE"
Personal tools