iVend POS – Transaction Server
Transaction Server is an API service hosted on the iVend Enterprise. Transaction Server reduces the data replication across the store network when Inter-store Transactions has been enabled in the system or when SQL Express is being used at the stores.
iVend POS can look for a transaction on the transaction server in event that the record is not found on the local store. Therefore, when there are inter-store refunds where the original transaction was performed at a different store, the system, on scanning the original receipt, will first connect to the Transaction Server service and will then fetch the details from the iVend Enterprise server.
Similarly, when the data is purged on the local store, the transaction details would be searched and fetched from the transaction server. The system can be configured in such a way that while searching the transaction, the system will always check the local Store database and the iVend Enterprise database for the available information.
To setup the Transaction Server, follow these steps:
1. Log into the iVend Management Console and go to: Administration > Enterprise
Please note that this option is only available at the iVend Enterprise.
Figure 1 – Transaction Server Settings
Refer to the table below for detailed information on each Transaction Server settings:
Settings | Description |
Is Transaction Server Integrated | Select this check box integrate the Transaction Server. |
Exchange Transaction Data Between Store | Select this check box to exchange transaction data between stores. |
Transaction Search Type | From the dropdown list, select the Transaction Search type option from either Local Server or Local and Enterprise Server. Note: If you select the Local Server value from the drop down list, At the POS, both buttons [F1 Search] and [Transaction Server Search] will be available. The [F1 Search] button will fetch the data from local Store server and [Transaction Server Search] will fetch the data from the iVend Enterprise server. Note: If you select the Local and Enterprise Server value from the drop down list, then at the POS only the [F1 Search] button is available and this will fetch the data from both the local and Enterprise server. |
Maximum Records Count To Return From Server | Specify the Maximum number of records count to be returned from the server when the search is performed. |
Validate Transaction Quantity on Refund | Select this checkbox if you wish the quantity in the original transaction to be verified to ensure quantity being returned was valid. |
1. Specify all the relevant details and options required for the Transaction Server settings.
1. Choose the [Ok] button to save the changes made to the settings in the Enterprise for Transaction Server.
How to use Transaction Server Search
at the POS.
To
use Transaction Server Search at the POS,
follow these steps:
1. Log
into the POS application, press [F6 Transaction Search].
Figure 2 – Transaction
Search Screen
1. As in the
example, the Transaction Search Type setting was
defined as Local Server from the drop down list,
therefore on the Transaction Search screen, both
buttons [F1 Search] and [Transaction Server Search] will
be available.
Figure 3 –
Transaction Search
1. In our example, the Administrator has run a data
purge for the store. Therefore, when the user
runs a standard search using the [F1 Search] option,
for a date before the data purge, the “No records found” message will appear to
the user.
Figure 4 –
Transaction Search
1. If the user then runs
a transaction search using the [Transaction Server Search] option
instead for the same date that falls in the data purge range, then they
will see data being returned.
Figure 5 –
Transaction Search
Note: If the data displayed in the
Transaction Server Search screen is then used to perform an action such as a
refund, then the data will be saved in the
local Store server database.
This concludes the KB on iVend POS –
Transaction Server.