SYSPRO Point of Sale

Run SELECT @@SERVERNAME on the server on which you are getting the error.

If it is the subscriber and has a different name from actual machine, and the instance name is returned, then the server might have been renamed after Microsoft SQL Server was installed.

Run sp_dropserver 'yourServerName\SQLInstance' GO sp_addserver yourServerName\SQLInstance', 'local'.

Remember to restart Microsoft SQL Server after the change and check the server name again.

1. Ensure that the publisher allows Microsoft SQL Server ports through the firewall.

   SQL usually uses port 1433.

2. If the CPU/Memory usage is maxed out, limit the amount of memory that SQL server is allowed to use.

3. Change the subscriber connection to ensure it is not using impersonate but rather SQL Server authentication.

4. Enter the SA account on the branch machine/server.

Allow NTAUTHORITY/ANONYMOUS at the subscriber server under Microsoft SQL Server Security.

The following steps explain how to re-create and re-initialize the publications on your main server:

1. Generate the scripts to create the publication.

2. Open the script and look for @subscriber_password = nullas.

   This must contain the correct password to connect to the subscriber (e.g. @ s u b s c r i b e r _ p a s s w o r d = N'passwordForBranchConnection').

   This process must be done three times - once for every publication for SYSPRO Point of Sale. Once you have the three scripts, you are ready to remove the current publications and subscriptions.

3. Delete the Publications.

   If it asks to delete all subscriptions, select YES.

   From here on, follow the steps for only the Sysprodb publication and not the SysproCompanyID_POS and SysproCompanyID publications.

   This ensures that if you experience any problems, your branches will not be affected. You can then identify the required steps to set everything up again and be able to repeat the steps for the other two publications.

4. Once the publication and subscriptions have been removed successfully, you can execute the script to recreate the publication and the subscription.

5. Once the publication and subscription have been recreated successfully, start the snapshot agent.

Give it a few seconds and the replication should then be up and running properly.

1. Check the three MIME mappings for Silverlight.
2. Restart Internet Information Services (IIS) after adding MIME types.
3. Grant read permission on Silverlight.js to the application pool identity (NETWORK SERVICE).
4. Grant read permission on the ClientBin folder to the application pool identity (NETWORK SERVICE).
5. Grant permission on exception.txt to the application pool identity (NETWORK SERVICE).

1. Right-click on AppPool in Internet Information Services (IIS) in which the application is hosted.
2. Select Advanced Settings.
3. Ensure that the Enable 32-Bit Applications option is defined as False.

1. Check which identity is used in Internet Information Services (IIS) by the AppPool.

   This is usually changed to Network Service and then this account is given permission to the C:\Windows\Temp directory.

2. Ensure that both the 32-bit and 64-bit versions for Crystal are installed.

1. Grant the AppPool identity access to the C:\inetpub\wwwroot\SysproPOS_CompanyID folder.
2. Add the user specified in the identity impersonate="true" tag to the admin group on the server.

1. Grant the identity impersonate="true" user full access to the C:\windows\temp folder.
2. Grant the identity impersonate="true" user full access to the C:\inetpub\wwwroot\SysproPOS_CompanyID\Temp folder.
3. Grant the AppPool identity user full access to the C:\windows\temp folder.
4. Grant the AppPool identity user full access to the C:\inetpub\wwwroot\SysproPOS_CompanyID\Temp folder.

This is not an error encountered but rather a random redirect that happens when running the application.

The URL contains strange values (e.g. you go to localhost/Pos/Default.aspx and then suddenly you get redirected to localhost/Pos/SD(sdfsdfsd-sdfsdf)/Default.aspx.

There is a setting in the web.config file that indicates cookieless="true", change this to be cookieless="false".

Network Service.

Microsoft .NET Framework 4 or higher.

IUSR and Network Service.

You should always setup a test company first. However, there is currently no way to use setup data in test company as a master copy for a live install.

No, there is no copy branch facility. The branch settings need to be carefully considered for each branch.

End of Day settings, allowed warehouses, payment types, etc. are different per branch so it is not advisable to copy a branch.

To assist with a smooth installation and optimal performance:

• the SQL port needs to be open (inbound and outbound).
• the port that SYSPRO Point of Sale is being hosted on (set in Internet Information Services (IIS)) must be open, both inbound and outbound.

There are 2 options when installing SYSPRO Point of Sale:

• Online version

  This must be installed on the same server that the main SYSPRO installation resides and provides full accessibility to all the functions provided by the SYSPRO Point of Sale system.

• Offline SYSPRO Point of Sale system

  This is installed at each location on a server and synchronizes with the head office server at time intervals, depending on your configuration.

Both versions can run simultaneously, or the online version can be run on its own. However, the offline version requires the online version to function.

The SYSPRO company is defined when SYSPRO Point of Sale is initially installed. Therefore, to run multiple SYSPRO Point of Sale companies simultaneously, multiple installs are required to cater for each company.

Yes.

However, an error may arise when HTTP Activation is not enabled for WCF services, as this prevents SYSPRO Point of Sale from communicating with the services it requires. The solution is to simply enable this within Windows Features as it is disabled by default.

Unfortunately, this is not something we can stipulate. We recommend that you get in a specialist who can assess your network, data size and all other elements that could affect your requirements.

The following factors need to be taken into account when considering line speeds:

• Number of users accessing the system
• Volume of transactions being processed

The installation rolls back if it encounters an error. However, if the install completes and the application fails to open, you can check the following possible causes:

• The domain exists, and that both the online main server and offline branch server(s) reside on the same domain.

• The SysproLoginForPos SQL user does not already exist.

  This SQL user is created (including password generation) and the necessary permissions are assigned to it during the installation process. Therefore, this user must not be changed.

  In addition, the _SysproPOSRole role is created within Microsoft SQL Server during the installation process, and it inherits permissions from the SQL user. Therefore, this role must not be altered in any way.

• The ISAPI and CGI restrictions are set up correctly in Internet Information Services (IIS).

• Permissions are configured correctly for the following:

  • LOG – ERROR.txt

  • SysproPos.xap

  • Silverlight.js

• The connection string in the web.config file is pointing the application to the correct server.

• That Microsoft Publisher allows Microsoft SQL Server ports through the firewall (this is generally port number 1433).

The Internet Information Services (IIS) WebSocket Protocol feature is required when installing one of the following:

• SYSPRO Avanti

• SYSPRO Point of Sale

Therefore, before installing either of these products, you can enable the Internet Information Services (IIS) WebSocket Protocol feature as follows:

1. Open the Turn Windows Features on or off program.

2. Navigate as follows:

   Internet Information Services > World Wide Web Services > Application Development Features

3. Enable the WebSocket Protocol option.

   

4. Save your changes.

No.

A SYSPRO Point of Sale user is linked to a SYSPRO Point of Sale branch. Therefore, if a user is linked to a branch that is flagged as offline, they are only able to log into that specific offline branch.

Similarly, a user linked to an online branch can't log into an offline branch with the same credentials. However, the online user can switch between online branches using the Branch Selection program within SYSPRO Point of Sale.

This is a SYSPRO operator that is created with full admin permissions and is flagged as POS Only.

This grants the POS user all the right permissions to use SYSPRO Point of Sale and simultaneously log into SYSPRO in the background.

While the POS user is linked to a SYSPRO operator with full admin rights, they will not be able to log into SYSPRO using this operator.

This operator is used to call the required business objects to retrieve setup information from SYSPRO.

It is also used to generate SYSPRO operators linked to SYSPRO Point of Sale operators for traceability of transactions in SYSPRO, however, none of these users can log into core SYSPRO.

Each SYSPRO Point of Sale operator has a generated (or existing where required) SYSPRO operator, which provides traceability and audit trails in SYSPRO at an operator level.

These generated operators are copied from __POS and are flagged as Point of Sale only operators, therefore they can't log into core SYSPRO.

Only SYSPRO Point of Sale programs use the __POS operator internally for retrieving required system information before a user has even logged in.

The head office server requires a fully licensed Microsoft SQL Server version (the minimum being Microsoft SQL Server 2008 R2).

This allows you to set-up replication and no additional licenses are required for the branches to subscribe.

Microsoft SQL Server Express 2008 R2 (free version) can be used at the branches for a branch server and requires no license.

As Microsoft SQL Server Express does not include the SQL Agent, SQL backups can't be scheduled.

Therefore, if you require scheduled back-ups, you need to purchase a full version of Microsoft SQL Server for the branches.

• Sysprodb
• SYSPRO Company
• SYSPRO Point of Sale database

SYSPRO Point of Sale queries the databases via stored procedures that are managed internally.

1. Log into the SQL instance used with the SQL user and password specified in the connection string of the Web.config file.

2. Check if the SQL login specified in the connection string has access to the database.

   If not, then log into SQL with a SQL administrator account and check that the database mappings for the SQL user in Web.config file are correct according to the documentation.

We recommend daily backups of the following:

• Head office SYSPRO Company
• SYSPRO Point of Sale database
• All of the branch's SYSPRO Point of Sale databases

No, only critical functionality is available offline.

It is the assumption that the lines to head office should be a good speed and should be connected most of the time, so in the event that they do go down (which should be the exception, not the norm) the branch will still be able to service customers.

Any store management functionality such as stock receipts, SCT’s etc. will have to be done when the lines are back up again, but this will not affect the branches ability to trade.

SYSPRO Point of Sale does have the option to allow stock to be sold if there is no quantity available, so they can continue to sell and when the lines are up, and the receipt has been done, the stock will be rectified.

Typically, in retail, stock is managed centrally and pushed down to all the stores who will then receipt in stock.

In this instance, the store may still require access to SCT's to allow them to transfer stock between branches for customer requests, or from Head Office if the business process allows.

The two interfaces cater for different retail environments:

• The SYSPRO Point of Sale interface is used for over-the-counter sales and is the true retail interface.

  This allows for stock to be scanned, payment taken, and receipt printed quickly to service the customer.

• The Manage Orders interface is used in a more sophisticated sales environment where there is a more involved sales process and one or more of the following is required:

  • Pick slips (where the stock is in a separate area to the sales person)
  • Deposit orders (in a make-to-order environment where customers may pay a deposit to begin production on an order)
  • Partial invoicing (where some items are available now and some will be delivered or collected later)
  • Printing to warehouse (pick slip, collection slip, delivery note)

Yes, SYSPRO Point of Sale has barcode template functionality to allow you to define and cross reference supplier barcodes.

Yes, SYSPRO Point of Sale has barcode template functionality to allow you to define a template that matches the barcode printed out by the weigh scale.

Typically, the barcodes printed out from the weigh scales will contain the stock code and quantity. Therefore, once this is defined in SYSPRO Point of Sale, you can scan the barcode and the system automatically adds the line with the correct quantity.

1. Discount reasons can be setup in SYSPRO Point of Sale and are time based. Therefore they can be configured to only be available for a specified time period. Operators can then select the discount during a sale to apply to a stock item.

2. Contract prices can be setup for a specified item or items for a time period with a discounted price that SYSPRO Point of Sale automatically picks up.

3. All standard TPM Promotions in SYSPRO are catered for in SYSPRO Point of Sale.

   For example:

   • Buy one get one free

   • Buy one get one at a discount

   • Buy one get another free or for a discount

No, TPM pricing is not available with SYSPRO Point of Sale.

SYSPRO Point of Sale handles the rounding of values based on the SYSPRO settings under Tax Options, and no additional rounding is done within SYSPRO Point of Sale itself.

Therefore, ensure that your Rounding options within the SYSPRO Setup Options program are defined correctly (Setup Options > Tax > Company Tax Options).

Yes, documents can be emailed from within SYSPRO Point of Sale.

Whenever a document is generated, the Printing Options window is displayed with an option to email the document.

Yes, standard document templates are provided with the product.

These can be customized using the Printing Designer program within SYSPRO Point of Sale.

The way each user's scanner works is determined by the properties defined.

If you want all user's scanners to be able to scan a barcode which automatically adds the stocked line to the order, then each individual scanner needs to be setup to SCAN and then ENTER.

After each new release of SYSPRO Point of Sale.

You can use the keyboard shortcut (Ctrl + R) or follow these steps:

1. Navigate to Tools (Alt-X).
2. Select development tools (F12).
3. Select the Cache tab.
4. Select the Clear cache option (Ctrl + R).

The Preserve Favorites website data check box.

The local instance.

In the IMPACT.INI file:

SQLDSN=SysproServer

To create a connection from SYSPRO to Microsoft SQL Server.

You need to use SQL authentication with a SQL admin user.

Offline branches do not have a complete SYSPRO installation, rather they have the SYSPRO Point of Sale offline foundation version installed. This version has all the business objects required to create all of the different transactions, but not post them to SYSPRO.

All of the offline transactions are saved in the SYSPRO Point of Sale database and are then copied later to the main server (where SYSPRO is installed) using the windows copy service. Once the transaction is copied, the windows posting service posts all of the transactions to SYSPRO.

All the data that is needed on the branch (e.g. customer information) is replicated down from the main server using SQL replication to ensure that the branch always has the most up to date information from SYSPRO.

SYSPRO Point of Sale has a Branch Invoice number and a Quote number that is unique to SYSPRO Point of Sale.

If the branch is offline, it will only ever print the Branch Invoice number for customers as the posting only happens in SYSPRO when the transactions are copied and posted.

The offline architecture in SYSPRO Point of Sale is not designed to cater for poor line speeds.

The offline architecture still has to copy transactions to head-office and retrieve data from head-office, therefore the internet lines need to be suitable to handle this.

Using the offline architecture enables operators to trade regardless of whether the lines are down, or the speed has dipped. If the lines do go down, the operator can still trade unaffected and completely independent of what is happening with the lines.

• Faster speeds

  One of the biggest benefits the offline architecture is speed.

  When processing sales from SYSPRO Point of Sale you don't have to wait for SYSPRO posting to occur to complete the sale as this gets done in the background by the posting services. This increases the processing speed substantially which is important in a true retail environment where high transaction volumes are being processed.

  This does not apply to Manage Orders as this functionality is only available when the lines are up and will post information to SYSPRO immediately.

• Always-on functionality

  The offline architecture ensures that the branch has limited or no down-time if there are connection issues to head-office or the main server goes down.

  This is critical in retail as it allows the branches to trade and service customers regardless of whether or not you are connected to head-office.

  Only operations that are critical to servicing customers are available in the event the lines go down:

  • Point of Sale, Quotes, Credit notes, Exchanges, Account payments, Cash-ups and End of Day's.

The following functionality is still available to operators when there is no connection to head office:

• Store:

  • Point of Sale

  • Account Payments

  • Manage Quotes

  • Credit Notes

  • Exchanges

• Query:

  • Customer Query

  • Inventory Query

• Finance:

  • Cash-up slip

  • Supervisor cash-up

  • End of day

  • Sales Report

  • Payments Report

This means that you can use also use SYSPRO Point of Sale for trade shows where there is no connection, and then sync everything at a later stage.

Because all of the functionality mentioned above is available when you are physically offline, so if you have SYSPRO Point of Sale installed on a laptop, you can then trade offline using off the offline functionality. As soon as you plug the laptop back into the network, it then automatically syncs and posts to SYSPRO.

The end of day posting is an initial transfer of all the money from your dummy bank (cash clearing bank) to your cash clearing general ledger (i.e. overs/unders) account.

From that general ledger account all the money is then transferred (in summary) to your actual banks in the cash book, as setup against the payment types in SYSPRO.

The transactional bank must never be the same as the live bank.

It is mandatory to have one (different) transactional bank configured in SYSPRO for each SYSPRO Point of Sale branch.

It is imperative that all transactions that initiate from SYSPRO Point of Sale are completed from SYSPRO Point of Sale to avoid balances on the Transactional bank.

Balances in the Transactional bank can however be caused by the following:

• Transactions remain in Manage Online

  These often get a posting error before the payment is applied in SYSPRO.

• Transactions remain in Manage Online, and then are manually completed in SYSPRO.

  If a user manually completes it in SYSPRO without understanding the flow correctly, the natural flow in SYSPRO would be to pay an invoice using the live bank.

  For example:

  The actual bank will be overstated by $300 and the transactional bank will be understated by $300.

• The end of days haven’t completed posting to SYSPRO and have an error that needs to be corrected before the posting can complete.

  In some instances, the withdrawal out of the Trial Balance would not have happened yet.

• Ensure that Manage Online is cleared daily and that SYSPRO banks are balanced daily.
• A Transactional bank and Variance general ledger codes must be defined per branch. These must be NEW accounts and banks created in SYSPRO.
• Make sure that the Transactional bank code is NOT the same as the live bank code defined against the payment type.
• Do not complete any transaction initiated from SYSPRO Point of Sale in SYSPRO manually.

The following process must be followed daily to manage SYSPRO Point of Sale:

• Manage the transactions stuck in Manage Online daily and ensure that all transactions are posted successfully through SYSPRO Point of Sale.

  If there is an error with a transaction not posting, it must be raised with SYSPRO support so that it can be rectified in the product to avoid the same thing happening in the future.

  There should be no manual corrections unless instructed otherwise by SYSPRO.

  In the even that this happens, a comment must ALWAYS be captured in the posting error column specifying what the manual steps taken were.

• End of Days must be checked daily to ensure that they have posted to SYSPRO correctly.

  Unfortunately, there is no standard way to do this in SYSPRO Point of Sale yet. But in the interim - there is an EODNotYetPostedToSYSPRO.sql script that has been created so that these can be queried daily and actioned accordingly.

  Pay attention to the PostingError and PostingStatus to see what the problem is.

• Finance should be balancing this daily in SYSPRO after confirmation that all transactions and end of days have been posted successfully.

The settings are configurable within each specific service's configuration file, which is located in the install directory of the specific service.

The Copy Service is a Windows service that runs on the main application server and is responsible for copying data from all the branch servers to the main server, and then to SYSPRO.

This is an essential service to successfully use the Offline architecture of SYSPRO Point of Sale.

In the SYSPROPOS database, a table called _BranchesSqlConnections contains the connection strings which the Copy Service references to copy the waiting offline branch data. Each offline branch requires a corresponding connection string in this table to be processed.

Each time the service runs, it determines which branch to copy next by comparing the ProcessDate field in the table, and the last branch processed is the first one to process next. The RecordsToCopy field is used to determine how many transactions will be copied at once.

When the copying process starts, the records being copied are flagged as Busy Copying. When this process completes, it updates with the status Copied.

Two types of data are copied via the Copy Service:

• Transaction data
• End of Day cash up data

The Sync Service is a Windows service that uses web services hosted on the main server to sync updates and changes to SYSPRO Point of Sale, as well as SYSPRO files at the various branches.

The Windows application logs (Event Viewer > Windows Logs > Application).

• SYSPRO Files Sync Started
• SYSPRO Files Synced
• POS Files Sync started
• POS Files Synced

• The SYSPRO Point of Sale Posting service's log tracing detail text file

  If this type of logging is enabled in the Posting service configuration file).

• The Windows application logs (Event Viewer > Windows Logs > Application)

All servers.

A local administrator account that has access to all printers.

This depends on what version of the Printing service is installed on the server:

• If an older version of the Printing service is installed, then you can look in the Temp directory of your C drive for the Printing service text file.
• If a newer version of the Printing service is installed, then you can look in the install directory of the Printing service for the LOG - OPERATIONAL.txt and LOG - ERROR.txt text files.

The replication setup is required to distribute the data down to all the offline branches.

Any changes happening at head office will be replicated down to the branches so that the branches are kept up to date with stock levels and customer balances, etc.

The type of replication chosen is transactional replication so that the updates are replicated down to the branches as soon as they happen, and this ensures that the branch data is as up-to- date as the internet connection allows for.

Deliberately stopping the replication is not recommended when running SYSPRO Point of Sale as this causes the offline branch to not function correctly.

No, the branch server must be switched on at all times, with the exception of temporary power failures.

If there is a connection to head office, the transactions will be copied to head office.

If the branch server fails it will lose minimal data - if any. Unless, there are - for example, 10 POS users at the branch doing 100’s of invoices every day; in which case, a better strategy is required where backups are made at the branch at specific time intervals.

It must be considered what the potential loss of data is versus the cost of implementing and managing backups at all the branches. This means you would potentially store the backups remotely or require an extra branch server at each of the stores which now also has to be managed.

But this is ultimately up to you to decide.

By default, it is set to immediate. This means it will replicate data to the subscribers as it changes, taking connectivity to the branch into consideration.

Any changes happening at Head office/Online will be replicated down to the Branches/Offline as soon as a connection is re-established.

Likewise, the Copy Service is running the whole time and will keep trying to copy data from the branches. So, when it fails, it will retry until there is a connection and copy any transactions and cash ups from the offline server to the online server, so that they can be posted.

Replication is instant once the initial snapshot has been copied to the branch, but in our experience, larger databases can take between 5-10 seconds.

Only customer, inventory, price, tax and other key setup information required. Basically, no transactional data is replicated due to high volumes of data.

In the replication publication articles.

The replication monitor.

The SYSPRO Point of Sale Sync service is set to run in 24-hour intervals by default.

Therefore, restart this service at the branches and monitor the windows application logs for the SYSPRO Files Synced status.

If a SYSPRO customer is setup to use contract pricing in SYSPRO, then the relevant pricing will pull through to SYSPRO Point of Sale when an order is created for the selected customer.

SYSPRO Point of Sale uses the standard price configured in SYSPRO.

In the case of the offline architecture being used, there is a base SYSPRO install done on the branch server that allows SYSPRO Point of Sale to call business objects from the branch server.

In addition to defining what warehouses you allow for a branch, you also need to select which warehouses you allow invoicing from.

This is more for the Manage Orders program because in some scenarios you may want operators to create orders for warehouses that are not necessarily at the same location, but they are not able to invoice out of those warehouses.

Therefore the SYSPRO Point of Sale screen filters the warehouses by what you can invoice out of.

This is because you have multiple warehouses setup against the SYSPRO Point of Sale branch.

SYSPRO Point of Sale only searches for stock in the specified warehouses so when it finds more than one warehouse that an item is stocked in, it prompts you to select which warehouse.

If it only finds one warehouse configured, or if you only have one warehouse defined against your branch, then this prompt is not displayed

If you do have more than one warehouse enabled for your branch, then you can override it at a user level. Therefore if you only give the operator access to sell out of a single warehouse, then the system will not ask for a warehouse selection.

If a credit limit is set for the customer, then this payment type will display when taking payment in SYSPRO Point of Sale.

This only displays as a payment option if the Credit checking setup options against your SYSPRO company are configured (Setup Options > Preferences > Distribution > Sales Orders).

This is also displayed if the SORRSH business object returns a value for CreditAvailable and CreditAvailableInclCreditBalance for the selected customer.

The customer cards and contact functionality is standard and available to you at no additional cost. These are used as a means to identify customers in SYSPRO Point of Sale.

Card summary:

1. A contact is added for a customer.
2. A customer card is then added and assigned to the contact.
3. The customer card is then presented when making purchases and is used to scan the barcode which identifies the customer. All contacts/customers matching the entered card number are returned for selection.

These can also be set up to send a purchase notification SMS to a customer, once a card has been used to make a purchase.

You need to open an account with the internet-based SMS messaging service provider: BulkSMS (http://www.bulksms.com/) and provide your BulkSMS user name and password in the branch setup.

Further setup is may be required at branch and customer level to enable and/or enforce SMS messages for either order notes, purchase approvals or notifications.

The existing access control in SYSPRO Point of Sale has been extended in the Manage Orders program so that you can control an operator's access to the Invoice function, regardless of the order's type or status.

Previously, this function was accessible except when working with deposit or suspended orders. You can now hide or disable the Invoice button by configuring your requirements within the Access Control Setup program (available from the Setup menu).

The search capability in SYSPRO Point of Sale has been extended to barcodes when searching for stock items.

In addition, when you use the Add/Edit Line screen of the Manage Orders program, you can now add stock items using a stock code, serial number or barcode (normal or integrated). Previously, this was only possible using stock codes.

You can also define your preferences as follows:

• Default filter options for the Manage Orders program can now be defined by barcode or serial number within the Search Defaults screens of the Branch Settings program.

• Default filter options for the Search program can now be defined by barcode within the Search Defaults screen of the Manage Users program.

To simplify the debugging process and reduce the persistence of files to the file system, SQL logging within SYSPRO Point of Sale is now recorded within the SQL database.

Previously, each query logged was output to a unique file on disk. From SYSPRO 8 2021 R1, it is now logged to the SQLQueryLogging database table to ensure that all information relevant to debugging is centralized and located at a single point for reference.

To simplify the fault-finding process when SQL Query Logging is enabled, SYSPRO Point of Sale and its SystemConfig.exe file have been altered to limit the logging of SQL queries executed, to functional queries only.

Previously, when SQL logging was enabled, multiple miscellaneous queries were logged which increased the size of the log file and made it difficult to identify queries.

From SYSPRO 8 2021 R1, a standard exclusions list is now included in the SystemConfig.exe file and allows for the exclusion of certain SQL queries by name. A new XML node <SQLQueryLoggingExclusions> has been implemented at parent level and the ChildNodes are named <QueryNameToExclude>.

Although you can add further queries to the list if required, the following SQL queries are now excluded by default:

• BranchSqlConnectionForBranchSelect

• OfflineService

• PoSTransactionListToProcessSelect

• SystemSettingsSelect

• UserSessionsCurrentUserStatusSelect

Each query included in the new exclusions list of the SystemConfig.exe file is not logged when the <OutputSqlQueries> element is set to TRUE.

The assigning of receipt numbers within the Account Payments program has been extended to the Account Payment Reallocations program.

From SYSPRO 8 2021 R1, receipt numbers are assigned (using the same numbering method as account payments) to both the reversal payment and new payment when you process an account payment reallocation in SYSPRO Point of Sale.

In addition, the receipts related to these transactions are now available to view, print or reprint within the Account Payment Query program.

To improve governance around account payment re-allocations, you can now enable supervisor authorization for these transactions by configuring the Allow Account Payment Reallocation option within the Branch Settings program.

The SYSPRO Avanti framework for SYSPRO Point of Sale has been enhanced to cater for providing data directly to SYSPRO Avanti.

This removes the need to first save data to disk - improving the grid layout and data binding speed when running SYSPRO Point of Sale in SYSPRO Avanti.

SYSPRO Point of Sale capabilities have been extended so that customers can now process credits against all kit type items directly in SYSPRO Point of Sale (previously this would have to be performed manually in the core SYSPRO product).

Kit types can now be credited either from the original invoice, or manually in the Credit Note program (available from the Store menu) or Manage Credit Notes program (available from the Store Management menu).

Requirements:

• Default bins must be defined in SYSPRO for parent and component lines for the warehouse.
• The ShowKitComponentLines element in the SystemConfig.xml file must be enabled (i.e. its value must be defined as true).

Limitations:

• This doesn't apply to the Point of Sale, Manage Quotes and Exchanges programs (available from the Store menu).
• Lot, bin and serialized items in kits are not supported. Therefore, this does not apply if the Multiple bins option is enabled.
• Kit type F is not supported, so you cannot enable the Ship from default bin option in SYSPRO Point of Sale.

The print template design process in SYSPRO Point of Sale has been simplified to use SYSPRO Reporting Services to support custom documents. This replaces the previous printing designer (Stimulsoft).

SYSPRO Point of Sale lets you monitor, control and report on all petty cash transactions to improve governance at branch level.

Petty Cash Query

The new Petty Cash Query program (accessible from the Query menu) lets you query, review and reprint petty cash transactions. You can search petty cash transactions by branch, document number, or date range.

Petty Cash Transactions

The existing Petty Cash transaction screen improves traceability for petty cash transactions by including petty cash document numbers for all petty cash transaction types.

Petty Cash Report

The existing Petty Cash Report caters for petty cash document numbers, as well as a reprint capability.

To enable the printing of the new receipt numbers, you need to update the petty cash template with the latest default template or dictionary and add the field onto the existing report.

Branch Settings

New options were added to the Petty Cash tab of the Branch Settings program that let you define transaction limits for petty cash expenditure and receipts, as well as configure whether supervisor authorization is required when limits are exceeded. The options are disabled by default:

• Enforce Petty Cash Expenditure
• Petty Cash Expenditure Limit
• Enforce Petty Cash Receipt Limit
• Petty Cash Receipt Limit

The existing access control within SYSPRO Point of Sale lets administrators more closely control various aspects of supply chain transfer functionality to improve governance at store level.

The following functions within the Manage SCT's program can now be controlled at Branch, Role, User and Device level:

• Add Item
• Edit Item
• Add Other
• Delete Item
• Allocate B/O
• Release B/O
• Invoice SCT
• Cancel SCT
• Update Header

Access Control

The new Access Control program (available from the Setup menu) serves as the interface for all newly added or existing access control items that have been enhanced. It lets administrators define the following types of visibility and/or functionality where relevant:

• Visibility

  These options let administrators define what functions (i.e. controls) are visible to operators, by selecting one of the following permission levels:

  • Collapsed: The function is hidden from the operator.
  • Visible: The function is visible to the operator.
  • Inherit: The system must check higher up in the access control hierarchy to determine the function’s visibility.

  All current controls default to Visible, but any new controls added in future will default to Collapsed.

• Functionality

  These options let administrators define the functionality available to operators, by selecting one of the following permission types:

  • Deny: The function is disabled.
  • Allow: The function is enabled and requires no supervisor authorization to proceed.
  • Allow (Auth req): The function is enabled but requires supervisor authorization to proceed.
  • Inherit: The system must check higher up in the access control hierarchy to determine the function's accessibility.

  All current controls default to Allow, but any new controls added in future will default to Deny.

The following programs in SYSPRO Point of Sale have been enhanced to assist operators to quickly identify stock availability and bin locations when adding a sales order or quote:

• Manage Orders (available from the Store Management menu)
• Point of Sale (available from the Store menu)
• Manage Quotes (available from the Store menu)
• Exchanges (available from the Store menu)

Administrators can now define an operator's visibility access (within the Access Control program) for the following display fields when adding sales orders or quotes:

• Quantity on hand
• Default bin

This increased visibility provides operators with vital information when they need it.

Improved transaction tracking and governance has been included in SYSPRO Point of Sale by providing an audit trail of all data changes relating to transaction processing and printing. You can now monitor, control, and report on key functions (e.g. granting of discounts).

You can configure which audit trails you require in the new Audit Trail Setup tab of the System Settings program. The new audit trail reports (available from the new Audit Trails menu tab in SYSPRO Point of Sale) include:

Supervisor authorizations

Two new programs (Header Authorization Audit Trail and Detail Authorization Audit Trail) detail all occurrences where a supervisor authorization has been applied to a sales order or quote header change (e.g. tax override, credit notes, price margin, etc.).

Detail line deletions

A new Line Delete Audit Trail program details all occurrences where a line has been deleted from a quote or sales order.

Special Discounts

A new Price And Discount Audit Trail program details any change made to a price or discount on sales order or quote lines in the Point of Sale or Manage Quotes programs (available from the Store menu).

The report also indicates whether a supervisor authorization was applied, including the details that were applied.

Document Printing

A new Print Audit Trail program provides an audit trail of any printing or reprinting of sales invoices and quotes performed in SYSPRO Point of Sale.

Changes to Ship methods

A new Ship Method Audit Trail report provides an audit trail of any changes made to the ship method on quotes and sales orders in the Point of Sale or Manage Quotes programs (available from the Store menu).

The report also indicates whether a supervisor authorization was applied, including the details that were applied.

Tax Code Changes

A new Tax Code Audit Trail report details any changes made to tax codes on quotes and sales orders in the Point of Sale or Manage Quotes programs (available from the Store menu).

Considerations:

• The EnableAuditTrailLogging element in the SystemConfig.xml file can be enabled or disabled per site.

• The new audit trail database (SysproComp_POS_AuditTrails) contains the following new tables:

  • _SystemAuditTrailPrinting

    This stores an audit trail of any prints performed.

  • _SystemAuditTrail

    This stores audit trail-specific information.

Limitations:

• Supply Chain Transfers are not included in the audit trail reports as SYSPRO Point of Sale posts SCT-related information directly to SYSPRO in real time. However, you can access SCT information directly from the SorAdditions, SorChanges and SorCancelled tables.
• Transactional data is not replicated in the SYSPRO company database to offline branches.

The SYSPRO Point of Sale software suite is now completely available on the SYSPRO Avanti platform.

Benefits:

• Cloud-related functionality (e.g. web interface).
• Screen customization and full use of SYSPRO custom form fields.
• The availability of Point of Sale on Cloud type devices (e.g. tablets).

The SYSPRO Point of Sale architecture has been enhanced to enable you to create your own custom dashboards, based on your specific business needs.

These dashboards make use of SYSPRO's Business Insights technology and can provide key information regarding the sales and performance of a Point of Sale branch.

To create a dashboard, simply use the Visual Designer when designing your home screen in SYSPRO Avanti. SYSPRO provides 2 samples which you can use to get you started.

An example of what can be done using this new functionality, would be a sales dashboard:

Statistics regarding the intensity of a Point of Sale branch’s performance can be highlighted, down to hourly trading, enabling you to actively monitor and manage your sales.

Trends that can be highlighted include the following:

• Sales Value

  This indicates the net value of sales, after all discounts, and excluding any sales tax.

• Footfall

  This indicates the number of transactions (i.e. sales invoices generated).

  SCT's and other non-revenue related inventory movements are excluded.

• Average Purchase Value

  This indicates the average value of sales to customers.

  This is determined by dividing the Sales Value by the Footfall for a specified time period.

You can now define negative stock capacity at warehouse level for SYSPRO Point of Sale transactions.

Allowing negative stock for a specified warehouse utilized by a branch solves the problem of having a customer at the till with goods in hand, but the till operator not being able to process the sale due to the system showing no stock on hand.

This configuration is available on the Warehouse 2 tab of the Branch Settings program within SYSPRO Point of Sale. From here you can also indicate if a warning must be displayed when a transaction will cause a negative stock situation.

SYSPRO Point of Sale now supports the same level of password control as SYSPRO and provides the following capabilities:

• Automatically expire user passwords after a defined period of time.
• Enforce rules regarding the construction of a password to ensure greater security.

Therefore, when a user changes their password in SYSPRO Point of Sale for any reason, it will be validated against these setup options to ensure the password meets the minimum requirements.

This configuration is available on the Password Settings tab of the System Settings program in SYSPRO Point of Sale.

The management and governance of deposits at branch level has been improved with new trial balance and audit trail capabilities.

The Deposits Trial Balance produces a deposit payment trial balance of all unapplied deposit liabilities recorded in SYSPRO Point of Sale for improved governance:

• All deposit values are listed by customer.

• Information is derived from the ArInvoicePay table, and is subtotaled by customer.

• The report is branch specific.

• Zero value balances are excluded by default, with an option for inclusion.

• The report defaults to the current system date, with an option to change the date to an earlier date. If you select an earlier date then the report excludes all entries subsequent to the selected date.

The Deposits Audit Trail provides an audit trail of deposits taken for sales orders in SYSPRO Point of Sale:

• New deposits, deposit applications against sales and deposit refunds are identified separately.

• All deposit transactions processed in SYSPRO Point of Sale are included, as recorded in the ArInvoicePay table.

• The report is branch specific and provides for financial period and date range selections.

These new programs are both available from the Query program in SYSPRO Point of Sale.

SYSPRO Point of Sale governance regarding the management and control of account payments has been enhanced.

The system now retains a list of receipt numbers and allocates a unique document number for all account payments received and processed at a Point of Sale store.

This occurs for both online and offline processing to prevent duplicate receipt numbers when the system is back online.

In addition, the new Account Payments program (available from the Query menu) provides Point of Sale administrators a view of all account payment processing for their store. By default, access to this program is only assigned to the Admin role.

Things you can do in this program include:

• View an audit trail report of all account payments.
• Query account payments by your preferred selection criteria.
• Reprint an account payment.

This significantly improves the management of and governance over account payment transactions processed through SYSPRO Point of Sale.

SYSPRO Point of Sale administrators can now control various aspects of supply chain transfer functionality at a more granular level, improving the governance and security over SCTs.

The new Access Control program (available from the Setup menu) includes the following capabilities at branch, role, user or device level:

• Visibility

  This pane enables you to define whether or not the option is available to the operator.

• Functionality

  This pane enables you to define an operator's access to various functions as follows:

  • Denied
  • Allowed without supervisor authorization
  • Allowed with supervisor authorization
  • Inherit access control according to hierarchy

You can therefore use this program to define the following abilities of a user for SCT transactions:

• Add item
• Edit item
• Add other
• Delete item
• Allocate back order
• Release back order
• Invoice SCT
• Cancel SCT
• Update header

Governance regarding the delivery of goods to customers has been improved, with new security in terms of a user's ability to change shipping methods in the Manage Orders and Manage Quotes programs of SYSPRO Point of Sale.

The new Access Control program (available from the Setup menu) enables you to define an operator's access to various functions (at branch, role, user or device level) as follows:

• Denied
• Allowed without supervisor authorization
• Allowed with supervisor authorization
• Inherit access control according to hierarchy

You can therefore use this program to define a users access rights for changing shipping methods on new or existing orders in SYSPRO Point of Sale.

The SYSPRO Point of Sale software suite is being converted to the SYSPRO Avanti platform.

Benefits:

• Cloud-related functionality (e.g. web interface).
• Screen customization and full use of SYSPRO custom form fields.
• The availability of Point of Sale on Cloud type devices (e.g. tablets).

A new dashboard provides key information regarding the sales and performance of a Point of Sale branch.

Benefits:

• Key statistics regarding the intensity of a Point of Sale branch's performance are highlighted.
• Point of Sale branches can set their own targets (over-and-above corporate budgets) to monitor their performance.
• Trends are highlighted for sales values, footfall and average purchase values.

SYSPRO Point of Sale now caters for kit type K in the Manage Orders program, demonstrating the products' awareness of grouped components that are typically purchased together.

Generally used for special offers, you can now process kits where the kit grouping or parent part is notational only and the components of the kit are separately detailed (pricing is at parent level).

The ability to remove optional items from a kit is also provided.

SYSPRO Point of Sale now caters for the partial crediting of a kit and you can process a credit for an item that was sold as part of a special offer, via a kit.

• Sales Orders now allow for tax codes to be applied by line item.
• The Quotes search now includes the originating operator.
• The Customer Query now displays Contacts as recorded in Contact Management.
• The Take Payments program now allows operators to review payments before finalizing a transaction.
• A security option has been added to request operator validation before taking payment.
• The Inventory Query program now displays defined custom form fields against stock items.

Invoice numbers and Quotation numbers can now be recorded separately as Point of Sale transactions.

Benefits:

• Supports governance requirements for Sales Tax Reporting
• Ensures sequential POS invoice numbering