<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://theoracle.magentaretail.com.au/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Trevor</id>
	<title>EnablerWiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://theoracle.magentaretail.com.au/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Trevor"/>
	<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/Special:Contributions/Trevor"/>
	<updated>2026-10-22T01:10:33Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.46.2</generator>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=Windows_Server_2012_required_components&amp;diff=1342</id>
		<title>Windows Server 2012 required components</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=Windows_Server_2012_required_components&amp;diff=1342"/>
		<updated>2013-05-02T02:22:59Z</updated>

		<summary type="html">&lt;p&gt;Trevor: Created page with &amp;quot;Created: 02 May 2013. Last Reviewed: 02 May 2013  ==Windows Server 2012 required components==  When installing Windows Server 2012 for installation of EEE, the following componen...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 02 May 2013. Last Reviewed: 02 May 2013&lt;br /&gt;
&lt;br /&gt;
==Windows Server 2012 required components==&lt;br /&gt;
&lt;br /&gt;
When installing Windows Server 2012 for installation of EEE, the following components must be installed:-&lt;br /&gt;
&lt;br /&gt;
===Windows Server Roles===&lt;br /&gt;
====Web Server (IIS)====  &lt;br /&gt;
* IIS should also include the following Role Services which are not default.&lt;br /&gt;
** Application Development: ASP.NET 4.5 (this also prompts you to install ISAPI Extensions, ISAPI Filters and .NET Extensibility 4.5)&lt;br /&gt;
** Security: Basic Authentication&lt;br /&gt;
** Security: Windows Authentication&lt;br /&gt;
** IIS 6 Management Compatibility(ALL)&lt;br /&gt;
&lt;br /&gt;
===Windows Features===&lt;br /&gt;
====.NET Framework 3.5 Features====&lt;br /&gt;
* &#039;&#039;&#039;Required on the Apps Server&#039;&#039;&#039;&lt;br /&gt;
* .NET Framework 3.5&lt;br /&gt;
* XPS Viewer&lt;br /&gt;
&lt;br /&gt;
The above roles and features must be installed prior to SQL Server being installed. Windows Updates should also be run to install all Windows updates which include security updates.&lt;br /&gt;
&lt;br /&gt;
===Enabler===&lt;br /&gt;
&lt;br /&gt;
Enabler is fully compatible with Windows Server 2012. If using FTPAgent to transfer files between EEE &amp;amp; Enabler, then please note that FTPAgent is &#039;&#039;&#039;NOT&#039;&#039;&#039; compatible with Windows Server 2012 (or 64 bit version of any Windows operating system).&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1341</id>
		<title>EEE WebService</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1341"/>
		<updated>2013-04-26T00:54:26Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 05 July 2012.  Last Reviewed: 26 April 2013&lt;br /&gt;
&lt;br /&gt;
===EEE WebService===&lt;br /&gt;
&lt;br /&gt;
EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.&lt;br /&gt;
&lt;br /&gt;
Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au&lt;br /&gt;
&lt;br /&gt;
Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities-&amp;gt;Configuration-&amp;gt;Configuration Settings-&amp;gt;Licensed Plugins tab.&lt;br /&gt;
&lt;br /&gt;
Magenta Retail provide EEE Web Service documentation which can be viewed from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.htm EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
or downloaded as a PDF from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.PDF EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
Recommendations / Processes&lt;br /&gt;
&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegrationRecommendationDiagram.pdf Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegratingGiftCards.pdf EEE Gift Card Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/8/85/EEE_Customer_Communications_-_Email_Click_and_Open_link_tracking.pdf EEE Email Click and Open link tracking Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/c/cf/EEE_Customer_Communications_-_Email_Verification_Process.pdf EEE Email Verification Process]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/b/b5/EEE_Customer_Communications.pdf EEE Customer Communications]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example XML and XSD files can be downloaded using the links below&lt;br /&gt;
&lt;br /&gt;
* Sample XML files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/XmlSample.zip Please click here]&lt;br /&gt;
* Sample Xsd files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/Xsd.zip Please click here]&lt;br /&gt;
&lt;br /&gt;
== See Also: ==&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1340</id>
		<title>EEE WebService</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1340"/>
		<updated>2013-04-26T00:54:13Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 05 July 2012.  Last Reviewed: 26 April 2013&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===EEE WebService===&lt;br /&gt;
&lt;br /&gt;
EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.&lt;br /&gt;
&lt;br /&gt;
Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au&lt;br /&gt;
&lt;br /&gt;
Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities-&amp;gt;Configuration-&amp;gt;Configuration Settings-&amp;gt;Licensed Plugins tab.&lt;br /&gt;
&lt;br /&gt;
Magenta Retail provide EEE Web Service documentation which can be viewed from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.htm EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
or downloaded as a PDF from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.PDF EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
Recommendations / Processes&lt;br /&gt;
&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegrationRecommendationDiagram.pdf Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegratingGiftCards.pdf EEE Gift Card Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/8/85/EEE_Customer_Communications_-_Email_Click_and_Open_link_tracking.pdf EEE Email Click and Open link tracking Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/c/cf/EEE_Customer_Communications_-_Email_Verification_Process.pdf EEE Email Verification Process]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/b/b5/EEE_Customer_Communications.pdf EEE Customer Communications]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example XML and XSD files can be downloaded using the links below&lt;br /&gt;
&lt;br /&gt;
* Sample XML files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/XmlSample.zip Please click here]&lt;br /&gt;
* Sample Xsd files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/Xsd.zip Please click here]&lt;br /&gt;
&lt;br /&gt;
== See Also: ==&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=File:EEE_Customer_Communications.pdf&amp;diff=1339</id>
		<title>File:EEE Customer Communications.pdf</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=File:EEE_Customer_Communications.pdf&amp;diff=1339"/>
		<updated>2013-04-26T00:49:02Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1337</id>
		<title>EEE WebService</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1337"/>
		<updated>2013-04-26T00:36:39Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 05 July 2012.  Last Reviewed: 26 April 2013&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;EEE WebService&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.&lt;br /&gt;
&lt;br /&gt;
Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au&lt;br /&gt;
&lt;br /&gt;
Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities-&amp;gt;Configuration-&amp;gt;Configuration Settings-&amp;gt;Licensed Plugins tab.&lt;br /&gt;
&lt;br /&gt;
Magenta Retail provide EEE Web Service documentation which can be viewed from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.htm EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
or downloaded as a PDF from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.PDF EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
Recommendations / Processes&lt;br /&gt;
&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegrationRecommendationDiagram.pdf Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegratingGiftCards.pdf EEE Gift Card Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/8/85/EEE_Customer_Communications_-_Email_Click_and_Open_link_tracking.pdf EEE Email Click and Open link tracking Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/c/cf/EEE_Customer_Communications_-_Email_Verification_Process.pdf EEE Email Verification Process]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/b/b5/EEE_Customer_Communications.pdf EEE Customer Communications]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example XML and XSD files can be downloaded using the links below&lt;br /&gt;
&lt;br /&gt;
* Sample XML files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/XmlSample.zip Please click here]&lt;br /&gt;
* Sample Xsd files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/Xsd.zip Please click here]&lt;br /&gt;
&lt;br /&gt;
== See Also: ==&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1336</id>
		<title>EEE WebService</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1336"/>
		<updated>2013-04-26T00:34:27Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 05 July 2012.  Last Reviewed: 26 April 2013&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;EEE WebService&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.&lt;br /&gt;
&lt;br /&gt;
Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au&lt;br /&gt;
&lt;br /&gt;
Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities-&amp;gt;Configuration-&amp;gt;Configuration Settings-&amp;gt;Licensed Plugins tab.&lt;br /&gt;
&lt;br /&gt;
Magenta Retail provide EEE Web Service documentation which can be viewed from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.htm EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
or downloaded as a PDF from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.PDF EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
Recommendations&lt;br /&gt;
&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegrationRecommendationDiagram.pdf Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegratingGiftCards.pdf EEE Gift Card Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/8/85/EEE_Customer_Communications_-_Email_Click_and_Open_link_tracking.pdf EEE Email Click and Open link tracking Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/c/cf/EEE_Customer_Communications_-_Email_Verification_Process.pdf EEE Email Verification Process]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example XML and XSD files can be downloaded using the links below&lt;br /&gt;
&lt;br /&gt;
* Sample XML files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/XmlSample.zip Please click here]&lt;br /&gt;
* Sample Xsd files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/Xsd.zip Please click here]&lt;br /&gt;
&lt;br /&gt;
== See Also: ==&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1335</id>
		<title>EEE WebService</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1335"/>
		<updated>2013-04-26T00:33:06Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 05 July 2012.  Last Reviewed: 26 April 2013&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;EEE WebService&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.&lt;br /&gt;
&lt;br /&gt;
Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au&lt;br /&gt;
&lt;br /&gt;
Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities-&amp;gt;Configuration-&amp;gt;Configuration Settings-&amp;gt;Licensed Plugins tab.&lt;br /&gt;
&lt;br /&gt;
Magenta Retail provide EEE Web Service documentation which can be viewed from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.htm EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
or downloaded as a PDF from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.PDF EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
Recommendations&lt;br /&gt;
&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegrationRecommendationDiagram.pdf Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegratingGiftCards.pdf EEE Gift Card Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/8/85/EEE_Customer_Communications_-_Email_Click_and_Open_link_tracking.pdf EEE Email Click and Open link tracking Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/8/85/EEE_Customer_Communications_-_Email_Verification_Process.pdf EEE Email Verification Process]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example XML and XSD files can be downloaded using the links below&lt;br /&gt;
&lt;br /&gt;
* Sample XML files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/XmlSample.zip Please click here]&lt;br /&gt;
* Sample Xsd files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/Xsd.zip Please click here]&lt;br /&gt;
&lt;br /&gt;
== See Also: ==&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1334</id>
		<title>EEE WebService</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1334"/>
		<updated>2013-04-26T00:31:40Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 05 July 2012.  Last Reviewed: 26 April 2013&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;EEE WebService&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.&lt;br /&gt;
&lt;br /&gt;
Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au&lt;br /&gt;
&lt;br /&gt;
Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities-&amp;gt;Configuration-&amp;gt;Configuration Settings-&amp;gt;Licensed Plugins tab.&lt;br /&gt;
&lt;br /&gt;
Magenta Retail provide EEE Web Service documentation which can be viewed from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.htm EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
or downloaded as a PDF from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.PDF EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
Recommendations&lt;br /&gt;
&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegrationRecommendationDiagram.pdf Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegratingGiftCards.pdf EEE Gift Card Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/8/85/EEE_Customer_Communications_-_Email_Click_and_Open_link_tracking.pdf EEE Email Click and Open link tracking Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/8/85/EEE_Customer_Communications_-_Email_Verification_Process.pdf EEE Email Verification Process]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Example XML and XSD files can be downloaded using the links below&lt;br /&gt;
&lt;br /&gt;
* Sample XML files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/XmlSample.zip Please click here]&lt;br /&gt;
* Sample Xsd files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/Xsd.zip Please click here]&lt;br /&gt;
&lt;br /&gt;
== See Also: ==&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=File:EEE_Customer_Communications_-_Email_Click_and_Open_link_tracking.pdf&amp;diff=1333</id>
		<title>File:EEE Customer Communications - Email Click and Open link tracking.pdf</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=File:EEE_Customer_Communications_-_Email_Click_and_Open_link_tracking.pdf&amp;diff=1333"/>
		<updated>2013-04-26T00:29:21Z</updated>

		<summary type="html">&lt;p&gt;Trevor: uploaded a new version of &amp;amp;quot;File:EEE Customer Communications - Email Click and Open link tracking.pdf&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=File:EEE_Customer_Communications_-_Email_Verification_Process.pdf&amp;diff=1331</id>
		<title>File:EEE Customer Communications - Email Verification Process.pdf</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=File:EEE_Customer_Communications_-_Email_Verification_Process.pdf&amp;diff=1331"/>
		<updated>2013-04-26T00:29:14Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1330</id>
		<title>EEE WebService</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1330"/>
		<updated>2013-04-26T00:05:53Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 05 July 2012.  Last Reviewed: 26 April 2013&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;EEE WebService&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.&lt;br /&gt;
&lt;br /&gt;
Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au&lt;br /&gt;
&lt;br /&gt;
Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities-&amp;gt;Configuration-&amp;gt;Configuration Settings-&amp;gt;Licensed Plugins tab.&lt;br /&gt;
&lt;br /&gt;
Magenta Retail provide EEE Web Service documentation which can be viewed from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.htm EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
or downloaded as a PDF from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.PDF EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
Recommendations&lt;br /&gt;
&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegrationRecommendationDiagram.pdf Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegratingGiftCards.pdf EEE Gift Card Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/8/85/EEE_Customer_Communications_-_Email_Click_and_Open_link_tracking.pdf EEE Email Click and Open link tracking Recommendations]&lt;br /&gt;
&lt;br /&gt;
Example XML and XSD files can be downloaded using the links below&lt;br /&gt;
&lt;br /&gt;
* Sample XML files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/XmlSample.zip Please click here]&lt;br /&gt;
* Sample Xsd files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/Xsd.zip Please click here]&lt;br /&gt;
&lt;br /&gt;
== See Also: ==&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1329</id>
		<title>EEE WebService</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1329"/>
		<updated>2013-04-25T23:59:12Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 05 July 2012.  Last Reviewed: 06 August 2012&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;EEE WebService&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.&lt;br /&gt;
&lt;br /&gt;
Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au&lt;br /&gt;
&lt;br /&gt;
Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities-&amp;gt;Configuration-&amp;gt;Configuration Settings-&amp;gt;Licensed Plugins tab.&lt;br /&gt;
&lt;br /&gt;
Magenta Retail provide EEE Web Service documentation which can be viewed from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.htm EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
or downloaded as a PDF from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.PDF EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
Recommendations&lt;br /&gt;
&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegrationRecommendationDiagram.pdf Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegratingGiftCards.pdf EEE Gift Card Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/8/85/EEE_Customer_Communications_-_Email_Click_and_Open_link_tracking.pdf EEE Email Click and Open link tracking Recommendations]&lt;br /&gt;
&lt;br /&gt;
Example XML and XSD files can be downloaded using the links below&lt;br /&gt;
&lt;br /&gt;
* Sample XML files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/XmlSample.zip Please click here]&lt;br /&gt;
* Sample Xsd files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/Xsd.zip Please click here]&lt;br /&gt;
&lt;br /&gt;
== See Also: ==&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1328</id>
		<title>EEE WebService</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1328"/>
		<updated>2013-04-25T23:58:42Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 05 July 2012.  Last Reviewed: 06 August 2012&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;EEE WebService&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.&lt;br /&gt;
&lt;br /&gt;
Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au&lt;br /&gt;
&lt;br /&gt;
Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities-&amp;gt;Configuration-&amp;gt;Configuration Settings-&amp;gt;Licensed Plugins tab.&lt;br /&gt;
&lt;br /&gt;
Magenta Retail provide EEE Web Service documentation which can be viewed from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.htm EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
or downloaded as a PDF from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.PDF EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
Recommendations&lt;br /&gt;
&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegrationRecommendationDiagram.pdf Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegratingGiftCards.pdf EEE Gift Card Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EmailClickandOpenlinktracking.pdf EEE Email Click and Open link tracking Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/8/85/EEE_Customer_Communications_-_Email_Click_and_Open_link_tracking.pdf EEE Email Click and Open link tracking Recommendations]&lt;br /&gt;
&lt;br /&gt;
Example XML and XSD files can be downloaded using the links below&lt;br /&gt;
&lt;br /&gt;
* Sample XML files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/XmlSample.zip Please click here]&lt;br /&gt;
* Sample Xsd files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/Xsd.zip Please click here]&lt;br /&gt;
&lt;br /&gt;
== See Also: ==&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=File:EEE_Customer_Communications_-_Email_Click_and_Open_link_tracking.pdf&amp;diff=1327</id>
		<title>File:EEE Customer Communications - Email Click and Open link tracking.pdf</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=File:EEE_Customer_Communications_-_Email_Click_and_Open_link_tracking.pdf&amp;diff=1327"/>
		<updated>2013-04-25T23:57:23Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1323</id>
		<title>EEE WebService</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1323"/>
		<updated>2013-04-24T06:37:51Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 05 July 2012.  Last Reviewed: 06 August 2012&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;EEE WebService&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.&lt;br /&gt;
&lt;br /&gt;
Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au&lt;br /&gt;
&lt;br /&gt;
Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities-&amp;gt;Configuration-&amp;gt;Configuration Settings-&amp;gt;Licensed Plugins tab.&lt;br /&gt;
&lt;br /&gt;
Magenta Retail provide EEE Web Service documentation which can be viewed from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.htm EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
or downloaded as a PDF from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.PDF EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
Recommendations&lt;br /&gt;
&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegrationRecommendationDiagram.pdf Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegratingGiftCards.pdf EEE Gift Card Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EmailClickandOpenlinktracking.pdf EEE Email Click and Open link tracking Recommendations]&lt;br /&gt;
&lt;br /&gt;
Example XML and XSD files can be downloaded using the links below&lt;br /&gt;
&lt;br /&gt;
* Sample XML files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/XmlSample.zip Please click here]&lt;br /&gt;
* Sample Xsd files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/Xsd.zip Please click here]&lt;br /&gt;
&lt;br /&gt;
== See Also: ==&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1321</id>
		<title>EEE WebService</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1321"/>
		<updated>2013-04-24T06:29:35Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 05 July 2012.  Last Reviewed: 06 August 2012&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;EEE WebService&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.&lt;br /&gt;
&lt;br /&gt;
Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au&lt;br /&gt;
&lt;br /&gt;
Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities-&amp;gt;Configuration-&amp;gt;Configuration Settings-&amp;gt;Licensed Plugins tab.&lt;br /&gt;
&lt;br /&gt;
Magenta Retail provide EEE Web Service documentation which can be viewed from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.htm EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
or downloaded as a PDF from here:-&lt;br /&gt;
&lt;br /&gt;
[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.PDF EEE Web Service Documentation]&lt;br /&gt;
&lt;br /&gt;
Recommendations&lt;br /&gt;
&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegrationRecommendationDiagram.pdf Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegratingGiftCards.pdf EEE Gift Card Integration Recommendations]&lt;br /&gt;
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_Customer_Communications_-_Email_Click_and_Open_link_tracking.pdf EEE Email Click and Open link tracking Recommendations]&lt;br /&gt;
&lt;br /&gt;
Example XML and XSD files can be downloaded using the links below&lt;br /&gt;
&lt;br /&gt;
* Sample XML files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/XmlSample.zip Please click here]&lt;br /&gt;
* Sample Xsd files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/Xsd.zip Please click here]&lt;br /&gt;
&lt;br /&gt;
== See Also: ==&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=Embedded_Barcodes&amp;diff=1317</id>
		<title>Embedded Barcodes</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=Embedded_Barcodes&amp;diff=1317"/>
		<updated>2013-02-05T04:58:28Z</updated>

		<summary type="html">&lt;p&gt;Trevor: Created page with &amp;quot;=== Price /weight embedded barcodes === There were three embedded price/weight embedded barcodes supported by Enabler these have been extended to include up to eight different fo...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Price /weight embedded barcodes ===&lt;br /&gt;
There were three embedded price/weight embedded barcodes supported by Enabler these have been extended to include up to eight different formats which can be configured via the Embedded Barcode Format browse screen. The new formats will include price embedded, weight embedded and/or price/weight embedded information. &lt;br /&gt;
&lt;br /&gt;
The table below shows the new formats which are configurable via BackOffice.&lt;br /&gt;
&lt;br /&gt;
=== Embedded Formats ===&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;border-spacing:0;&amp;quot;&lt;br /&gt;
| style=&amp;quot;border:0.035cm solid #00000a;padding:0cm;&amp;quot;| FORMAT&lt;br /&gt;
| style=&amp;quot;border-top:0.035cm solid #00000a;border-bottom:0.035cm solid #00000a;border-left:none;border-right:0.035cm solid #00000a;padding:0cm;&amp;quot;| Description&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;border-top:none;border-bottom:0.035cm solid #00000a;border-left:0.035cm solid #00000a;border-right:0.035cm solid #00000a;padding:0cm;&amp;quot;| FFPPPPXCCCCCY&lt;br /&gt;
| style=&amp;quot;border-top:none;border-bottom:0.035cm solid #00000a;border-left:none;border-right:0.035cm solid #00000a;padding:0cm;&amp;quot;| 2 digit prefix, 4 digit plu, 1 digit check for plu, 5 digit price, 1 digit check&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;border-top:none;border-bottom:0.035cm solid #00000a;border-left:0.035cm solid #00000a;border-right:0.035cm solid #00000a;padding:0cm;&amp;quot;| FFPPPPPXCCCCY&lt;br /&gt;
| style=&amp;quot;border-top:none;border-bottom:0.035cm solid #00000a;border-left:none;border-right:0.035cm solid #00000a;padding:0cm;&amp;quot;| 2 digit prefix, 5 digit plu, 1 digit check for plu, 4 digit price, 1 digit check&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;border-top:none;border-bottom:0.035cm solid #00000a;border-left:0.035cm solid #00000a;border-right:0.035cm solid #00000a;padding:0cm;&amp;quot;| FFPPPPPPCCCCY&lt;br /&gt;
| style=&amp;quot;border-top:none;border-bottom:0.035cm solid #00000a;border-left:none;border-right:0.035cm solid #00000a;padding:0cm;&amp;quot;| 2 digit prefix, 6 digit plu, 4 digit price, 1 digit check&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;border-top:none;border-bottom:0.035cm solid #00000a;border-left:0.035cm solid #00000a;border-right:0.035cm solid #00000a;padding:0cm;&amp;quot;| FFPPPPXWWWWWY&lt;br /&gt;
| style=&amp;quot;border-top:none;border-bottom:0.035cm solid #00000a;border-left:none;border-right:0.035cm solid #00000a;padding:0cm;&amp;quot;| 2 digit prefix, 4 digit plu, 5 digit weight (use price from product table, prompt for price if price is 0$), 1 digit check&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;border-top:none;border-bottom:0.035cm solid #00000a;border-left:0.035cm solid #00000a;border-right:0.035cm solid #00000a;padding:0cm;&amp;quot;| FFPPPPPXWWWWY&lt;br /&gt;
| style=&amp;quot;border-top:none;border-bottom:0.035cm solid #00000a;border-left:none;border-right:0.035cm solid #00000a;padding:0cm;&amp;quot;| 2 digit prefix, 5 digit plu, 4 digit weight (use price from product table, prompt for price if price is 0$), 1 digit check&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;border-top:none;border-bottom:0.035cm solid #00000a;border-left:0.035cm solid #00000a;border-right:0.035cm solid #00000a;padding:0cm;&amp;quot;| FFPPPPPWWWWWY&lt;br /&gt;
| style=&amp;quot;border-top:none;border-bottom:0.035cm solid #00000a;border-left:none;border-right:0.035cm solid #00000a;padding:0cm;&amp;quot;| 2 digit prefix, 5 digit plu, 5 digit weight (use price from product table, prompt for price if price is 0$), 1 digit check&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;border-top:none;border-bottom:0.035cm solid #00000a;border-left:0.035cm solid #00000a;border-right:0.035cm solid #00000a;padding:0cm;&amp;quot;| FFPPPPPPWWWWY&lt;br /&gt;
| style=&amp;quot;border-top:none;border-bottom:0.035cm solid #00000a;border-left:none;border-right:0.035cm solid #00000a;padding:0cm;&amp;quot;| 2 digit prefix, 6 digit plu, 4 digit weight (might not be too useful), (use price from Product table, prompt for price if price is 0$), 1 digit check&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;border-top:none;border-bottom:0.035cm solid #00000a;border-left:0.035cm solid #00000a;border-right:0.035cm solid #00000a;padding:0cm;&amp;quot;| FPPPPPPCCCCCWWWWWY&lt;br /&gt;
| style=&amp;quot;border-top:none;border-bottom:0.035cm solid #00000a;border-left:none;border-right:0.035cm solid #00000a;padding:0cm;&amp;quot;| 1 digit prefix, 6 digit plu, 5 digit price, 5 digit weight, 1 digit check&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
Formats 1-3 have price embedded in the barcode, formats 4-7 have weight embedded in the barcodes. For weight embedded barcodes the price information is obtained from file. If the item price is $0.00, the user will be prompted to enter the price in the selling screen. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
An Enabler option allows Enabler to support the new user configured barcodes.&lt;br /&gt;
&lt;br /&gt;
ProductsProduct OptionsBarcode printing/Scanning&lt;br /&gt;
&lt;br /&gt;
* Use configured embedded barcode formats (ignore internal embedded formats) &lt;br /&gt;
&lt;br /&gt;
With the option flagged ON the internal embedded formats cannot be used.&lt;br /&gt;
&lt;br /&gt;
[[Image:Embedded_Barcode_image001.png]]&lt;br /&gt;
&lt;br /&gt;
=== Setup Embedded formats ===&lt;br /&gt;
To setup the new barcode formats, a global configuration option is available.&lt;br /&gt;
&lt;br /&gt;
Products Embedded Barcode Formats (Global)&lt;br /&gt;
&lt;br /&gt;
This can be accessed via Global configuration or Local Store configuration menu option.&lt;br /&gt;
&lt;br /&gt;
[[Image:Embedded_Barcode_image002.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Embedded Barcode Format browse screen allows the user to add/configure new embedded barcode formats which can be interpreted by Enabler.&lt;br /&gt;
&lt;br /&gt;
[[Image:Embedded_Barcode_image003.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Embedded_Barcode_image004.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A barcode format is to be identified by its prefix. The first seven barcode formats require a two digit prefix. The price/weight embedded barcode (Barcode 8) has a prefix of 2. This prefix must be used for this barcode. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Include prefix as part of PLU &#039;&#039;&#039;- This option extends the PLU range by up to 2 digits. For example a barcode &lt;br /&gt;
&lt;br /&gt;
2565311004522 with the format FFPPPPPWWWWWY has a 5 digit PLU (65311). With the above option enabled the PLU becomes 2565311 or 7 digits long. &lt;br /&gt;
&lt;br /&gt;
Configured barcodes are stored locally in the BCODEFMT table.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Importing of barcode format files ===&lt;br /&gt;
The barcode format may be imported into Enabler using the normal import mechanism. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Embedded Barcode Format Maintenance&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
FieldDescriptionData TypeExample&lt;br /&gt;
&lt;br /&gt;
01Record IdentifierC-22A, 2C, 2D&lt;br /&gt;
&lt;br /&gt;
02Embedded Barcode PrefixC-2&lt;br /&gt;
&lt;br /&gt;
03Embedded Barcode DescriptionC-60&lt;br /&gt;
&lt;br /&gt;
04 Embedded Barcode FormatC-20&lt;br /&gt;
&lt;br /&gt;
05 Include prefix as part of PLULY/N&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Exporting Embedded Barcode formats  ===&lt;br /&gt;
The barcode format table (BCODEFMT) will be exported when a branch\tills configuration is exported. Also the barcode format table can be exported by doing a master file load or a branch load from enabler. A category “Barcode Formats File” has been added to the Full Till Load screen which exports the barcode formats table.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Embedded_Barcode_image005.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once configured the barcodes can be used identify products in the selling screen as per current practice.&lt;br /&gt;
&lt;br /&gt;
=== Printing and decoding “alias codes” from Weight &amp;amp; Price embedded barcodes  ===&lt;br /&gt;
This option enables client to generate price and weight embedded barcodes for packaged items such as meat. Enabler already supports scanning ITF barcodes with weight and price data embedded and can easily be further developed to allow printing of such labels. However, these barcodes support numeric-only characters and only 6 characters are allocated for the SKU. The full data format for these labels is:&lt;br /&gt;
&lt;br /&gt;
2sssssspppppwwwwwd where:&lt;br /&gt;
&lt;br /&gt;
2 is a fixed prefix1 characters&lt;br /&gt;
&lt;br /&gt;
ssssss = SKU code 6 characters&lt;br /&gt;
&lt;br /&gt;
ppppp = Price5 characters&lt;br /&gt;
&lt;br /&gt;
wwwww = weight5 characters&lt;br /&gt;
&lt;br /&gt;
d = check digit1 character&lt;br /&gt;
&lt;br /&gt;
18 characters total&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For example, product 128212 which is $13.29 per kilo is packaged in a 0.541 kilo pack, the barcode would be: 212821200719005415 Note the maximum weight supported by this format is 99.999kg and the maximum price $999.99. Note that the system would compute the extended price based on the standard file price for this SKU when the label is generated ($13.29 x 0.541 = $7.19). Should the system file price for this SKU change between printing of the label and selling the item, the price embedded in the barcode (and printed on the label) would still apply – as it must!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note that items for which price and weight embedded barcodes are required must have a numeric-only SKU of no more than 6 digits. If this cannot be achieved then a separate 6 digit barcode (or “alias”) would have to be associated with that subset of products for which price/weight embedded barcode support is required. Enabler can optionally resolve the “alias” barcode to the true, underlying 12 character SKU upon scanning these barcodes.&lt;br /&gt;
&lt;br /&gt;
The process to produce a label would be:&lt;br /&gt;
&lt;br /&gt;
1. Place the item on the attached scale&lt;br /&gt;
&lt;br /&gt;
2.Specify (key or search) the SKU in Enabler&lt;br /&gt;
&lt;br /&gt;
3.Label in user-customisable format would be produced showing the product details (code and description), weight, unit price and total price in text (i.e. human-readable) and with the price and weight embedded barcode.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In order for Enabler to decode the price and weight embedded I2of5 barcodes, the following option must be enabled.&lt;br /&gt;
&lt;br /&gt;
Product Product Option Barcode printing /Scanning&lt;br /&gt;
&lt;br /&gt;
* Use configured embedded barcode formats (ignore internal embedded format)&lt;br /&gt;
&lt;br /&gt;
[[Image:Embedded_Barcode_image006.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In addition, the following format must be enabled in your global settings for “Embedded barcode formats”. If decoding alias codes is required, then also check the resolve option. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Products Embedded Barcode Format (Local)&lt;br /&gt;
&lt;br /&gt;
* Resolve PLU prtion against product/barcode database&lt;br /&gt;
&lt;br /&gt;
[[Image:Embedded_Barcode_image007.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Printing embedded barcode label ===&lt;br /&gt;
A price &amp;amp; weight embedded barcode can be added to a Barcode label format by adding a “Price &amp;amp; Weight Embedded Barcode” field to label format.&lt;br /&gt;
&lt;br /&gt;
Product Barcode Label formatting&lt;br /&gt;
&lt;br /&gt;
[[Image:Embedded_Barcode_image008.png]]&lt;br /&gt;
&lt;br /&gt;
[[Image:Embedded_Barcode_image009.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Example embedded barcodes: ===&lt;br /&gt;
&#039;&#039;&#039;Price Embedded&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
0255010112995 – Product Code – 550101. Price - $12.99&lt;br /&gt;
&lt;br /&gt;
0255010108998 – Product Code – 550101. Price - $8.99&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Price/Weight Embedded&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
200820000684004561 – Product Code – 8200. Price - $6.84. Weight - 0.456 Kg&lt;br /&gt;
&lt;br /&gt;
200820001884012561 – Product Code – 8200. Price - $18.84. Weight – 1.256 Kg&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Using these sample barcodes in the format: FF-CCCCC-PPPPP-WWWWW-CD&lt;br /&gt;
&lt;br /&gt;
200000109995000010 Prod 1 (non-weighed), $99.95, 1 unit&lt;br /&gt;
&lt;br /&gt;
200000109995008955 Prod 1 (non-weighed), $99.95, qty = 0.895&lt;br /&gt;
&lt;br /&gt;
200820009995008954 Prod 8200 (weighed), $99.95, 895g&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1)2236121012990. PLU – 361210. Barcode – 22361210. Include Prefix option should be enabled. Resolve PLU portion against product/barcode option should be enabled. This user configured barcode is of format type FFPPPPPPCCCY&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
2)212821200719005415. PLU – 8212. Barcode – 128212. Include Prefix option should be disabled. Resolve PLU portion against product/barcode option should be enabled. This user configured barcode is of format type FPPPPPPCCCCCWWWWWY&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
3)200821200719005412. Same as above but should resolve the PLU directly.&lt;br /&gt;
&lt;br /&gt;
4)2112644012368. PLU – 264. Barcode – 1264. Include Prefix option should be disabled. Resolve PLU portion against product/barcode option should be enabled. This user configured barcode is of format type FFPPPPXWWWWWY&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You can use the following barcodes for testing&lt;br /&gt;
&lt;br /&gt;
Price embedded barcodes&lt;br /&gt;
&lt;br /&gt;
Barcode 1 – 0255010112995 – Product Code – 550101 Price - $12.99&lt;br /&gt;
&lt;br /&gt;
Barcode 2 – 0255010108998 – Product Code – 550101 Price - $8.99&lt;br /&gt;
&lt;br /&gt;
These barcodes contain a 6 digit PLU, so the option in the configuration to include prefix in screenshot above must be off. If you want to test with 5 digit PLU in the barcode, turn that option on: e.g. 0200850702172 which has a Product Code of 00850 which becomes 850 when leading zeroes are stripped and has a price of $2.17&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Weight embedded barcodes - For a refresher on weight embedded barcodes refer to version notes section 4-33-01&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Barcode 1 – 2 008200 00684 00456 1 – Product Code – 8200. Price - $6.84. Weight - 0.456 Kg&lt;br /&gt;
&lt;br /&gt;
SKU: 008200&lt;br /&gt;
&lt;br /&gt;
Price: $6.84&lt;br /&gt;
&lt;br /&gt;
Weight: 0.456 kg&lt;br /&gt;
&lt;br /&gt;
File Price: $15.00 (per kg)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Barcode: &lt;br /&gt;
&lt;br /&gt;
200820000684004561&lt;br /&gt;
&lt;br /&gt;
200820000748004995&lt;br /&gt;
&lt;br /&gt;
200820003121044656&lt;br /&gt;
&lt;br /&gt;
2 008200 03121 04465 6&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Barcode 2 – 2 128212 00719 00541 5 – Product Code – 128212. Price - $7.19. Weight – 0.541 Kg&lt;br /&gt;
&lt;br /&gt;
SKU: 128212&lt;br /&gt;
&lt;br /&gt;
Price: $7.19&lt;br /&gt;
&lt;br /&gt;
Weight: 0.541 kg&lt;br /&gt;
&lt;br /&gt;
File Price: $13.29 (per kg)&lt;br /&gt;
&lt;br /&gt;
Barcode: &lt;br /&gt;
&lt;br /&gt;
212821200719005415&lt;br /&gt;
&lt;br /&gt;
212821200719005415&lt;br /&gt;
&lt;br /&gt;
212821200719005415&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{I,B,0,1,0,0,0|}&lt;br /&gt;
&lt;br /&gt;
{F,25,A,R,M,700,380,&amp;quot;PLabel1&amp;quot;|&lt;br /&gt;
&lt;br /&gt;
C,650,20,0,2,1,1,O,L,0,0,&amp;quot;HFM&amp;quot;,0 | &lt;br /&gt;
&lt;br /&gt;
C,600,150,0,2,1,1,O,L,0,3,&amp;quot;$69.95&amp;quot;,0 | &lt;br /&gt;
&lt;br /&gt;
C,600,40,0,2,2,1,O,L,0,3,&amp;quot;TWEETY TABLE LAMP&amp;quot;,0 | &lt;br /&gt;
&lt;br /&gt;
B,4,8,F,10,170,6,2,75,7,L,0 | R,61 | R,1,&amp;quot;20002008&amp;quot; | &lt;br /&gt;
&lt;br /&gt;
C,0,20,0,2,1,1,O,L,0,0,&amp;quot;000200&amp;quot;,0 | &lt;br /&gt;
&lt;br /&gt;
C,0,100,0,2,2,1,O,L,0,0,&amp;quot;1.555&amp;quot;,0 | &lt;br /&gt;
&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
{B,25,N,1 | E,0,0,1,1,2,1 |}&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=File:Embedded_Barcode_image009.png&amp;diff=1316</id>
		<title>File:Embedded Barcode image009.png</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=File:Embedded_Barcode_image009.png&amp;diff=1316"/>
		<updated>2013-02-05T04:39:48Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=File:Embedded_Barcode_image008.png&amp;diff=1315</id>
		<title>File:Embedded Barcode image008.png</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=File:Embedded_Barcode_image008.png&amp;diff=1315"/>
		<updated>2013-02-05T04:39:48Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=File:Embedded_Barcode_image007.png&amp;diff=1314</id>
		<title>File:Embedded Barcode image007.png</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=File:Embedded_Barcode_image007.png&amp;diff=1314"/>
		<updated>2013-02-05T04:39:48Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=File:Embedded_Barcode_image006.png&amp;diff=1313</id>
		<title>File:Embedded Barcode image006.png</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=File:Embedded_Barcode_image006.png&amp;diff=1313"/>
		<updated>2013-02-05T04:39:48Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=File:Embedded_Barcode_image005.png&amp;diff=1312</id>
		<title>File:Embedded Barcode image005.png</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=File:Embedded_Barcode_image005.png&amp;diff=1312"/>
		<updated>2013-02-05T04:39:48Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=File:Embedded_Barcode_image004.png&amp;diff=1311</id>
		<title>File:Embedded Barcode image004.png</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=File:Embedded_Barcode_image004.png&amp;diff=1311"/>
		<updated>2013-02-05T04:39:48Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=File:Embedded_Barcode_image003.png&amp;diff=1310</id>
		<title>File:Embedded Barcode image003.png</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=File:Embedded_Barcode_image003.png&amp;diff=1310"/>
		<updated>2013-02-05T04:39:48Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=File:Embedded_Barcode_image002.png&amp;diff=1309</id>
		<title>File:Embedded Barcode image002.png</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=File:Embedded_Barcode_image002.png&amp;diff=1309"/>
		<updated>2013-02-05T04:39:48Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=File:Embedded_Barcode_image001.png&amp;diff=1308</id>
		<title>File:Embedded Barcode image001.png</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=File:Embedded_Barcode_image001.png&amp;diff=1308"/>
		<updated>2013-02-05T04:39:47Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=Database_errors&amp;diff=1306</id>
		<title>Database errors</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=Database_errors&amp;diff=1306"/>
		<updated>2013-01-14T03:36:43Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 24 November 2008. Last Reviewed: 24 April 2009 &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Database errors in Enabler, although not common, can occur for a variety of reasons. Below are some sample errors with suggested resolutions. With all database errors, unless you are 100% sure of the method for fixing the problem, it is strongly recommended that you contact Magenta Retail for assistance before proceeding.&lt;br /&gt;
&lt;br /&gt;
= Database Error – Read Failure =&lt;br /&gt;
[[Image:Database_errors_Figure_1.jpg]]&lt;br /&gt;
&lt;br /&gt;
Need to determine whether the database (.dbf) or the index (.mdx) is corrupt: &lt;br /&gt;
&lt;br /&gt;
# Close all Enabler applications including Nibbler &lt;br /&gt;
# Delete the index relating to the error. In the above sample this is c:\enabler\local\posdiv.mdx. &lt;br /&gt;
# Re-index the database that experienced the error. In the above sample this is c:\enabler\local\posdiv.dbf so the reindex command would be c:\enabler&amp;gt;&#039;&#039;&#039;infoctrl indexlocal posdiv&#039;&#039;&#039;) &lt;br /&gt;
# Start POS again.&lt;br /&gt;
# If Database error re-occurs then most likely the .dbf is corrupt.&lt;br /&gt;
# If the database is in the LOCAL folder, refer to “Enabler Database Files – LOCAL” for information about replacing or recovering the file.If the database is in the LANTRAN folder, refer to “Enabler Database Files – LANTRAN” for information about replacing or recovering the file. If the database is in the LANMNT folder, refer to “Enabler Database Files – LANMNT” for information about replacing or recovering the file. If unsure, please contact Magenta Retail for further advice. &lt;br /&gt;
&lt;br /&gt;
= Required Database Missing =&lt;br /&gt;
While a missing index can often be corrected by Enabler automatically reindexing the database for the missing index, which re-creates the index, a missing database file cannot be repaired automatically in most cases.&lt;br /&gt;
&lt;br /&gt;
[[Image:Database_errors_Figure_2.jpg]]&lt;br /&gt;
&lt;br /&gt;
To determine the best course of action, refer to the suggestions below.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* If the database is in the LOCAL folder, refer to “Enabler Database Files – LOCAL” for information about replacing or recovering the file.&lt;br /&gt;
* If the database is in the LANTRAN folder, refer to “Enabler Database Files – LANTRAN” for information about replacing or recovering the file. &lt;br /&gt;
* If the database is in the LANMNT folder, refer to “Enabler Database Files – LANMNT” for information about replacing or recovering the file. If unsure, please contact Magenta Retail for further advice. &lt;br /&gt;
&lt;br /&gt;
= Unknown fieldname =&lt;br /&gt;
An unknown fieldname error message indicates an incompatibility between the database structures and the fields that Enabler is expecting to see in the database. This could occur if problems happened with an Enabler upgrade, or if a file was replaced from a different version of Enabler.&lt;br /&gt;
&lt;br /&gt;
[[Image:Database_errors_Figure_3.jpg]]&lt;br /&gt;
&lt;br /&gt;
The first check to be done is to ensure every till in the store is on the same version of Enabler. They aren’t then all tills should be upgraded to the same version. The store server must ALWAYS be on the same or a higher version of Enabler as the tills.&lt;br /&gt;
&lt;br /&gt;
If all tills are on the same version, in most cases the error can be fixed by performing a migrate. The command for this would be:-&lt;br /&gt;
&lt;br /&gt;
Infoctrl migrate&lt;br /&gt;
&lt;br /&gt;
which needs to be run from a command prompt in the folder where Enabler is installed, which in the above example would be c:\enabler. Ensure that all Enabler applications are closed before running this command.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Number is out of range =&lt;br /&gt;
A “Number is out of range” message will likely have a similar cause to the “Unknown Fieldname” message, and can often occur immediately after the “Unknown Fieldname” error.&lt;br /&gt;
&lt;br /&gt;
[[Image:Database_errors_Figure_4.jpg]]&lt;br /&gt;
&lt;br /&gt;
The first check to be done is to ensure every till in the store is on the same version of Enabler. They aren’t then all tills should be upgraded to the same version. The store server must ALWAYS be on the same or a higher version of Enabler as the tills.&lt;br /&gt;
&lt;br /&gt;
If all tills are on the same version, in most cases the error can be fixed by performing a migrate. The command for this would be:-&lt;br /&gt;
&lt;br /&gt;
Infoctrl migrate&lt;br /&gt;
&lt;br /&gt;
which needs to be run from a command prompt in the folder where Enabler is installed, which in the above example would be c:\enabler. Ensure that all Enabler applications are closed before running this command.&lt;br /&gt;
&lt;br /&gt;
= See Also =&lt;br /&gt;
[[Enabler_Database_Files_-_LANMNT]]&lt;br /&gt;
&lt;br /&gt;
[[Enabler_Database_Files_-_LANTRAN]]&lt;br /&gt;
&lt;br /&gt;
[[Enabler_Database_Files_-_LOCAL]]&lt;br /&gt;
&lt;br /&gt;
[[Anti-virus_software|Anti Virus Software]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Retrieved from &amp;quot;[http://192.168.2.6/wiki/index.php/Database_errors http://192.168.2.6/wiki/index.php/Database_errors]&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Views[[Image:]][[Image:]][[Image:]][[Image:]][[Image:]][[Image:]]&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=Store_Closing_Checklist&amp;diff=1305</id>
		<title>Store Closing Checklist</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=Store_Closing_Checklist&amp;diff=1305"/>
		<updated>2013-01-14T03:33:11Z</updated>

		<summary type="html">&lt;p&gt;Trevor: Created page with &amp;quot;Created: 14 January 2013. Last Reviewed: 14 January 2013  == Store Closing Checklist ==   === Overview ===  When closing a store using enabler integrated with EEE, there are a nu...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 14 January 2013. Last Reviewed: 14 January 2013&lt;br /&gt;
&lt;br /&gt;
== Store Closing Checklist == &lt;br /&gt;
&lt;br /&gt;
=== Overview ===&lt;br /&gt;
&lt;br /&gt;
When closing a store using enabler integrated with EEE, there are a number of steps that should be performed to ensure that all sales from the store have updated in EEE, and that no further maintenance records are created for the closed store in EEE.&lt;br /&gt;
The steps below should be following when closing a store.&lt;br /&gt;
&lt;br /&gt;
=== Enabler Store Server ===&lt;br /&gt;
The following steps need to be performed on the store server before closure. &lt;br /&gt;
&lt;br /&gt;
•	If layby and /or customer orders modules are in use ensure all layby/orders have been flagged as Taken or Cancelled&lt;br /&gt;
&lt;br /&gt;
•	If Inter Branch Transfers are used, ensure all transfers have been completed.&lt;br /&gt;
&lt;br /&gt;
•	If Good Receipting is used, ensure all items on pending purchase orders have been flagged as received or cancelled.&lt;br /&gt;
&lt;br /&gt;
•	Transfer out any remaining stock to another branch if required.&lt;br /&gt;
&lt;br /&gt;
•	To clear any remaining inventory, perform a stocktake and post with no counts. (Inventory Menu Stocktake)&lt;br /&gt;
&lt;br /&gt;
•	Manually export the host log from the store server to ensure all transactions have been sent to EEE, (File Menu-  Export Host Log).&lt;br /&gt;
&lt;br /&gt;
•	Manually export the nibble file from Store Server in Back Office (File Menu  Export Nibble messages now)&lt;br /&gt;
&lt;br /&gt;
•	If not configured for Enabler Internal communications, then the normal process in use for transferring files from stores to HO should then be run to transfer all data from the store back to HO.&lt;br /&gt;
&lt;br /&gt;
•	Confirm all files exported from store server have been received at H/O Enabler and EEE (Enabler Event log and EEE Dataloader Activity Log)&lt;br /&gt;
&lt;br /&gt;
•	Once all of the above has been done, equipment can be packed up.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
=== EEE Branch Record ===&lt;br /&gt;
The following configurations are required to be set for branch record when store has ceased trading. These options can be located under EEE menu option&lt;br /&gt;
Location ManagementBranch&lt;br /&gt;
&lt;br /&gt;
•	Branch Closed Date – Enter the date branch ceased trading&lt;br /&gt;
&lt;br /&gt;
•	Branch Closed -  Flag option to indicate  Branch as closed &lt;br /&gt;
&lt;br /&gt;
•	Exclude this branch from data exports -  Enabling this option will stop EEE Data Exporter from sending new records to this store and will automatically flag the branch code as offline in the Enabler H/O Global  configuration &lt;br /&gt;
&lt;br /&gt;
•	Prevent stock transfers to this branch – Enabling this option will stop other stores transferring stock to this branch.&lt;br /&gt;
&lt;br /&gt;
•	Prevent stock transfer requests from this branch – Enabling this option will stop stores requesting stock from this branch.&lt;br /&gt;
&lt;br /&gt;
•	Consider branch when Re-ordering - This option should be turned off so re-orders are not performed for this branch.&lt;br /&gt;
&lt;br /&gt;
•	Consider branch when Re-plenishing - This option should be turned off so replenishment is not performed for this branch.&lt;br /&gt;
&lt;br /&gt;
•	Allow purchase ordering for this branch - This option should be turned off so that purchase orders cannot be created for this branch.&lt;br /&gt;
&lt;br /&gt;
•	Maintain costs - This option should be turned off so that costs are not automatically generated for this branch. Costs are created when functions such as creating styles/products are done.&lt;br /&gt;
&lt;br /&gt;
•	Maintain prices - This option should be turned off so that prices are not automatically generated for this branch. Prices are created when functions such as creating styles/products are done.&lt;br /&gt;
&lt;br /&gt;
•	Maintain Min Max - This option should be turned off so that Min Max are not updated for this branch.&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=Changing_Company_Details_on_Purchase_Orders&amp;diff=1304</id>
		<title>Changing Company Details on Purchase Orders</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=Changing_Company_Details_on_Purchase_Orders&amp;diff=1304"/>
		<updated>2013-01-14T03:21:35Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 30 January 2009. Last Reviewed: 14 January 2013&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Purchase Order configuration details are now all held in the EEE database. To change the company details displayed on supplier copies of Purchase Orders, login to EEE and go to Utilities-&amp;gt;Configuration-&amp;gt;Purchasing Configuration&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=POS_Auto_Relicense&amp;diff=1303</id>
		<title>POS Auto Relicense</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=POS_Auto_Relicense&amp;diff=1303"/>
		<updated>2013-01-14T03:17:51Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 18 June 2012. Last Reviewed: 14 January 2013&lt;br /&gt;
&lt;br /&gt;
Enabler and EEPOS require a licence key to operate.  Licence keys expire from time to time, usually after 12 months.  When POS detects that it is within one month of its licence expiration date, POS can automatically relicense itself via the Magenta licensing server.  &lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
Some simple configuration is required.  You must enter:&lt;br /&gt;
# Magenta&#039;s relicensing server address:  &#039;&#039;&#039;http://licensing.magentaretail.com.au/magentawebservice/magentawebservice.asmx&#039;&#039;&#039;&lt;br /&gt;
# Your user code issued by Magenta&lt;br /&gt;
# Your licensing password issued by Magenta&lt;br /&gt;
# Text that will display to your store operators should auto-relicensing be unsuccessful&lt;br /&gt;
&lt;br /&gt;
[[Image:Auto_Relicense_Figure_1.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Network Requirements ==&lt;br /&gt;
Relicensing requires that each POS terminal has port 80 access to the Magenta licensing server.  To check if your POS machines have appropriate network access, open a browser on the POS machine and try to navigate to &#039;&#039;&#039;http://licensing.magentaretail.com.au/magentawebservice/magentawebservice.asmx&#039;&#039;&#039;.  If this succeeds then the basic network requirements are met.  If this fails the cause of the failure will need to be identified and resolved before POS will be able to automatically renew its licence.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Other Requirements ==&lt;br /&gt;
In order for Enabler to invoke the licensing web service, the POS machine must have the Microsoft .NET framework 3.5 installed.  Older versions of Enabler POS may fail silently if this requirement is not met, later versions will log this in the Enabler event log.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
If POS is failing to renew its licence and the network test above is successful, check the POS event log at the time the POS relicensing message was displayed for a record indicating the reason for the relicensing failure. From EEE version 1.66, an alert email is also generated each morning, which indicates which tills have failed auto relicensing.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Key Words: licence license relicense autolicence autorelicense unlicensed&#039;&#039;&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=Main_Page&amp;diff=1302</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=Main_Page&amp;diff=1302"/>
		<updated>2012-11-09T05:11:58Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:Magenta_Retail_Logo_White.jpg]]&lt;br /&gt;
&lt;br /&gt;
===Welcome to Magenta Retail&#039;s EEE and Enabler Wiki===&lt;br /&gt;
&lt;br /&gt;
Enter the topic you would like to search for in the seach box to the left and please enjoy our Wiki!&lt;br /&gt;
&lt;br /&gt;
* To see all articles on our WIKI [[Special:AllPages|please click here]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
EEE Manuals and Technical documentation for both Enabler and EEE are available on our website. &lt;br /&gt;
&lt;br /&gt;
As the website links to our FTP site, you must be a client of Magenta Retail with an FTP usercode and password &lt;br /&gt;
to be able to access this documentation.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Magenta Technical Documentation [http://www.magentaretail.com.au/documents.php Please click here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you would like to submit a suggestion for an article to be added to the WIKI, please use this email link [mailto:support@magentaretail.com.au?Subject=WIKI%20Suggestion Suggestion:]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Other Links ==&lt;br /&gt;
&lt;br /&gt;
* Magenta&#039;s Web site [http://www.magentaretail.com.au www.magentaretail.com.au]&lt;br /&gt;
* Magenta&#039;s FTP site [ftp://ftp.magentaretail.com.au Please click here]&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=Main_Page&amp;diff=1301</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=Main_Page&amp;diff=1301"/>
		<updated>2012-11-09T05:11:30Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:Magenta_Retail_Logo_White.jpg]]&lt;br /&gt;
&lt;br /&gt;
===Welcome to Magenta Retail&#039;s EEE and Enabler Wiki===&lt;br /&gt;
&lt;br /&gt;
Enter the topic you would like to search for in the seach box to the left and please enjoy our Wiki!&lt;br /&gt;
&lt;br /&gt;
* To see all articles on our WIKI [[Special:AllPages|please click here]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
EEE Manuals and Technical documentation for both Enabler and EEE are available on our website. &lt;br /&gt;
&lt;br /&gt;
As the website links to our FTP site, you must be a client of Magenta Retail with an FTP user and password &lt;br /&gt;
to be able to access this documentation.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Magenta Technical Documentation [http://www.magentaretail.com.au/documents.php Please click here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you would like to submit a suggestion for an article to be added to the WIKI, please use this email link [mailto:support@magentaretail.com.au?Subject=WIKI%20Suggestion Suggestion:]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Other Links ==&lt;br /&gt;
&lt;br /&gt;
* Magenta&#039;s Web site [http://www.magentaretail.com.au www.magentaretail.com.au]&lt;br /&gt;
* Magenta&#039;s FTP site [ftp://ftp.magentaretail.com.au Please click here]&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_Upgrade_Installation_Notes&amp;diff=1300</id>
		<title>EEE Upgrade Installation Notes</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_Upgrade_Installation_Notes&amp;diff=1300"/>
		<updated>2012-10-26T03:47:50Z</updated>

		<summary type="html">&lt;p&gt;Trevor: Replaced content with &amp;quot;Created: 23 January 2009. Last Reviewed: 26 October 2012

&amp;#039;&amp;#039;&amp;#039;Enabler Enterprise Edition Upgrade Installation Procedures&amp;#039;&amp;#039;&amp;#039;
= Introduction =
Magenta Retail periodically releas...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 23 January 2009. Last Reviewed: 26 October 2012&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Enabler Enterprise Edition Upgrade Installation Procedures&#039;&#039;&#039;&lt;br /&gt;
= Introduction =&lt;br /&gt;
Magenta Retail periodically release new version of EEE. These are generally released 3 to 4 times per year.&lt;br /&gt;
&lt;br /&gt;
Instructions for installing EEE Upgrades can be found at the link below:&lt;br /&gt;
&lt;br /&gt;
[ftp://ftp.magentaretail.com.au/documents/EEE_Manuals/Installation_Upgrades/EEE%20Upgrade%20Installation%20Notes.PDF Installing EEE Upgrades]&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=Installing_EEE_Service_Packs&amp;diff=1299</id>
		<title>Installing EEE Service Packs</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=Installing_EEE_Service_Packs&amp;diff=1299"/>
		<updated>2012-10-26T01:29:08Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 27 January 2009. Last Reviewed: 26 October 2012&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Installing EEE Service Packs&#039;&#039;&#039;&lt;br /&gt;
= Introduction =&lt;br /&gt;
Magenta Retail periodically releases EEE Service Packs, which are primarily used to install fixes, but can also be used to install new functionality. Each service pack contains a document listing all the changes made in this release of EEE and all service packs including the current service pack.&lt;br /&gt;
&lt;br /&gt;
All service packs are cumulative, so you only need to install the latest service release for a EEE version.&lt;br /&gt;
&lt;br /&gt;
Instructions for applying EEE Service Releases can be found at the link below:&lt;br /&gt;
&lt;br /&gt;
[ftp://ftp.magentaretail.com.au/documents/EEE_Manuals/Installation_Upgrades/Installing_EEE_Service_Packs.PDF Installing EEE Service Releases]&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_Notification_warnings&amp;diff=1291</id>
		<title>EEE Notification warnings</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_Notification_warnings&amp;diff=1291"/>
		<updated>2012-08-06T04:17:30Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 02 February 2011. Last Reviewed: 06 August 2012&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you receive an alert email titled EEE Notifications Warning, and the email is similar to below, the most likely explanation is the SQL Server has locked the file and not released the lock.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 Failed to created the notifications file        at: d:\eeedata\production\notifications\2323\232302.NOT&lt;br /&gt;
         for till: 232302&lt;br /&gt;
         with content: 0&lt;br /&gt;
         failed with error: mscorlib The process cannot access the file&lt;br /&gt;
 &#039;d:\eeedata\production\notifications\2323\232302.NOT&#039; because it is being used&lt;br /&gt;
 by another process..&lt;br /&gt;
 The till may have the notifications path configured incorrectly or the folder security is incorrect.&lt;br /&gt;
&lt;br /&gt;
This has happened a number of times at one client, so the information below relates to fixing the problem on their server.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To fix the issue, use Process Explorer on the SQL Server.&lt;br /&gt;
&lt;br /&gt;
At this client, this can be located in D:\Temp\ProcessExplorer\procexp64.exe. &lt;br /&gt;
&lt;br /&gt;
- Click the Find menu, then &#039;Find Handle or dll...&#039;&lt;br /&gt;
&lt;br /&gt;
- Search for the name of the file that is being reported as locked in the alert email.&lt;br /&gt;
&lt;br /&gt;
- Select the result and the bottom half of the screen will show the file handle. Most likely this will be locked by sqlservr.exe.&lt;br /&gt;
&lt;br /&gt;
- Right click the handle and select close handle&lt;br /&gt;
&lt;br /&gt;
- You&#039;ll be prompted to confirm, say OK, then the errors should stop and SQL should be able to update the file next time a change is detected.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Further information on using Process Explorer, plus a download link can be found here: [http://technet.microsoft.com/en-us/sysinternals/bb896653 http://technet.microsoft.com/en-us/sysinternals/bb896653]&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=Enabler_Duplicate_Server_error&amp;diff=1290</id>
		<title>Enabler Duplicate Server error</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=Enabler_Duplicate_Server_error&amp;diff=1290"/>
		<updated>2012-07-12T05:59:40Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 30 July 2009. Last Reviewed: 12 July 2012&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Duplicate Server Error&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
With the introduction of Enabler internal comms which added the ability of moving files to/from HO without the use of batch files or FTP scripts, also came the possibility of an incorrectly configured Enabler machine being added to the network and potentially picking up files destined for a different branch.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Enabler now guards against this by creating a file called workstation.dat in the stores export folder on the HO server. This is the folder where EEE Exporter creates its export files and will be something like \eeedata\production\export\RRBB where RRBB is the store’s logical address. This file contains the machine name of the store server, and is checked when Enabler starts on the store server.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If the machine name of the Enabler machine is different than the name recorded in workstation.dat, a message will be displayed on the screen:-&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Another machine has been detected on the network operating as a store server. Nibbler will not run under these conditions.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Existing server name:MachineName&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you genuinely need to change the name of an Enabler store server, apart from changing the Enabler configurations for the tills attached to the store server, you will need to delete the workstation.dat file found in the stores export folder.&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_Report_Logos&amp;diff=1289</id>
		<title>EEE Report Logos</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_Report_Logos&amp;diff=1289"/>
		<updated>2012-07-06T02:32:20Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 20 February 2009. Last Reviewed: 06 July 2012&lt;br /&gt;
&lt;br /&gt;
== EEE Report Logos ==&lt;br /&gt;
EEE Reports display a logo image, which can be customised.&lt;br /&gt;
&lt;br /&gt;
The default image that is installed is a “Magenta Retail” logo.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To display a customised logo, 2 versions of the image must be provided, in GIF format.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For 3 special reports (Customer Statement, Customer Statement With Remittance, and Customer Tax Invoice Credit Note), a larger size image is required. This must be named logo2.gif.&lt;br /&gt;
&lt;br /&gt;
N.B. These 3 reports are used internally by EEE versions 1.34.0.0 and later to produce Debtors Statements and Invoices/Credit Notes, and cannot be run from the Report menus.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For all other reports, a smaller size image is required. This must be named logo.gif.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Guidelines on image size and resolution&lt;br /&gt;
&lt;br /&gt;
For best results, logo.gif ideally should be no more than 1.2cm or 45 pixels high and 6.2cm or 200 pixels wide, and logo2.gif ideally should be no more than 3cm or 350 pixels high and 14cm or 1600 pixels wide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The image files will need to be uploaded into SQL Server Reporting Services, overwriting the existing logo.gif/logo2.gif.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There are two ways of uploading a logo to Reporting Services&lt;br /&gt;
&lt;br /&gt;
===Using SQL Management Studio===&lt;br /&gt;
&lt;br /&gt;
1.	Click on the SQL Server Management Studio icon&lt;br /&gt;
&lt;br /&gt;
2.	On the Connect to Server screen, change the Server Type to “Reporting Services” and then clicon on Connect.&lt;br /&gt;
&lt;br /&gt;
3.	Expand the HOME folder&lt;br /&gt;
&lt;br /&gt;
4.	Expand the EEEReportsEEE folder, or if the reports folder is called something different, expand that folder.&lt;br /&gt;
&lt;br /&gt;
5.	Locate logo.gif. This will be found at the end of the list of files&lt;br /&gt;
&lt;br /&gt;
6.	Right click on logo.gif and click on “Replace Resource”&lt;br /&gt;
&lt;br /&gt;
7.	In the Replace with field use the search button to locate the updated logo.gif&lt;br /&gt;
&lt;br /&gt;
8.	Click OK the replace the logo.gif with the updated logo.gif&lt;br /&gt;
&lt;br /&gt;
9.	To check the new logo, right click on logo.gif again and select “Open Resource”. The new logo will be displayed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Using Report Manager===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1. Open Report Manager in Internet Explorer. The url for this is normally [http://machinename/reports http://machinename/reports] (this will depend on whether the default options were chosen when reporting services was installed).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:EEE_Report_Logos_Figure_1.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
2. Click on the EEE Reports folder link to open it. This is often called “EEEReportsEEE”. There may be more than 1 folder to update if there are multiple EEE databases.&lt;br /&gt;
&lt;br /&gt;
3. Click on the “Upload File” button on the grey toolbar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:EEE_Report_Logos_Figure_2.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
4.Browse for the image file, and specify the full path and file name. Make sure the “Overwrite this item if it exists” checkbox is ticked. Click OK. This will upload the image into the Reporting Services EEE Reports folder.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:EEE_Report_Logos_Figure_3.jpg]]&lt;br /&gt;
&lt;br /&gt;
== See Also: ==&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_Report_Logos&amp;diff=1288</id>
		<title>EEE Report Logos</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_Report_Logos&amp;diff=1288"/>
		<updated>2012-07-06T02:31:02Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 20 February 2009. Last Reviewed: 06 July 2012&lt;br /&gt;
&lt;br /&gt;
== EEE Report Logos ==&lt;br /&gt;
EEE Reports display a logo image, which can be customised.&lt;br /&gt;
&lt;br /&gt;
The default image that is installed is a “Magenta Retail” logo.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To display a customised logo, 2 versions of the image must be provided, in GIF format.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For 3 special reports (Customer Statement, Customer Statement With Remittance, and Customer Tax Invoice Credit Note), a larger size image is required. This must be named logo2.gif.&lt;br /&gt;
&lt;br /&gt;
N.B. These 3 reports are used internally by EEE versions 1.34.0.0 and later to produce Debtors Statements and Invoices/Credit Notes, and cannot be run from the Report menus.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For all other reports, a smaller size image is required. This must be named logo.gif.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Guidelines on image size and resolution&lt;br /&gt;
&lt;br /&gt;
For best results, logo.gif ideally should be no more than 1.2cm or 45 pixels high and 6.2cm or 200 pixels wide, and logo2.gif ideally should be no more than 3cm or 350 pixels high and 14cm or 1600 pixels wide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The image files will need to be uploaded into SQL Server Reporting Services, overwriting the existing logo.gif/logo2.gif.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There are two ways of uploading a logo to Reporting Services&lt;br /&gt;
&lt;br /&gt;
===Using SQL Management Studio===&lt;br /&gt;
&lt;br /&gt;
1.	Click on the SQL Server Management Studio icon&lt;br /&gt;
&lt;br /&gt;
2.	On the Connect to Server screen, change the Server Type to “Reporting Services” and then clicon on Connect.&lt;br /&gt;
&lt;br /&gt;
3.	Expand the HOME folder&lt;br /&gt;
&lt;br /&gt;
4.	Expand the EEEReportsEEE folder, or if the reports folder is called something different, expand that folder.&lt;br /&gt;
&lt;br /&gt;
5.	Locate logo.gif. This will be found at the end of the list of files&lt;br /&gt;
&lt;br /&gt;
6.	Right click on logo.gif and click on “Replace Resource”&lt;br /&gt;
&lt;br /&gt;
7.	In the Replace with field use the search button to locate the updated logo.gif&lt;br /&gt;
&lt;br /&gt;
8.	Click OK the replace the logo.gif with the updated logo.gif&lt;br /&gt;
&lt;br /&gt;
9.	To check the new logo, right click on logo.gif again and select “Open Resource”. The new logo will be displayed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Using Report Manager===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1. Open Report Manager in Internet Explorer. The url for this is normally [http://machinename/reports http://machinename/reports] (this will depend on whether the default options were chosen when reporting services was installed).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:EEE_Report_Logos_Figure_1.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
2. Click on the EEE Reports folder link to open it. This is often called “EEEReportsEEE”. There may be more than 1 folder to update if there are multiple EEE databases.&lt;br /&gt;
&lt;br /&gt;
3. Click on the “Upload File” button on the grey toolbar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:EEE_Report_Logos_Figure_2.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
4.Browse for the image file, and specify the full path and file name. Make sure the “Overwrite this item if it exists” checkbox is ticked. Click OK. This will upload the image into the Reporting Services EEE Reports folder.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:EEE_Report_Logos_Figure_3.jpg]]&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_Report_Logos&amp;diff=1287</id>
		<title>EEE Report Logos</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_Report_Logos&amp;diff=1287"/>
		<updated>2012-07-06T02:30:07Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 20 February 2009. Last Reviewed: 06 July 2012&lt;br /&gt;
&lt;br /&gt;
== EEE Report Logos ==&lt;br /&gt;
EEE Reports display a logo image, which can be customised.&lt;br /&gt;
&lt;br /&gt;
The default image that is installed is a “Magenta Retail” logo.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To display a customised logo, 2 versions of the image must be provided, in GIF format.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For 3 special reports (Customer Statement, Customer Statement With Remittance, and Customer Tax Invoice Credit Note), a larger size image is required. This must be named logo2.gif.&lt;br /&gt;
&lt;br /&gt;
N.B. These 3 reports are used internally by EEE versions 1.34.0.0 and later to produce Debtors Statements and Invoices/Credit Notes, and cannot be run from the Report menus.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For all other reports, a smaller size image is required. This must be named logo.gif.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Guidelines on image size and resolution&lt;br /&gt;
&lt;br /&gt;
For best results, logo.gif ideally should be no more than 1.2cm or 45 pixels high and 6.2cm or 200 pixels wide, and logo2.gif ideally should be no more than 3cm or 350 pixels high and 14cm or 1600 pixels wide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The image files will need to be uploaded into SQL Server Reporting Services, overwriting the existing logo.gif/logo2.gif.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There are two ways of uploading a logo to Reporting Services&lt;br /&gt;
&lt;br /&gt;
===Using SQL Management Studio===&lt;br /&gt;
&lt;br /&gt;
1.	Click on the SQL Server Management Studio icon&lt;br /&gt;
&lt;br /&gt;
2.	On the Connect to Server screen, change the Server Type to “Reporting Services” and then clicon on Connect.&lt;br /&gt;
&lt;br /&gt;
3.	Expand the HOME folder&lt;br /&gt;
&lt;br /&gt;
4.	Expand the EEEReportsEEE folder, or if the reports folder is called something different, expand that folder.&lt;br /&gt;
&lt;br /&gt;
5.	Locate logo.gif. This will be found at the end of the list of files&lt;br /&gt;
&lt;br /&gt;
6.	Right click on logo.gif and click on “Replace Resource”&lt;br /&gt;
&lt;br /&gt;
7.	In the Replace with field use the search button to locate the updated logo.gif&lt;br /&gt;
&lt;br /&gt;
8.	Click OK the replace the logo.gif with the updated logo.gif&lt;br /&gt;
&lt;br /&gt;
9.	To check the new logo, right click on logo.gif again and select “Open Resource”. The new logo will be displayed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Using Report Manager===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1. Open Report Manager in Internet Explorer. The url for this is normally [http://machinename/reports http://machinename/reports] (this will depend on whether the default options were chosen when reporting services was installed).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:EEE_Report_Logos_Figure_1.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
2. Click on the EEE Reports folder link to open it. This is often called “EEEReportsEEE”. There may be more than 1 folder to update if there are multiple EEE databases.&lt;br /&gt;
&lt;br /&gt;
3. Click on the “Upload File” button on the grey toolbar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:EEE_Report_Logos_Figure_2.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
4.Browse for the image file, and specify the full path and file name. Make sure the “Overwrite this item if it exists” checkbox is ticked. Click OK. This will upload the image into the Reporting Services EEE Reports folder.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:EEE_Report_Logos_Figure_3.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
An alternative method of uploading the logo images is to use Microsoft SQL Server 2005 Management Studio instead of Report Manager. For instructions on how to do this, refer to Microsoft SQL Server Reporting Services Books Online &amp;quot;How to: Upload a File or Report (Management Studio)&amp;quot;.&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_Report_Logos&amp;diff=1286</id>
		<title>EEE Report Logos</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_Report_Logos&amp;diff=1286"/>
		<updated>2012-07-06T02:29:34Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 20 February 2009. Last Reviewed: 06 July 2012&lt;br /&gt;
&lt;br /&gt;
== EEE Report Logos ==&lt;br /&gt;
EEE Reports display a logo image, which can be customised.&lt;br /&gt;
&lt;br /&gt;
The default image that is installed is a “Magenta Retail” logo.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To display a customised logo, 2 versions of the image must be provided, in GIF format.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For 3 special reports (Customer Statement, Customer Statement With Remittance, and Customer Tax Invoice Credit Note), a larger size image is required. This must be named logo2.gif.&lt;br /&gt;
&lt;br /&gt;
N.B. These 3 reports are used internally by EEE versions 1.34.0.0 and later to produce Debtors Statements and Invoices/Credit Notes, and cannot be run from the Report menus.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For all other reports, a smaller size image is required. This must be named logo.gif.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Guidelines on image size and resolution&lt;br /&gt;
&lt;br /&gt;
For best results, logo.gif ideally should be no more than 1.2cm or 45 pixels high and 6.2cm or 200 pixels wide, and logo2.gif ideally should be no more than 3cm or 350 pixels high and 14cm or 1600 pixels wide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The image files will need to be uploaded into SQL Server Reporting Services, overwriting the existing logo.gif/logo2.gif.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There are two ways of uploading a logo to Reporting Services&lt;br /&gt;
&lt;br /&gt;
===Using SQL Management Studio===&lt;br /&gt;
&lt;br /&gt;
1.	Click on the SQL Server Management Studio icon&lt;br /&gt;
&lt;br /&gt;
2.	On the Connect to Server screen, change the Server Type to “Reporting Services” and then clicon on Connect.&lt;br /&gt;
&lt;br /&gt;
3.	Expand the HOME folder&lt;br /&gt;
4.	Expand the EEEReportsEEE folder, or if the reports folder is called something different, expand that folder.&lt;br /&gt;
5.	Locate logo.gif. This will be found at the end of the list of files&lt;br /&gt;
6.	Right click on logo.gif and click on “Replace Resource”&lt;br /&gt;
7.	In the Replace with field use the search button to locate the updated logo.gif&lt;br /&gt;
8.	Click OK the replace the logo.gif with the updated logo.gif&lt;br /&gt;
9.	To check the new logo, right click on logo.gif again and select “Open Resource”. The new logo will be displayed.&lt;br /&gt;
&lt;br /&gt;
===Using Report Manager===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1. Open Report Manager in Internet Explorer. The url for this is normally [http://machinename/reports http://machinename/reports] (this will depend on whether the default options were chosen when reporting services was installed).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:EEE_Report_Logos_Figure_1.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
2. Click on the EEE Reports folder link to open it. This is often called “EEEReportsEEE”. There may be more than 1 folder to update if there are multiple EEE databases.&lt;br /&gt;
&lt;br /&gt;
3. Click on the “Upload File” button on the grey toolbar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:EEE_Report_Logos_Figure_2.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
4.Browse for the image file, and specify the full path and file name. Make sure the “Overwrite this item if it exists” checkbox is ticked. Click OK. This will upload the image into the Reporting Services EEE Reports folder.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:EEE_Report_Logos_Figure_3.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
An alternative method of uploading the logo images is to use Microsoft SQL Server 2005 Management Studio instead of Report Manager. For instructions on how to do this, refer to Microsoft SQL Server Reporting Services Books Online &amp;quot;How to: Upload a File or Report (Management Studio)&amp;quot;.&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_Report_Logos&amp;diff=1285</id>
		<title>EEE Report Logos</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_Report_Logos&amp;diff=1285"/>
		<updated>2012-07-06T02:29:06Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 20 February 2009. Last Reviewed: 06 July 2012&lt;br /&gt;
&lt;br /&gt;
== EEE Report Logos ==&lt;br /&gt;
EEE Reports display a logo image, which can be customised.&lt;br /&gt;
&lt;br /&gt;
The default image that is installed is a “Magenta Retail” logo.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To display a customised logo, 2 versions of the image must be provided, in GIF format.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For 3 special reports (Customer Statement, Customer Statement With Remittance, and Customer Tax Invoice Credit Note), a larger size image is required. This must be named logo2.gif.&lt;br /&gt;
&lt;br /&gt;
N.B. These 3 reports are used internally by EEE versions 1.34.0.0 and later to produce Debtors Statements and Invoices/Credit Notes, and cannot be run from the Report menus.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For all other reports, a smaller size image is required. This must be named logo.gif.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Guidelines on image size and resolution&lt;br /&gt;
&lt;br /&gt;
For best results, logo.gif ideally should be no more than 1.2cm or 45 pixels high and 6.2cm or 200 pixels wide, and logo2.gif ideally should be no more than 3cm or 350 pixels high and 14cm or 1600 pixels wide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The image files will need to be uploaded into SQL Server Reporting Services, overwriting the existing logo.gif/logo2.gif.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
There are two ways of uploading a logo to Reporting Services&lt;br /&gt;
&lt;br /&gt;
===Using SQL Management Studio===&lt;br /&gt;
&lt;br /&gt;
1.	Click on the SQL Server Management Studio icon&lt;br /&gt;
2.	On the Connect to Server screen, change the Server Type to “Reporting Services” and then clicon on Connect.&lt;br /&gt;
3.	Expand the HOME folder&lt;br /&gt;
4.	Expand the EEEReportsEEE folder, or if the reports folder is called something different, expand that folder.&lt;br /&gt;
5.	Locate logo.gif. This will be found at the end of the list of files&lt;br /&gt;
6.	Right click on logo.gif and click on “Replace Resource”&lt;br /&gt;
7.	In the Replace with field use the search button to locate the updated logo.gif&lt;br /&gt;
8.	Click OK the replace the logo.gif with the updated logo.gif&lt;br /&gt;
9.	To check the new logo, right click on logo.gif again and select “Open Resource”. The new logo will be displayed.&lt;br /&gt;
&lt;br /&gt;
===Using Report Manager===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
1. Open Report Manager in Internet Explorer. The url for this is normally [http://machinename/reports http://machinename/reports] (this will depend on whether the default options were chosen when reporting services was installed).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:EEE_Report_Logos_Figure_1.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
2. Click on the EEE Reports folder link to open it. This is often called “EEEReportsEEE”. There may be more than 1 folder to update if there are multiple EEE databases.&lt;br /&gt;
&lt;br /&gt;
3. Click on the “Upload File” button on the grey toolbar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:EEE_Report_Logos_Figure_2.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
4.Browse for the image file, and specify the full path and file name. Make sure the “Overwrite this item if it exists” checkbox is ticked. Click OK. This will upload the image into the Reporting Services EEE Reports folder.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:EEE_Report_Logos_Figure_3.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
An alternative method of uploading the logo images is to use Microsoft SQL Server 2005 Management Studio instead of Report Manager. For instructions on how to do this, refer to Microsoft SQL Server Reporting Services Books Online &amp;quot;How to: Upload a File or Report (Management Studio)&amp;quot;.&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=Error_Messages&amp;diff=1284</id>
		<title>Error Messages</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=Error_Messages&amp;diff=1284"/>
		<updated>2012-07-05T03:46:01Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 27 November 2008. Last Reviewed: 05 July 2012&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Error Messages&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;New Autoscan function&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Autoscan examines every .dbf file to make one of the three following determinations.&lt;br /&gt;
&lt;br /&gt;
* The file is accessible but in need of a reindex&lt;br /&gt;
* The file is inaccessible – it may be in use or corrupt&lt;br /&gt;
* The file appears to be okay&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Shared Memory Error – Shared Memory Conflict&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Cause: &lt;br /&gt;
&lt;br /&gt;
This is likely to occur when Enabler applications are started for the first time on a Windows2000/XP machine, the error relates to the BDE (Borland Database Engine) that Enabler uses. Nibbler would be running and then you have attempted to start POS. An example of this would be POS attempting to restart after the completion of the End of Day processes.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Solution:&lt;br /&gt;
&lt;br /&gt;
From Enabler Back Office select Till Setup, Database Setup.&lt;br /&gt;
&lt;br /&gt;
* Key in one of the recommended values into the BDE Shared Memory Address field&lt;br /&gt;
* Close ALL Enabler applications then power off/on the machine&lt;br /&gt;
* Try starting nibbler, once running you should be able to start POS without getting the error.&lt;br /&gt;
* If this is unsuccessful you will need to try another value, the value can vary from machine to machine.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Database Error – Unknown Field Name&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Cause:&lt;br /&gt;
&lt;br /&gt;
This might occur if a dbf file was copied from a machine on a different version of Enabler&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Solution:&lt;br /&gt;
&lt;br /&gt;
Perform a migrate of the databases&lt;br /&gt;
&lt;br /&gt;
* Close ALL Enabler applications including Nibbler&lt;br /&gt;
* From the Run command line type:-&lt;br /&gt;
&lt;br /&gt;
x:\enabler\infoctrl migrate (where x: is the drive the Enabler is installed on)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Database Error – Nibbler has detected a database error…&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Cause:&lt;br /&gt;
&lt;br /&gt;
An application has crashed or been abnormally terminated&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Solution&lt;br /&gt;
&lt;br /&gt;
End the task and re-index all databases&lt;br /&gt;
&lt;br /&gt;
* Close ALL Enabler applications including Nibbler&lt;br /&gt;
* From the Run command line type:- x:\enabler\infoctrl\indexall (where x: is the drive the Enabler is installed on)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Lan Error – The LAN sever can not be contacted at this time&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Cause:&lt;br /&gt;
&lt;br /&gt;
A LAN (local area network) message would occur if a till was trying to access a file on the server and can’t because the network is unavailable. It is likely that Nibbler would have an X through it on the till. The system will try for 40 seconds to connect before displaying the message.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Solution:&lt;br /&gt;
&lt;br /&gt;
Check the network connection&lt;br /&gt;
&lt;br /&gt;
* Power the till off and on&lt;br /&gt;
* On the till try to drill down past the enserver share to the enabler folder on the store server&lt;br /&gt;
* On the store server drill down past the en share to the enabler folder on the till&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Database Corruption&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Cause:&lt;br /&gt;
&lt;br /&gt;
On occasion, a .DBF file might be physically corrupt.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Solution:&lt;br /&gt;
&lt;br /&gt;
In these cases you might need to replace the file with a copy from another computer, or from Head Office, or as a last resort from \upgbase. If you replace from \upgbase you would be erasing the data in that table. It is recommended that you run chkdsk.&lt;br /&gt;
&lt;br /&gt;
* Close ALL Enabler applications including Nibbler&lt;br /&gt;
* Copy \UPGBASE\LOCAL\filename.dbf to \ENABLER\LOCAL&lt;br /&gt;
* You will need to perform a reindex&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;When replacing a data file keep a copy of the file being replaced in case the replacement doesn’t fix the problem e.g. registry corruption.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Reporting – Crystal Run Time Error&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Cause:&lt;br /&gt;
&lt;br /&gt;
This can happen when the suppliers report printer drivers have been used.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Solution:&lt;br /&gt;
&lt;br /&gt;
Add the report printer using Windows drivers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Retrieving Error Messages when Further Investigation is Required&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
.ERR and .DBE files can be copied from the \enabler directory&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Transaction Recovery File&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
When transacting a sale, Enabler maintains a journal log of the transaction to date. This is used to recover the transaction to exactly the same point in the event of a system crash, power failure etc. (A setup flag within Sales Options controls this feature) On occasion, the journal log file has been found to become corrupt. This can cause the POS module to crash as soon as it tries to access the transaction recovery file. To overcome this, either hold down the CTRL key while the POS application is loading (keep holding the key until the main POS screen appears), or erase the file from the \enabler folder. The filename is TRANSLOG.JNL&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Database Error – Required Database Missing&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Cause:&lt;br /&gt;
&lt;br /&gt;
An application has crashed or been abnormally terminated&lt;br /&gt;
&lt;br /&gt;
Solution:&lt;br /&gt;
&lt;br /&gt;
Check to see if the database file physically exists, if so:&lt;br /&gt;
&lt;br /&gt;
* Delete the index (.mdx) and try and re-index the file&lt;br /&gt;
* If the database is missing you will need to replace it from another machine or from \upgbase. &lt;br /&gt;
&lt;br /&gt;
NOTE: If the file is in \enabler\lantran on a store server you will be erasing all history, tills don’t write to lantran locally so replacing from a till (node) will NOT recover the history e.g. sales processed on a node are being written to the \enabler\lantran folder on the store server.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Database Errors that might occur when Staging a Machine&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Required database missing \branch.dbf. This could occur when you start Back Office for the first time and select the diskette option to import configuration. This error is a result of attempting to import Enabler configuration on a machine where you have cloned from a machine that has Enabler on a different drive. E.g. a till was cloned on the Head Office server from a branch that has Enabler installed on D: drive, the machine you are wanting to import on has Enabler on the C: drive.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Nibbler wants to start up as a server, but cannot obtain a lock necessary to do so. Check to see if there is another server.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Cause:&lt;br /&gt;
&lt;br /&gt;
This can occur if a stores till locks the \\storeserver\enserver\lanmnt\comflg.dbf database preventing the store server from opening this file when Nibbler starts. It is likely that Nibbler would have a X through it on the tills.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Solution:&lt;br /&gt;
&lt;br /&gt;
Replace the comflg.dbf&lt;br /&gt;
&lt;br /&gt;
* Shutdown nibbler on all tills&lt;br /&gt;
* On the store server, replace the \enabler\lanmnt\comflg.dbf with an empty file from an upgrade pack for the same Enabler version being used in the store&lt;br /&gt;
* On the store server startup Enabler and verify that Nibbler starts without an error&lt;br /&gt;
* On the tills startup Enabler and verify they startup correctly and nibbler is yellow on all tills and the store server&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= See Also =&lt;br /&gt;
&lt;br /&gt;
[[Anti-virus_software|Anti Virus Software]]&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=Error_Messages&amp;diff=1283</id>
		<title>Error Messages</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=Error_Messages&amp;diff=1283"/>
		<updated>2012-07-05T03:45:31Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 27 November 2008. Last Reviewed: 05 July 2012&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Error Messages&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;New Autoscan function&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Autoscan examines every .dbf file to make one of the three following determinations.&lt;br /&gt;
&lt;br /&gt;
* The file is accessible but in need of a reindex&lt;br /&gt;
* The file is inaccessible – it may be in use or corrupt&lt;br /&gt;
* The file appears to be okay&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Shared Memory Error – Shared Memory Conflict&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Cause: &lt;br /&gt;
&lt;br /&gt;
This is likely to occur when Enabler applications are started for the first time on a Windows2000/XP machine, the error relates to the BDE (Borland Database Engine) that Enabler uses. Nibbler would be running and then you have attempted to start POS. An example of this would be POS attempting to restart after the completion of the End of Day processes.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Solution:&lt;br /&gt;
&lt;br /&gt;
From Enabler Back Office select Till Setup, Database Setup.&lt;br /&gt;
&lt;br /&gt;
* Key in one of the recommended values into the BDE Shared Memory Address field&lt;br /&gt;
* Close ALL Enabler applications then power off/on the machine&lt;br /&gt;
* Try starting nibbler, once running you should be able to start POS without getting the error.&lt;br /&gt;
* If this is unsuccessful you will need to try another value, the value can vary from machine to machine.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Database Error – Unknown Field Name&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Cause:&lt;br /&gt;
&lt;br /&gt;
This might occur if a dbf file was copied from a machine on a different version of Enabler&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Solution:&lt;br /&gt;
&lt;br /&gt;
Perform a migrate of the databases&lt;br /&gt;
&lt;br /&gt;
* Close ALL Enabler applications including Nibbler&lt;br /&gt;
* From the Run command line type:-&lt;br /&gt;
&lt;br /&gt;
x:\enabler\infoctrl migrate (where x: is the drive the Enabler is installed on)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Database Error – Nibbler has detected a database error…&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Cause:&lt;br /&gt;
&lt;br /&gt;
An application has crashed or been abnormally terminated&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Solution&lt;br /&gt;
&lt;br /&gt;
End the task and re-index all databases&lt;br /&gt;
&lt;br /&gt;
* Close ALL Enabler applications including Nibbler&lt;br /&gt;
* From the Run command line type:- x:\enabler\infoctrl\indexall (where x: is the drive the Enabler is installed on)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Lan Error – The LAN sever can not be contacted at this time&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Cause:&lt;br /&gt;
&lt;br /&gt;
A LAN (local area network) message would occur if a till was trying to access a file on the server and can’t because the network is unavailable. It is likely that Nibbler would have an X through it on the till. The system will try for 40 seconds to connect before displaying the message.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Solution:&lt;br /&gt;
&lt;br /&gt;
Check the network connection&lt;br /&gt;
&lt;br /&gt;
* Power the till off and on&lt;br /&gt;
* On the till try to drill down past the enserver share to the enabler folder on the store server&lt;br /&gt;
* On the store server drill down past the en share to the enabler folder on the till&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Database Corruption&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Cause:&lt;br /&gt;
&lt;br /&gt;
On occasion, a .DBF file might be physically corrupt.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Solution:&lt;br /&gt;
&lt;br /&gt;
In these cases you might need to replace the file with a copy from another computer, or from Head Office, or as a last resort from \upgbase. If you replace from \upgbase you would be erasing the data in that table. It is recommended that you run chkdsk.&lt;br /&gt;
&lt;br /&gt;
* Close ALL Enabler applications including Nibbler&lt;br /&gt;
* Copy \UPGBASE\LOCAL\filename.dbf to \ENABLER\LOCAL&lt;br /&gt;
* You will need to perform a reindex&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;When replacing a data file keep a copy of the file being replaced in case the replacement doesn’t fix the problem e.g. registry corruption.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Reporting – Crystal Run Time Error&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Cause:&lt;br /&gt;
&lt;br /&gt;
This can happen when the suppliers report printer drivers have been used.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Solution:&lt;br /&gt;
&lt;br /&gt;
Add the report printer using Windows drivers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Retrieving Error Messages when Further Investigation is Required&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
.ERR and .DBE files can be copied from the \enabler directory&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Transaction Recovery File&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
When transacting a sale, Enabler maintains a journal log of the transaction to date. This is used to recover the transaction to exactly the same point in the event of a system crash, power failure etc. (A setup flag within Sales Options controls this feature) On occasion, the journal log file has been found to become corrupt. This can cause the POS module to crash as soon as it tries to access the transaction recovery file. To overcome this, either hold down the CTRL key while the POS application is loading (keep holding the key until the main POS screen appears), or erase the file from the \enabler folder. The filename is TRANSLOG.JNL&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Database Error – Required Database Missing&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Cause:&lt;br /&gt;
&lt;br /&gt;
An application has crashed or been abnormally terminated&lt;br /&gt;
&lt;br /&gt;
Solution:&lt;br /&gt;
&lt;br /&gt;
Check to see if the database file physically exists, if so:&lt;br /&gt;
&lt;br /&gt;
* Delete the index (.mdx) and try and re-index the file&lt;br /&gt;
* If the database is missing you will need to replace it from another machine or from \upgbase. &lt;br /&gt;
&lt;br /&gt;
NOTE: If the file is in \enabler\lantran on a store server you will be erasing all history, tills don’t write to lantran locally so replacing from a till (node) will NOT recover the history e.g. sales processed on a node are being written to the \enabler\lantran folder on the store server.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Database Errors that might occur when Staging a Machine&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Required database missing \branch.dbf. This could occur when you start Back Office for the first time and select the diskette option to import configuration. This error is a result of attempting to import Enabler configuration on a machine where you have cloned from a machine that has Enabler on a different drive. E.g. a till was cloned on the Head Office server from a branch that has Enabler installed on D: drive, the machine you are wanting to import on has Enabler on the C: drive.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Nibbler wants to start up as a server, but cannot obtain a lock necessary to do so. Check to see if there is another server.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Cause:&lt;br /&gt;
&lt;br /&gt;
This can occur if a stores till locks the \\storeserver\enserver\lanmnt\comflg.dbf database preventing the store server from opening this file when Nibbler starts. It is likely that Nibbler would have a X through it on the tills.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Solution:&lt;br /&gt;
&lt;br /&gt;
Replace the comflg.dbf&lt;br /&gt;
&lt;br /&gt;
* Shutdown nibbler on all tills&lt;br /&gt;
* On the store server, replace the \enabler\lanmnt\comflg.dbf with an empty file from an upgrade pack for the same Enabler version being used in the store&lt;br /&gt;
* On the store server startup Enabler and verify that Nibbler starts without an error&lt;br /&gt;
* On the tills startup Enabler and verify they startup correctly and nibbler is yellow on all tills and the store server&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= See Also =&lt;br /&gt;
&lt;br /&gt;
[[Anti-virus_software|Anti Virus Software]]&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=Changing_Company_Details_on_Purchase_Orders&amp;diff=1282</id>
		<title>Changing Company Details on Purchase Orders</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=Changing_Company_Details_on_Purchase_Orders&amp;diff=1282"/>
		<updated>2012-07-05T02:43:07Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 30 January 2009. Last Reviewed: 05 July 2012&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To change company details displayed on suppliers copies of Purchase orders would require edit of text files located in C:\Inetpub\wwwroot\EEE\CompanyConfig. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above procedure is no longer applicable as Purchase Order configuration details are now all held in the EEE database. To change the company details displayed on supplier copies of Purchase Orders, login to EEE and go to Utilities-&amp;gt;Configuration-&amp;gt;Purchasing Configuration&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1281</id>
		<title>EEE WebService</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1281"/>
		<updated>2012-07-05T02:33:42Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 05 July 2012.  Last Reviewed: 05 July 2012&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;EEE WebService&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.&lt;br /&gt;
&lt;br /&gt;
Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au&lt;br /&gt;
&lt;br /&gt;
Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities-&amp;gt;Configuration-&amp;gt;Configuration Settings-&amp;gt;Licensed Plugins tab.&lt;br /&gt;
&lt;br /&gt;
Magenta Retail provide EEE Web Service documentation which can be downloaded from here:-&lt;br /&gt;
&lt;br /&gt;
[[Media:EEE WebService.pdf|EEE Web Service Documentation]]&lt;br /&gt;
&lt;br /&gt;
Example XML and XSD files can be downloaded from our FTP site using the links below&lt;br /&gt;
&lt;br /&gt;
* Sample XML files [ftp://ftp.magentaretail.com.au/Documents/EEEWebService/XmlSample.zip Please click here]&lt;br /&gt;
* Sample Xsd files [ftp://ftp.magentaretail.com.au/Documents/EEEWebService/Xsd.zip Please click here]&lt;br /&gt;
&lt;br /&gt;
== See Also: ==&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1280</id>
		<title>EEE WebService</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1280"/>
		<updated>2012-07-05T02:31:54Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 05 July 2012.  Last Reviewed: 05 July 2012&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;EEE WebService&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.&lt;br /&gt;
&lt;br /&gt;
Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au&lt;br /&gt;
&lt;br /&gt;
Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities-&amp;gt;Configuration-&amp;gt;Configuration Settings-&amp;gt;Licensed Plugins tab.&lt;br /&gt;
&lt;br /&gt;
Magenta Retail provide EEE Web Service documentation which can be downloaded from here:-&lt;br /&gt;
&lt;br /&gt;
[[Media:EEE WebService.pdf|EEE Web Service Documentation]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Sample XML files [ftp://ftp.magentaretail.com.au/Documents/EEEWebService/XmlSample.zip Please click here]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== See Also: ==&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1279</id>
		<title>EEE WebService</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1279"/>
		<updated>2012-07-05T02:24:19Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 05 July 2012.  Last Reviewed: 05 July 2012&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;EEE WebService&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.&lt;br /&gt;
&lt;br /&gt;
Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au&lt;br /&gt;
&lt;br /&gt;
Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities-&amp;gt;Configuration-&amp;gt;Configuration Settings-&amp;gt;Licensed Plugins tab.&lt;br /&gt;
&lt;br /&gt;
Magenta Retail provide EEE Web Service documentation which can be downloaded from here:-&lt;br /&gt;
&lt;br /&gt;
[[Media:EEE WebService.pdf|EEE Web Service Documentation]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== See Also: ==&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1278</id>
		<title>EEE WebService</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1278"/>
		<updated>2012-07-05T02:22:52Z</updated>

		<summary type="html">&lt;p&gt;Trevor: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 05 July 2012.  Last Reviewed: 05 July 2012&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;EEE WebService&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.&lt;br /&gt;
&lt;br /&gt;
Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au&lt;br /&gt;
&lt;br /&gt;
Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities-&amp;gt;Configuration-&amp;gt;Configuration Settings-&amp;gt;Licensed Plugins tab.&lt;br /&gt;
&lt;br /&gt;
Magenta Retail provide EEE Web Service documentation which can be downloaded from here:-&lt;br /&gt;
&lt;br /&gt;
[[Media:EEE WebService.pdf|EEE Web Service Documentation]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See Also:&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1277</id>
		<title>EEE WebService</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=EEE_WebService&amp;diff=1277"/>
		<updated>2012-07-05T02:22:06Z</updated>

		<summary type="html">&lt;p&gt;Trevor: Created page with &amp;quot;Created: 05 July 2012.  Last Reviewed: 05 July 2012   ---EEE WebService---  EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a we...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Created: 05 July 2012.  Last Reviewed: 05 July 2012&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
---EEE WebService---&lt;br /&gt;
&lt;br /&gt;
EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.&lt;br /&gt;
&lt;br /&gt;
Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au&lt;br /&gt;
&lt;br /&gt;
Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities-&amp;gt;Configuration-&amp;gt;Configuration Settings-&amp;gt;Licensed Plugins tab.&lt;br /&gt;
&lt;br /&gt;
Magenta Retail provide EEE Web Service documentation which can be downloaded from here:-&lt;br /&gt;
&lt;br /&gt;
[[Media:EEE WebService.pdf|EEE Web Service Documentation]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See Also:&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
	<entry>
		<id>https://theoracle.magentaretail.com.au/index.php?title=File:EEE_WebService.pdf&amp;diff=1276</id>
		<title>File:EEE WebService.pdf</title>
		<link rel="alternate" type="text/html" href="https://theoracle.magentaretail.com.au/index.php?title=File:EEE_WebService.pdf&amp;diff=1276"/>
		<updated>2012-07-05T02:20:24Z</updated>

		<summary type="html">&lt;p&gt;Trevor: uploaded a new version of &amp;amp;quot;File:EEE WebService.pdf&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Trevor</name></author>
	</entry>
</feed>