Creating new stores with EEE: Difference between revisions

From EnablerWiki
Jump to navigationJump to search
← Older editNewer edit →

Brant (talk | contribs)

92 edits
mNo edit summary
Brant (talk | contribs)
92 edits
No edit summary
Line 1: Line 1:
Created: 14 October 2009. Last Reviewed: 14 January 2011
Created: 14 October 2009. Last Reviewed: 3 October 2014


== Process for creating new stores with EEE & Enabler ==


'''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.
 
'''Add the new branch in EEE (with a EEE environment)'''
# From the EEE menu select Location Management
# From the Location menu select Branch and then click on ADD
# Type in the required details for the new branch. Items shown with a red * are mandatory fields. Ensure that the logical address you used when setting up the store in Enabler H/O, is entered in the Logical Address field on this screen, and the branch is setup in the same Region as was used in Enabler H/O. (If the store is not ready to go online, you must tick the option “Exclude this branch from data exports”)
# Click on Save to save the new branch.
# On save of a new branch a prompt to clone Prices, Costs, Purge Parameters, and Min/Max levels from another branch will occur.
#* If you don’t clone prices/costs etc from another store, then there will be no prices/costs available to export to a store until they have been entered. You have an option to SKIP this step and perform the cloning at a later stage.
Enter new branch code to “clone to branch” and enable the prices required and branch code that prices will be cloned from.
<nowiki>Set the last export date/time for master file exports. Data cannot be exported to a branch until the export date and time has been completed for that branch.</nowiki>
 
<nowiki>Set the Last Export Date/Time. Master file records will only be exported from this date onwards.</nowiki>
 
''Any records modified before this date will not be sent. (If you have a large product database, you can keep a master copy of the master file databases as at a certain date, and then only export records modified since that date. This will make processing the initial isl-file.dat much quicker. The master copy of the databases would be copied to the store machines when they are being set up).''


<nowiki>Leave Export Date/Time unchanged. This will result in all Master file records being exported to the branch.</nowiki>


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”.
'''Add the new branch in Enabler (no EEE environment)'''
# On the Enabler Head Office Server from Back Office select Global Setup
# Highlight region code and select Add for a new branch record
# Enter All Branch details required.
#* Branch code (can be either alpha or numerical or both)
#* Logical address is normally four digits made up of region code and branch code.
#* Ensure offline flag is set correctly. Once disabled maintenance files will be created for new branch.
# Select OK enter to save new branch records


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.
'''Add the store server in Enabler'''
# On the Enabler Head Office Server from Back Office select Global Setup and highlight new branch. (If using EEE confirm new branch code has been added and flowed down to Enabler H/O . Can be manually exported from EEE using data exporter to send branch records but will usually flow down during scheduled export if H/O branch is included in exports from EEE)
# To add new server we always recommend cloning from an existing store so configurations are consistent. Need to first highlight an existing store server then click on the clone button (try to 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)if possible)
# Drag and click clone arrow over the name of the Branch  where you are adding the new store server
# Key in the branch code, press Tab then key in the 2 digit till number, key in the name/location of the till, press enter to save
# Highlight the new server on the left hand side then highlight System Parameters on left and click on config button to open screen
# Key in the new branch details, press enter to save
# Highlight the new server on the left hand side then expand Sales and highlight  Docket Setup, click on config button to open screen then key in the correct header details, press enter to save
# Highlight the new server on the left hand side then expand Transaction Processing / Comms, highlight Communication click on config button to open screen. Replace the cloned machine name with the store servers machine name in the following fields:
#*Database server (UNC name) \\servername
#*Time Server (UNC name) \\servername
# If you have multiple tills and wish to backup your Enabler databases and configuration to another machine on the local network, follow this step. <br /><br />Highlight the new server on the left hand side then expand Transaction Processing / Comms, highlight, Backup Options Setup click on config button to open screen. Replace the backup path with the path to another machine on your local network or to a another drive letter , e.g.: ''\\tillname\en\enabler\backup or d:\backup''




# 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.
# 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 <nowiki>*</nowiki>.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
# 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.
# 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.
# 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.
# 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.
# 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'''
# 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)''
# Click on the name of the Branch where you are adding the new store server
# 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.
# Highlight the new branch name on the left hand side then select System Parameters
# Key in the new branch details, press enter.
# Select Sales, Docket Setup then key in the correct header details, press enter.
# 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
# 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
# If there is only one machine (store server) in the new branch, skip to “export the configuration”.<br/> '''Add Any Tills (nodes)'''
# Highlight a till(node on an existing branch then click on Clone.
# 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.
# Highlight the new till on the left hand side
# Select Sales, Docket Setup then key in the correct header details, then press Enter.
# 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'''Configuration Base directory''' \\servername\enserver\enabler\comms\config'''
# 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]
# 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'''
# From Back Office select Global Setup
# Highlight the Store Branch Name
# Specify a shared folder location
# Click on the Export button
# Type in the shared path name when prompted for a path
# 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
# You should see a configuration successfully exported message when finished


For further information, see the Magenta document “Staging and Support”
'''Add tills (nodes) in Enabler'''
# On the Enabler Head Office Server from Back Office select Global Setup
# Highlight a till (node) in any existing branch then click on Clone (select a till where enabler is installed on same drive as new till)
# Drag and click clone arrow over the name of the Branch  where you are adding the new till then key in the 2 digit till number, then key in the name/location of the till, press enter to save.
# Highlight the new branch on the left hand side
# Highlight the new branch on the left hand side then highlight System Parameters on left and click on config button to open screen. Select All to update till docket setup configurations with those already configured for the server.
# As above highlight branch and Expand Sales and highlight Docket Setup, click on config button to open screen, Select All to update till docket setup configurations with those of the server. press enter to save changes to till
# This screen requires access at till level so ensure the till is highlighted, expand Transaction Processing / Comms, and highlight Communication click on config button to open screen. Replace the machine name with the new store servers machine name in the following fields:
#* Database server (UNC name) \\servername
#* Time Server (UNC name) \\servername
#* Configuration Base directory \\servername\enserver\enabler\comms\config
# This screen requires access at till level so ensure the till is highlighted Highlight Database Setup click on config button to open screen then replace the machine name with the store servers machine name in the following fields:
#* Lan Transactions \\servername\enserver\enabler\lantran
#* Lan Master Files \\servername\enserver\enabler\local
#* Lan Maintenance files \\servername\enserver\enabler\lanmnt
# Select Transaction Processing / Comms, Version Control Setup then replace the machine name with the store servers machine name:<br />Upgrade Package Path: ''\\servername\enserver\enabler\comms\upgpack'' <br />(if the upgrade path refers to a central location rather than the store server, then leave this setting unchanged)

Revision as of 04:56, 3 October 2014

Created: 14 October 2009. Last Reviewed: 3 October 2014

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.

Add the new branch in EEE (with a EEE environment)

  1. From the EEE menu select Location Management
  2. From the Location menu select Branch and then click on ADD
  3. Type in the required details for the new branch. Items shown with a red * are mandatory fields. Ensure that the logical address you used when setting up the store in Enabler H/O, is entered in the Logical Address field on this screen, and the branch is setup in the same Region as was used in Enabler H/O. (If the store is not ready to go online, you must tick the option “Exclude this branch from data exports”)
  4. Click on Save to save the new branch.
  5. On save of a new branch a prompt to clone Prices, Costs, Purge Parameters, and Min/Max levels from another branch will occur.
    • If you don’t clone prices/costs etc from another store, then there will be no prices/costs available to export to a store until they have been entered. You have an option to SKIP this step and perform the cloning at a later stage.

Enter new branch code to “clone to branch” and enable the prices required and branch code that prices will be cloned from.

Set the last export date/time for master file exports. Data cannot be exported to a branch until the export date and time has been completed for that branch.

Set the Last Export Date/Time. Master file records will only be exported from this date onwards.

Any records modified before this date will not be sent. (If you have a large product database, you can keep a master copy of the master file databases as at a certain date, and then only export records modified since that date. This will make processing the initial isl-file.dat much quicker. The master copy of the databases would be copied to the store machines when they are being set up).

Leave Export Date/Time unchanged. This will result in all Master file records being exported to the branch.


Add the new branch in Enabler (no EEE environment)

  1. On the Enabler Head Office Server from Back Office select Global Setup
  2. Highlight region code and select Add for a new branch record
  3. Enter All Branch details required.
    • Branch code (can be either alpha or numerical or both)
    • Logical address is normally four digits made up of region code and branch code.
    • Ensure offline flag is set correctly. Once disabled maintenance files will be created for new branch.
  4. Select OK enter to save new branch records


Add the store server in Enabler

  1. On the Enabler Head Office Server from Back Office select Global Setup and highlight new branch. (If using EEE confirm new branch code has been added and flowed down to Enabler H/O . Can be manually exported from EEE using data exporter to send branch records but will usually flow down during scheduled export if H/O branch is included in exports from EEE)
  2. To add new server we always recommend cloning from an existing store so configurations are consistent. Need to first highlight an existing store server then click on the clone button (try to 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)if possible)
  3. Drag and click clone arrow over the name of the Branch where you are adding the new store server
  4. Key in the branch code, press Tab then key in the 2 digit till number, key in the name/location of the till, press enter to save
  5. Highlight the new server on the left hand side then highlight System Parameters on left and click on config button to open screen
  6. Key in the new branch details, press enter to save
  7. Highlight the new server on the left hand side then expand Sales and highlight Docket Setup, click on config button to open screen then key in the correct header details, press enter to save
  8. Highlight the new server on the left hand side then expand Transaction Processing / Comms, highlight Communication click on config button to open screen. Replace the cloned machine name with the store servers machine name in the following fields:
    • Database server (UNC name) \\servername
    • Time Server (UNC name) \\servername
  9. If you have multiple tills and wish to backup your Enabler databases and configuration to another machine on the local network, follow this step.

    Highlight the new server on the left hand side then expand Transaction Processing / Comms, highlight, Backup Options Setup click on config button to open screen. Replace the backup path with the path to another machine on your local network or to a another drive letter , e.g.: \\tillname\en\enabler\backup or d:\backup


Add tills (nodes) in Enabler

  1. On the Enabler Head Office Server from Back Office select Global Setup
  2. Highlight a till (node) in any existing branch then click on Clone (select a till where enabler is installed on same drive as new till)
  3. Drag and click clone arrow over the name of the Branch where you are adding the new till then key in the 2 digit till number, then key in the name/location of the till, press enter to save.
  4. Highlight the new branch on the left hand side
  5. Highlight the new branch on the left hand side then highlight System Parameters on left and click on config button to open screen. Select All to update till docket setup configurations with those already configured for the server.
  6. As above highlight branch and Expand Sales and highlight Docket Setup, click on config button to open screen, Select All to update till docket setup configurations with those of the server. press enter to save changes to till
  7. This screen requires access at till level so ensure the till is highlighted, expand Transaction Processing / Comms, and highlight Communication click on config button to open screen. Replace the machine name with the new store servers machine name in the following fields:
    • Database server (UNC name) \\servername
    • Time Server (UNC name) \\servername
    • Configuration Base directory \\servername\enserver\enabler\comms\config
  8. This screen requires access at till level so ensure the till is highlighted Highlight Database Setup click on config button to open screen then replace the machine name with the store servers machine name in the following fields:
    • Lan Transactions \\servername\enserver\enabler\lantran
    • Lan Master Files \\servername\enserver\enabler\local
    • Lan Maintenance files \\servername\enserver\enabler\lanmnt
  9. Select Transaction Processing / Comms, Version Control Setup then replace the machine name with the store servers machine name:
    Upgrade Package Path: \\servername\enserver\enabler\comms\upgpack
    (if the upgrade path refers to a central location rather than the store server, then leave this setting unchanged)
Retrieved from "https://theoracle.magentaretail.com.au/index.php?title=Creating_new_stores_with_EEE&oldid=1362"